Home » Ripple (XRP) » Ripple CTO Emeritus Reveals Why XRP Took BTC’s Code.

Here’s why XRP’s Ledger still supports the original elliptic curve that Bitcoin uses for signatures.

David Schwartz, Ripple’s CTO Emeritus and one of the original architects of the XRP Ledger, explained a deliberate early design choice this week.

Responding to a post about the ledger’s technical roots, he wrote: “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.”.

The discussion began with XRPL validator Vet, who noted that the ledger’s earliest code included helper functions and comments from Bitcoin’s original client, written by Satoshi Nakamoto and copied by early developer Jed McCaleb.

Did you know all of us on the XRP Ledger use design choices by Satoshi daily?15 years ago, the XRP Ledger started out using some Bitcoin code, including helper functions from the Bitcoin client that Satoshi wrote.Jed copied Satoshi's timekeeping code into the XRPL, including… pic.twitter.com/IZOaa4w0bz.

Most of that code was removed 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.

Industry observers note that two design choices remain. The XRP Ledger still supports the secp256k1 elliptic curve that Bitcoin uses for signatures (it also supports the newer Ed25519 curve, so not every account relies on secp256k1).

Separately, every XRPL address is still generated the Bitcoin way: the public key is hashed with SHA-256 and then with RIPEMD-160 before encoding. Those steps are used by every account on the network today.

Sources indicate that david Schwartz’s explanation is straightforward. In the network’s first years, the team preferred to reuse cryptographic primitives already proven in Bitcoin rather than introduce untested alternatives that crypto critics, particularly in the Bitcoin community, could attack as weaker or experimental.

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.

Using the same curve and address-generation method removed one potential line of criticism before it could be raised. Ripple CTO Emeritus has noted it is impossible to know whether different choices would actually have drawn that criticism; the point was to avoid having to defend the cryptography at all.

The early code sharing was limited and temporary. The consensus mechanism, transaction model, and most of the ledger’s architecture were built independently.

Industry observers note that it's hard to say. Obviously, we never got those criticisms. But it's hard to know if we would have. I'm not sure we would have come up with better ones had we made our own decisions anyway.

According to recent reports, what survived are two well-understood cryptographic building blocks that have remained secure and widely implemented for more than a decade. Later additions, including Ed25519 support, gave users and developers additional options without removing the original path.

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.

Discover DailyCoin’s top crypto news today:Project Helix Xbox Console Will Run PC Games: What It Means for Web3Banxa’s Shaun Heng Warns Rapid Fintech Growth Can Conceal Hidden Risks.

Get the biggest crypto stories, price insights, and DailyCoin exclusives in your inbox.

→ Read original article