Compare versions
Version 1 → Version 5. Removed · Added. This shows the entry's text as it is written, including its formatting marks.
Version 1 · Version 5 · Version history
Side by side · Together
Version 1Version 5
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]

*Via Wikimedia Commons: [Xrp-symbol-black-128](https://commons.wikimedia.org/wiki/File:Xrp-symbol-black-128.png) by Alexavier Guzman, [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0).*
6 unchanged paragraphs
## 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
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]
3 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]
## The built-in exchange
The ledger has a decentralized exchange built into the protocol; its documentation says it "has possibly the world's oldest decentralized exchange," running since the ledger launched in 2012.[6] A trade is placed as an Offer, which the documentation calls "effectively a limit order to buy or sell a specific amount of one currency" for another, where the currency can be XRP or a token.[6] Offers are matched "starting with the best exchange rate first," and any unfilled remainder stays in the ledger as a passive Offer that later Offers or cross-currency payments can consume.[6] When two tokens are traded, the ledger can route the trade through XRP if that is cheaper than a direct token-to-token trade, a feature the documentation calls auto-bridging.[6]
The same page lists limits. Trades execute only when a ledger closes, about every 3 to 5 seconds, so the ledger is not suited to high-frequency trading, and it has no native market orders, stop orders or leverage trading.[6] The ledger holds no identity information on traders and cannot restrict who trades.[6]
## Changing the rules: amendments
Changes to how the ledger processes transactions are introduced as amendments, which validators vote on; no individual server can enable or disable one on its own.[7] Only the votes of trusted validators count.[7] An amendment is enabled only if it keeps the support of more than 80% of trusted validators for two weeks; if support falls to 80% or below, the two-week period restarts.[7] Votes are read on each flag ledger, which occurs every 256 ledgers, and once the amendment passes, it applies to transactions from two ledgers after that flag ledger.[7]
## Accounts and reserves
Every account on the ledger must hold a minimum amount of XRP, called a reserve, which the documentation says protects the shared global ledger from growing excessively large.[8] As of the documentation read on 17 November 2026, the base reserve on the main network is 1 XRP per address, and an owner reserve of 0.2 XRP applies to each object an account owns.[8] Reserved XRP cannot be sent to others, but the documentation notes that some of it can be recovered by deleting the account.[8] Unlike a transaction fee, the reserve is not described as destroyed.[8]
The reserve amounts and the transaction cost are not fixed in the protocol. They change through fee voting, in which validators whose preferred settings differ from the current ones attach a vote to their ledger validation, and each validator then takes the median of the votes from the validators it trusts.[8][10] Any change has to be approved by the consensus process.[8] The votes are cast around a flag ledger (the same every-256th-ledger point used for amendments), and new settings take effect two ledgers after the flag ledger if the resulting SetFee pseudo-transaction reaches consensus.[10]
## Tokens and XRP
The ledger can represent assets other than XRP as tokens; the documentation says that all assets other than XRP can be represented this way, and that anyone can issue them.[9] A token holder must first send a transaction indicating willingness to hold it, whereas the documentation states that all accounts can receive XRP from anyone by default.[9] XRP itself is not usually called a token, it has six decimal places, and no new XRP can be minted.[9] In the stablecoin model the documentation describes, the issuer holds assets off the ledger and issues tokens on the ledger that represent their value.[9] Tokens can be traded on the built-in exchange described above.[6][9]
## 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.
6. XRP Ledger documentation, "Decentralized Exchange", xrpl.org, https://xrpl.org/docs/concepts/tokens/decentralized-exchange (opened 16 November 2026).
7. XRP Ledger documentation, "Amendments", xrpl.org, https://xrpl.org/docs/concepts/networks-and-servers/amendments (opened 16 November 2026).
8. XRP Ledger documentation, "Reserves", xrpl.org, https://xrpl.org/docs/concepts/accounts/reserves (opened 17 November 2026).
9. XRP Ledger documentation, "Tokens", xrpl.org, https://xrpl.org/docs/concepts/tokens (opened 17 November 2026).
10. XRP Ledger documentation, "Fee Voting", xrpl.org, https://xrpl.org/docs/concepts/consensus-protocol/fee-voting (opened 17 November 2026).