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

Re: Blockchains and interledger (left-over question from the workshop)

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Wed, 2 Mar 2016 02:41:56 +0100
Message-ID: <CAKaEYhJMfu5OU=o_z5JGDdhsM8r62nyN8tKxhxV0qZrLkjoFNw@mail.gmail.com>
To: Bob Way <bob@ripple.com>
Cc: Evan Schwartz <evan@ripple.com>, Interledger Community Group <public-interledger@w3.org>
On 2 March 2016 at 00:21, Bob Way <bob@ripple.com> wrote:

> I’ll add that a blockchain base ledger can serve easily serve in the role
> of an ILP ledger. All that is needed is to implement the ILP escrowed
> transfer mechanism.
>
> I see that a key role of the Interledger Protocol will become connecting
> blockchain based asset management ledgers (stocks, bonds, commodities,
> cryptocurrencies) together, and also to connect them to existing
> non-blockchain based ledgers (banks, payment networks).
>

How many confirmations are needed for inter ledger transfers between two
block chains?

If I've understood block chains correctly, you can never be certain one
chain is the longest

How does ILP get around this?


> Bob Way
>
> Integration Architect | Ripple
> bob@ripple.com <ben@ripple.com> | ripple.com
>
>
>
>
>
>
>
> On Mar 1, 2016, at 11:45 AM, Evan Schwartz <evan@ripple.com> wrote:
>
> Do you see blockchain as a competing technology? If so, how does the value
>> proposition for interledger stack up against that for the blockchain?
>
>
> ILP is a protocol for transferring value securely across centralized and
> decentralized ledgers / blockchains. Interledger and blockchains operate at
> different levels: blockchains are databases, whereas interledger is an
> approach for connecting different databases. (I would argue that a number
> of the value propositions attributed to blockchains have been overstated
> beyond what they're actually good at, and many of them could be achieved in
> more efficient ways. But's that's a longer discussion)
>
> --
> Evan Schwartz | Software Architect | Ripple
> [image: ripple.com] <http://ripple.com/>
>
>
>
Received on Wednesday, 2 March 2016 01:42:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 01:42:28 UTC