The XRP Ledger's earliest developers leaned on Bitcoin's cryptographic building blocks because they wanted a security story that skeptics could not easily pick apart, according to David Schwartz, Ripple's chief technology officer emeritus.

In a November 16 post on X, Schwartz said the team deliberately chose cryptographic functions already proven in Bitcoin rather than rolling its own. The reasoning, he wrote, was to keep the new network's core security from becoming a target for critics, particularly Bitcoin supporters who might question whether XRPL had cut corners on cryptography.

The explanation came after a prominent XRPL validator who goes by Vet traced threads of Bitcoin's original software inside the ledger's early codebase. According to the validator, some of the helper functions in the first XRPL releases were lifted directly from Bitcoin, including timekeeping routines written by Satoshi Nakamoto. Even a comment line left by Bitcoin's pseudonymous creator turned up in the XRPL code, the validator said.

Schwartz framed the borrowing as a practical hedge. Bitcoin, by then, had become the reference point for how a cryptocurrency should handle cryptography, so adopting its approaches gave XRPL a defensible baseline at a moment when the project was still unproven. Picking different algorithms, he suggested, would have invited accusations that the new network was experimenting with weaker security.

He was candid about what he cannot prove. Schwartz acknowledged that he has no way of knowing whether the decision actually spared XRPL from criticism, since the objections he anticipated never materialized. Nor could he say with confidence that the team, left to its own devices, would have arrived at better cryptographic choices. That uncertainty, he indicated, is part of why established designs made sense during the ledger's formative period.

A paper trail from 2011

The technical lineage runs back to the project's origins. XRPL's foundation was laid in 2011 by Schwartz, Jed McCaleb and Arthur Britto, who set out to build a payments-oriented system that could address what they saw as Bitcoin's shortcomings in speed and energy use. Schwartz wrote the first lines of the ledger's core code on November 11, 2011, according to Hussein Zangana, community manager at the XRP Ledger Foundation.

McCaleb, an early developer who later went on to found Stellar, copied several helper functions from Bitcoin's original implementation, per the validator's account. The functions handled routine operations rather than the ledger's consensus mechanism, but their presence underscored how closely the two projects were entangled in those early months.

The borrowed code did not last. Nik Bougalis, then Ripple's engineering lead, deleted the final remnant of Nakamoto's timekeeping code in December 2014, the validator said, part of a broader cleanup as the old scaffolding became redundant and the codebase was streamlined.

Two design decisions with Bitcoin roots survived the purge, however:

Note: The two surviving elements concern signature verification and address derivation rather than consensus or transaction processing.

The secp256k1 curve remains available to XRPL users, though the network also accepts Ed25519 signatures, so no single scheme is mandatory. Address generation still follows Bitcoin's approach of hashing a public key with SHA-256 and then RIPEMD-160, a method applied across every address on the ledger.

Why the history matters now

The exchange is a reminder of how much of today's crypto infrastructure descends from a single 2008 design, and how early projects borrowed from it selectively. For XRPL, the takeaway is narrower: the ledger inherited Bitcoin's cryptographic primitives but not its architecture, and it has spent more than a decade differentiating itself.

For holders and developers, the practical implications are limited. The cryptographic choices under discussion are long settled, and the removed code has no bearing on how the network operates today. What the episode does illustrate is the path dependency in blockchain security: once a curve or a hashing scheme becomes standard, switching costs are high and the reputational benefit of sticking with a familiar design is real.

Schwartz has been unusually forthcoming about the early days of late. In a separate post, he defended having cut his personal XRP position by roughly 88%, from about 26 million tokens to three million, saying the sales followed a written plan agreed with his wife to trim exposure whenever crypto assets hit record highs. He said he also reduced Bitcoin holdings from about 1,500 BTC to one BTC and Ethereum from 40,000 ETH to six ETH, and that lawyers reviewed each arrangement at least 30 days in advance.

He rejected the inference that the sales signaled doubts about XRP's future, pointing to his continuing stake in Ripple as his largest remaining risk position. XRP traded near $0.956 on November 16, according to the same account, as the broader crypto market softened.

The technical disclosure, meanwhile, drew interest chiefly from developers and long-time followers of the ledger's history. It also left open the question Schwartz himself raised: whether the caution of 2011 produced a more secure network, or merely a more defensible one.

Once added, BigGo Finance appears first in Google Search Top Stories, so you get the broadest, most up-to-the-minute, and most comprehensive global financial news first.

More Related News