From nobody Tue Oct 2 13:21:23 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAEAF130FF0 for ; Tue, 2 Oct 2018 13:21:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QytJMeeXBaLe for ; Tue, 2 Oct 2018 13:21:17 -0700 (PDT) Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A373613112E for ; Tue, 2 Oct 2018 13:21:17 -0700 (PDT) Received: by mail-oi1-x232.google.com with SMTP id a203-v6so2662563oib.0 for ; Tue, 02 Oct 2018 13:21:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=G0/R3tRfFU6hwzi0G6pEFXKm5uzQ0peSUYCZZIT8C2E=; b=JU8bmneu3ri6/PQyNr8gvcIKlebhMRdZkagFqvSuop8nXtazXOYlXQkCdg3q83Oage KLj70Hj+Cv6KbgG9gDKDFjBbvtmM0/hV6fsqXTv8Zt9Z72qw/gog5QMZvD8xS30OkJPo QDGSU3klPFLWD6VUgsnlgIqIEOPSVHeqpJheo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=G0/R3tRfFU6hwzi0G6pEFXKm5uzQ0peSUYCZZIT8C2E=; b=jN0yHhcceRH2WpeEezqqkEuMIrGbtK2qvXZyo1qXGf5xMe15xfdwRjiLqfseZZEU1Y XB/oKoXzG1LO/xZqwlVsV3zw/StZ9lfkekF9UKhkAnud9SLi90sVn46Y9ssYDVfkt2xu SgrnriHxFyyF5NqUajydLXucfX+wvaQYUeBCDN8psduR4zpiD/vaA2uQWjsaE2G9WKg3 WavecYPcwy0DPWxGSbBgFnqdLltZ89mzFZ7Fdp3xIHQewZAEY6AJmzyxiHgs1Q4wPSqS GWzYNB5/kAPQg9VA/5rzuj8CJIqDc1floE80i81mHznm8FeF7lzv1pNN7tUN4q3o6OX/ XqQA== X-Gm-Message-State: ABuFfoioBwwKwIJzmtdwWts9ZNEECddIduvuK/tD3pbEStAH7/dN1W8E 4rjSZCXMmvoPsHTCrC7eX463zbedAG5KmqzqcL/B9g== X-Google-Smtp-Source: ACcGV63n3z4yvTxrauSe2F0reO49kcRz7h/kcf5C7u7hIxzIF9TsJ+fNwVi48ZeY58N8rpWEjARt9vdwzikyLjTEH6s= X-Received: by 2002:aca:c701:: with SMTP id x1-v6mr8918566oif.66.1538511676745; Tue, 02 Oct 2018 13:21:16 -0700 (PDT) MIME-Version: 1.0 From: Adrian Hope-Bailie Date: Tue, 2 Oct 2018 22:21:05 +0200 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF , Hyperledger Quilt Mailing List Content-Type: multipart/mixed; boundary="000000000000fa1b27057744a980" Archived-At: Subject: [Ledger] AGENDA - Interledger Call - 3 October - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 20:21:22 -0000 --000000000000fa1b27057744a980 Content-Type: multipart/alternative; boundary="000000000000fa1b24057744a97e" --000000000000fa1b24057744a97e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, No fixed agenda this week but I hope we can get an update from the Strata Labs and Kava teams on their latest developments. As always, if you have something to raise please bring it to the call or send to the list (reply to this mail) to add to the agenda. I'll unfortunately be on a plane so thanks to Evan for running things. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/s/377506344 Or iPhone one-tap: US: +14086380968,,377506344# or +16468769923,,377506344# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 408 638 0968 <+1%20408%20638%200968> or +1 646 876 9923 <+1%20646%20876%209923> or +1 669 900 6833 <+1%20669%20900%206833> Meeting ID: 377 506 344 International numbers available: https://zoom.us/u/cbrUAzE3W --000000000000fa1b24057744a97e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
No fixed agenda this week but I hope we can get an= update from the Strata Labs and Kava teams on their latest developments.
=
As always, if you have something t= o raise please bring it to the call or send to the list (reply to this mail= ) to add to the agenda.

I'll unfortunately be on a plane so thanks = to Evan for running things.

Join from = PC, Mac, Linux, iOS or Android:=C2=A0h= ttps://zoom.us/s/377506344

Or iPhone one-tap:
=C2=A0=C2=A0=C2=A0=C2=A0US: +14086380968,,37= 7506344# or +16468769923,,377506344#

Or Telephone:
=
<= font style=3D"font-family:sans-serif">=C2=A0=C2=A0=C2=A0=C2=A0Dial(for high= er quality, dial a number based on your current location):=C2=A0
=C2=A0=C2=A0=C2=A0=C2= =A0US:=C2=A0+1 408 638 0968=C2=A0or=C2=A0<= font style=3D"font-family:sans-serif">+1 646 876 9923=C2=A0or=C2=A0+1 669 900 6833<= /a>=C2=A0
--000000000000fa1b24057744a97e-- --000000000000fa1b27057744a980 Content-Type: text/calendar; charset="US-ASCII"; name="ilp-2018-10-03.ics" Content-Disposition: attachment; filename="ilp-2018-10-03.ics" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_jms61vi40 QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpCRUdJTjpW RVZFTlQNCkRUU1RBTVA6MjAxODEwMDNUMDAwNDU0Wg0KVUlEOjIwMTgxMDAzQGludGVybGVkZ2Vy Lm9yZw0KRFRTVEFSVDoyMDE4MTAwM1QxNTAwMDBaDQpEVEVORDoyMDE4MTAwM1QxNjAwMDBaDQpT VU1NQVJZOkludGVybGVkZ2VyIENvbW11bml0eSBDYWxsDQpVUkw6aHR0cHMlM0ElMkYlMkZ6b29t LnVzJTJGcyUyRjM3NzUwNjM0NA0KREVTQ1JJUFRJT046Sm9pbiBmcm9tIFBDXCwgTWFjXCwgTGlu dXhcLCBpT1Mgb3IgQW5kcm9pZDogaHR0cHM6Ly96b29tLnVzL3MvMzc3NTA2MzQ0XG5cbk9yIGlQ aG9uZSBvbmUtdGFwOlxuICAgIFVTOiArMTQwODYzODA5NjhcLFwsMzc3NTA2MzQ0IyBvciArMTY0 Njg3Njk5MjNcLFwsMzc3NTA2MzQ0I1xuXG5PciBUZWxlcGhvbmU6XG4gICAgRGlhbChmb3IgaGln aGVyIHF1YWxpdHlcLCBkaWFsIGEgbnVtYmVyIGJhc2VkIG9uIHlvdXIgY3VycmVudCBsb2NhdGlv bik6IFxuICAgIFVTOiArMSA0MDggNjM4IDA5Njggb3IgKzEgNjQ2IDg3NiA5OTIzIG9yICsxIDY2 OSA5MDAgNjgzMyBcbiAgICBNZWV0aW5nIElEOiAzNzcgNTA2IDM0NFxuICAgIEludGVybmF0aW9u YWwgbnVtYmVycyBhdmFpbGFibGU6IGh0dHBzOi8vem9vbS51cy91L2NiclVBekUzV1xuDQpFTkQ6 VkVWRU5UDQpFTkQ6VkNBTEVOREFS --000000000000fa1b27057744a980-- From nobody Wed Oct 3 05:32:11 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95E0A131270 for ; Wed, 3 Oct 2018 05:32:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ripple.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMAlU4l9YlJ9 for ; Wed, 3 Oct 2018 05:32:06 -0700 (PDT) Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 510AC130FBD for ; Wed, 3 Oct 2018 05:32:06 -0700 (PDT) Received: by mail-qt1-x835.google.com with SMTP id q40-v6so5658819qte.0 for ; Wed, 03 Oct 2018 05:32:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripple.com; s=google; h=date:from:to:message-id:subject:mime-version; bh=fpJlYXuwDqxdGhQHo1ZhaHwMWAkhIjvS1s0pIc36f3c=; b=l3Y8MMJ3EuDwxTfrzjQNu6tvO70L5NBb9366nyiGVzCe9q9Pga6Y1GdJ5q/QJcFw/x ZwQqV/K1EmgfoIucj3Nc6stVJFPsR/CFdBsfYdlRxs3T+CWEM++RjEUPW9EFqvz+GMyT oITcRT0k9PyQCaHCfG8/a+lMgXPOL08KJHvNY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:subject:mime-version; bh=fpJlYXuwDqxdGhQHo1ZhaHwMWAkhIjvS1s0pIc36f3c=; b=fA8gwBnm/bQD0MTIZQYUiVvFGtBh/VpkwGKz/LGUXgKuVjFCoMNxQB10rIfbdiJWYN ioMFpT8s2jHLEo/isGIqx4w6NHyoA4eVBTr/7+Qh5NCRYiND+6xxyV5pHRy9f9myM1Bz x4FpDyoMFKK2F5plxPlFv5A/qXQKzNKBuqrvVIw4Swd8m/wgfjt6KlRfxLW6mIp9lrhF osiMcmrzdzD8V6GFP37oBtswBeyf6xp2zTWiFWN67KBHiNkJGA9KTMY4qyy4quqspuNB 77jFlbc6W3UwrYwcP9XMbBJj6WCJQpAsknCiT/3yR1eOunM5Hl9W431fsvsXtmmQxJZI TNQg== X-Gm-Message-State: ABuFfoilNLntiixqSNTtwAhmwq4/nfmG6JX2OO54cX2U2SIo6FHPHaFF GnEarm41ox70grqNc6USVn4xX61Yvio= X-Google-Smtp-Source: ACcGV627MscQUs4rJUHgU+jI/y6jjCUdV0yo85KovwP8aQ1Q9fp5Cf55aNewTOSfyCsefs4ziEbqFw== X-Received: by 2002:ac8:1628:: with SMTP id p37-v6mr951073qtj.113.1538569925338; Wed, 03 Oct 2018 05:32:05 -0700 (PDT) Received: from arch (inet-64-112-177-6.bos.netblazr.com. [64.112.177.6]) by smtp.gmail.com with ESMTPSA id x34-v6sm566991qth.86.2018.10.03.05.32.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Oct 2018 05:32:04 -0700 (PDT) Date: Wed, 3 Oct 2018 08:32:01 -0400 From: Evan Schwartz To: Interledger Community Group , Interledger Mailing List - IETF Message-ID: <1538569618.local-b7e7b227-2e05-v1.4.2-f587b7b7@getmailspring.com> X-Mailer: Mailspring MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5bb4b6c1_6a77c807_2bbc" Archived-At: Subject: [Ledger] Blog post explaining "What is Interledger?" X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 12:32:09 -0000 --5bb4b6c1_6a77c807_2bbc Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline A number of people commented that we need more documents that give a simple overview of what Interledger is. Vanessa Pestritto and I put together this post to explain a bit about the network and some of the key features of the protocol: Interledger (https://medium.com/xpring/interledger-how-to-interconnect-all-blockchains-and-value-networks-74f432e64543): (https://medium.com/xpring/interledger-how-to-interconnect-all-blockchains-and-value-networks-74f432e64543) How to Interconnect All Blockchains and Value Networks (https://medium.com/xpring/interledger-how-to-interconnect-all-blockchains-and-value-networks-74f432e64543) If you could help share it around, it would be much appreciated! Comments and questions are welcome, as always. This should also be one of many posts detailing various parts of the Interledger vision/tech/impact (so you should also feel free to write up your perspective on it)! Evan --5bb4b6c1_6a77c807_2bbc Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
A number of people commented that we need more documents that give a= simple overview of what Interledger is. Vanessa Pestritto and I put toge= ther this post to explain a bit about the network and some of the key fea= tures of the protocol:
<= br>
If y= ou could help share it around, it would be much appreciated=21

