XRP News

How Bitcoin’s Limitations Inspired the XRP Ledger

If you want more content like this, please visit Ripple.com.


Top Cryptocurrency Hardware Wallets
Crypto Ledger (Check price) | KeepKey (Check price) | Ledger Nano (Check price) | Trezor (Check price)

https://www.buzzsprout.com/938995/4953512-how-bitcoin-s-limitations-inspired-the-xrp-ledger-coil-ceo-stefan-thomas-part-1-or-2.js?container_id=buzzsprout-player-4953512&player=small

The latest episode of Block Stars is the first of a two-part conversation between current Ripple CTO, David Schwartz and former Ripple CTO and current CEO of Coil, Stefan Thomas. David and Stefan first met at Ripple after Stefan was hired based on his previous work bringing Bitcoin to web browsers.

“My claim to fame was to be the browser crypto guy,” he tells David. Stefan wanted to help make Bitcoin more accessible and mainstream but the limitations of a pre-existing shared ledger meant that change was slow and experimentation impossible.

His chance to innovate with features like support for different currencies and faster confirmation times came when he joined Ripple and helped create the Interledger Protocol (ILP) and further develop the XRP Ledger. Though sometimes ideas didn’t work out, as revealed by a fascinating discussion about the decision to not build smart contract capability into the XRP Ledger.

“We wanted to optimize for security, performance and the basic functionality,” he recalls. “Smart contracts were an interesting opportunity for the future, but…the better architecture was not to have the code inside of the ledger itself.”  

Listen to part one of David and Stefan’s conversation now to hear how ILP has become that separate system for powering smart contracts, as well as more anecdotes and insights about the early days of Bitcoin and building the company, Ripple.

The post How Bitcoin’s Limitations Inspired the XRP Ledger appeared first on Ripple.





Please visit Ripple.com for more information.

Leave a Reply

Your email address will not be published. Required fields are marked *