← XRP

Compare versions

Version 1 → Version 2. Removed · Added. This shows the entry's text as it is written, including its formatting marks.

Version 1 · Version 2 · Version history

Side by side · Together

Version 1Version 2
7 unchanged paragraphs
XRP is the native digital currency of the XRP Ledger, a decentralized blockchain in which servers agree on each batch of transactions through a consensus process among validators they choose to trust.[1][2]
XRP is the native digital currency of the XRP Ledger, a decentralized blockchain in which servers agree on each batch of transactions through a consensus process among validators they choose to trust.[1][2]
## Origins and supply
## Origins and supply
The XRP Ledger was built between 2011 and early 2012 by Jed McCaleb, Arthur Britto and David Schwartz.[1] According to the ledger's own documentation, 100 billion XRP existed at the time of its creation.[1] In September 2012 a decision was made to gift 80 billion XRP to Ripple, which was formed that month under the name OpenCoin Inc., in exchange for development work on the ledger.[1] In 2017 the company placed 55 billion XRP in escrow so that new supply entering circulation would be predictable.[1] The same page records that the company has regularly sold XRP and has used it to support markets and liquidity and to fund development of the ecosystem.[1]
The XRP Ledger was built between 2011 and early 2012 by Jed McCaleb, Arthur Britto and David Schwartz.[1] According to the ledger's own documentation, 100 billion XRP existed at the time of its creation.[1] In September 2012 a decision was made to gift 80 billion XRP to Ripple, which was formed that month under the name OpenCoin Inc., in exchange for development work on the ledger.[1] In 2017 the company placed 55 billion XRP in escrow so that new supply entering circulation would be predictable.[1] The same page records that the company has regularly sold XRP and has used it to support markets and liquidity and to fund development of the ecosystem.[1]
The documentation also dates the community's choice of a new "X" symbol for XRP to May 2018, and the assignment of the "XRP" trademark to the XRP Ledger Foundation to 2022.[1]
The documentation also dates the community's choice of a new "X" symbol for XRP to May 2018, and the assignment of the "XRP" trademark to the XRP Ledger Foundation to 2022.[1]
## Fees and the role of XRP on the ledger
## Fees and the role of XRP on the ledger
Every transaction on the ledger carries a fee paid in XRP. The fee is not paid to any party: the documentation states that "the XRP is irrevocably destroyed."[3] The exact amount written in a transaction's `Fee` field is destroyed, even if it is more than the current minimum, and the fee is charged once the transaction is included in a validated ledger, including a transaction that fails with a `tec` result code.[3] The cheapest non-free transaction, called the reference transaction, costs 10 drops before load scaling, where a drop is the ledger's smallest unit of XRP; under heavy load the minimum can rise above that figure.[3]
Every transaction on the ledger carries a fee paid in XRP. The fee is not paid to any party: the documentation states that "the XRP is irrevocably destroyed."[3] The exact amount written in a transaction's `Fee` field is destroyed, even if it is more than the current minimum, and the fee is charged once the transaction is included in a validated ledger, including a transaction that fails with a `tec` result code.[3] The cheapest non-free transaction, called the reference transaction, costs 10 drops before load scaling, where a drop is the ledger's smallest unit of XRP; under heavy load the minimum can rise above that figure.[3]
## How the ledger reaches agreement
## How the ledger reaches agreement
The XRP Ledger does not use mining. Each participant instead chooses a set of validators, servers configured to take part in consensus, and the list of validators a participant trusts is called its Unique Node List (UNL).[2] Validators are expected to behave honestly most of the time, and the chosen set should be one whose members are unlikely to collude to break the rules in the same way.[2] When validators disagree, they adjust their proposals toward those of the validators they trust and repeat this over several rounds until they agree.[2]
Each participant in the network chooses a set of validators, which are servers configured to take part in consensus, and the list of validators a participant trusts is called its Unique Node List (UNL).[2] Validators are expected to behave honestly most of the time, and the chosen set should be one whose members are unlikely to collude to break the rules in the same way.[2] When validators disagree, they adjust their proposals toward those of the validators they trust and repeat this over several rounds until they agree.[2]
5 unchanged paragraphs
The documentation states that "as long as fewer than 20% of trusted validators are faulty, consensus can continue unimpeded," and that if more than 20% but less than 80% are faulty, "the network stops making progress."[2]
The documentation states that "as long as fewer than 20% of trusted validators are faulty, consensus can continue unimpeded," and that if more than 20% but less than 80% are faulty, "the network stops making progress."[2]
The protocol was first described in a 2014 paper by David Schwartz, Noah Youngs and Arthur Britto, which presented it as a low-latency algorithm that tolerates Byzantine failures, meaning nodes that behave arbitrarily or maliciously, by relying on collectively trusted subnetworks.[4] That paper now carries a notice from its publisher that it does not reflect the current state of the protocol or its analysis and should not be used as a reference.[4]
The protocol was first described in a 2014 paper by David Schwartz, Noah Youngs and Arthur Britto, which presented it as a low-latency algorithm that tolerates Byzantine failures, meaning nodes that behave arbitrarily or maliciously, by relying on collectively trusted subnetworks.[4] That paper now carries a notice from its publisher that it does not reflect the current state of the protocol or its analysis and should not be used as a reference.[4]
A 2018 analysis by Brad Chase and Ethan MacBrough of Ripple Research, posted to arXiv on 20 February 2018, examined how much the validator lists of two participants must overlap for the network to stay consistent.[5] It reports that the 2014 paper's requirement was originally believed to be roughly 20 percent of the list, that an independent analysis later suggested more than 40 percent, and that the authors' own corrected bound for the original fault model lies between the two, at about 41 percent of the average list size.[5] They add that under a more general fault model, one commonly used in the research literature and not considered in the 2014 paper, the minimum overlap is roughly more than 90 percent.[5]
A 2018 analysis by Brad Chase and Ethan MacBrough of Ripple Research, posted to arXiv on 20 February 2018, examined how much the validator lists of two participants must overlap for the network to stay consistent.[5] It reports that the 2014 paper's requirement was originally believed to be roughly 20 percent of the list, that an independent analysis later suggested more than 40 percent, and that the authors' own corrected bound for the original fault model lies between the two, at about 41 percent of the average list size.[5] They add that under a more general fault model, one commonly used in the research literature and not considered in the 2014 paper, the minimum overlap is roughly more than 90 percent.[5]
## Sources
## Sources
1. XRP Ledger Foundation, "What is XRP?", xrpl.org, https://xrpl.org/docs/introduction/what-is-xrp (opened 16 November 2026). 2. XRP Ledger documentation, "Consensus Protocol", xrpl.org, https://xrpl.org/docs/concepts/consensus-protocol (opened 16 November 2026). 3. XRP Ledger documentation, "Transaction Cost", xrpl.org, https://xrpl.org/docs/concepts/transactions/transaction-cost (opened 16 November 2026). 4. David Schwartz, Noah Youngs and Arthur Britto, "The Ripple Protocol Consensus Algorithm", Ripple Labs Inc., 2014, https://ripple.com/files/ripple_consensus_whitepaper.pdf (opened 16 November 2026). 5. Brad Chase and Ethan MacBrough, "Analysis of the XRP Ledger Consensus Protocol", arXiv:1802.07242, 20 February 2018, https://arxiv.org/abs/1802.07242.
1. XRP Ledger Foundation, "What is XRP?", xrpl.org, https://xrpl.org/docs/introduction/what-is-xrp (opened 16 November 2026). 2. XRP Ledger documentation, "Consensus Protocol", xrpl.org, https://xrpl.org/docs/concepts/consensus-protocol (opened 16 November 2026). 3. XRP Ledger documentation, "Transaction Cost", xrpl.org, https://xrpl.org/docs/concepts/transactions/transaction-cost (opened 16 November 2026). 4. David Schwartz, Noah Youngs and Arthur Britto, "The Ripple Protocol Consensus Algorithm", Ripple Labs Inc., 2014, https://ripple.com/files/ripple_consensus_whitepaper.pdf (opened 16 November 2026). 5. Brad Chase and Ethan MacBrough, "Analysis of the XRP Ledger Consensus Protocol", arXiv:1802.07242, 20 February 2018, https://arxiv.org/abs/1802.07242.