| Authors | David Schwartz; Noah Youngs; Arthur Britto |
|---|---|
| Year | 2014 |
| Project | Ripple / XRP Ledger (historical paper) |
| License | Not stated in the paper |
| Official Source | The Ripple Protocol Consensus Algorithm (PDF) |
This page is an educational summary of the linked paper, not a verbatim reproduction. CryptoGloss does not claim authorship of the original work; the paper remains the work of its authors and publisher.
What the 2014 paper describes
Published by Ripple Labs in 2014, The Ripple Protocol Consensus Algorithm describes a payment-ledger design built around collectively trusted subnetworks. Rather than requiring every server to know or vote with every participant, each server uses a validator list called a Unique Node List (UNL) when considering proposals. The paper frames the problem around correctness, agreement, and utility: rejecting invalid state changes, keeping honest servers aligned, and reaching an outcome with useful latency.
The paper is a historical description of an early protocol design. Its proofs rely on assumptions about faulty participants and the connections among servers’ UNLs; they are not a blanket guarantee for every possible configuration.
How the paper’s model works
In the paper’s multi-round process, a server gathers valid candidate transactions, shares its candidate set with peers on its UNL, and revises its proposal as it receives votes. Transactions that meet the paper’s round-specific thresholds can advance; the paper describes an 80% threshold in the final round. That figure belongs to the paper’s 2014 description, not a promise that every implementation parameter is permanent.
This is not “80% of everyone in the XRP ecosystem.” A server evaluates the validators in its own UNL, so the relationship between different lists matters. Current XRPL documentation also separates transaction-set consensus from the later validation of a resulting ledger version; a proposed transaction is not final merely because it appeared in a proposal.
UNL choice and the safety trade-off
Each server operator chooses which validators to trust. Operators can select a list themselves or use one or more signed recommended lists. The XRPL documentation describes the default server configuration as combining lists published by the XRPL Foundation and Ripple. This gives operators choice, while widely used recommendations can still influence which validators appear in many servers’ trusted sets.
Overlap is a safety condition, not a cosmetic preference: servers with poorly overlapping UNLs can disagree about which ledger is validated and risk a fork. Current XRPL documentation says an earlier 60% overlap belief was superseded by research showing that 90% may be required in the worst case. That constraint limits how independently operators can customize lists while preserving agreement. It is more accurate to describe a coordination and governance trade-off than to claim that the whitepaper alone proves the network either fully centralized or fully decentralized.
How to read the paper alongside today’s XRPL
The PDF itself warns that it does not reflect the current ledger consensus protocol or its analysis, says it is hosted for historical interest, and points readers to the 2018 analysis by Brad Chase and Ethan MacBrough. That analysis explains the protocol and derives conditions for safety and liveness. Current XRPL documentation describes a protocol that continues to evolve, including a validation stage distinct from transaction-set consensus and a Negative UNL mechanism that can adjust quorum calculations when validators are considered offline or malfunctioning. The Negative UNL has safeguards, including a minimum quorum relative to the configured list.
Use the 2014 paper to understand the original RPCA design and its assumptions. Use current XRPL documentation for present-day behavior, and consult the independent analysis for formal conditions and limits. Do not treat the old paper’s timing or threshold figures as current performance guarantees.
Social Media Sentiment
A small r/RippleTalk discussion dated February 8, 2026, titled “XRP Ledger Decentralization Debate Reignited”, shows a defensive tone in the visible replies: one commenter dismisses the debate, while another points to operator choice of UNLs and optional recommended lists. This is one low-engagement thread, not a representative survey or evidence about how the network is controlled; its claims are not used as technical proof.
Last updated: 2026-10
Related Terms
See Also
- The Stellar Consensus Protocol — another federated consensus design.
- Algorand: Scaling Byzantine Agreements for Cryptocurrencies — a different Byzantine agreement approach.
- Bitcoin: A Peer-to-Peer Electronic Cash System — a contrasting proof-of-work consensus model.
Sources
- Schwartz, D., Youngs, N., and Britto, A. (2014), The Ripple Protocol Consensus Algorithm — original design and its warning that the paper is historical, not current protocol guidance.
- XRPL Documentation, Consensus Protocol — current protocol goals, limitations, and the note that the protocol continues to evolve.
- XRPL Documentation, Consensus Structure — candidate transaction sets, consensus, and ledger validation.
- XRPL Documentation, Unique Node List (UNL) — operator choice, recommended-list publishers, and UNL overlap.
- XRPL Documentation, Negative UNL — the quorum adjustment mechanism for validators considered unreliable.
- Chase, B. and MacBrough, E. (2018), Analysis of the XRP Ledger Consensus Protocol — independent derivation of safety and liveness conditions.
- r/RippleTalk discussion, XRP Ledger Decentralization Debate Reignited (February 8, 2026) — the narrow community sample summarized above.