<= div>Comments and questions are welcome, as always. This should also be on= e of many posts detailing various parts of the Interledger vision/tech/im= pact (so you should also feel free to write up your perspective on it)=21=
Evan
--5bb4b6c1_6a77c807_2bbc-- From davidnicol@gmail.com Wed Oct 10 11:24:58 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA5412785F for ; Wed, 10 Oct 2018 11:24:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fsac44kwSIhu for ; Wed, 10 Oct 2018 11:24:56 -0700 (PDT) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC3B91252B7 for ; Wed, 10 Oct 2018 11:24:55 -0700 (PDT) Received: by mail-qt1-x836.google.com with SMTP id v19-v6so6837245qtg.2 for ; Wed, 10 Oct 2018 11:24:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/mELqw28stgqPfhrtx/ib7c75vWUnjHcj1Qh4pb+Gn8=; b=rLUsXdoL8EhFdeBehOlNwhHeh0tNlM5YX7I2SSWksUc+w2R1cI9k7/ghGf151G2nCW kEpXxJ9KuhJBvU6XPvLYGVKPwneJxAVflNH8FIww9Hvf42c2bpnf+g7BYKSpOStBfPrC oKyl4QQxN9mUj/6YPnbPad6lIokMMHjcUfvaQ1aQP9vNSN84vDHr0hRzhq+5cfft5zeT sIE0a5VI3tuGrHIFZ2ACyF4eYmAyA79uZdntSAAss/5qijGIIBqGRAg6Xr+CO+8OS3MY zvnThoKN8fJxPGaZYMja5u7vJQmFOQ0FQSTWFJJG/nJfOPYWqFnJ6L+MSnCNkl8wuJ6Z hiSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/mELqw28stgqPfhrtx/ib7c75vWUnjHcj1Qh4pb+Gn8=; b=S/7z7nQm/ikCDUtk74V7Oz8AZ27E9YvU4z5w0+Z38oCfO2e43qHYyMfUbBRqApmrOs Ey6hinaVNHfw5yuveHac92eW871m/+G95xoMPsp1HrxjiFLHo4PgkXI57vWxZITf2JQb Nkvj6weNsWh+kFLRyZuYA4CNFotIEOgi57ulKqjSpnVR0duNjzmz9jlgzfPIgPQXeaUI tP3i1pb2txEJKthkQvMzDymS9WDGQGOB+P5EwF/D9xzU67GKdnCiRCx6PvjLanQbX6Bc ZzWRyNPXn6+uiFD2X6Slzx8hhBvNa7SGERnf/ZMSxX84noJIfzn2xoFmABP0gqi8ThrO haOg== X-Gm-Message-State: ABuFfoj+yvk94i5YdFx06NutxCc2fAzyiXB7XifcNLNY/KSOQjIVolKK TEhXLyvyvNxX1Vc7VU8p8rMaUiJlzLOh/CcuUhDOQW0P X-Google-Smtp-Source: ACcGV60DRGh5nhqipjbCrl+xohGED6zEP266E0iehooA+0BNV+0ZFcRwG11nOBPTtwZLiq6njfkkRJQA7skfRdOhAwQ= X-Received: by 2002:ac8:2837:: with SMTP id 52-v6mr21437901qtq.243.1539195894865; Wed, 10 Oct 2018 11:24:54 -0700 (PDT) MIME-Version: 1.0 References: <1538569618.local-b7e7b227-2e05-v1.4.2-f587b7b7@getmailspring.com> In-Reply-To: <1538569618.local-b7e7b227-2e05-v1.4.2-f587b7b7@getmailspring.com> From: David Nicol Date: Wed, 10 Oct 2018 13:24:19 -0500 Message-ID: To: Evan Schwartz Cc: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="0000000000008da4730577e3f817" Archived-At: Subject: Re: [Ledger] Blog post explaining "What is Interledger?" X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 18:28:26 -0000 --0000000000008da4730577e3f817 Content-Type: text/plain; charset="UTF-8" Good introduction! I'm writing to propose a copy-edit. Only the receiver could generate the correct proof, which is a simple preimage of a hash. "simple preimage of a hash" is jargon and in this introductory document may easily get misconstrued as obfuscatory mumbo-jumbo. I recommend either dropping the clause or replacing it with a full-on, repeatable, hand-wave indirection such as Only the receiver can generate the correct proof, using established cryptographic principles. On Wed, Oct 3, 2018 at 7:34 AM Evan Schwartz wrote: > A number of people commented that we need more documents that give a > simple overview of what Interledger is. Vanessa Pestritto and I put > together this post to explain a bit about the network and some of the key > features of the protocol: > > Interledger > > : > > How to Interconnect All Blockchains and Value Networks > > > If you could help share it around, it would be much appreciated! > > Comments and questions are welcome, as always. This should also be one of > many posts detailing various parts of the Interledger vision/tech/impact > (so you should also feel free to write up your perspective on it)! > > Evan > -- "I don't know about that, as it is outside of my area of expertise." -- competent specialized practitioners, all the time --0000000000008da4730577e3f817 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=
Good introduction! I'm writing to propose a copy-edit.

=

Only the receiver could generate the = correct proof, which is a simple preimage of a hash.

<= /div>
"simple preimage o= f a hash" is jargon and in this introductory document may easily get m= isconstrued as obfuscatory mumbo-jumbo.

I recommend either dropping the clause or replacing it wit= h a full-on, repeatable, hand-wave indirection such as
<= div>
Only the receiver can generate the correct proof, using established = cryptographic principles.=C2=A0=C2=A0


On Wed, Oct 3, 2018 at 7:34 AM Evan Schw= artz <evan@ripple.com> wrote:<= br>
A number of peopl= e commented that we need more documents that give a simple overview of what= Interledger is. Vanessa Pestritto and I put together this post to explain = a bit about the network and some of the key features of the protocol:=


If you could help share it around, it = would be much appreciated!

Comments= and questions are welcome, as always. This should also be one of many post= s detailing various parts of the Interledger vision/tech/impact (so you sho= uld also feel free to write up your perspective on it)!
= <= br>
Evan

=
--
"I don't know about that, as it is outside of my = area of expertise." -- competent specialized practitioners, all the ti= me
--0000000000008da4730577e3f817-- From nobody Wed Oct 10 11:47:49 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 085BA126F72 for ; Wed, 10 Oct 2018 11:47:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uthsEAOFi6UD for ; Wed, 10 Oct 2018 11:47:46 -0700 (PDT) Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3A68126BED for ; Wed, 10 Oct 2018 11:47:45 -0700 (PDT) Received: by mail-qt1-x82e.google.com with SMTP id d14-v6so6913780qto.4 for ; Wed, 10 Oct 2018 11:47:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SdOsiMdLcg2S7odYTTI/+gaWO+LoKbxsKgAiYet5T8I=; b=ZSKIza4zD3lY0W9UgeA/DX1PQ9Tg8o/Ca9QuatPFSHZUjxt6cN1+171F2wAsb+OuUV bNb4s6xnXBZ4Nj03rrYiGR4hOo2DLPzxAdXr7NSfcMrplpxiE5ZLUJHySgrIeCeiBxEY ae+QVwHTdv7uoOPb2K6Qsj8AdFLOicaCZeQfRl5CbH5L3aR76dQwfl5hGnF5u+rCFlit 0JnyDmk+0JD1VH8zSAqN3va5+dBxFe5eZxhwsNE7yJQgXjPBLCT3op9nAdo9mgZU0U/V oqoS/s13qYaB6pWzkfr4MvH+H3tHyTEKExRH09N0e4XXWPe+fNQdR55wvSVe3o2/cQds tNGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SdOsiMdLcg2S7odYTTI/+gaWO+LoKbxsKgAiYet5T8I=; b=NG270CN1xbmLJKjaZEhe7+0NRqROaYIGNDcYAizBZOolJ0BreMP5Zq+/UyekwnW3P+ 5sWVt+kdSvG5+68W5HpTGrODSj1oegaDCbmY4fbSO3mO3raQyZA//z131S7pWU/DONbz WaGc+sp+1tJfuf3l59R0kCnTsO6Jz7JukMpWy6nD8HahDhhxinnaoomXObQ3kXdV5Pat nZ0WYg4+XulbEG4TiOyqrQWLfFfNGMfBjyOkpWzUC/p6TEX10+NsiW1YAREEf9CZXrLv 1fUiH4liAurS/aUlJWdWg10LQIqJxrxVZiXJYjMO+i6jHoCv/2Hw0ZEfkZzsMPvUhdN2 VYhg== X-Gm-Message-State: ABuFfoiYpdnjYecyGBGKZDHxowTHSGfJ855gTYaJ8mt+pjPIoh6VPP7q fKAVaYt+rOhek1vovAlj2ardpnI2HVT49n+2szM= X-Google-Smtp-Source: ACcGV63qNsF4Von6ss1v2+5BRDWE5WTsayzAqDTDs4wteWe8iuYp6qNMxd3qm56fB7WUiPfhkvUq7rRmGyd0emEnltQ= X-Received: by 2002:aed:24c3:: with SMTP id u3-v6mr24536044qtc.230.1539197265160; Wed, 10 Oct 2018 11:47:45 -0700 (PDT) MIME-Version: 1.0 References: <1538569618.local-b7e7b227-2e05-v1.4.2-f587b7b7@getmailspring.com> In-Reply-To: From: David Nicol Date: Wed, 10 Oct 2018 13:47:09 -0500 Message-ID: To: Evan Schwartz Cc: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="0000000000003aae5b0577e44a62" Archived-At: Subject: Re: [Ledger] Blog post explaining "What is Interledger?" X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 18:47:48 -0000 --0000000000003aae5b0577e44a62 Content-Type: text/plain; charset="UTF-8" After reviewing the current protocol a spot, executionCondition UInt256 SHA-256 hash digest of the fulfillment that will execute the transfer of value represented by this packet. Connectors MUST NOT modify this field. The receiver must be able to fulfill this condition to receive the money. maybe "Only the receiver can demonstrate knowledge of the secret, previously shared with the sender, that allows all stages of the transaction to complete." I didn't notice while reading the article that it says anywhere that the receiver has to somehow share a per-transaction secret with the sender, before the sender invokes ILP. --0000000000003aae5b0577e44a62 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
After reviewing the current protocol a spot,

executionCondition<= /td>UInt256SHA-256 hash digest of the=C2= =A0fulfillment=C2=A0that will execute the transfer of val= ue represented by this packet. Connectors MUST NOT modify this field. The r= eceiver must be able to fulfill this condition to receive the money.

maybe &qu= ot;Only the receiver can demonstrate knowledge of the secret, previously sh= ared with the sender, that allows all stages of the transaction to complete= ."
=C2=A0
I didn't notice while reading the ar= ticle that it says anywhere that the receiver has to somehow share a per-tr= ansaction secret with the sender, before the sender invokes ILP.
=


