From nobody Wed Nov 7 10:58:35 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 342B2130DCB for ; Wed, 7 Nov 2018 10:58:33 -0800 (PST) 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=[AC_DIV_BONANZA=0.001, 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 jZztTbk7aNDu for ; Wed, 7 Nov 2018 10:58:30 -0800 (PST) Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 7AB30130934 for ; Wed, 7 Nov 2018 10:58:30 -0800 (PST) Received: by mail-qk1-x731.google.com with SMTP id u68so22230567qkg.9 for ; Wed, 07 Nov 2018 10:58:30 -0800 (PST) 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=RR8aYgr2iKdplTMedqwu4GKO7WDlD0M4cQn70gOTrmQ=; b=igK7IRcYNWugOjIsJJsRvysauE6d8Mq5+OhXE73cUPMsIBfBLa/ouljXKKx+c9oUT5 g9Nf69FF2Q1oqU+vdcbf0N/Ohdd9aEK7Qu6ArEqkl5SiMZHcMhRRCX1e9p2hP4aiUIu1 jKRFrjIiQK54L1cjx+/YEI9wUteJBWSILY+H8= 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=RR8aYgr2iKdplTMedqwu4GKO7WDlD0M4cQn70gOTrmQ=; b=X+8DN7nw8izISzRYELLuYMnNLyJorRANaJerEg1Bi2+X33f+85sWmff/yNbM/gCWQ8 igDws0VYo4OcWXU74fml5buoL1BPlP4SHGz2wHY3KBz01+5+TnMOos7l0S5SCZ/Ra0ei tb04Fc5QzxiGG76LfKYmHJw18o7Q0qve6cKVBI7b/oXcv5nqXJsMcYdnpSQGKAwMafVS c7qu3mE4RRCmJxb2E1KNrIDz2hiDCmRUkaMLWNiECDeLMy0cp1q3NT3RRi/+S9Os1H2l QBo4DDe0LIEliQYOGTlF3+TSLdrW8OapKmcyjOpg78SPc2M8yvYP4Fku+ohJXWAbkru2 fYBw== X-Gm-Message-State: AGRZ1gJ0oy0tERK4iHeiL0WnMVV6DdggKi2oZASVigzNi5CqqgJmkRUH MnIsgQIfQ3CkLKfyIEeJS5c0Zg== X-Google-Smtp-Source: AJdET5ceqgTU+m91PnR7PQp5IusK5vLR/m537cxqWceNPOPXRWeZz17MYJyEjiifcuGHWQ+cWRPcbw== X-Received: by 2002:a37:af85:: with SMTP id y127mr1315893qke.352.1541617109264; Wed, 07 Nov 2018 10:58:29 -0800 (PST) Received: from arch (inet-64-112-177-6.bos.netblazr.com. [64.112.177.6]) by smtp.gmail.com with ESMTPSA id w81-v6sm1031508qka.87.2018.11.07.10.58.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Nov 2018 10:58:28 -0800 (PST) Date: Wed, 7 Nov 2018 13:58:27 -0500 From: Evan Schwartz To: Nathan Aw Cc: "=?utf-8?Q?public-interledger=40w3.org?=" , "=?utf-8?Q?ledger=40ietf.org?=" Message-ID: <1541607114.local-533ea95e-c371-v1.5.1-da141eaf@getmailspring.com> In-Reply-To: References: X-Mailer: Mailspring MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5be335d3_3ddf2058_20c9" 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: Wed, 07 Nov 2018 18:58:33 -0000 --5be335d3_3ddf2058_20c9 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Nathan, Do you need that whole transaction to happen atomically or for the balances to just end up that way? Also, do you need every party to maintain their own view of the state of the balances, or is there a single central party that could track them? On Nov 7 2018, at 9:03 am, Nathan Aw wrote: > > Hi Evan, > > I came up with a gridlock diagram/scenario to illustrate what I wish to hope to solve (or perhaps build) with interledger. Please refer to the gridlock diagram below. Since interledger is the routing layer/network, the gridlock mechanism is something that will be extremely relevant. This mechanism will be a game-changer -- any thoughts/inputs, please? > > > > Regards, > > Nathan Aw > https://www.linkedin.com/in/awnathan/ > https://datatracker.ietf.org/meeting/103/materials/slides-103-dinrg-decentralized-identity-00 > > > > > > > > > > > > > > > > > > > > On Sun, Oct 14, 2018 at 12:22 AM 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/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --5be335d3_3ddf2058_20c9 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Nathan,

Do you need that whole transaction to happe= n atomically or for the balances to just end up that way=3F Also, do you = need every party to maintain their own view of the state of the balances,= or is there a single central party that could track them=3F

On Nov 7 2018, at 9:03 am, Na= than Aw <nathan.mk.aw=40gmail.com> wrote:

Hi Evan,

I came up with a g= ridlock diagram/scenario to illustrate what I wish to hope to solve (or p= erhaps build) with interledger. Please refer to the gridlock diagram belo= w. Since interledger is the routing layer/network, the gridlock mechanism= is something that will be extremely relevant. This mechanism will be a g= ame-changer -- any thoughts/inputs, please=3F




On Sun, Oct 14, 20= 18 at 12:22 AM Evan Schwartz <evan=40ripple.com> wrote:<= /div>
The same construction can be used no mat= ter what the underlying assets are. They can be cryptocurrencies, fiat cu= rrencies, shares of stock or other divisible assets.

=
If you want to use this method for a swap you can send a =22pay= ment=22 from one of your accounts to another.

On = Sat, Oct 13, 2018, 8:27 AM Nathan Aw <nathan.mk.a= w=40gmail.com> 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 cros= s border payments with partial to full decentralization in mind. 

With the goal in mind, I like to understand techni= cally how can this paradigm be applied to achieve payment vs payment (pvp= ) with semi-trusted nodes such as clearinghouses, banks and individual pl= ayers=3F Applying the same concept of a crypto swap between ETH and BTC, = the same can be applied between SGD and HKD=3F  

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


On Sat, Oct 13, 2018 at 12:39 AM Nathan Aw <nathan.mk.aw=40gmail.com> 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 network= s for asset swaps to achieve cross border payments with partial to full d= ecentralization in mind. 

With the goal in = mind, I like to understand technically how can this paradigm be applied t= o achieve payment vs payment (pvp) with semi-trusted nodes such as cleari= nghouses, banks and individual players=3F Applying the same concept of a = crypto swap between ETH and BTC, the same can be applied between SGD and = HKD=3F  

Also, I hope to understand th= e models around how liquidity can be maintained between these nodes=3F

Thank you=21 

--5be335d3_3ddf2058_20c9-- From nobody Wed Nov 7 11:08:50 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 854C0130DCA for ; Wed, 7 Nov 2018 11:08:48 -0800 (PST) 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 btDMpy2YOFUN for ; Wed, 7 Nov 2018 11:08:47 -0800 (PST) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 31A7E130934 for ; Wed, 7 Nov 2018 11:08:47 -0800 (PST) Received: by mail-qk1-x72c.google.com with SMTP id e4so22318111qkh.6 for ; Wed, 07 Nov 2018 11:08:47 -0800 (PST) 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=orABGc0+mYr5d87fTDiDmeYKB213w40qsqETP7EjrDs=; b=aHP/aPwqnh/EOySeo9aXeOJu2KOlvddXOj1YsjZthrRaSeOCZjv51ff/B4c0hoXE78 X5E7vcP8RQMwKoMnWpDfG/D0RV95d1xtLf3JEZW5Oaq8k2m5iKVT30bEUlW4pfaA+1er 3t7wvfBW2ntUhCaO+HdBt5d78aNLeUXWJybCZ2cp/OrMAUxAscXCZNn2HfYHmNn7JSgp foyMsrI4VdAMI45THNsUb/dLMI+sK8Fp3R7uuqKI0ZEGDy+VWJHmtOpuvoDrK/4qNPAK chdYUGRf2oCkDOhOG0kGnpZum0tcGpSadDiekerwLgABDXjrKk1M8Zl1lto3vANYuFDs ND3w== 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=orABGc0+mYr5d87fTDiDmeYKB213w40qsqETP7EjrDs=; b=nDjy7djybzeThmAzR6Tm2368KOV+C4P0EqjqML9dG7YXGQAsnfvzDXEoyObKL8IrwC 4/p6WMa+zi13M4wvS+Bcz5+6aufAkPkNwspMvA600xeYVSzDtLi8N56aRxBu4b9J9Adm mGBGIMpziNPDnpGBfc4qePwh0P51yi6/LLWFEozrmFaKfx8O1TmvHvoNj2b1mU18OQfd m/COCJrTQX1M8rrB9Ig9MA1gqxm9XcK1Pjww/IrVi/e1AbVbxsCwHyELTZErZZn8nAvb bYyv/9hGSexAZABfQSEGQAfQIm5PPmMboienMOjRrB27oNxczeGIQ1dxpOGpYWvHuTIW mrfg== X-Gm-Message-State: AGRZ1gK0VNCmfwn1oH4XWb2Xgb5yvbynd4UzKpYkcMbsjCKVYKmvyq7J C0fF8V/HkiM8iOhVW+Qmf9v+fUfibuhCltMGHLo= X-Google-Smtp-Source: AJdET5crbIkcP9oTRIa4c3E0R4ApVipHU6gKvUoiP9/CIJWdmPSoI5WnATHaBjA4SIqV7GqO/pUJFwUqShDk7PeB7K4= X-Received: by 2002:a0c:fa46:: with SMTP id k6mr1520448qvo.36.1541617726420; Wed, 07 Nov 2018 11:08:46 -0800 (PST) MIME-Version: 1.0 References: <1541607114.local-533ea95e-c371-v1.5.1-da141eaf@getmailspring.com> In-Reply-To: <1541607114.local-533ea95e-c371-v1.5.1-da141eaf@getmailspring.com> From: David Nicol Date: Wed, 7 Nov 2018 13:08:11 -0600 Message-ID: To: Evan Schwartz Cc: Nathan Aw , Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="000000000000f6812e057a17d822" 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: Wed, 07 Nov 2018 19:08:49 -0000 --000000000000f6812e057a17d822 Content-Type: text/plain; charset="UTF-8" this may or may not assist, but I see multi-party transactions as something that should be set up by defining a light-weight entity to represent the transaction, which receives all the inputs (including proofs of completion, for contract payment proxy kinds of applications) and then disburses the inputs after it has everything. In the event that you don't want your funds tied up in multiple pending smart-contract objects that aren't going to get disbursed until well into the future, well that's where banking as such comes into play, isn't it. -- "I don't know about that, as it is outside of my area of expertise." -- competent specialized practitioners, all the time --000000000000f6812e057a17d822 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

this may or may not assist, but I see multi= -party transactions as something that should be set up by defining a light-= weight entity to represent the transaction, which receives all the inputs (= including proofs of completion, for contract payment proxy kinds of applica= tions) and then disburses the inputs after it has everything. In the event = that you don't want your funds tied up in multiple pending smart-contra= ct objects that aren't going to get disbursed until well into the futur= e, well that's where banking as such comes into play, isn't it.
=

--
"I don't know about= that, as it is outside of my area of expertise." -- competent special= ized practitioners, all the time
--000000000000f6812e057a17d822-- From nobody Mon Nov 12 11:18:46 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 55D741274D0 for ; Mon, 12 Nov 2018 11:18:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, 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, TVD_PH_BODY_ACCOUNTS_PRE=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 vRYwPg--XpRS for ; Mon, 12 Nov 2018 11:18:40 -0800 (PST) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 5E1E8130E4B for ; Mon, 12 Nov 2018 11:18:40 -0800 (PST) Received: by mail-qk1-x730.google.com with SMTP id e4so15306396qkh.6 for ; Mon, 12 Nov 2018 11:18:40 -0800 (PST) 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=zSyf8JnBUnaI6xNdkESq6dske2cYvzRKNA1er7qDIRQ=; b=cTjMxGxqeA5WWT8pmLThMKyAgB+I86/pOiqALnouaUQxH4hULY1LSSW+NDrgl0blaC Y9leEaJdIQ/EgIp0Cz4t/UsNohQOPuVUQ6jZn6n+6tzsQLVTezLuDsiI/11FKMaOmEmh 7HuGapcjm/pSamaH25rJAKBbD0MtUqdrkWuNI= 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=zSyf8JnBUnaI6xNdkESq6dske2cYvzRKNA1er7qDIRQ=; b=dycS5549obnfvxiAylCe5GvDxKE14204LR5z9qzsL9mGnOlMd/mKH2etLfXDXFrR/t wvj6hgsdZO6Jwa41SOLNiA9/BnmMPJY0SnEaGQH+D+4US0aG7KW6tBdkNbatBcTfvgNQ SFaQ3CHK+tMLvUbnn5YoFdLPJguAxqzx1x9C9NR7e9vAv3BnMBuY7htgYmfMhnIj22Gg cI8gNE6UcExTS8SjDqa7TEkbLW7Q6FkKQ1VhnK9aoYqLTP8hWdKGmxYHRD8yyLqIa0XV a1oxWOZt7K2UTNWJ0FLn4+C25880PiBXnU317qGMpUmXWHHx1fRJPEmL2DAaRtBqdMpp 9HCw== X-Gm-Message-State: AGRZ1gLSKdlB8rv/yF/nxkQoZyq8MASbzW8wIPA+FIYSnE2tzs+qz8be RrSiyl7/7sZ8H10+jIQkvB36LA== X-Google-Smtp-Source: AJdET5eAmmy+BZQAM7rCjaTYGWsSAfYel+HQLavPh7s1bGzGUiBDezHifFqvn13jfeli4C3zlwMKFA== X-Received: by 2002:ac8:27c8:: with SMTP id x8mr2123443qtx.352.1542050319240; Mon, 12 Nov 2018 11:18:39 -0800 (PST) Received: from arch (inet-64-112-177-6.bos.netblazr.com. [64.112.177.6]) by smtp.gmail.com with ESMTPSA id a9-v6sm8057507qtg.70.2018.11.12.11.18.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Nov 2018 11:18:38 -0800 (PST) Date: Mon, 12 Nov 2018 14:18:36 -0500 From: Evan Schwartz To: Nathan Aw Cc: "=?utf-8?Q?public-interledger=40w3.org?=" , "=?utf-8?Q?ledger=40ietf.org?=" Message-ID: <1542050036.local-813916f2-fc62-v1.5.2-31660462@getmailspring.com> In-Reply-To: References: X-Mailer: Mailspring MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5be9d20c_47087044_1d25" 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: Mon, 12 Nov 2018 19:18:46 -0000 --5be9d20c_47087044_1d25 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Nathan, This isn't a case we've specifically been designing around but streaming payments may help address it. If each of those payments is being streamed in some smaller increment, it would help avoid the gridlock issue. If one of the accounts runs out while the stream is in process, the sender could just keep retrying and the money would keep flowing as soon as the incoming balance had been credited to the account. Settlement times and mechanisms are determined on a bilateral basis, so pairs of connectors could choose to forward any amount they want on credit. Hope that helps, Evan On Nov 10 2018, at 10:35 am, Nathan Aw wrote: > > Hi Evan, > > Would like to quickly check with you on the questions below. Thanks! > > 1. Do you need that whole transaction to happen atomically or for the balances to just end up that way? > Nathan Aw: Probably the latter? Might be possible to have the different transactions to happen atomically? > > 2. Also, do you need every party to maintain their own view of the state of the balances, or is there a single central party that could track them? > Nathan Aw: Ideally no central party. the decentralized network should be and ideally be intelligent enough to identify these gridlocks and address them automatically, perhaps with the help of some configuration? > > > Are there any of such capabilities in the roadmap? > > Regards, > > Nathan Aw > On Thu, Nov 8, 2018 at 11:31 PM Nathan Aw wrote: > > Hi Evan, > > > > Have provided my response below. Thanks! > > > > 1. Do you need that whole transaction to happen atomically or for the balances to just end up that way? > > Nathan Aw: Probably the latter? Might be possible to have the different transactions to happen atomically? > > > > 2. Also, do you need every party to maintain their own view of the state of the balances, or is there a single central party that could track them? > > Nathan Aw: Ideally no central party. the decentralized network should be and ideally be intelligent enough to identify these gridlocks and address them automatically, perhaps with the help of some configuration? > > > > > > Are there any of such capabilities in the roadmap? > > > > Thank you. > > > > Regards, > > > > Nathan Aw > > https://sg.linkedin.com/in/awnathan > > > > https://datatracker.ietf.org/meeting/103/materials/slides-103-dinrg-decentralized-identity-01 > > https://www.hyperledger.org/news/speakersbureau > > https://erc725alliance.org/ > > https://www.hyperledger.org/community/technical-ambassador > > https://www.meetup.com/BlockChain-Dapps-Technology/events/254556114/ > > https://www.hyperledger.org/blog/2017/12/05/developer-showcase-series-nathan-aw-ntt-data > > https://www.meetup.com/Hyperledger-HK/events/248011521/ > > https://blockchain.ieee.org/newsletter/editorial-board > > > > > > > > On Thu, Nov 8, 2018 at 2:58 AM Evan Schwartz wrote: > > > Hi Nathan, > > > > > > Do you need that whole transaction to happen atomically or for the balances to just end up that way? Also, do you need every party to maintain their own view of the state of the balances, or is there a single central party that could track them? > > > On Nov 7 2018, at 9:03 am, Nathan Aw wrote: > > > > > > > > Hi Evan, > > > > > > > > I came up with a gridlock diagram/scenario to illustrate what I wish to hope to solve (or perhaps build) with interledger. Please refer to the gridlock diagram below. Since interledger is the routing layer/network, the gridlock mechanism is something that will be extremely relevant. This mechanism will be a game-changer -- any thoughts/inputs, please? > > > > > > > > > > > > > > > > Regards, > > > > > > > > Nathan Aw > > > > https://www.linkedin.com/in/awnathan/ > > > > https://datatracker.ietf.org/meeting/103/materials/slides-103-dinrg-decentralized-identity-00 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sun, Oct 14, 2018 at 12:22 AM 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/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --5be9d20c_47087044_1d25 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Nathan,

This isn't a case we've specifically been d= esigning around but streaming payments may help address it. If each of th= ose payments is being streamed in some smaller increment, it would help a= void the gridlock issue. If one of the accounts runs out while the stream= is in process, the sender could just keep retrying and the money would k= eep flowing as soon as the incoming balance had been credited to the acco= unt.

Settlement times and mechanisms are determined on a bi= lateral basis, so pairs of connectors could choose to forward any amount = they want on credit.

Hope that helps,
Evan
<= br>
On Nov 10 2018, at 10:3= 5 am, Nathan Aw <nathan.mk.aw=40gmail.com> wrote:
=
Hi Evan,

Would like to quickl= y check with you on the questions below. Thanks=21

1. Do you need that whole transaction to happen atomically or for= the balances to just end up that way=3F 
    Na= than Aw: Probably the latter=3F Might be possible to have the different t= ransactions to happen atomically=3F 

2= . Also, do you need every party to maintain their own view of the state o= f the balances, or is there a single central party that could track them=3F=
    Nathan Aw: Ideally no central party. = the decentralized network should be and ideally be intelligent enough to = identify these gridlocks and address them automatically,    &nb= sp;     perhaps with the help of some configuration=3F

Are there any of such capabilities in the roadmap=3F=  
<= div>

Regards,

Nathan Aw=
=

On Thu, Nov 8, 2018 at 11:31 P= M Nathan Aw <nathan.mk.aw=40gmail.com> wrote= :
Hi Evan,

Have provided my response below. Thanks=21

1. D= o you need that whole transaction to happen atomically or for the balance= s to just end up that way=3F 
    Nathan Aw: Pro= bably the latter=3F Might be possible to have the different transactions = to happen atomically=3F 

2. Also, do y= ou need every party to maintain their own view of the state of the balanc= es, or is there a single central party that could track them=3F
    Nathan Aw: Ideally no central party. the decent= ralized network should be and ideally be intelligent enough to identify t= hese gridlocks and address them automatically,       =   perhaps with the help of some configuration=3F

<= div>
On Thu, Nov 8, 2018 at 2:58 AM Evan Schwartz <eva= n=40ripple.com> wrote:
Hi Nathan,
Do you need that whole transaction to happen atomically or for = the balances to just end up that way=3F Also, do you need every party to = maintain their own view of the state of the balances, or is there a singl= e central party that could track them=3F

On Nov 7 2018, at = 9:03 am, Nathan Aw <nathan.mk.aw=40gmail.com&= gt; wrote:

Hi Evan,

I came up with a gridlock diagram/scenario to illustrat= e what I wish to hope to solve (or perhaps build) with interledger. Pleas= e refer to the gridlock diagram below. Since interledger is the routing l= ayer/network, the gridlock mechanism is something that will be extremely = relevant. This mechanism will be a game-changer -- any thoughts/inputs, p= lease=3F




On Sun, Oct 14, 2018 at 12:22 AM Evan Schwartz <evan=40ripple.com> wrote:
Th= e 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 m= ethod for a swap you can send a =22payment=22 from one of your accounts t= o another.

On Sat, Oct 13, 2018, 8:27 AM Nathan A= w <nathan.mk.aw=40gmail.com> wrote:
<= /div>
Hi all,

Second t= ry. Thank you. 

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

I am looking to leverage the Hashed-Timelock Agreem= ents (HTLAs) paradigm for establishing atomicity between different DLT ne= tworks for asset swaps to achieve cross border payments with partial to f= ull decentralization in mind. 

With the goa= l in mind, I like to understand technically how can this paradigm be appl= ied to achieve payment vs payment (pvp) with semi-trusted nodes such as c= learinghouses, banks and individual players=3F Applying the same concept = of a crypto swap between ETH and BTC, the same can be applied between SGD= and HKD=3F  

Also, I hope to understa= nd the models around how liquidity can be maintained between these nodes=3F=


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

<= /div>
I am a blockchain engineer based out of Singapore working at a = leading bank in ASEAN. 

I am looking to lev= erage the Hashed-Timelock Agreements (HTLAs) paradigm for establishing at= omicity between different DLT networks for asset swaps to achieve cross b= order payments with partial to full decentralization in mind. 
=

With the goal in mind, I like to understand technical= ly how can this paradigm be applied to achieve payment vs payment (pvp) w= ith semi-trusted nodes such as clearinghouses, banks and individual playe= rs=3F Applying the same concept of a crypto swap between ETH and BTC, the= same can be applied between SGD and HKD=3F  

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

Thank you=21&= nbsp;

=
--5be9d20c_47087044_1d25-- From nobody Tue Nov 13 14:31:03 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 C144A12F18C for ; Tue, 13 Nov 2018 14:30:55 -0800 (PST) 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 qe-JZyEDOV54 for ; Tue, 13 Nov 2018 14:30:52 -0800 (PST) Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 C7A99130DE7 for ; Tue, 13 Nov 2018 14:30:52 -0800 (PST) Received: by mail-ot1-x32b.google.com with SMTP id 40so12947604oth.4 for ; Tue, 13 Nov 2018 14:30:52 -0800 (PST) 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=VBudheJu9rt6benuh81t2nga29opyESkGIqzG5I2zp8=; b=Eo5hovgS4DLIrnYwokpRYGJexN3peHd95zV9z8zEexgOMgjZQED7gw1nkFTZgqesLj fGTgVlM+BHWfeH5yxlcs5/kPX3vkYZtt7k2cEfZ1OlbgPFKG0Nsi9yz7v9MtT6QHo4az ndJiWW0ZuhgiBmw3DwVqZL4mjhzmh6T7lxw14= 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=VBudheJu9rt6benuh81t2nga29opyESkGIqzG5I2zp8=; b=I+vqozkEa7rKV+fYNR0dyFCPuGVQ6xoYT5sEBWiUg+fPLe3tK9r/LUOcj6UamsIZ7w crTuVkaD6pApnmjiuvyIIoXK8kcK+nyyhpd7KLK2gqgQhsx2mrnOlnjgR6OFUIpnFTIS r5Ka5Ouh7SYGcDreE8unPy0qDoI0jA4efEBlnEyMwo4QWOAkpQicTE6YCyEY5i38FIQe pcjC5H2og8fj0H6S7XI1dMYrbbNpJnxYZCADiVkQH50VxdBQQl4O4rMGnBVBmw8+MJVQ snTA0n8A9+T//OkWrq5Kuk8QKIJ9me9U66OHeOOLP0FZ6K7LfT0DOva0f0qaIP/1nc4W ylRA== X-Gm-Message-State: AGRZ1gIxR1GX0HPnjp4CCBggpaNQbH+BpSl8O14TpRN1iADwUtzXjWtl oyH4FKZPQC0ndBk0z8wsS8xnaU271pPG7DNskbD6iQ== X-Google-Smtp-Source: AJdET5dsv2kQnYSMo8Lwe52uvtzrGATqCsSEU9GHFaoAaryhbnh+Lj02lwVh2Rc/2AfTBlc4kNUoaHS8TeBBKUYEUQo= X-Received: by 2002:a9d:b8e:: with SMTP id 14mr4023869oth.279.1542148251869; Tue, 13 Nov 2018 14:30:51 -0800 (PST) MIME-Version: 1.0 From: Adrian Hope-Bailie Date: Wed, 14 Nov 2018 00:30:38 +0200 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF , Hyperledger Quilt Mailing List Content-Type: multipart/mixed; boundary="000000000000beaa0a057a935e66" Archived-At: Subject: [Ledger] AGENDA - Interledger Call - 14 November - 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, 13 Nov 2018 22:30:56 -0000 --000000000000beaa0a057a935e66 Content-Type: multipart/alternative; boundary="000000000000beaa02057a935e64" --000000000000beaa02057a935e64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, I have a quick demo to show you of the load testing tools we've been working on for ILP components. We can also provide some feedback on the re-architecting we've been experimenting with around the connector and plugins. Some other topics I'd like to discuss as they're at risk of going stale on the issues list: - Licensing for RFCs and specifically patent licensing : https://github.com/interledger/rfcs/issues/473 - Documenting the PING protocol: https://github.com/interledger/rfcs/issues/433 - Documenting the routing protocol: https://github.com/interledger/rfcs/issues/432 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 --000000000000beaa02057a935e64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
<= br>
I have a quick demo to show you of the load testing tools we&= #39;ve been working on for ILP components.

We can = also provide some feedback on the re-architecting we've been experiment= ing with around the connector and plugins.

=
Some other topics I'd like to discuss as they're at risk of go= ing stale on the issues list:
=C2=A0- Licensing for R= FCs and specifically patent licensing :=C2=A0https://github.com/interledg= er/rfcs/issues/473
=C2=A0- Documenting the PING protocol:=C2= =A0https://github.com/interledger/rfcs/issues/433
=C2=A0- D= ocumenting the routing protocol:=C2=A0https://github.com/interledger/rfcs= /issues/432

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

Or iPhone one-tap:
=C2=A0=C2=A0=C2=A0=C2=A0US: +1408638096= 8,,377506344# or +16468769923,,377506344#

Or Telephone:
=
=C2=A0=C2=A0=C2=A0=C2=A0Dial(for= 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
--000000000000beaa02057a935e64-- --000000000000beaa0a057a935e66 Content-Type: text/calendar; charset="US-ASCII"; name="ilp-2018-11-14.ics" Content-Disposition: attachment; filename="ilp-2018-11-14.ics" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_jogb8nv80 QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpCRUdJTjpW RVZFTlQNCkRUU1RBTVA6MjAxODExMTRUMDAwNDU0Wg0KVUlEOjIwMTgxMTE0QGludGVybGVkZ2Vy Lm9yZw0KRFRTVEFSVDoyMDE4MTExNFQxNTAwMDBaDQpEVEVORDoyMDE4MTExNFQxNjAwMDBaDQpT VU1NQVJZOkludGVybGVkZ2VyIENvbW11bml0eSBDYWxsDQpVUkw6aHR0cHMlM0ElMkYlMkZ6b29t LnVzJTJGcyUyRjM3NzUwNjM0NA0KREVTQ1JJUFRJT046Sm9pbiBmcm9tIFBDXCwgTWFjXCwgTGlu dXhcLCBpT1Mgb3IgQW5kcm9pZDogaHR0cHM6Ly96b29tLnVzL3MvMzc3NTA2MzQ0XG5cbk9yIGlQ aG9uZSBvbmUtdGFwOlxuICAgIFVTOiArMTQwODYzODA5NjhcLFwsMzc3NTA2MzQ0IyBvciArMTY0 Njg3Njk5MjNcLFwsMzc3NTA2MzQ0I1xuXG5PciBUZWxlcGhvbmU6XG4gICAgRGlhbChmb3IgaGln aGVyIHF1YWxpdHlcLCBkaWFsIGEgbnVtYmVyIGJhc2VkIG9uIHlvdXIgY3VycmVudCBsb2NhdGlv bik6IFxuICAgIFVTOiArMSA0MDggNjM4IDA5Njggb3IgKzEgNjQ2IDg3NiA5OTIzIG9yICsxIDY2 OSA5MDAgNjgzMyBcbiAgICBNZWV0aW5nIElEOiAzNzcgNTA2IDM0NFxuICAgIEludGVybmF0aW9u YWwgbnVtYmVycyBhdmFpbGFibGU6IGh0dHBzOi8vem9vbS51cy91L2NiclVBekUzV1xuDQpFTkQ6 VkVWRU5UDQpFTkQ6VkNBTEVOREFS --000000000000beaa0a057a935e66-- From nobody Wed Nov 14 06:53:24 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 E5B26130E9E for ; Wed, 14 Nov 2018 06:53:22 -0800 (PST) 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 25TWzQWFkai3 for ; Wed, 14 Nov 2018 06:53:20 -0800 (PST) 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 8A677130E99 for ; Wed, 14 Nov 2018 06:53:20 -0800 (PST) Received: by mail-ot1-x336.google.com with SMTP id z33so14912190otz.11 for ; Wed, 14 Nov 2018 06:53:20 -0800 (PST) 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 :cc; bh=ev+v3pKdvWEkSWhkGqerdGCd5ciOcVJXMXIjzvQ0mXE=; b=PXqevids26ibPRr7taqAUxF0XZm8idYYWmwkO5SKyDgSDhyxS/uY6IxuQCVF9Oz4d2 TzWsq/Y7kc9aQRGL1P97/r2GWeI4Ct3e6Ck3RcYJIJQOlGHy2oxr53GWUHan4E3u6yyo 9DHH5O1ntZwO0uxm05mu/qo27Q3yVR0VDWO9w= 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=ev+v3pKdvWEkSWhkGqerdGCd5ciOcVJXMXIjzvQ0mXE=; b=XW24BmVVVTpsQ2lEwOnSm06ThYJ0xhWWZ9fhsmwMoUFSKWz8ukg36HSWdmOJHi9s/Q cjECKR07ySB4n0FJb1Jeo815JgyeDQUgv5dlRyDopNqlE9Kc0RGDcl0BDMC0U3768WcT ZSh+lSff9rkIGDSQ5kVV05N74+B9g6SjDVd7THbxHRtiIzq4Y+ppoibI3hmwNKMNzKQU T77+G86rR5ysgEI2Zttsl4QQtrHcRkPYhFyxsNgJ0LH6Ft1RCoLzppVW4+W/G1srwchA //cT7XezMofJvXKVfmbdu6rKwV+ebspKmm3lZNneoxi0zDXY37VvE6Ahtx9z0epqoUSY JScg== X-Gm-Message-State: AGRZ1gKfV7Rbkc0JBjW1IicjSXklTzhNt9MXVbJPFdvMtxv1pIGLhwf5 Dy0o50WSZKzJpBJ8BT6NG8diVyJW+Rm2uI2+SK8a4Q== X-Google-Smtp-Source: AJdET5eGqsL8N3dSt64AvSdS4ja9IvLc5ovYb/F8PmCjDqQxwwM/fClzOYncq7c6FxyIaBXTy1y+DDb3RplO4pSGHJk= X-Received: by 2002:a9d:48c6:: with SMTP id a6mr1281701otj.181.1542207199628; Wed, 14 Nov 2018 06:53:19 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Hope-Bailie Date: Wed, 14 Nov 2018 16:53:08 +0200 Message-ID: To: taiga.nakayama@gmail.com Cc: Interledger Community Group , Interledger Mailing List - IETF , Hyperledger Quilt Mailing List Content-Type: multipart/alternative; boundary="0000000000004e09f3057aa1182e" Archived-At: Subject: Re: [Ledger] AGENDA - Interledger Call - 14 November - 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, 14 Nov 2018 14:53:23 -0000 --0000000000004e09f3057aa1182e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Taiga, Actually I was hoping to find some people to help with this. We spent some time making notes on PING so I plan to put those into a doc and would appreciate some help reviewing them. Adrian On Wed, 14 Nov 2018 at 14:50, Taiga Nakayama wrote: > Hi all, > > > - Documenting the PING protocol: > https://github.com/interledger/rfcs/issues/433 > > - Documenting the routing protocol: > https://github.com/interledger/rfcs/issues/432 > > These are my issues, and sorry for having them left so long. > I'll fix around Route Broadcasting Protocol this weekend, > and then do Ping Protocol next. > I have to go on a business trip later this month (re:Invent), > so maybe, the start will be early next month. > > > 2018=E5=B9=B411=E6=9C=8814=E6=97=A5(=E6=B0=B4) 7:33 Adrian Hope-Bailie : > > > > Hi all, > > > > I have a quick demo to show you of the load testing tools we've been > working on for ILP components. > > > > We can also provide some feedback on the re-architecting we've been > experimenting with around the connector and plugins. > > > > Some other topics I'd like to discuss as they're at risk of going stale > on the issues list: > > - Licensing for RFCs and specifically patent licensing : > https://github.com/interledger/rfcs/issues/473 > > - Documenting the PING protocol: > https://github.com/interledger/rfcs/issues/433 > > - Documenting the routing protocol: > https://github.com/interledger/rfcs/issues/432 > > > > 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 or +1 646 876 9923 or +1 669 900 6833 > > Meeting ID: 377 506 344 > > International numbers available: https://zoom.us/u/cbrUAzE3W > --0000000000004e09f3057aa1182e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey Taiga,

Actually I was hoping to fin= d some people to help with this.
We spent some time making notes = on PING so I plan to put those into a doc and would appreciate some help re= viewing them.

Adrian

On Wed, 14 Nov 2018 at 14:50, Taiga Nakayama = <taiga.nakayama@gmail.com> wrote:
Hi all,

>=C2=A0 - Documenting the PING protocol: https://gi= thub.com/interledger/rfcs/issues/433
>=C2=A0 - Documenting the routing protocol: https:/= /github.com/interledger/rfcs/issues/432

These are my issues, and sorry for having them left so long.
I'll fix around Route Broadcasting Protocol this weekend,
and then do Ping Protocol next.
I have to go on a business trip later this month (re:Invent),
so maybe, the start will be early next month.


2018=E5=B9=B411=E6=9C=8814=E6=97=A5(=E6=B0=B4) 7:33 Adrian Hope-Bailie <= adrian@hopebaili= e.com>:
>
> Hi all,
>
> I have a quick demo to show you of the load testing tools we've be= en working on for ILP components.
>
> We can also provide some feedback on the re-architecting we've bee= n experimenting with around the connector and plugins.
>
> Some other topics I'd like to discuss as they're at risk of go= ing stale on the issues list:
>=C2=A0 - Licensing for RFCs and specifically patent licensing : https://github.com/interledger/rfcs/issues/473
>=C2=A0 - Documenting the PING protocol: https://gi= thub.com/interledger/rfcs/issues/433
>=C2=A0 - Documenting the routing protocol: https:/= /github.com/interledger/rfcs/issues/432
>
> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/s/37750634= 4
>
> Or iPhone one-tap:
>=C2=A0 =C2=A0 =C2=A0US: +14086380968,,377506344# or +16468769923,,37750= 6344#
>
> Or Telephone:
>=C2=A0 =C2=A0 =C2=A0Dial(for higher quality, dial a number based on you= r current location):
>=C2=A0 =C2=A0 =C2=A0US: +1 408 638 0968 or +1 646 876 9923 or +1 669 90= 0 6833
>=C2=A0 =C2=A0 =C2=A0Meeting ID: 377 506 344
>=C2=A0 =C2=A0 =C2=A0International numbers available: https://zoom.us/= u/cbrUAzE3W
--0000000000004e09f3057aa1182e-- From nobody Fri Nov 16 01:23:13 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 8CB4C124D68 for ; Fri, 16 Nov 2018 01:23:11 -0800 (PST) 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 qSFUcs7-ItwS for ; Fri, 16 Nov 2018 01:23:09 -0800 (PST) Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 90C9312896A for ; Fri, 16 Nov 2018 01:23:09 -0800 (PST) Received: by mail-oi1-x235.google.com with SMTP id g188-v6so19118631oif.8 for ; Fri, 16 Nov 2018 01:23:09 -0800 (PST) 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=NbC3JzQUnotwHz+OS3NC8XNjCy+CB64UHRkbEGaYrQE=; b=WIZntgfa1GtoMtPusvALo1T6Sa5NswYcAjQ65NISzAABLB1aDxwhlVohVtseYKCaky 3zQAZjm3FZZFtDoA85VFmjkyJiDdUB8N2/XEIFo7+6bl0xtIheGNanTm7gAFRISqX1dg dzn0aTXK3gn9bzU/U2jnfCqGUmXrwQy8Mfodw= 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=NbC3JzQUnotwHz+OS3NC8XNjCy+CB64UHRkbEGaYrQE=; b=hoBYSPSk6nbUMnQore1adoiGNkPOVNkLl8jhS31PVdoxrISW/28Sv8MEZGbwuMvdHC X6X0Rtcb2N8gbTOBKOhA0yW+MNNHypC0rLXl5lEYDzPVyYCMJFTkLXPSP2sFfOiuA3BV keqvE8imvRoO9vDjeL+ThdaDRVQ/9fM0tRchbrieW2UYusHge67DP2O8/7vw99PXWKvK bJgyCLm5AVgUXO+fsRcrm4/Fi/BZyuI+S8IFJ6dJMhELCIYcYkT9kEf0DOZKanvstH0J CdSFIgVP1VzFzOK9+PnRQ2+hUeP0dSPIIG1VhJ4kpBkXtyHyF8o3tuYjCLXCaEbSISfd cxDQ== X-Gm-Message-State: AGRZ1gIAl0YpRRld5l2qT0wqbq9M0nff+3MJit3YcqemKUQFVve2g2+F Z5Cz9CUkTO7g9nHUOPS+zGG7+fI26R343a7KHZOYmkUSpVjjKw== X-Google-Smtp-Source: AJdET5fUnkCa192CT2AFLkkXeZ9M62AfHzNuDkT8O0OYlvndNwGbgsiDqwkxWe+pTT7f2krgQH1aVmcPtZUuGfuv5zo= X-Received: by 2002:aca:af48:: with SMTP id y69mr509652oie.274.1542360187963; Fri, 16 Nov 2018 01:23:07 -0800 (PST) MIME-Version: 1.0 From: Adrian Hope-Bailie Date: Fri, 16 Nov 2018 11:22:56 +0200 Message-ID: To: Interledger Mailing List - IETF , Interledger Community Group , Hyperledger Quilt Mailing List Content-Type: multipart/alternative; boundary="0000000000001ebf18057ac4b7c3" Archived-At: Subject: [Ledger] ILP load testing tools 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, 16 Nov 2018 09:23:12 -0000 --0000000000001ebf18057ac4b7c3 Content-Type: text/plain; charset="UTF-8" Hi all, As discussed on the call this week I've been working on some load testing tools. They are still pretty rough but are good enough to start experimenting with. This repo has some scripts to generate the JMeter test plan, user config and connector configuration. https://github.com/adrianhopebailie/ilp-load-test This is the code for the JMeter plugin you'll need. https://github.com/adrianhopebailie/jmeter-ilp-samplers Once these are cleaned up they'll get pulled into the relevant project repos. Happy load testing! --0000000000001ebf18057ac4b7c3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

As discussed on the call this week I've been working on some load te= sting tools.
They are still pretty rough but are good enough to s= tart experimenting with.

This repo has some script= s to generate the JMeter test plan, user config and connector configuration= .

https://github.com/adrianhopebailie/ilp-load-test

This is the code for the JMeter plugin you'll nee= d.


Once these are cleaned up they'll ge= t pulled into the relevant project repos.

Happy lo= ad testing!
--0000000000001ebf18057ac4b7c3-- From nobody Tue Nov 27 20:36:46 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 36B9212F1A2 for ; Tue, 27 Nov 2018 20:36:44 -0800 (PST) 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 Au8KURLTFrCL for ; Tue, 27 Nov 2018 20:36:42 -0800 (PST) Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 2DB7112875B for ; Tue, 27 Nov 2018 20:36:42 -0800 (PST) Received: by mail-oi1-x22c.google.com with SMTP id u18so21460701oie.10 for ; Tue, 27 Nov 2018 20:36:42 -0800 (PST) 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=E0BGC1YgePvN8Uxx3Hu6SbG0iJNdwsnf9ojBkniuG78=; b=LfiQwoeztF18GN/W0gqICSXdwvWwWrzXSffZrXQ+Ts9Z7fu8tLy4G4fJdGv4fBvhIp j8/GMgo/J4Ky7/s6YhKqNf4udTA43UA5pvzxlKs1gf06IL6pYV4mJRtvyhWDs7Ux/WbT vm6ZeVRVJ484tzdaaGnoDQjR4//b3G7rLgPqw= 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=E0BGC1YgePvN8Uxx3Hu6SbG0iJNdwsnf9ojBkniuG78=; b=qm1aczYrBnaIeCNu9Rkdq/KI3l781nlE/MsGkQ9EJAD95sgByf+Ve1z9Ostq1lXuIU Nh7t5lzF5WiGBgtE/8I08XJI7cLdxP8zWo91Zgt0CDxUUxbs+c8AZr1EmHugIPQRso9N Dl7BfeogssWtLXCsivlmEJvCOLhRJh09n8DiDuaNDpGWgJZr2kUumaaSk4YiEtYlhg4Y s2OS61+xZ+/QIvwg2IbRakZ0D8axoTkJIHXC9+Ec6gtY/+iYRXMFc4MPiPdSnTTJ92VL b74ywG6v2W9XIPIgZ69dWvuAYod/rgiecWCPzoOsefO9VmGfb37/JgmtIH46ePZpE5OG uSuw== X-Gm-Message-State: AGRZ1gK/XP61Ihup/EUm1TZS9j2hJExUK9pKOZm2XnJXxejVUxVOgqZM 8NYLe9zA3xwOPxxfxakaLrypSGN0mCm0+jCbPaGWYw== X-Google-Smtp-Source: AJdET5fR/cIx5YG1biskExFklyuy8RIs8k81F9Dk4d5aYa7DPKoLm43j7oTtkDVcWpcEBC//By0AeWNmOJCg9cAk9Ww= X-Received: by 2002:aca:a648:: with SMTP id p69mr19084169oie.205.1543379801312; Tue, 27 Nov 2018 20:36:41 -0800 (PST) MIME-Version: 1.0 From: Adrian Hope-Bailie Date: Tue, 27 Nov 2018 20:36:29 -0800 Message-ID: To: Interledger Community Group , Hyperledger Quilt Mailing List , Interledger Mailing List - IETF Content-Type: multipart/mixed; boundary="000000000000d035d6057bb21c87" Archived-At: Subject: [Ledger] AGENDA - Interledger Call - 28 November - 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, 28 Nov 2018 04:36:44 -0000 --000000000000d035d6057bb21c87 Content-Type: multipart/alternative; boundary="000000000000d035d3057bb21c85" --000000000000d035d3057bb21c85 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, No specific topics to cover on the call this week. I can provide a brief update on the refactoring work and then it would be great to hear from anyone else that has updates on other components and services. Adrian 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 --000000000000d035d3057bb21c85 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

No specific topics to cover on = the call this week.

I can provide a brief update o= n the refactoring work and then it would be great to hear from anyone else = that has updates on other components and services.

Adrian

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

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

Or Telephone:
=C2=A0=C2=A0=C2=A0=C2=A0Dial(for 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<= font style=3D"font-family:sans-serif">+1 646 876 9923=C2=A0or=C2=A0+1 669 900 6833<= /a>=C2=A0
--000000000000d035d3057bb21c85-- --000000000000d035d6057bb21c87 Content-Type: text/calendar; charset="US-ASCII"; name="ilp-2018-11-28.ics" Content-Disposition: attachment; filename="ilp-2018-11-28.ics" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_jp0oh1ep0 QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpCRUdJTjpW RVZFTlQNCkRUU1RBTVA6MjAxODExMjdUMDAwNDU0Wg0KVUlEOjIwMTgxMTI4QGludGVybGVkZ2Vy Lm9yZw0KRFRTVEFSVDoyMDE4MTEyOFQxNTAwMDBaDQpEVEVORDoyMDE4MTEyOFQxNjAwMDBaDQpT VU1NQVJZOkludGVybGVkZ2VyIENvbW11bml0eSBDYWxsDQpVUkw6aHR0cHMlM0ElMkYlMkZ6b29t LnVzJTJGcyUyRjM3NzUwNjM0NA0KREVTQ1JJUFRJT046Sm9pbiBmcm9tIFBDXCwgTWFjXCwgTGlu dXhcLCBpT1Mgb3IgQW5kcm9pZDogaHR0cHM6Ly96b29tLnVzL3MvMzc3NTA2MzQ0XG5cbk9yIGlQ aG9uZSBvbmUtdGFwOlxuICAgIFVTOiArMTQwODYzODA5NjhcLFwsMzc3NTA2MzQ0IyBvciArMTY0 Njg3Njk5MjNcLFwsMzc3NTA2MzQ0I1xuXG5PciBUZWxlcGhvbmU6XG4gICAgRGlhbChmb3IgaGln aGVyIHF1YWxpdHlcLCBkaWFsIGEgbnVtYmVyIGJhc2VkIG9uIHlvdXIgY3VycmVudCBsb2NhdGlv bik6IFxuICAgIFVTOiArMSA0MDggNjM4IDA5Njggb3IgKzEgNjQ2IDg3NiA5OTIzIG9yICsxIDY2 OSA5MDAgNjgzMyBcbiAgICBNZWV0aW5nIElEOiAzNzcgNTA2IDM0NFxuICAgIEludGVybmF0aW9u YWwgbnVtYmVycyBhdmFpbGFibGU6IGh0dHBzOi8vem9vbS51cy91L2NiclVBekUzV1xuDQpFTkQ6 VkVWRU5UDQpFTkQ6VkNBTEVOREFS --000000000000d035d6057bb21c87--