The XRP Ledger’s earliest builders leaned on Bitcoin’s cryptographic constructing blocks as a result of they needed a safety story that skeptics couldn’t simply decide aside, in accordance to David Schwartz, Ripple’s chief know-how officer emeritus.
In a November 16 submit on X, Schwartz stated the crew intentionally selected cryptographic features already confirmed in Bitcoin fairly than rolling its personal. The reasoning, he wrote, was to hold the brand new community’s core safety from turning into a goal for critics, significantly Bitcoin supporters who would possibly query whether or not XRPL had reduce corners on cryptography.
The reason got here after a distinguished XRPL validator who goes by Vet traced threads of Bitcoin’s unique software program contained in the ledger’s early codebase. In accordance to the validator, among the helper features within the first XRPL releases have been lifted straight from Bitcoin, together with timekeeping routines written by Satoshi Nakamoto. Even a remark line left by Bitcoin’s pseudonymous creator turned up within the XRPL code, the validator stated.
Schwartz framed the borrowing as a sensible hedge. Bitcoin, by then, had develop into the reference level for a way a cryptocurrency ought to deal with cryptography, so adopting its approaches gave XRPL a defensible baseline at a second when the venture was nonetheless unproven. Choosing totally different algorithms, he urged, would have invited accusations that the brand new community was experimenting with weaker safety.
He was candid about what he can’t show. Schwartz acknowledged that he has no manner of understanding whether or not the choice really spared XRPL from criticism, for the reason that objections he anticipated by no means materialized. Nor may he say with confidence that the crew, left to its personal gadgets, would have arrived at higher cryptographic decisions. That uncertainty, he indicated, is a part of why established designs made sense in the course of the ledger’s formative interval.
A paper path from 2011
The technical lineage runs again to the venture’s origins. XRPL’s basis was laid in 2011 by Schwartz, Jed McCaleb and Arthur Britto, who set out to construct a payments-oriented system that would tackle what they noticed as Bitcoin’s shortcomings in pace and power use. Schwartz wrote the primary strains of the ledger’s core code on November 11, 2011, in accordance to Hussein Zangana, neighborhood supervisor on the XRP Ledger Basis.
McCaleb, an early developer who later went on to discovered Stellar, copied a number of helper features from Bitcoin’s unique implementation, per the validator’s account. The features dealt with routine operations fairly than the ledger’s consensus mechanism, however their presence underscored how carefully the 2 tasks have been entangled in these early months.
The borrowed code didn’t final. Nik Bougalis, then Ripple’s engineering lead, deleted the ultimate remnant of Nakamoto’s timekeeping code in December 2014, the validator stated, a part of a broader cleanup because the outdated scaffolding grew to become redundant and the codebase was streamlined.
Two design selections with Bitcoin roots survived the purge, nonetheless:
| Aspect | Origin | Standing on XRPL |
|---|---|---|
| secp256k1 signature curve | Bitcoin | Nonetheless supported, alongside Ed25519 |
| Tackle era by way of SHA-256 then RIPEMD-160 | Bitcoin | Normal for all ledger addresses |
| Timekeeping helper features | Bitcoin | Eliminated by December 2014 |
Observe: The 2 surviving parts concern signature verification and tackle derivation fairly than consensus or transaction processing.
The secp256k1 curve stays accessible to XRPL customers, although the community additionally accepts Ed25519 signatures, so no single scheme is obligatory. Tackle era nonetheless follows Bitcoin’s strategy of hashing a public key with SHA-256 after which RIPEMD-160, a way utilized throughout each tackle on the ledger.
Why the historical past issues now
The alternate is a reminder of how a lot of immediately’s crypto infrastructure descends from a single 2008 design, and the way early tasks borrowed from it selectively. For XRPL, the takeaway is narrower: the ledger inherited Bitcoin’s cryptographic primitives however not its structure, and it has spent greater than a decade differentiating itself.
For holders and builders, the sensible implications are restricted. The cryptographic decisions underneath dialogue are lengthy settled, and the eliminated code has no bearing on how the community operates immediately. What the episode does illustrate is the trail dependency in blockchain safety: as soon as a curve or a hashing scheme turns into customary, switching prices are excessive and the reputational advantage of sticking with a well-known design is actual.
Schwartz has been unusually forthcoming concerning the early days of late. In a separate submit, he defended having reduce his private XRP place by roughly 88%, from about 26 million tokens to three million, saying the gross sales adopted a written plan agreed along with his spouse to trim publicity at any time when crypto belongings hit file highs. He stated he additionally lowered Bitcoin holdings from about 1,500 BTC to one BTC and Ethereum from 40,000 ETH to six ETH, and that legal professionals reviewed every association at the very least 30 days prematurely.
He rejected the inference that the gross sales signaled doubts about XRP’s future, pointing to his persevering with stake in Ripple as his largest remaining threat place. XRP traded close to $0.956 on November 16, in accordance to the identical account, because the broader crypto market softened.
The technical disclosure, in the meantime, drew curiosity mainly from builders and long-time followers of the ledger’s historical past. It additionally left open the query Schwartz himself raised: whether or not the warning of 2011 produced a safer community, or merely a extra defensible one.












