Schwartz Says XRP Ledger Chose Bitcoin’s Cryptographic Options to Avoid Security Criticism
Early ledger code included Bitcoin client helpers, but the last timekeeping code and a Satoshi Nakamoto comment were removed in December 2014.

Ripple CTO Emeritus David Schwartz said early XRP Ledger developers chose cryptographic options used by Bitcoin (BTC) to avoid questions about whether their own choices were secure.
“We did things that way in the very early days because we didn't want to be potentially facing criticism that our choices for those core crypto functions were less secure than Bitcoin's,” Schwartz wrote Monday, Nov. 16. He said it is impossible to know whether they would have faced criticism if they had made different choices: “Obviously we never got those criticisms. But it's hard to know if we would have.”
XRP Ledger validator Vet described a separate connection to Bitcoin’s early code. In the ledger’s early days, McCaleb copied Bitcoin client code that handled timekeeping. Vet said Nik Bougalis removed the remaining timekeeping code and a comment by Satoshi Nakamoto in December 2014. “By the end of 2014, the original Satoshi code was gone,” Vet wrote.
The network retains two specific cryptographic choices Vet identified: the secp256k1 signature curve and deriving account IDs from public keys by applying SHA-256 followed by RIPEMD-160. The XRP Ledger supports secp256k1 and Ed25519, so secp256k1 is not its only key option.