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

Actually, I was mentally thinking about some of the new “block chain technology” projects that don’t rely other types of consensus processes. For example, the original HyperLedger and OpenLedger.

For bitcoin, litecoin, etc. Stefan and Evan have worked out an ILP compatible flow.
Bob Way
Integration Architect | Ripple
bob@ripple.com <mailto:ben@ripple.com> | ripple.com <http://ripple.com/>







> On Mar 1, 2016, at 5:41 PM, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
> 
> 
> 
> On 2 March 2016 at 00:21, Bob Way <bob@ripple.com <mailto: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 <mailto:ben@ripple.com> | ripple.com <http://ripple.com/>
> 
> 
> 
> 
> 
> 
> 
>> On Mar 1, 2016, at 11:45 AM, Evan Schwartz <evan@ripple.com <mailto: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
>>  <http://ripple.com/>
>