- From: Stefan Thomas <stefan@ripple.com>
- Date: Tue, 9 Feb 2016 10:48:28 -0800
- To: Jan <jan.h.xie@gmail.com>
- Cc: Interledger Community Group <public-interledger@w3.org>
Received on Tuesday, 9 February 2016 18:49:25 UTC
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 Tuesday, 9 February 2016 18:49:25 UTC