--0000000000003aae5b0577e44a62-- From nobody Wed Oct 10 18:23:58 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C40130DF2 for ; Wed, 10 Oct 2018 18:23:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nhjftuetluiy for ; Wed, 10 Oct 2018 18:23:54 -0700 (PDT) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A2FF130DDC for ; Wed, 10 Oct 2018 18:23:54 -0700 (PDT) Received: by mail-qt1-x830.google.com with SMTP id e10-v6so8041959qtq.12 for ; Wed, 10 Oct 2018 18:23:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AI6sid89pvt2kH4tiSZS97osPnEAy+OkX/5mIvp4mUc=; b=g6DGkcwJJBBIdTfGSLw0/iPgrKe258KVI5Rkw01AcNk5UyZMaL0CKl2CFBLTf1Cgpd l9PzvZnEJKe7Zu2okjV8kjnvypHqSVCWghH3s76dGD7Zubezs875n5bA60nU5Y/FSRP2 hcIPWHbdcUGgSq/SyRLT6ZHxU6mGi9w9npMofTeTSCxSJRNy4fl0pZ+LB8nGBAVfBy/y WV8Mm4VDEFYvArkCdbEd+WqMQ08Q7MegkjP4lCj71bj1VAxPZLIHFgD0/kmlzbCXWUT8 IWc/SJXEv/yT3redXfAQ6eKASFdEHGvBfukcjw69KVzv+YhXLk28qkYcW7Pycrz5GCb1 OmIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AI6sid89pvt2kH4tiSZS97osPnEAy+OkX/5mIvp4mUc=; b=QR69LXAxKz1KcSwMVPpaoSLaDxxlkGzLa62Pkf5bkuPXKiPTbV1O1H+yCVV+lHJyaA 9Qk6X6S4TUOb+HvvtR8G1C4Bs7owWXaPQNtsY3zx9pElpjN8GUhWFjoj4QCh7w9iGU7m XhUIwWGW1J20fBr/TPeslZbv79amgzO/2gkVcND5s4Lb4BR9MoGxCvZ/XhgC3JJK9UfO +ttiTWMc525eImbew4npa8mxV5MCFNEgZxhtv8YomWFuuBldWsoDqRivCqTpeQV+jICO pd+YbzKpRhmCkkyg6ss1os0OXOBJj7rvk7KtC706wnTzDeGpz6AtCRvMQyNxMP744g5K H5fw== X-Gm-Message-State: ABuFfohImQgOUoevsZkvGMrQ8C9vefkhhrkVT50A39QOhQ2sM+/fx+QZ 8jIo1W7MnWKaQ0VgR/udLj6e84ACT39ZLD/D01k= X-Google-Smtp-Source: ACcGV61mUQVvrwLwNhBfJOWp6Fenw0DTjR2z0RgsWYo3Eo/sSsmYXPItqj5fPTTZThWEYYFMO733wyb/LY8kqZAWvBk= X-Received: by 2002:a0c:fe11:: with SMTP id x17mr4819052qvr.150.1539221033147; Wed, 10 Oct 2018 18:23:53 -0700 (PDT) MIME-Version: 1.0 References: <1538569618.local-b7e7b227-2e05-v1.4.2-f587b7b7@getmailspring.com> In-Reply-To: From: David Nicol Date: Wed, 10 Oct 2018 20:17:09 -0500 Message-ID: To: fiatjaf@alhur.es Cc: Evan Schwartz , Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="000000000000e96abd0577e9d2a2" Archived-At: Subject: Re: [Ledger] Blog post explaining "What is Interledger?" X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 01:23:57 -0000 --000000000000e96abd0577e9d2a2 Content-Type: text/plain; charset="UTF-8" that it works with shared secrets instead of asymmetric crypto was news to me. On Wed, Oct 10, 2018 at 2:13 PM Giovanni P wrote: > I think everybody knows what a hash is, but "preimage" is a little > more advanced/obscure. > > "established cryptographic principles" is much more mumbo-jumbo than > saying "hash". > > If the idea is to gather interest among developers and insiders it > makes more sense to say more about how it works than to just drop > magical words. > > Actually, I think even normal people are sick of hearing magical > words: "oh, this works and does amazing stuff because cryptography!", > there are thousands of claims like that everywhere and most are false, > so actually saying Interledger is simple, it's not magic, you can > understand it, it just happens to be clever with simple principles -- > that can have a lot of appeal. > > On 10/10/18, David Nicol wrote: > > After reviewing the current protocol a spot, > > > > executionCondition UInt256 SHA-256 hash digest of the fulfillment that > will > > execute the transfer of value represented by this packet. Connectors MUST > > NOT modify this field. The receiver must be able to fulfill this > condition > > to receive the money. > > > > maybe "Only the receiver can demonstrate knowledge of the secret, > > previously shared with the sender, that allows all stages of the > > transaction to complete." > > > > I didn't notice while reading the article that it says anywhere that the > > receiver has to somehow share a per-transaction secret with the sender, > > before the sender invokes ILP. > > > -- "I don't know about that, as it is outside of my area of expertise." -- competent specialized practitioners, all the time --000000000000e96abd0577e9d2a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

that it works with shared secrets instead of asym= metric crypto was news to me.

On Wed, Oct 10, 2018 at 2:13 PM Giovanni P <fiatjaf@alhur.es> wrote:
I think everybody knows what a hash is, but "preima= ge" is a little
more advanced/obscure.

"established cryptographic principles" is much more mumbo-jumbo t= han
saying "hash".

If the idea is to gather interest among developers and insiders it
makes more sense to say more about how it works than to just drop
magical words.

Actually, I think even normal people are sick of hearing magical
words: "oh, this works and does amazing stuff because cryptography!&qu= ot;,
there are thousands of claims like that everywhere and most are false,
so actually saying Interledger is simple, it's not magic, you can
understand it, it just happens to be clever with simple principles --
that can have a lot of appeal.

On 10/10/18, David Nicol <davidnicol@gmail.com> wrote:
> After reviewing the current protocol a spot,
>
> executionCondition UInt256 SHA-256 hash digest of the fulfillment that= will
> execute the transfer of value represented by this packet. Connectors M= UST
> NOT modify this field. The receiver must be able to fulfill this condi= tion
> to receive the money.
>
> maybe "Only the receiver can demonstrate knowledge of the secret,=
> previously shared with the sender, that allows all stages of the
> transaction to complete."
>
> I didn't notice while reading the article that it says anywhere th= at the
> receiver has to somehow share a per-transaction secret with the sender= ,
> before the sender invokes ILP.
>


--
"I don't know about that, as it is outside of my area of = expertise." -- competent specialized practitioners, all the time
=
--000000000000e96abd0577e9d2a2-- From nobody Fri Oct 12 12:04:34 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E61130E7E for ; Fri, 12 Oct 2018 12:04:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IjOj_4kbCDjj for ; Fri, 12 Oct 2018 12:04:30 -0700 (PDT) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E341130E94 for ; Fri, 12 Oct 2018 12:04:29 -0700 (PDT) Received: by mail-qk1-x735.google.com with SMTP id 12-v6so8279249qkj.10 for ; Fri, 12 Oct 2018 12:04:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O7qz+DTPHd48PlTNYP/Zv3/LNMJOrytTQ5rGwJ5WOzE=; b=pjKdXwjONi2/6o38+hTN6su/DjamWbc3m0p6cnlVt4fesVPjDlYyw7TQnLveKkDz6d /nMYfVCq/XKYy6RNC6yPljoj2l1ceta6BMOWHsHdcLuWOG1W2D1TKHuFUzVK/b2yDcCK 0bbUj+JcKL0Ld5AoYXiiywzlROrFa9JIx+dZmBB1szSLOBuIIW7oULIo4UftspxaCMG8 Qd+iFduN8y9BhXdjamoHL/E2cibAZfCTSjPep0rNJbN5cnKyKmfTOu6f7oZGrkTG6qie HpWD2RrZvIS6o9oatv+1r3Y1EXnRRd5WbqV6kezQe2HLVX77cJyJC74mokY/wW3WOu84 c0Ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O7qz+DTPHd48PlTNYP/Zv3/LNMJOrytTQ5rGwJ5WOzE=; b=UbhjKsCH0kmozMmEhes8rykH5zcpHtOER8dsOoz7Sbpfj3oSOCIOP9J40r0ML3xd5T ZcQ0mNC43f30n2gbajBsbUSdj72/KQysHZJKY4lgYhT1326/YXrpBLE+ZsvyWVB57NrP ty8UoxgkXOwzjAUY6lBHPsH8djVuWUGquqEp0CsItR0h8iPcRe449w1aS83eqZfraV7Q vkAxz9JFI+Wn17XIb6NjJ4oSJCRCu1y4VjGV4nx3Q+X+/ms23jx9q8WwiiN0HUkuT9/q K4YFfH92JqLRXMbh/dXAOfOa5ckPuwT5KEBpsSX24iMvhhcF8QFoa08UY3L0uYAze/YW b9ZA== X-Gm-Message-State: ABuFfoj6i4sdbx5VQyqHJVDtXLgAo5kiRYRoErI57Tk+OxtwOW9i4ZOT ibr+AfL4mPKlcLn0EsztKf4mssXC1AWU+9w7m1Q= X-Google-Smtp-Source: ACcGV60hFQjx6uDI1g+I6vIM6Hn/8MwaFn7la+zd9zsVkb13v3jxRvcBnhoIpm1dStUc5Lt659IWloLH+nz9gaSYF9g= X-Received: by 2002:a37:7f81:: with SMTP id a123-v6mr6895139qkd.37.1539371068726; Fri, 12 Oct 2018 12:04:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Nicol Date: Fri, 12 Oct 2018 14:03:51 -0500 Message-ID: To: nathan.mk.aw@gmail.com Cc: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="000000000000baa1d605780cc163" Archived-At: Subject: Re: [Ledger] Going Beyond Only Two Parties (Sender and Receiver): Enabling Multilateral Netting through implementing Liquidity-Saving Mechanisms (LSM) on Interledger X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 19:04:33 -0000 --000000000000baa1d605780cc163 Content-Type: text/plain; charset="UTF-8" I think this kind of thing would be handled by a Connector, within the current interledger vision. Please confirm? On Fri, Oct 12, 2018 at 12:15 PM Nathan Aw wrote: > Hi all, > > Today, interledger is able to connect a pair of sender and receiver via > senders to deliver payment of value. > > In the financial markets, we need to go beyond only just two parties. > > Therefore, I am exploring if it is possible to enable a multilateral > netting model through implementing Liquidity-Saving Mechanisms (LSM) on > Interledger. > > Are there any similar thoughts around this area of research? > -- "I don't know about that, as it is outside of my area of expertise." -- competent specialized practitioners, all the time --000000000000baa1d605780cc163 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think this kind of thing would be handled by a Connector= , within the current interledger vision.

Please confirm?
=
On Fri, Oct 12, 2018 at 12:= 15 PM Nathan Aw <nathan.mk.aw@= gmail.com> wrote:
Hi all,

Today, interledger is = able to connect a pair of sender and receiver via senders to deliver paymen= t of value.=C2=A0

In the financial markets, we nee= d to go beyond only just two parties.

Therefore, I= am exploring if it is possible to enable a multilateral netting model thro= ugh implementing Liquidity-Saving Mechanisms (LSM) on Interledger.

