Send $1,000 across the XRP Ledger and it settles in four seconds, costing roughly $0.0001 in fees — fees that go to no validator, no miner, and no treasury. They are simply destroyed. That design reflects deliberate trade-offs that make the XRP Ledger (XRPL) work very differently from other major blockchains, and understanding how a blockchain transaction works at the protocol level makes those differences easier to grasp.
This is Part 1 of a four-part series on XRP and Ripple. Part 2 covers the SEC enforcement case and XRP's legal classification, Part 3 examines Ripple's institutional payment rails and the RLUSD stablecoin, and Part 4 explores on-ledger DeFi tools including the native DEX and AMM.
Origins: A Ledger Built to Replace Mining
The XRP Ledger launched in June 2012. Its three engineers — David Schwartz, Jed McCaleb, and Arthur Britto — admired Bitcoin's concept of a decentralized digital currency but wanted to eliminate energy-intensive proof-of-work mining. Shortly after the ledger launched, the three founders joined entrepreneur Chris Larsen and incorporated NewCoin in September 2012, which was quickly renamed OpenCoin and then Ripple.
At genesis, all 100 billion XRP were created at once — pre-mined in the terminology of the space. The founders gifted 80 billion XRP to the company; the founders retained 20 billion between them. An important distinction: Ripple the company and the XRPL the ledger are separate entities. The ledger is open-source and permissionless — any party can run a node or validator independently.
On September 24, 2020, an independent nonprofit called the XRPL Foundation was established with a $6.5 million donation from Coil, Ripple, and GateHub, to steward ledger development and validator diversity at arm's length from any single company.
The Consensus Protocol: Federated Agreement, Not Competition
The XRP Ledger uses the XRP Ledger Consensus Protocol (XLCP), sometimes called the Ripple Protocol Consensus Algorithm (RPCA). It belongs to a family called federated Byzantine agreement — neither proof-of-work nor proof-of-stake.
Validators do not compete. Instead, they share and compare proposed transaction sets in rounds. A set is accepted when a supermajority — 80% of a node's trusted validators — agree on it. This process completes approximately every 3–5 seconds, closing a new ledger version (the XRPL equivalent of a block) with deterministic finality. Once validated, a ledger is immediately final. There is no confirmation depth to wait for and no probabilistic reversal risk of the kind inherent in proof-of-work chains.
No mining occurs: there is no block reward, no coinbase transaction, and no token issuance — a deliberate contrast to Bitcoin's block subsidy, which halves every 210,000 blocks. Validators earn nothing financially for their participation; the incentive is reputational. Organizations run validators to support a network they depend on or believe in.
No staking exists either. XRP holders do not lock tokens to participate in consensus, and there are no staking rewards or slashing conditions.
Unique Node Lists: How the Network Decides Who to Trust
Each server operator on the XRPL configures a Unique Node List (UNL) — a set of validators whose votes that server will count during consensus. Validation messages from nodes outside a server's UNL are ignored.
By default, most XRPL servers rely on one or both of two published UNLs: one from the XRPL Foundation and one from Ripple. These lists are usually nearly identical and together form the default UNL (dUNL), which currently contains approximately 35 validators.
Understanding nodes and decentralisation in a federated model differs from proof-of-work systems. As of late 2025, the broader XRPL network has over 190 active validators, most operating independently of Ripple. Ripple itself now operates only one validator on the dUNL — under 3% of the trusted set — down from a larger share in earlier years. The XRPL Foundation publishes its own UNL independently, providing a second institutional anchor that reduces single-company control over the default trust configuration.
The safety threshold follows from the 80% supermajority rule: the protocol is safe as long as fewer than 20% of a node's trusted validators are faulty or colluding. Confirming an invalid transaction would require more than 80% of the dUNL to collude simultaneously.
Operators can choose their own UNL entirely, making validator trust user-defined rather than protocol-enforced. This gives participants meaningful choice but also means the security guarantees for any given server depend on the quality of the UNL it selects.
Supply: 100 Billion, Fixed at Birth
All 100 billion XRP were created at genesis in 2012. No new XRP can ever be created; the protocol has no issuance mechanism. The supply ceiling is permanently fixed.
XRP is mildly deflationary. Every submitted transaction permanently destroys a small amount of XRP — the transaction cost covered in the next section. As of January 2026, approximately 14.2 million XRP had been burned since launch — a tiny fraction of total supply, but the total can only ever decrease.
In December 2017, Ripple placed 55 billion XRP into time-locked, on-ledger escrow contracts enforced by ledger consensus rather than Ripple's discretion. Each month, one or more escrow contracts mature and release up to 1 billion XRP. Ripple typically uses only a fraction for institutional sales, ecosystem grants, or liquidity provision, returning the unused portion — often 700 to 900 million XRP — to new escrow contracts with updated expiry dates.
As of January 2026, approximately 65.78 billion XRP were outside escrow (including Ripple's operational holdings), with 34.185 billion XRP remaining in programmatic escrow. Standard circulating supply figures — which exclude tokens held directly by Ripple — were approximately 58–60 billion XRP by mid-2026.
The escrow structure makes Ripple's XRP releases publicly visible: monthly unlocks are on-ledger events that any observer can track, providing a degree of predictability not common in corporate token holdings.
Transaction Fees: Burned, Not Paid to Anyone
Every XRPL transaction destroys a small amount of XRP called the transaction cost. The minimum is 0.00001 XRP — or 10 drops, where 1 XRP equals 1,000,000 drops (so 1 drop equals 0.000001 XRP).
This destroyed XRP goes to no validator, no Ripple entity, and no treasury. It is irrevocably removed from supply. The sole purpose of the mechanism is anti-spam: without a cost, flooding the network with transactions would be free.
The cost scales dynamically with network load. During congestion, the open-ledger fee rises exponentially, making it economically infeasible to sustain a flood attack. This design is structurally opposite to proof-of-work fee markets, where fees are revenue for miners. On the XRPL, validators have no financial stake in fee collection.
Account Reserves: Why New Addresses Need Funding
The XRPL requires every account to hold a minimum XRP balance — the base reserve — to prevent spam accounts from expanding the ledger's state database indefinitely.
On December 2, 2024, XRPL validators voted to reduce the base reserve from 10 XRP to 1 XRP (a 90% reduction) via the network's fee-voting mechanism, confirmed in ledger 92508417. Simultaneously, the owner reserve — additional XRP required per object an account holds on the ledger (trust lines, DEX offers, escrow contracts) — fell from 2 XRP to 0.2 XRP per item.
A brand-new XRP address does not exist in ledger state until someone sends it at least 1 XRP. This explains the account-not-found error that users sometimes encounter when querying a newly generated, unfunded address.
The reserve reduction illustrates the XRPL's governance mechanism in practice: changes require a collective validator vote, not a company decision or a hard fork.
Decentralization: Ripple's Role and the Ledger's Independence
Critics of the XRPL cite the dUNL's small size (~35 validators) and Ripple's historical influence as centralization concerns. The Nakamoto coefficient — the minimum number of entities that must collude to disrupt the network — is lower than in large proof-of-work chains.
Ripple has progressively reduced its dUNL presence and states a policy of decommissioning one of its own validators for every two independent validators added. The XRPL has operated without a single core network disruption since 2012 — a 13-year track record. Critics counter that a federated model with a small trusted set provides less resistance to coordinated action than a globally distributed mining network with thousands of participants.
The distinction the community draws: Ripple the company builds products on the XRPL; XRPL the ledger is the open-source protocol. Any entity can operate a validator. Ripple holds no protocol-level veto over transaction validity.
Recent Protocol Upgrades (2024–2026)
AMM Amendment (March 22, 2024): The XLS-30 Automated Market Maker amendment integrated on-ledger liquidity pools with the existing decentralized exchange. Each asset pair can have one AMM; liquidity providers receive LP tokens proportional to their contribution. The full DEX and AMM mechanics are covered in Part 4 of this series.
Lower Reserves (December 2, 2024): The base account reserve dropped from 10 XRP to 1 XRP; the owner reserve dropped from 2 XRP to 0.2 XRP per object — significantly reducing the cost of on-chain participation.
Multi-Purpose Tokens (2025): A new fungible token primitive optimized for stablecoins and regulated assets, simpler and cheaper than the existing trust-line model.
Credentials Amendment (2025): On-chain tools for compliance authorization, enabling issuers to bind KYC and AML attestations to specific accounts.
Smart Escrow — WASM (targeting 2026): A WebAssembly-based programmability layer allowing custom conditions on escrow releases — the XRPL's first general-purpose programmability feature. In late devnet and audit phase as of mid-2026.
The XRPL's approach to programmability is incremental: the stated goal is not to become a general smart-contract platform but to add focused functionality to native primitives like escrow, lending, and the DEX.
Key Takeaways
- The XRP Ledger launched in June 2012 with all 100 billion XRP pre-mined at genesis; no new XRP can ever be created, and approximately 14.2 million have been permanently burned through transaction fees as of early 2026.
- Consensus is federated, not mined or staked: an 80% supermajority of a node's trusted validators must agree before a ledger version closes, with deterministic finality in 3–5 seconds and no reorg risk.
- Transaction fees are permanently destroyed — they flow to no validator, miner, or treasury — and scale dynamically with network load to deter spam.
- A minimum balance of 1 XRP (the base reserve, reduced 90% in December 2024) is required for an account to exist on the ledger; new, unfunded addresses are invisible to the state database.
- Ripple now operates only 1 of ~35 default-UNL validators; the XRPL Foundation publishes a second independent UNL; over 190 validators participate across the broader network.
