- From: Jan <jan.h.xie@gmail.com>
- Date: Wed, 10 Feb 2016 04:13:52 +0000
- To: Stefan Thomas <stefan@ripple.com>
- Cc: Interledger Community Group <public-interledger@w3.org>
Received on Wednesday, 10 February 2016 04:14:36 UTC
Cool, thanks for the great work! A suggestion: do you think it's good to put the whitepaper on github for easy collaboration? Jan On Wed, Feb 10, 2016 at 2:48 AM Stefan Thomas <stefan@ripple.com> wrote: > Hey Jan, > > You're totally right, good catch. Evan and I went in and fixed it - thanks > for reporting! > > - Stefan > > On Wed, Feb 3, 2016 at 5:50 AM, Jan <jan.h.xie@gmail.com> wrote: > >> Greetings, >> >> in "3.4.3 Preparation": >> >> > The sender p_1 first authorizes and sends the instruction to >> > prepare the first transfer b_1 on l_1 . p_1 then requests that >> > the first connector p_2 prepare b_2 on l_2 . The connector >> > p_2 is comfortable preparing b_2 because b_1 is prepared >> > and the funds have been escrowed by l_1 . Similarly, each >> > connector p_i prepares transfer b_{i-1} once it is notified that >> > l_i has prepared b_i and escrowed the corresponding funds. >> >> It looks like the last description is reversed, correction: >> >> > each connector p_i prepares transfer b_i once it is notified that >> > l_{i-1} has prepared b_{i-1} and ... >> >> Not sure if this is the place to post this .. >> >> Regards >> Jan >> > >
Received on Wednesday, 10 February 2016 04:14:36 UTC