Markets
BTC $55,755 -9.85% ETH $1,561 -10.22% BNB $511 -10.68% XRP $0.8716 -10.11% SOL $65.48 -9.94% LINK $8.07 -9.19% BTC $55,755 -9.85% ETH $1,561 -10.22% BNB $511 -10.68% XRP $0.8716 -10.11% SOL $65.48 -9.94% LINK $8.07 -9.19% TOTAL $1.96T BTC.D 57.2%

Altcoins

Why the XRP Ledger Still Signs Transactions the Bitcoin Way

David Schwartz says early developers borrowed Satoshi's cryptography to pre-empt any claim that their choices were weaker than Bitcoin's.

David Schwartz, Ripple’s chief technology officer emeritus and one of the XRP Ledger’s original architects, has explained why the network still leans on cryptographic choices inherited from Bitcoin more than a decade ago.

The exchange began with an observation from XRPL validator Vet, who noted that the ledger’s earliest code carried helper functions and comments lifted from Bitcoin’s original client, written by Satoshi Nakamoto and copied across by early developer Jed McCaleb. His framing was that users of the network lean on those choices daily without noticing. Schwartz replied that the team did things that way in the very early days because it did not want to face criticism that its core crypto functions were less secure than bitcoin’s.

Most of that borrowed code was gone by the end of 2014. In December of that year, then-engineering lead Nik Bougalis deleted the last of the timekeeping routines along with one of Satoshi’s comments. Two design decisions survived.

The first is elliptic-curve support. The XRP Ledger still accepts secp256k1, the curve Bitcoin uses for signatures, alongside the newer Ed25519 — so not every account depends on the older scheme. The second is address generation. Every XRPL address is still built the Bitcoin way: the public key is hashed with SHA-256, then with RIPEMD-160, before encoding. Those steps apply to every account on the network today.

The reasoning was defensive. In the network’s first years, the team preferred cryptographic primitives already proven in Bitcoin over untested alternatives that critics — particularly in the Bitcoin community — could attack as weak or experimental. Reusing the same curve and the same address method removed an argument before anyone could make it.

Schwartz conceded the counterfactual is unverifiable. The team never received those criticisms, and he said it is hard to know whether it would have. The point was to avoid having to defend the cryptography at all.

The code sharing was limited and temporary regardless. The consensus mechanism, the transaction model and most of the ledger’s architecture were built independently, which is why the surviving borrowings are narrow: a signature curve, a hashing sequence, and a set of routines that were deleted twelve years ago.

Share this article

Viber uses viber://forward?text= when the app is installed.