Are there any similar thoughts around this area of researc= h?
=C2=A0
--
"I don't know about that, as it is outside of my are= a of expertise." -- competent specialized practitioners, all the time<= /div>
--000000000000baa1d605780cc163-- From nobody Sat Oct 13 09:18:16 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3986C130EF5 for ; Sat, 13 Oct 2018 09:18:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ripple.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCwFJ-i8aT_K for ; Sat, 13 Oct 2018 09:18:12 -0700 (PDT) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00DEA130E0C for ; Sat, 13 Oct 2018 09:18:11 -0700 (PDT) Received: by mail-qt1-x836.google.com with SMTP id o17-v6so17159635qtr.1 for ; Sat, 13 Oct 2018 09:18:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripple.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fzoZOzF0/ZDmUDMm/q/ohwMDcR18+2AzcihhrG2Cses=; b=nFdjZy55sHEf1vc57B/wzWt8ayo7WjF6MVZH5s1eIk/Zrvi77ZoxAOZqspdf9QbYHE wCfp6RxV9TfBEq6ttM58g/8B5MuWlKhZbHLVfoxuKPdDutceDzF4QieBJi0IST2D1Kqg 7WI7z6Xb6a5BCJMxwp4HCL3jgeAYd0aWPoUsg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fzoZOzF0/ZDmUDMm/q/ohwMDcR18+2AzcihhrG2Cses=; b=sEWzVosw2G8fEHUV0UiezqLdJeJfBuPvuezi3BvnoH+WYxIli5X5qGJBo7Zj8dJ0BT zsK3KrP1uNXWnhxUYDZ4iXogkZnmD3l6kfLhRsWSNOOLvWwaup3lAw9KZZGWCFvol3sT lghnjgjV+3qYMq/IcNfIMptt6uhgY95xDciMtzHFZ+oD9AVLx94yV0FIBXiZsRyosTRw aBN4ncTEEjH5I9Ftof8lPkXXljgSH9IvsT4QptbtdCEncxY/XxHh7uo0UGX0rq/K3VHh utfiAd5B2OdfxsiUps4jDibBJEEgIV+/Z4ksKzAgxyOPoSY7HwPKfIrdaOZWP6nzOU5W tvXQ== X-Gm-Message-State: ABuFfoga4OTu+UECdUhoJ9XAD2vslMyAFPHy3rr1z3SEv2YUPOyougrd jZPSZvtG2CBye72SctwpuCAmEuhaJd10xfBcLisyOg== X-Google-Smtp-Source: ACcGV60qCtTy/cg4NgIKO+ThfX1j6FyOrlcuVofO2Nk9yspeozfLvsXh5cOdOvJssGAEIp3OwnvL7drmN4RzaQkG9PM= X-Received: by 2002:a0c:b257:: with SMTP id k23mr5385850qve.87.1539447491015; Sat, 13 Oct 2018 09:18:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Evan Schwartz Date: Sat, 13 Oct 2018 09:17:59 -0700 Message-ID: To: Nathan Aw Cc: David Nicol , Interledger Community Group , ledger@ietf.org Content-Type: multipart/alternative; boundary="000000000000da48a205781e8cd8" Archived-At: Subject: Re: [Ledger] Going Beyond Only Two Parties (Sender and Receiver): Enabling Multilateral Netting through implementing Liquidity-Saving Mechanisms (LSM) on Interledger X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 16:18:14 -0000 --000000000000da48a205781e8cd8 Content-Type: text/plain; charset="UTF-8" That's correct. Interledger packets go between a single sender and receiver but transactions can be done on credit and then netted and settled later. If multiple connectors wanted to net out the obligations among themselves automatically they could either track their balances separately and use a service to find an optional way to settle, or they could use another connector between them that would automatically track each of their obligations and net them out. For the second option, nothing additional would need to be built, but that connector would need to be capable of processing all of the packets between the connectors (which may mean the first option is a better approach). On Sat, Oct 13, 2018, 9:00 AM Nathan Aw wrote: > Hi David, > > Thats my guess too. Certainly this enhancement/capability will fall in the > scope of connector and perhaps also sender and receiver as we are > introducing a multilateral netting liquidity saving mechanism across > different parties. > > For interledger to work within existing capital markets vis-a-vis cryptos, > we will need such liquidity saving mechanisms to be implemented across > sender, receiver and connectors. > > Can the interledger experts chime in as well? On the possibility of > implementing central banks liquidity saving mechanism within interledger -- > perhaps an additional layer/abstraction on top of today's interledger > network. > > Would love to explore and deep dive into such a model/layer/abstraction. > > Nathan Aw > > On Sat, 13 Oct 2018, 03:04 David Nicol, wrote: > >> I think this kind of thing would be handled by a Connector, within the >> current interledger vision. >> >> Please confirm? >> >> On Fri, Oct 12, 2018 at 12:15 PM Nathan Aw >> wrote: >> >>> Hi all, >>> >>> Today, interledger is able to connect a pair of sender and receiver via >>> senders to deliver payment of value. >>> >>> In the financial markets, we need to go beyond only just two parties. >>> >>> Therefore, I am exploring if it is possible to enable a multilateral >>> netting model through implementing Liquidity-Saving Mechanisms (LSM) on >>> Interledger. >>> >>> Are there any similar thoughts around this area of research? >>> >> >> -- >> "I don't know about that, as it is outside of my area of expertise." -- >> competent specialized practitioners, all the time >> > --000000000000da48a205781e8cd8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That's correct. Interledger packets go between a sing= le sender and receiver but transactions can be done on credit and then nett= ed and settled later.

If multi= ple connectors wanted to net out the obligations among themselves automatic= ally they could either track their balances separately and use a service to= find an optional way to settle, or they could use another connector betwee= n them that would automatically track each of their obligations and net the= m out. For the second option, nothing additional would need to be built, bu= t that connector would need to be capable of processing all of the packets = between the connectors (which may mean the first option is a better approac= h).

On Sat, Oct = 13, 2018, 9:00 AM Nathan Aw <n= athan.mk.aw@gmail.com> wrote:
Hi David,

<= div dir=3D"auto">Thats my guess too. Certainly this enhancement/capability = will fall in the scope of connector and perhaps also sender and receiver as= we are introducing a multilateral netting liquidity saving mechanism acros= s different parties.

For interledger = to work within existing capital markets vis-a-vis cryptos, we will need suc= h liquidity saving mechanisms to be implemented across sender, receiver and= connectors.=C2=A0

Can the interledger experts= chime in as well?=C2=A0 On the possibility of implementing central banks l= iquidity saving mechanism within interledger -- perhaps an additional layer= /abstraction on top of today's interledger network.=C2=A0
Would love to explore and deep dive into such a model/layer/abs= traction.=C2=A0
=C2=A0
Nathan Aw

=
On Sat, 13 Oct 2018, 03:04 Davi= d Nicol, <davidnicol@gmail.com> wrote:
--000000000000da48a205781e8cd8-- From nobody Sat Oct 13 09:22:58 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23772130EF5 for ; Sat, 13 Oct 2018 09:22:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ripple.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SODOHiU7x01F for ; Sat, 13 Oct 2018 09:22:53 -0700 (PDT) Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2B2C130E23 for ; Sat, 13 Oct 2018 09:22:53 -0700 (PDT) Received: by mail-qt1-x833.google.com with SMTP id d14-v6so17146178qto.4 for ; Sat, 13 Oct 2018 09:22:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripple.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=x2KjAjYQTC1Jio09qjJD7/m8oprMbRA8pn7cjZlKRMM=; b=adbx6rsnK0z2jcntJpdZmnwfvn6LqlAxSsSG92M0mb8TVypagvPXbRbYPB4qo5TY8j 2R6eDrGgI4cESlSl6R0GtXeme0IfjzoRb+cZSrkX+u+1jMb8WegvHQRhDIGRK7nD0PA5 kmaPHLYy9Bug7Y9Q9JGxqr0/GsWgReIB6kPzo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=x2KjAjYQTC1Jio09qjJD7/m8oprMbRA8pn7cjZlKRMM=; b=D4eR2jwcvdhrAxdShlEAIuuUMNG2SGQTKVWAWI3YsZaafrl5qOg4rMUNuzd6AiYFGQ /pMOwMBWI6RJRR9v/sBzZ97R910QfvvvSY8Xoei9GH7LvVNj8OBXw6ZhQx6ABvnyuZCE nTx+ws8fEHVmpxPdP4lvwDWo0+1I0t1zguU3ivUROE+38tt54cQFwf+LpGazVeteQLE3 q9qLk7zzstVoNLcr87UU8d0C2HlHZB9p1zqSp2QRCppzvWEEIF+cU5etiNkdaE4DH0Ik +3CsraDLc9DRgXfk+ZPspJ6+YTVFllr/g4jm9W/E2cjtzfzLchB6IBJeODNhUabGVHyp n4XA== X-Gm-Message-State: ABuFfohZsjxBnyW9xG0XmDOTAqHG1nUIUTYWO+xNR69Jy0U1RjaMBOCB 0vLO6O9XoG43TEMvYToge6d4RiX40z++3lJTEWDx7g== X-Google-Smtp-Source: ACcGV62DjCRvaVX6GCkU9SR/yt9rjNniVVrOb0QyUMzObSEohR87zQwC7eq0a5ORvyJFIvlPw8w+RG9dQ4lwe6dB1uU= X-Received: by 2002:ac8:6754:: with SMTP id n20-v6mr10052476qtp.70.1539447772719; Sat, 13 Oct 2018 09:22:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Evan Schwartz Date: Sat, 13 Oct 2018 09:22:41 -0700 Message-ID: To: Nathan Aw Cc: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="000000000000a4c30105781e9d18" Archived-At: Subject: Re: [Ledger] Researching to leverage Hashed-Timelock Agreements (HTLAs) paradigm for establishing atomicity between different DLT networks for asset swaps with full decentralization X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 16:22:56 -0000 --000000000000a4c30105781e9d18 Content-Type: text/plain; charset="UTF-8" The same construction can be used no matter what the underlying assets are. They can be cryptocurrencies, fiat currencies, shares of stock or other divisible assets. If you want to use this method for a swap you can send a "payment" from one of your accounts to another. On Sat, Oct 13, 2018, 8:27 AM Nathan Aw wrote: > Hi all, > > Second try. Thank you. > > I am a blockchain engineer based out of Singapore working at a leading > bank in ASEAN. > > I am looking to leverage the Hashed-Timelock Agreements (HTLAs) paradigm > for establishing atomicity between different DLT networks for asset swaps > to achieve cross border payments with partial to full decentralization in > mind. > > With the goal in mind, I like to understand technically how can this > paradigm be applied to achieve payment vs payment (pvp) with semi-trusted > nodes such as clearinghouses, banks and individual players? Applying the > same concept of a crypto swap between ETH and BTC, the same can be applied > between SGD and HKD? > > Also, I hope to understand the models around how liquidity can be > maintained between these nodes? > > Regards, > > Nathan Aw > https://sg.linkedin.com/in/awnathan > > https://erc725alliance.org/ > > > > On Sat, Oct 13, 2018 at 12:39 AM Nathan Aw wrote: > >> Hi all, >> >> I am a blockchain engineer based out of Singapore working at a leading >> bank in ASEAN. >> >> I am looking to leverage the Hashed-Timelock Agreements (HTLAs) paradigm >> for establishing atomicity between different DLT networks for asset swaps >> to achieve cross border payments with partial to full decentralization in >> mind. >> >> With the goal in mind, I like to understand technically how can this >> paradigm be applied to achieve payment vs payment (pvp) with semi-trusted >> nodes such as clearinghouses, banks and individual players? Applying the >> same concept of a crypto swap between ETH and BTC, the same can be applied >> between SGD and HKD? >> >> Also, I hope to understand the models around how liquidity can be >> maintained between these nodes? >> >> Thank you! >> >> Regards, >> >> Nathan Aw >> https://sg.linkedin.com/in/awnathan >> https://erc725alliance.org/ >> >> >> --000000000000a4c30105781e9d18 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The same construction can be used no matter what the= underlying assets are. They can be cryptocurrencies, fiat currencies, shar= es of stock or other divisible assets.

If you want to use this method for a swap you can send a &qu= ot;payment" from one of your accounts to another.

Hi all,

Second try. Thank you.=C2=A0

I am a blockchain engineer based out of Singap= ore working at a leading bank in ASEAN.=C2=A0

I am= looking to leverage the Hashed-Timelock Agreements (HTLAs) paradigm for es= tablishing atomicity between different DLT networks for asset swaps to achi= eve cross border payments with partial to full decentralization in mind.=C2= =A0

With the goal in mind, I like to understand te= chnically how can this paradigm be applied to achieve payment vs payment (p= vp) with semi-trusted nodes such as clearinghouses, banks and individual pl= ayers? Applying the same concept of a crypto swap between ETH and BTC, the = same can be applied between SGD and HKD?=C2=A0=C2=A0

Also, I hope to understand the models around how liquidity can be mainta= ined between these nodes?


On Sat, Oct 13, 2018 at 12:39 AM N= athan Aw <nathan.mk.aw@gmail.com> wrote:
=
Hi all,
I am a blockchain engineer based out of Singapore working = at a leading bank in ASEAN.=C2=A0

I am looking to = leverage the Hashed-Timelock Agreements (HTLAs) paradigm for establishing a= tomicity between different DLT networks for asset swaps to achieve cross bo= rder payments with partial to full decentralization in mind.=C2=A0

With the goal in mind, I like to understand technically ho= w can this paradigm be applied to achieve payment vs payment (pvp) with sem= i-trusted nodes such as clearinghouses, banks and individual players? Apply= ing the same concept of a crypto swap between ETH and BTC, the same can be = applied between SGD and HKD?=C2=A0=C2=A0

Also, I h= ope to understand the models around how liquidity can be maintained between= these nodes?

