David Schwartz, CTO Emeritus at Ripple and a chief architect of the XRP Ledger, addressed the origins of the ledger’s core cryptographic features this week, clarifying why the network adopted several technical elements familiar to early Bitcoin users.
Origins of XRPL’s Cryptographic Design
The discussion stemmed from comments made by XRPL validator Vet, who highlighted traces of Bitcoin’s original code in the XRP Ledger’s initial releases. These included not only cryptographic functions but also early comments and helper routines written by Bitcoin’s creator, Satoshi Nakamoto, and integrated by XRP Ledger co-founder Jed McCaleb.
According to Schwartz, the early Ripple team adopted these features intentionally. He stated that the primary goal was to avoid potential criticism regarding the security of XRPL’s cryptographic choices when compared to Bitcoin. “We did things that way in the very early days because we didn’t want to face potential criticism that our choices of those core crypto functions were less secure than bitcoin’s,” Schwartz explained.
We did things that way in the very early days because we didn’t want to face potential criticism that our choices of those core crypto functions were less secure than bitcoin’s.
Much of the shared code was phased out by the end of 2014. In December of that year, Nik Bougalis—a lead engineer at Ripple—removed the remaining timekeeping functions and the last Satoshi-originated comment from XRPL’s codebase.
Retained Elements from Bitcoin
Despite removing most direct code imports, two core cryptographic choices remain in the XRP Ledger to this day. Firstly, XRPL supports the secp256k1 elliptic curve for digital signatures, the same curve used by Bitcoin. Over time, support for Ed25519, a newer and widely respected elliptic curve, was introduced, providing users with an alternative for account creation and security.
Secondly, XRPL addresses continue to be generated using a method identical to Bitcoin: a public key is hashed first with SHA-256 and then with RIPEMD-160 before encoding. This process is still standard for all accounts active on the XRP Ledger today.
Schwartz emphasized that these decisions helped ease trust among early users and developers. By leveraging cryptographic tools already regarded as secure within the broader community, Ripple avoided having to defend its alternatives against scrutiny from Bitcoin proponents.
Mini dictionary: secp256k1 is an elliptic curve used in cryptography for creating digital signatures, most prominently utilized in Bitcoin and several other blockchain networks. RIPEMD-160 is a cryptographic hash function commonly combined with SHA-256 in blockchain address generation for enhanced security.
Independent Development and Lasting Features
Most of the XRP Ledger’s transaction model, architecture, and consensus mechanism were developed separately and do not derive from Bitcoin’s code or design. The overlap was limited to temporary early practices focused on cryptographic assurance.
“It is impossible to know whether different choices would have actually attracted that criticism,” Schwartz noted, stressing that the early team’s strategy was to entirely sidestep the debate by sticking with familiar and proven cryptographic standards.
The exchange is a small window into how the XRP Ledger was constructed: deliberately conservative on core cryptography in its first years, then gradually cleaned of borrowed code once the project had its footing. The two pieces are still in daily use by everyone on-chain.
Today, both secp256k1 and the Bitcoin-style address generation remain central to the XRP Ledger’s operation, while added features like Ed25519 have provided greater flexibility for network participants. These cryptographic decisions continue to offer a blend of compatibility and security for all users.






