W3C home > Mailing lists > Public > public-interledger@w3.org > January 2016

Re: Ripple protocol changes for Interledger support

From: Evan Schwartz <evan@ripple.com>
Date: Thu, 28 Jan 2016 10:46:39 -0800
Message-ID: <CAONA2jWyEKJ=B0L0hcf4Pm9fbHEMotFt2W7Ap3dGSHiUGVE_Hw@mail.gmail.com>
To: Steven Roose <stevenroose@gmail.com>
Cc: Interledger Community Group <public-interledger@w3.org>
The main requirement for a ledger to be ILP-capable is supporting
cryptographic escrow, which is done in RCL using Suspended Payments.

To quote nikb from the XRPChat forum
> Suspended payments, introduced with this commit:
> https://github.com/ripple/rippled/commit/3f0eacf5e70c43715a1e726d7a228d0ee307ee4e.
> Basically, a suspended payment "sequesters" the specified amount of XRP in
> its own ledger entry until either the suspended payment is completed (and
> the XRP is delivered to the destination) or canceled (and the XRP is
> returned to sender).
> I guess you could say it's similar to escrow, but this is done directly in
> the ledger, without the involvement of a third party.

The SusPay feature has been implemented and is available in the altnet but
not yet on the production network.

On Thu, Jan 28, 2016 at 7:19 AM, Steven Roose <stevenroose@gmail.com> wrote:

> Hi
> I know this is not entirely the right place for this question, but since I
> suppose a lot of Ripple Labs folks are in this mailing list, as well as
> there not being a Ripple-related mailing list and this question actually
> being somehow related to Interledger, I think I'm fine.
> In the Interledger Protocol presentation, Stefan Thomas and Evan Schwartz
> mention that in order for Ripple to work with Interledger, some
> modifications have to be made to the Ripple protocol.
> I would like to know exactly what modifications/additions will be made,
> some documentation would be awesome, and when they are planned to be
> available.
> Thanks and best regards
> Steven Roose

Evan Schwartz | Software Architect | Ripple
[image: ripple.com] <http://ripple.com>
Received on Thursday, 28 January 2016 18:47:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 28 January 2016 18:47:31 UTC