Thank you!=C2=A0
--000000000000a4c30105781e9d18-- From jake@amdenfinancialtechnology.com Mon Oct 15 11:40:47 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220FE130DD1 for ; Mon, 15 Oct 2018 11:40:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=amdenfinancialtechnology-com.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3XzTFr8HDdLx for ; Mon, 15 Oct 2018 11:40:43 -0700 (PDT) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB4E2130ED4 for ; Mon, 15 Oct 2018 11:40:41 -0700 (PDT) Received: by mail-lj1-x22e.google.com with SMTP id o14-v6so18481098ljj.2 for ; Mon, 15 Oct 2018 11:40:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amdenfinancialtechnology-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5haVJyuCDRC0kHv9mVZb9hZE3OhymwyxRp2Wed61RIA=; b=XphaHYYieXF1f4lNMy/jG1GPKwFIXwwo+bcEatwms6IX3EH8NHHA7sNDpC9KqrxIrH bwWh+mmq/QmvhRaN8UcTMhAJ1ssC2Glg5Whj3InKsISdnsUK2dAb+btwqLNodbRQq2+T OUoO3ncQCri33yrvpna8IiH5p3KJtBy1HUeD18lim2swxnYXC5M4ASrsmyy5QqpilkYL ACBaxlxpsXXC9Ie+WrVpx3WDBpTRlDZ5rL1MvIhCcGOXXTq7yeKtwpTPWju0IL/0jPj0 venN3EhhuQVrU7cvh6odUcZeCEw5/w4SYoEHTn5pAEpy52cLyy24aMBPlq7Mbf0orx2W /DFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5haVJyuCDRC0kHv9mVZb9hZE3OhymwyxRp2Wed61RIA=; b=ZoETsisBqZlqWXznv/GZdgnkkM1mxFF48JojgIuuDuXgyxsJz0qQDZsZ6mnfMGBIQ2 Iv8Ppdo7DlWcT1QIUHNYxb+wminF9skEncTS7IxZeYakv6rESB+3UaLvULnfdrHcbteF L1orFi/vs5EgKve7vKmOLj9RahI5++P8oZ42sTdZCzGGaepkhdCOv8WIx04TIto5azdG 2VQzzPrK574bF9tZ40rvE9fhxUMej0Ojtegv0YqToIKlYDtGvXwfIUQDYQyeTF+XmkXr onGXiRT/44FaMV7s5EezjmrZ95G1zqH+oQRcBxpZcNaB8fDJBUJ2l6vpZ2Ok2YSPOxVd yDyQ== X-Gm-Message-State: ABuFfogWpDxQxNzfb03jroyXdV9CSF3Kz7JaMDbj1ZZ7wcS1u9mEA2HE h/ytgvNH9E85Xc4iwHHzZKjEgrSG1JuvFGJaUzvmPsF0 X-Google-Smtp-Source: ACcGV61mblZBgMpZzCK7yrQ4ITYZQ6jQFooBBMlLuenc6bIOIJ86GB9sIrFZErk+PB2jpcJ5PTmamcHe81Oh9R66qOw= X-Received: by 2002:a2e:9955:: with SMTP id r21-v6mr11136899ljj.5.1539628839621; Mon, 15 Oct 2018 11:40:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jake Carter Date: Mon, 15 Oct 2018 14:40:27 -0400 Message-ID: To: Nathan Aw Cc: Evan Schwartz , public-interledger@w3.org, ledger@ietf.org Content-Type: multipart/alternative; boundary="000000000000126bca057848c61a" Archived-At: X-Mailman-Approved-At: Tue, 16 Oct 2018 10:09:25 -0700 Subject: Re: [Ledger] Researching to leverage Hashed-Timelock Agreements (HTLAs) paradigm for establishing atomicity between different DLT networks for asset swaps with full decentralization X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2018 19:56:47 -0000 --000000000000126bca057848c61a Content-Type: text/plain; charset="UTF-8" Nathan, Fixed income products are cleared with DvP - Delivery vs Payment Many Tri-Party repos are also cleared the same way. https://en.wikipedia.org/wiki/Delivery_versus_payment https://www.fanniemae.com/content/fact_sheet/dvp-dvf-comparison.pdf A good example (potential) of what you are describing is the current FX Inter-bank Market and how CLS Bank is used for clearing, although much different technology. https://www.bis.org/publ/qtrpdf/r_qt0809y.htm Hope this might provide some existing use cases and business flows. Hope this might help, Jake On Mon, Oct 15, 2018 at 8:59 AM Nathan Aw wrote: > Hi Evan, > > Thanks! Would there be gridlock if more than one parties swap an asset > with each other? > > Thinking and designing from a multilateral netting perspective and how > best to resolve gridlocks and optimizing liquidity among multiparties. > > Also, liquidity saving mechanisms can already be achieved today with DLT > solutions. Looking ahead, there are many consortiums are out there and > therefore htlc across multiple dlt networks is something that I am > thinking, researching and engineering with. > > Thank you. > > Nathan Aw > > > On Sun, 14 Oct 2018, 00:22 Evan Schwartz, wrote: > >> The same construction can be used no matter what the underlying assets >> are. They can be cryptocurrencies, fiat currencies, shares of stock or >> other divisible assets. >> >> If you want to use this method for a swap you can send a "payment" from >> one of your accounts to another. >> >> On Sat, Oct 13, 2018, 8:27 AM Nathan Aw wrote: >> >>> Hi all, >>> >>> Second try. Thank you. >>> >>> I am a blockchain engineer based out of Singapore working at a leading >>> bank in ASEAN. >>> >>> I am looking to leverage the Hashed-Timelock Agreements (HTLAs) paradigm >>> for establishing atomicity between different DLT networks for asset swaps >>> to achieve cross border payments with partial to full decentralization in >>> mind. >>> >>> With the goal in mind, I like to understand technically how can this >>> paradigm be applied to achieve payment vs payment (pvp) with semi-trusted >>> nodes such as clearinghouses, banks and individual players? Applying the >>> same concept of a crypto swap between ETH and BTC, the same can be applied >>> between SGD and HKD? >>> >>> Also, I hope to understand the models around how liquidity can be >>> maintained between these nodes? >>> >>> Regards, >>> >>> Nathan Aw >>> https://sg.linkedin.com/in/awnathan >>> >>> https://erc725alliance.org/ >>> >>> >>> >>> On Sat, Oct 13, 2018 at 12:39 AM Nathan Aw >>> wrote: >>> >>>> Hi all, >>>> >>>> I am a blockchain engineer based out of Singapore working at a leading >>>> bank in ASEAN. >>>> >>>> I am looking to leverage the Hashed-Timelock Agreements (HTLAs) >>>> paradigm for establishing atomicity between different DLT networks for >>>> asset swaps to achieve cross border payments with partial to full >>>> decentralization in mind. >>>> >>>> With the goal in mind, I like to understand technically how can this >>>> paradigm be applied to achieve payment vs payment (pvp) with semi-trusted >>>> nodes such as clearinghouses, banks and individual players? Applying the >>>> same concept of a crypto swap between ETH and BTC, the same can be applied >>>> between SGD and HKD? >>>> >>>> Also, I hope to understand the models around how liquidity can be >>>> maintained between these nodes? >>>> >>>> Thank you! >>>> >>>> Regards, >>>> >>>> Nathan Aw >>>> https://sg.linkedin.com/in/awnathan >>>> https://erc725alliance.org/ >>>> >>>> >>>> -- *_______________________________________* *Jake Carter* *Tel **1-801-864-1651* *jake@amdens.com * *Amdens* / --000000000000126bca057848c61a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Nathan,

Fixed income products are clear= ed with DvP -=C2=A0 Delivery vs Payment
Many Tri-Party repos are also c= leared the same way.=C2=A0=C2=A0

A good ex= ample (potential)=C2=A0 of what you are describing is the current FX Inter-= bank Market and how CLS Bank is used for clearing, although much different = technology.

=
Hope this might provide some existing use cases and business flows.

Hope this might help,
Jake

<= /div>

=C2=A0

On Mon, Oct 15, 2018 at 8:59 AM Nathan Aw <nathan.mk.aw@gmail.com> wrote:
Hi Evan,

Thanks! Would there be gridlock if = more than one parties swap an asset with each other?

Thinking and designing from a multilateral net= ting perspective and how best to resolve gridlocks and optimizing liquidity= among multiparties.

Als= o, liquidity saving mechanisms can already be achieved today with DLT solut= ions. Looking ahead, there are many consortiums are out there and therefore= htlc across multiple dlt networks is something that I am thinking, researc= hing and engineering with.

Thank you.

Nathan Aw


<= div class=3D"gmail_quote">
On Sun, 14 Oct 2018, 00:22 Evan = Schwartz, <evan@ripple.com> wrote:
The same construction can be used no matter = what the underlying assets are. They can be cryptocurrencies, fiat currenci= es, shares of stock or other divisible assets.

<= /div>
If you want to use this method for a swap you can se= nd a "payment" from one of your accounts to another.

On Sat, Oct 13, 2018, 8= :27 AM Nathan Aw <nathan.mk.aw@gmail.com> wrote:
H= i all,

Second try. Thank you.=C2=A0

=
I am a blockchain engineer based out of Singapore working at a le= ading bank in ASEAN.=C2=A0

I am looking to leverag= e the Hashed-Timelock Agreements (HTLAs) paradigm for establishing atomicit= y between different DLT networks for asset swaps to achieve cross border pa= yments with partial to full decentralization in mind.=C2=A0

<= /div>
With the goal in mind, I like to understand technically how can t= his paradigm be applied to achieve payment vs payment (pvp) with semi-trust= ed nodes such as clearinghouses, banks and individual players? Applying the= same concept of a crypto swap between ETH and BTC, the same can be applied= between SGD and HKD?=C2=A0=C2=A0

Also, I hope to = understand the models around how liquidity can be maintained between these = nodes?


On Sat, Oct 13, 2018 = at 12:39 AM Nathan Aw <nathan.mk.aw= @gmail.com> wrote:
Hi all,

I am a blockchain engi= neer based out of Singapore working at a leading bank in ASEAN.=C2=A0
=

I am looking to leverage the Hashed-Timelock Agreements= (HTLAs) paradigm for establishing atomicity between different DLT networks= for asset swaps to achieve cross border payments with partial to full dece= ntralization in mind.=C2=A0

With the goal in mind,= I like to understand technically how can this paradigm be applied to achie= ve payment vs payment (pvp) with semi-trusted nodes such as clearinghouses,= banks and individual players? Applying the same concept of a crypto swap b= etween ETH and BTC, the same can be applied between SGD and HKD?=C2=A0=C2= =A0

Also, I hope to understand the models around h= ow liquidity can be maintained between these nodes?

Thank you!=C2=A0

--

_______________________________________=

Jake Carter

= Tel=C2=A01-801-864-1651

jake@amdens.com

Amdens

<= span style=3D"font-size:7.5pt;font-family:"akzidenz grotesk ce light&q= uot;;color:rgb(221,255,255)">/

