In this article4 sections
The XRP Ledger still carries two design choices that trace back to Bitcoin’s pseudonymous creator, Satoshi Nakamoto, according to Hussein Zangana, the XRP Ledger Foundation’s director of community, who posts as Vet. In a post on X dated November 16, 2026, Vet described the code inheritance from the earliest days of the ledger, which U.Today reported.
The XRP Ledger was started in 2011 by three engineers, David Schwartz, Jed McCaleb and Arthur Britto, who set out to build a faster, more payment-focused digital asset. Schwartz, now Ripple’s CTO emeritus, wrote the first line of code for the core ledger on November 11, 2011, roughly 15 years ago.
Also readXRP Ledger Bug-Fix Amendment Nears Oct. 23 Activation With 29 Votes
Key facts
- Vet said the XRP Ledger began by reusing Bitcoin client helper functions written by Satoshi Nakamoto, and McCaleb copied Satoshi’s timekeeping code into the XRPL, including one of his comments.
- Former Ripple engineering lead Nik Bougalis removed the last of that timekeeping code, and Satoshi’s comment, in December 2014; Vet said the original Satoshi code was gone from the ledger by the end of that year.
- Two Satoshi design choices remain: support for the secp256k1 signature curve, and address generation that applies SHA-256 followed by RIPEMD-160 to the public key.
- Vet noted that the XRPL also supports Ed25519, so not every user relies on secp256k1, though the SHA-256/RIPEMD-160 address method is used across all XRPL addresses.
What remains and why
Of the two surviving design choices, secp256k1 is the curve Bitcoin uses. Vet recalled Schwartz’s reasoning for adopting it: that using the same curve as Bitcoin would leave no doubt about the security. The ledger still supports it alongside Ed25519, so the choice is optional for users.
The second is the address derivation method. XRPL addresses are generated from public keys by hashing with SHA-256 and then RIPEMD-160, an approach inherited from Bitcoin that remains common to every XRPL address.
Also readXRP Ledger Proposes 4 Fixes to Close Restricted Token Gaps
Vet also touched on the maritime phrase Satoshi placed in the Bitcoin source code, often used to argue for redundant systems and attributed to the Bitcoin creator’s file: “Never go to sea with two chronometers; take one or three.” The XRP Ledger’s copy of the comment was removed with Bougalis’s cleanup in December 2014.
Asked why the timekeeping code and comment were cut, Vet said the code had become unused as new functions were introduced, so it was cleaned up—rather than removed for any security or functional reason.
Why it matters
The details matter mostly to XRPL developers and users who rely on its cryptography, because they show how much of the ledger’s original design came from Bitcoin and how much has been replaced over 15 years. It also clarifies what remains: the same signature curve Bitcoin uses, and a hashing sequence that determines every XRPL address. For builders, that inheritance means tooling and key-handling practices familiar from Bitcoin can carry over to XRPL, while the added Ed25519 support gives them another option.
What to watch
Vet’s post described the topic as one of many early-history details worth exploring, so further public commentary from XRPL Foundation figures or Bill—former Ripple engineers on the ledger’s original code—could follow. No protocol change is tied to the post, and the two design choices remain in place.
This article reports historical software details and is not financial advice. Crypto markets are volatile and uncertain, and nothing here should be read as a recommendation about XRP or any other asset.
Source: U.Today