--000000000000126bca057848c61a-- From nobody Tue Oct 16 11:44:22 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC132130E26 for ; Tue, 16 Oct 2018 11:44:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLFxLe-dRLc2 for ; Tue, 16 Oct 2018 11:44:19 -0700 (PDT) Received: from mail-oi1-x243.google.com (mail-oi1-x243.google.com [IPv6:2607:f8b0:4864:20::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01208130E25 for ; Tue, 16 Oct 2018 11:44:18 -0700 (PDT) Received: by mail-oi1-x243.google.com with SMTP id u197-v6so18945878oif.5 for ; Tue, 16 Oct 2018 11:44:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=5gCge2SwglqWj7YXrD7LjvnCNPfjBkErCKQO670W57g=; b=Y2+A8BvYLlQTVbg2TwhX+0EY8w+lkNSoWe0GYGoD9wHVyHdTK2uzMn0ubI70brqR3u ap1TUNjYYoiqiv87l4zZEiDupl1M1HgRUSeuG5CAlOHSboDVV/ktS0fOSgeBgGQlmD5B Osh6AZ+kyXxZ2lKStsnOPzLoO0XCfQjqUM7Ok= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5gCge2SwglqWj7YXrD7LjvnCNPfjBkErCKQO670W57g=; b=uBT9oe4ye6dCmz0hwTsIusg/GC2UWqO982hKNwguJbs4XJzqTQXRH1kRnv9Irf0Dm4 3pK8aOY8P6ZmWFMD32/ffJScMhAl+t4Z+0YExvsKwj/uzJal6ZcFYcKjqhNMmMEMvYTY MBTXylEod4u150d68owxL21fJD3p5Bw8JzvrgQ8QAlP9i8XzndOo8on/guxRIF8aCMmV XYtHvgEDfDJGBvTGFc83ZLdyQHxIRh6pSAEvTo35TxEraIk7CWCd/2+HP1rUhHpzkgUC 5Scoaqu05E4Sw0xNNgBgEDMYIjz3KSY12PsWj7KcQfK8H9DYeLLgmIrGct9SWlKp2H5v Wr4g== X-Gm-Message-State: ABuFfog5WJJ6hXHQIOfa1VaEV2IKBc3pZHrFCSDnhldXkYJ+2WCaRWs1 0hxC/I97k/3PiWN//wdqtaMSKismqMx+gczGYOFCvuJHd4E= X-Google-Smtp-Source: ACcGV6000l0rJjmMvsbFuRZGOeWfvb6Bt8KWgQapxMM8Rhg9ty5A5unl7ut1FcnVrWpjET7E2Vz9MVLK/EzUzzNisN8= X-Received: by 2002:aca:d6cd:: with SMTP id n196-v6mr11690517oig.32.1539715457662; Tue, 16 Oct 2018 11:44:17 -0700 (PDT) MIME-Version: 1.0 From: Adrian Hope-Bailie Date: Tue, 16 Oct 2018 20:44:05 +0200 Message-ID: To: Interledger Mailing List - IETF , Interledger Community Group , Hyperledger Quilt Mailing List Content-Type: multipart/mixed; boundary="000000000000e8ede805785cf022" Archived-At: Subject: [Ledger] AGENDA - Interledger Call - 17 October - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 18:44:21 -0000 --000000000000e8ede805785cf022 Content-Type: multipart/alternative; boundary="000000000000e8ede405785cf020" --000000000000e8ede405785cf020 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, Strata have 2 updates to share on the call: 1. They will be launching a new test connector soon, supporting multiple settlement currencies 2. They are involved in hackharvard.io this weekend and will provide some details on what it involves and how you can get involved (hint, some nice prizes to win!) I'd like to open a discussion on community management and engagement. We're looking for people to run events, organize these calls, maintain the website etc. If anyone would like to become more active in running the community please join the call and let us know how you are able to contribute. As always, if you have something to raise please bring it to the call or send to the list (reply to this mail) to add to the agenda. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/s/377506344 Or iPhone one-tap: US: +14086380968,,377506344# or +16468769923,,377506344# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 408 638 0968 <+1%20408%20638%200968> or +1 646 876 9923 <+1%20646%20876%209923> or +1 669 900 6833 <+1%20669%20900%206833> Meeting ID: 377 506 344 International numbers available: https://zoom.us/u/cbrUAzE3W --000000000000e8ede405785cf020 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
Strata have 2 upd= ates to share on the call:
1. They will be launching a new test c= onnector soon, supporting multiple settlement currencies
= 2. They are involved in hackharvard.io=C2=A0this weekend and will provide some details on what it involves and h= ow you can get involved (hint, some nice prizes to win!)
I'd like to open a discussion on community management and engage= ment.=C2=A0We're looking for people to run events, organ= ize these calls, maintain the website etc.=C2=A0If anyone would lik= e to become more active in running the community please join the call and l= et us know how you are able to contribute.
As always, if y= ou have something to raise please bring it to the call or send to the list = (reply to this mail) to add to the agenda.


Or iPho= ne one-tap:
=C2=A0=C2=A0=C2=A0=C2=A0US: +14086380968,,377506344# or +16468769923,,3775= 06344#

= Or Telephone:
=C2=A0=C2=A0=C2=A0=C2=A0Dial(for higher quality, dial a number base= d on your current location):=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0US:=C2=A0<= a href=3D"tel:+1%20408%20638%200968" title=3D"tel:+1 408 638 0968" target= =3D"_blank">+1 408 638 0968=C2=A0or=C2=A0+1 646 876 9923<= /a>=C2=A0or=C2= =A0+1 669 900 6833=C2=A0
<= span style=3D"color:rgb(35,31,32)">=C2=A0=C2=A0=C2=A0=C2=A0Meeting ID: 377 506= 344
= =C2=A0=C2=A0=C2=A0=C2=A0International numbers available:=C2=A0https://zoom.us/u/cbrUAzE3W
--000000000000e8ede405785cf020-- --000000000000e8ede805785cf022 Content-Type: text/calendar; charset="US-ASCII"; name="ilp-2018-10-17.ics" Content-Disposition: attachment; filename="ilp-2018-10-17.ics" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_jnc2rup70 QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpCRUdJTjpW RVZFTlQNCkRUU1RBTVA6MjAxODEwMTZUMDAwNDU0Wg0KVUlEOjIwMTgxMDE3QGludGVybGVkZ2Vy Lm9yZw0KRFRTVEFSVDoyMDE4MTAxN1QxNTAwMDBaDQpEVEVORDoyMDE4MTAxN1QxNjAwMDBaDQpT VU1NQVJZOkludGVybGVkZ2VyIENvbW11bml0eSBDYWxsDQpVUkw6aHR0cHMlM0ElMkYlMkZ6b29t LnVzJTJGcyUyRjM3NzUwNjM0NA0KREVTQ1JJUFRJT046Sm9pbiBmcm9tIFBDXCwgTWFjXCwgTGlu dXhcLCBpT1Mgb3IgQW5kcm9pZDogaHR0cHM6Ly96b29tLnVzL3MvMzc3NTA2MzQ0XG5cbk9yIGlQ aG9uZSBvbmUtdGFwOlxuICAgIFVTOiArMTQwODYzODA5NjhcLFwsMzc3NTA2MzQ0IyBvciArMTY0 Njg3Njk5MjNcLFwsMzc3NTA2MzQ0I1xuXG5PciBUZWxlcGhvbmU6XG4gICAgRGlhbChmb3IgaGln aGVyIHF1YWxpdHlcLCBkaWFsIGEgbnVtYmVyIGJhc2VkIG9uIHlvdXIgY3VycmVudCBsb2NhdGlv bik6IFxuICAgIFVTOiArMSA0MDggNjM4IDA5Njggb3IgKzEgNjQ2IDg3NiA5OTIzIG9yICsxIDY2 OSA5MDAgNjgzMyBcbiAgICBNZWV0aW5nIElEOiAzNzcgNTA2IDM0NFxuICAgIEludGVybmF0aW9u YWwgbnVtYmVycyBhdmFpbGFibGU6IGh0dHBzOi8vem9vbS51cy91L2NiclVBekUzV1xuDQpFTkQ6 VkVWRU5UDQpFTkQ6VkNBTEVOREFS --000000000000e8ede805785cf022-- From nobody Thu Oct 18 08:13:49 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B0812D4E8 for ; Thu, 18 Oct 2018 08:13:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eue_yae1kc4C for ; Thu, 18 Oct 2018 08:13:44 -0700 (PDT) Received: from mail-qt1-x843.google.com (mail-qt1-x843.google.com [IPv6:2607:f8b0:4864:20::843]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8793912426A for ; Thu, 18 Oct 2018 08:13:44 -0700 (PDT) Received: by mail-qt1-x843.google.com with SMTP id q41-v6so34610879qtq.10 for ; Thu, 18 Oct 2018 08:13:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gWDxLSHsSrE45Mv3pbaqdYE3NicHyLxtW0PiNKqbHVc=; b=hT+EV/8kfFzpC8BXMQNZKRHx2VaxB2c0/t6DUtonucAL916hnj7giSruiUjhpTd3OP u5WMnN2eXJpYacW/g/aR7U2tkkkvg+fgQHgSMcpnXTNeQ+wncPd5u3rFslSVZRmOyO4y uLhjXU7NyjnNqiS6gcY7AwPC60V3Y4OoaooOnjcMp1HDoF1pvyGcyn02AHXHYOgSH50I Krbw5jrgkTaaCL7aSUxxgEDgai71A4eynHNwD7hBw8BiOIMZunoBlmqHMJIxMl3AzsA9 a04PjYCH1esdqT9/hcIFySvg1tyr4T+jy2pxTqi7JZaKU9OmrQv7E8a9HrTMI1CPi2YF nUag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gWDxLSHsSrE45Mv3pbaqdYE3NicHyLxtW0PiNKqbHVc=; b=dlMBLBMpnkg38Z0hz2KnJXPZhoGhtdWZ/PsV/uWQ1I8BPT8KFmsSutb6zbggxh1Yfo zJsZ0mTnfOdTUYXirLSV7JwAtFWr/nr1XzHn1esZG7UHu+AG33nGiTC1q1eOvAI7xm6r lfjbALhzswuJTJxCczzfibr/zIOtFlQhB4P+9MFuklBi1Rv58rhz038vVcWKzFle4tYV Zfgyq2xp6yvf4Q+Zo4Tmm6e7tAqc46MHOvMOMKExGEpJ+VjP9jsbZ4MQNgT5J+IRh5to ZJpZ4OC9pjf++GTL2cNbPJKFb+JvyndA4/4ZZBmkqZfCyYxY5wleYFYQz5HlaADoqju6 d+0g== X-Gm-Message-State: ABuFfohp/9vlVwbL5wz88jIUpdDnStvfWlpkCzBdMt+Z2NiT+RSoTIbi IU3mIjASi78T0RASY9BOdmNjb2eZ9gdn1cDxCDFeSA== X-Google-Smtp-Source: ACcGV61ZudZykcMn82or9/m62dRzwWYG5hjDTmcikWwJucdCulEsh0Qii3KdctHgpMY+VTZ7zDgiOTE15ay2s2EDA84= X-Received: by 2002:aed:3e12:: with SMTP id l18-v6mr30183296qtf.62.1539875623769; Thu, 18 Oct 2018 08:13:43 -0700 (PDT) MIME-Version: 1.0 References: <1538569618.local-b7e7b227-2e05-v1.4.2-f587b7b7@getmailspring.com> In-Reply-To: From: David Nicol Date: Thu, 18 Oct 2018 10:13:09 -0500 Message-ID: To: fiatjaf@alhur.es Cc: Evan Schwartz , Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="0000000000008d9d6c0578823b3f" Archived-At: Subject: Re: [Ledger] Blog post explaining "What is Interledger?" X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 15:13:46 -0000 --0000000000008d9d6c0578823b3f Content-Type: text/plain; charset="UTF-8" how about calling the preimage a "per-transaction password" and say "one-way hash function" to avoid confusion with signatures? > On Wed, Oct 10, 2018 at 2:13 PM Giovanni P wrote: > >> I think everybody knows what a hash is, but "preimage" is a little >> more advanced/obscure. >> >> "established cryptographic principles" is much more mumbo-jumbo than >> saying "hash". > > -- "I don't know about that, as it is outside of my area of expertise." -- competent specialized practitioners, all the time --0000000000008d9d6c0578823b3f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


<= div>how about calling the preimage a "per-transaction password" a= nd say "one-way hash function" to avoid confusion with signatures= ?

=C2=A0
On= Wed, Oct 10, 2018 at 2:13 PM Giovanni P <fiatjaf@alhur.es> wrote:
I think everybody knows what a hash is, but "prei= mage" is a little
more advanced/obscure.

"established cryptographic principles" is much more mumbo-jumbo t= han
saying "hash".

--
"I don't know about that, as it = is outside of my area of expertise." -- competent specialized practiti= oners, all the time
--0000000000008d9d6c0578823b3f-- From nobody Tue Oct 30 09:29:30 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8723B130E26 for ; Tue, 30 Oct 2018 09:29:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ripple.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ifRaRnu64xB9 for ; Tue, 30 Oct 2018 09:29:22 -0700 (PDT) Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AD2C130DF3 for ; Tue, 30 Oct 2018 09:29:21 -0700 (PDT) Received: by mail-qt1-x834.google.com with SMTP id k12so8316726qtf.7 for ; Tue, 30 Oct 2018 09:29:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ripple.com; s=google; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=9vPtN0brBMVNdVTr8q/XCKwEEFhHin86iN6LFtJ7Zcc=; b=pB7MrPsRj6ai7oxCQv1YHK6p/9inprfjNs5aCrBhWnvcCwybo4nXkOKtKJP2OdVTyH aa17to9zIK77jXHObvvxonWlSvkC86KpFI6CsVPx8hADygXecWLXZlfRiXDbBKemYA2f smVrEZYMjz8kAnxAnjTxKRZSi6qTqk+ptttE8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=9vPtN0brBMVNdVTr8q/XCKwEEFhHin86iN6LFtJ7Zcc=; b=bgpzoZWxV5W0N/J4rP3/TUhTKiYaF73HpTzynYeL7BK2IPykZDYUeWR/yqyGLtyDlS i0CjEjqe1/xHNYXpOrumCNh2z8WCZSTe3U08wUamu+E9zPMuVW+I2akkk/OPdOtDDePC GoqMUSV/iadmYnnXFL/l2ZNWXY+/h/WiMiaPtG7p2yhtIyeVGoVfmxvim5mJpSypv10o JT/bW5hyXjD4ZF1bB3TooOHlrxnzp20pjFhegrAIV5x9JhduuFtTwKTR/otyf+IogGOi 0e730Mcq4kRUx1vYAjrerDovFUIxigkimowF4BRBMoMWxAZaFdUSf9hhJ1bHjxtluIAJ O2EA== X-Gm-Message-State: AGRZ1gIEXaKB5X2HCH9m2CJWFm4np5HEDAMmoxE/qx7f/HXEhTphrnQE 0cWDjQ2aiIr3HF+s8WCrC9Ibzg== X-Google-Smtp-Source: AJdET5dIv8E9L/GoRAKFfm/TOzQ4PDtyvoCy8zfWP51BpCyWT43bIZzSj+czG7wmFalFn0na4VaiOg== X-Received: by 2002:a0c:d1a2:: with SMTP id e31mr17969457qvh.24.1540916960920; Tue, 30 Oct 2018 09:29:20 -0700 (PDT) Received: from arch (inet-64-112-177-6.bos.netblazr.com. [64.112.177.6]) by smtp.gmail.com with ESMTPSA id s127-v6sm5867680qkf.40.2018.10.30.09.29.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Oct 2018 09:29:20 -0700 (PDT) Date: Tue, 30 Oct 2018 12:29:18 -0400 From: Evan Schwartz To: David Nicol Cc: "=?utf-8?Q?fiatjaf=40alhur.es?=" , Interledger Community Group , Interledger Mailing List - IETF Message-ID: <1540916601.local-f6330735-ac58-v1.5.1-da141eaf@getmailspring.com> In-Reply-To: References: X-Mailer: Mailspring MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5bd886de_60236019_3951" Archived-At: Subject: Re: [Ledger] Blog post explaining "What is Interledger?" X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2018 16:29:27 -0000 --5bd886de_60236019_3951 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline I see pros and cons to both ways of describing the hash and preimage. I'm always unsure with these pieces what level of technical detail to include or what level of knowledge to assume. Re: sharing secrets. The hash and preimage are effectively ways to authenticate the ILP packet and response and make sure it got to the right recipient. Originally, we thought that the sender and receiver would exchange the condition out of band for each packet, but that doesn't work well with the streaming payments or packetized value model. Exchanging a shared secret up front allows you to authenticate any number of subsequent packets. STREAM assumes you start with a shared symmetric key but it doesn't specify how you get that. In practice, most higher-level protocols will use public key cryptography to generate that shared secret, whether that means going through the internet and TLS (like SPSP does) or doing the key exchange through ILP. On Oct 18 2018, at 11:13 am, David Nicol wrote: > > > > how about calling the preimage a "per-transaction password" and say "one-way hash function" to avoid confusion with signatures? > > > > > On Wed, Oct 10, 2018 at 2:13 PM Giovanni P wrote: > > > I think everybody knows what a hash is, but "preimage" is a little > > > more advanced/obscure. > > > > > > "established cryptographic principles" is much more mumbo-jumbo than > > > saying "hash". > > > > > > > > -- > "I don't know about that, as it is outside of my area of expertise." -- competent specialized practitioners, all the time > > > > --5bd886de_60236019_3951 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I see pros and cons to both ways of describing the hash and preimage= . I'm always unsure with these pieces what level of technical detail to i= nclude or what level of knowledge to assume.

Re: sharing secrets. The hash and preimage = are effectively ways to authenticate the ILP packet and response and make= sure it got to the right recipient. Originally, we thought that the send= er and receiver would exchange the condition out of band for each packet,= but that doesn't work well with the streaming payments or packetized val= ue model. Exchanging a shared secret up front allows you to authenticate = any number of subsequent packets.

STREAM assumes you start = with a shared symmetric key but it doesn't specify how you get that. In p= ractice, most higher-level protocols will use public key cryptography to = generate that shared secret, whether that means going through the interne= t and TLS (like SPSP does) or doing the key exchange through ILP.
On Oct 18 2018, at 11:13= am, David Nicol <davidnicol=40gmail.com> wrote:
<= br>


how about calling th= e preimage a =22per-transaction password=22 and say =22one-way hash funct= ion=22 to avoid confusion with signatures=3F

&nb= sp;

On Wed, Oct 10, 2018 at 2:13 PM G= iovanni P <fiatjaf=40alhur.es> wrote:
I think everybody knows what a hash is, but =22preimage=22 is= a little
more advanced/obscure.

=22established c= ryptographic principles=22 is much more mumbo-jumbo than
saying= =22hash=22.

--
=22I don't know about that, as it is outside of= my area of expertise.=22 -- competent specialized practitioners, all the= time
--5bd886de_60236019_3951-- From nobody Tue Oct 30 13:10:11 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2F4130DD6 for ; Tue, 30 Oct 2018 13:10:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjRBHeGLBrvL for ; Tue, 30 Oct 2018 13:10:09 -0700 (PDT) Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BCC012D4F0 for ; Tue, 30 Oct 2018 13:10:09 -0700 (PDT) Received: by mail-ot1-x32f.google.com with SMTP id p23so12378087otf.11 for ; Tue, 30 Oct 2018 13:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=6XV6JVZa3idz96myL7i4ADwDNh1ahRUYJBS7ynoKLnA=; b=YsV6X95R+wgv8dfLHIYPTiEyDeRPGTDK6IGLth1rawGSP6FhogPCVZ0GRFxbB67cPZ 9u0s6rUXvmaYuZlaMuNJLkurZ9lywJSw9x+PrRhleqyEsD/SLsa5bEdkOCZ1lR1kycwM LrXoE3rNj2psCWn7b+9PdN+heT26Tx+zSEa+E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6XV6JVZa3idz96myL7i4ADwDNh1ahRUYJBS7ynoKLnA=; b=e7i5xj3FlQjFs96kAzBKm/bdEqBW9b3lfwt0f4LgPgM71IYs4myCLvoJfu3P0Ej1rs D3Sb2VT6k/lU0oBUHhUDGZmcvAKpjzRDQptNJeHef4V3Z2D8dTmPVPvHY40G7Wze8Utv TVEBftssQjhx4yGPkLr34p7hDbTM6t+WNatoi0CKYzSVysRB4UAp7HNviN+Qc83/gvSQ /ZON8WOwOE984NxcdV0d5Th4TgCgfNlArWPANAjr7I1G5hQSKeQY4i08J9xCSBY+sZbL LhhiITvQUQhnTlkGfw4FVA+kysblu+haXTAU1zl5NWsmmCAW9EmDAQ5QOFUqrGGumgo/ VI1g== X-Gm-Message-State: AGRZ1gLXpnv7BhYT4hvdIGfiPQ3yYF+P7hORnoMzIrCwt7dg9Rx+72// c5Usm08FjPM5jCSRVc+ypuRWssCigOqBX4uVhCi7og== X-Google-Smtp-Source: AJdET5eF42ZCBd91ht7dqmgydID8Yttn+gTZ0+deINSPrP8kyjWwPAiJd01qcPGMYyOIoxc/1C6JzHXYZPYxEVBEtBY= X-Received: by 2002:a9d:524c:: with SMTP id q12mr132367otg.164.1540930208309; Tue, 30 Oct 2018 13:10:08 -0700 (PDT) MIME-Version: 1.0 From: Adrian Hope-Bailie Date: Tue, 30 Oct 2018 22:09:56 +0200 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF , Hyperledger Quilt Mailing List Content-Type: multipart/alternative; boundary="000000000000b0bda3057977c5ae" Archived-At: Subject: [Ledger] AGENDA - Interledger Call - 17 October - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2018 20:10:11 -0000 --000000000000b0bda3057977c5ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, This week I hope we have some of the team from Hack Harvard available to give us a report back on the event and some of the cool stuff built on ILP. I also want to spend some time talking about some work we're doing on the connector architecture to make connectors easier to run in a high-availability environment. Any other topics, feel free to let me know ahead of time and I'll add them to the agenda. p.s. If you haven't seen it already check out Evan's latest post on ILP: https://medium.com/xpring/layer-3-is-for-interoperability-ca387fa5f7e2 Join from PC, Mac, Linux, iOS or Android: https://zoom.us/s/377506344 Or iPhone one-tap: US: +14086380968,,377506344# or +16468769923,,377506344# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 408 638 0968 <+1%20408%20638%200968> or +1 646 876 9923 <+1%20646%20876%209923> or +1 669 900 6833 <+1%20669%20900%206833> Meeting ID: 377 506 344 International numbers available: https://zoom.us/u/cbrUAzE3W --000000000000b0bda3057977c5ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

This week I hope we have some of the team from Hack Harvard avail= able to give us a report back on the event and some of the cool stuff built= on ILP.

I also want to spend some= time talking about some work we're doing on the connector architecture= to make connectors easier to run in a high-availability environment.

Any other topics, feel free to=C2=A0let= me know ahead of time and I'll add them to the agenda.

= p.s. If you haven't seen it already ch= eck out Evan's latest post on ILP:
https://m= edium.com/xpring/layer-3-is-for-interoperability-ca387fa5f7e2

Join from PC, Mac, Linux,= iOS or Android:=C2=A0https= ://zoom.us/s/377506344

Or iPhone one-tap:
<= div>=C2=A0=C2=A0=C2=A0=C2=A0US: +140863809= 68,,377506344# or +16468769923,,377506344#

Or Telephone:
=C2=A0=C2=A0=C2=A0=C2=A0Dial(fo= r higher quality, dial a number based on your current location):=C2=A0
=C2=A0=C2=A0= =C2=A0=C2=A0US:=C2=A0= +1 408 638 0968= =C2=A0or=C2=A0= +1 646 876 9923=C2=A0or=C2=A0+1 6= 69 900 6833=C2=A0
= =C2= =A0=C2=A0=C2=A0=C2=A0Meeting ID: 377 506 344
=C2=A0=C2=A0=C2=A0=C2=A0Internation= al numbers available:=C2=A0https://zoom.us/u/cbrUAzE= 3W
--000000000000b0bda3057977c5ae-- From nobody Wed Oct 31 02:44:20 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A210F126CB6 for ; Wed, 31 Oct 2018 02:44:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntYkk_EBBWCL for ; Wed, 31 Oct 2018 02:44:16 -0700 (PDT) Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D088128D0C for ; Wed, 31 Oct 2018 02:44:16 -0700 (PDT) Received: by mail-oi1-x232.google.com with SMTP id j202-v6so12603815oih.10 for ; Wed, 31 Oct 2018 02:44:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=MciMEvf0yKcs4+Gnzg7IUP/95uWnXrlt7qBWhJBYw6w=; b=KIz6ViGYKxnaXGlECkFR8PKo3kl+XAwHpElacOHQJcC4va2cYL31lWpAuXcfId70op LKLXktlyZ+RNJG3DwSgcX4WxLtgV9FyxCPkQXjT+6iOdielIUz/9kZbeQoOWoVBd7pQc jSfRT4kqqFa1Qtg0wA+/eu7wRR1l6sBPqokCw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=MciMEvf0yKcs4+Gnzg7IUP/95uWnXrlt7qBWhJBYw6w=; b=O0ev/XHLiTgc3MSz3eqPtEAobuCW4NXZ9BxugB3qT1fp7iodUGrFeQKeK1GS2icI+S s/Qjk6kZSGRj5Y4zNYq1B5nDVe0jmVl4IgnIcslImtAEbK0waYQINQa09cyD4/Zu0H5X c1uPxHXIq/1JF7dhoUhJ7Oo5K4NDZkVse0jL73Q8Ww8A0RfcdDh9ZK61oZkyal/P71A3 b21TNjMNVzKsqL183Lfa1GqnYnUbwex2SQnWzDLvv6u/b1lw7n4MNhp9cdoP63hWlq1W Eim8rnz8RdJVuq/Q1jPrQ22vO2UGUbFg/05OvxTHe6FW8Au/C7yKrjgFTE3mc1w7pzdg /I9g== X-Gm-Message-State: AGRZ1gKZpaikXjuVoPm8W0R1CVkurcefcVy93irMVJ+9/FsVRUXaN49H SqrW3fdLTn0x9t9+7lNeNq4r6Umx8L6X9fDkQDcE3g== X-Google-Smtp-Source: AJdET5euzFYx1yyIYP23vSuSItsG1COD76j1Ltuzo/E2MNHcPsULQSwZvsiBrvVpEviTRfYHAsUllPw9ymGuDUvxDlI= X-Received: by 2002:aca:4d46:: with SMTP id a67-v6mr1258918oib.205.1540979055519; Wed, 31 Oct 2018 02:44:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Hope-Bailie Date: Wed, 31 Oct 2018 11:44:03 +0200 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF , Hyperledger Quilt Mailing List Content-Type: multipart/mixed; boundary="000000000000362355057983251b" Archived-At: Subject: Re: [Ledger] AGENDA - Interledger Call - 17 October - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 09:44:19 -0000 --000000000000362355057983251b Content-Type: multipart/alternative; boundary="0000000000003623510579832519" --0000000000003623510579832519 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 30 Oct 2018 at 22:09, Adrian Hope-Bailie wrote: > Hi, > > This week I hope we have some of the team from Hack Harvard available to > give us a report back on the event and some of the cool stuff built on IL= P. > > I also want to spend some time talking about some work we're doing on the > connector architecture to make connectors easier to run in a > high-availability environment. > > Any other topics, feel free to let me know ahead of time and I'll add the= m > to the agenda. > > p.s. If you haven't seen it already check out Evan's latest post on ILP: > https://medium.com/xpring/layer-3-is-for-interoperability-ca387fa5f7e2 > > Join from PC, Mac, Linux, iOS or Android: https://zoom.us/s/377506344 > > > Or iPhone one-tap: > US: +14086380968,,377506344# or +16468769923,,377506344# > > Or Telephone: > Dial(for higher quality, dial a number based on your current > location): > US: +1 408 638 0968 <+1%20408%20638%200968> or +1 646 876 9923 > <+1%20646%20876%209923> or +1 669 900 6833 <+1%20669%20900%206833> > Meeting ID: 377 506 344 > International numbers available: https://zoom.us/u/cbrUAzE3W > > --0000000000003623510579832519 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


= On Tue, 30 Oct 2018 at 22:09, Adrian Hope-Bailie <adrian@hopebailie.com> wrote:
Hi,

This week I hope we have some of the team fr= om Hack Harvard available to give us a report back on the event and some of= the cool stuff built on ILP.

I al= so want to spend some time talking about some work we're doing on the c= onnector architecture to make connectors easier to run in a high-availabili= ty environment.

Any other topics, = feel free to=C2=A0let me know ahead of time and I'll add them to the ag= enda.

p.s. If you haven'= ;t seen it already check out Evan's latest post on ILP:https://medium.com/xpring/layer-3-is-for-inte= roperability-ca387fa5f7e2

Join from PC, Mac, Linux, iOS or Android:=C2=A0https://zoom.us/s/377506344

Or iPho= ne one-tap:
=C2=A0=C2=A0=C2=A0=C2=A0US: +14086380968,,377506344# or +16468769923,,3775= 06344#

= Or Telephone:
=C2=A0=C2=A0=C2=A0=C2=A0Dial(for higher quality, dial a number base= d on your current location):=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0US:=C2=A0<= a href=3D"tel:+1%20408%20638%200968" title=3D"tel:+1 408 638 0968" target= =3D"_blank">+1 408 638 0968=C2=A0or=C2=A0+1 646 876 9923<= /a>=C2=A0or=C2= =A0+1 669 900 6833=C2=A0
<= span style=3D"color:rgb(35,31,32)">=C2=A0=C2=A0=C2=A0=C2=A0Meeting ID: 377 506= 344
= =C2=A0=C2=A0=C2=A0=C2=A0International numbers available:=C2=A0https://zoom.us/u/cbrUAzE3W
--0000000000003623510579832519-- --000000000000362355057983251b Content-Type: text/calendar; charset="US-ASCII"; name="ilp-2018-10-31.ics" Content-Disposition: attachment; filename="ilp-2018-10-31.ics" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_jnwz4p4b0 QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpCRUdJTjpW RVZFTlQNCkRUU1RBTVA6MjAxODEwMTZUMDAwNDU0Wg0KVUlEOjIwMTgxMDMxQGludGVybGVkZ2Vy Lm9yZw0KRFRTVEFSVDoyMDE4MTAzMVQxNTAwMDBaDQpEVEVORDoyMDE4MTAzMVQxNjAwMDBaDQpT VU1NQVJZOkludGVybGVkZ2VyIENvbW11bml0eSBDYWxsDQpVUkw6aHR0cHMlM0ElMkYlMkZ6b29t LnVzJTJGcyUyRjM3NzUwNjM0NA0KREVTQ1JJUFRJT046Sm9pbiBmcm9tIFBDXCwgTWFjXCwgTGlu dXhcLCBpT1Mgb3IgQW5kcm9pZDogaHR0cHM6Ly96b29tLnVzL3MvMzc3NTA2MzQ0XG5cbk9yIGlQ aG9uZSBvbmUtdGFwOlxuICAgIFVTOiArMTQwODYzODA5NjhcLFwsMzc3NTA2MzQ0IyBvciArMTY0 Njg3Njk5MjNcLFwsMzc3NTA2MzQ0I1xuXG5PciBUZWxlcGhvbmU6XG4gICAgRGlhbChmb3IgaGln aGVyIHF1YWxpdHlcLCBkaWFsIGEgbnVtYmVyIGJhc2VkIG9uIHlvdXIgY3VycmVudCBsb2NhdGlv bik6IFxuICAgIFVTOiArMSA0MDggNjM4IDA5Njggb3IgKzEgNjQ2IDg3NiA5OTIzIG9yICsxIDY2 OSA5MDAgNjgzMyBcbiAgICBNZWV0aW5nIElEOiAzNzcgNTA2IDM0NFxuICAgIEludGVybmF0aW9u YWwgbnVtYmVycyBhdmFpbGFibGU6IGh0dHBzOi8vem9vbS51cy91L2NiclVBekUzV1xuDQpFTkQ6 VkVWRU5UDQpFTkQ6VkNBTEVOREFS --000000000000362355057983251b-- From nobody Wed Oct 31 11:50:37 2018 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE0A128BCC for ; Wed, 31 Oct 2018 11:50:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3O7b3QM4EilE for ; Wed, 31 Oct 2018 11:50:33 -0700 (PDT) Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C8391277C8 for ; Wed, 31 Oct 2018 11:50:33 -0700 (PDT) Received: by mail-ot1-x336.google.com with SMTP id k9so15523485otl.10 for ; Wed, 31 Oct 2018 11:50:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2Z0XQBnzJKfCogNy9BDy7/d/lcSnZ8dCugGjS3g8ZoM=; b=R5k03NQRPv+X41UPxpqjf9lk12SDqm+I3d/NjdtrsAlUfiCkjw55DYwc1g2cope3r7 8JqZwEztZK8KHzswJiQR0DVJLKVditQQEqUn6cRESf3iRQHUaIMS+/sFyEX+nkPZkB04 gAddN0q0hXj9PPD14Q/yADEvD3RzfwOsExcok= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2Z0XQBnzJKfCogNy9BDy7/d/lcSnZ8dCugGjS3g8ZoM=; b=jBcduACaq2GyGy9/yiZ82NS9YX2QL1rqPnkncmFomBNSL8ecp2j6vOlBU36WpohCvL KzmNqdSMKFom8IchD64vm6y2wDbnxykjmO2d5GkoCzB8/uSFIQ7oRiefaxWLOUtOP7iJ 8GpyJUsJeLWbbzjZly4cG/hOl8hStniiHUfVZnc9LudntWRZuwf5M4pT3mmxtuREEiJi 93lqrVPbftNurRJ+EBie+1Scy2rqQJkB72IpQTfJ2b+ASpHlThG96eTJH3oabrpzJ8cN zpVvKo7/GIWhDaPBDA9zp+TiDa3uVkd7pw6jcfFBKNcFWoLHGHaKYky8LShdXf/+MHnC QGSQ== X-Gm-Message-State: AGRZ1gIaJtevkqF4o1LuNbrWJsNHE8e+1OFCL9MTcBxAyKL6lfujNJhs n3UlMvPBZiaKWNe3n2dzQA5WUnUhBv7gR++mBU1ELA== X-Google-Smtp-Source: AJdET5dlzr8+lbT74L52YBxh74peiz3KRisUlPk1m8OfWXum1YEYDl3eUAOvOPCr0Bd+b0xXu+puE/N5NLBYQT60cc4= X-Received: by 2002:a9d:263:: with SMTP id 90mr1797951otb.164.1541011832185; Wed, 31 Oct 2018 11:50:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Hope-Bailie Date: Wed, 31 Oct 2018 20:50:20 +0200 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF , Hyperledger Quilt Mailing List Content-Type: multipart/alternative; boundary="000000000000da65a605798ac6dd" Archived-At: Subject: Re: [Ledger] AGENDA - Interledger Call - 17 October - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 18:50:35 -0000 --000000000000da65a605798ac6dd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here are the slides I used today. Recording is at: https://zoom.us/recording/share/sLhThBAx0XN3-0K_9bCOcQaKj5Lj8rJ4jTLVKiZmMW6= wIumekTziMw On Wed, 31 Oct 2018 at 11:44, Adrian Hope-Bailie wrote: > > > On Tue, 30 Oct 2018 at 22:09, Adrian Hope-Bailie > wrote: > >> Hi, >> >> This week I hope we have some of the team from Hack Harvard available to >> give us a report back on the event and some of the cool stuff built on I= LP. >> >> I also want to spend some time talking about some work we're doing on th= e >> connector architecture to make connectors easier to run in a >> high-availability environment. >> >> Any other topics, feel free to let me know ahead of time and I'll add >> them to the agenda. >> >> p.s. If you haven't seen it already check out Evan's latest post on ILP: >> https://medium.com/xpring/layer-3-is-for-interoperability-ca387fa5f7e2 >> >> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/s/377506344 >> >> >> Or iPhone one-tap: >> US: +14086380968,,377506344# or +16468769923,,377506344# >> >> Or Telephone: >> Dial(for higher quality, dial a number based on your current >> location): >> US: +1 408 638 0968 <+1%20408%20638%200968> or +1 646 876 9923 >> <+1%20646%20876%209923> or +1 669 900 6833 <+1%20669%20900%206833> >> Meeting ID: 377 506 344 >> International numbers available: https://zoom.us/u/cbrUAzE3W >> >> > --000000000000da65a605798ac6dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, 31 Oct 2018 at 11:= 44, Adrian Hope-Bailie <adrian@= hopebailie.com> wrote:


On Tu= e, 30 Oct 2018 at 22:09, Adrian Hope-Bailie <adrian@hopebailie.com> wrote:
H= i,

This week I hope we have some o= f the team from Hack Harvard available to give us a report back on the even= t and some of the cool stuff built on ILP.

I also want to spend some time talking about some work we're d= oing on the connector architecture to make connectors easier to run in a hi= gh-availability environment.

Any o= ther topics, feel free to=C2=A0let me know ahead of time and I'll add t= hem to the agenda.

p.s. If = you haven't seen it already check out Evan's latest post on ILP:
https://medium.com/xpring/layer-= 3-is-for-interoperability-ca387fa5f7e2

Join from PC, Mac, Linux, iOS or Android:=C2=A0<= /font>https://zoom.us/s/377506344<= /a>
--000000000000da65a605798ac6dd--