XRP Ledger: The Original Payment-Optimized Settlement Network
XRP Ledger (XRPL) is a purpose-built settlement network launched June 2012, predating Ethereum by three years. Instead of a general-purpose VM, XRPL ships a native DEX, the XLS-30 AMM (activated March 2024) and built-in token issuance, settled by the XRP Ledger Consensus Protocol — a federated BFT mechanism that closes ledgers every 4 seconds with deterministic finality. The native asset XRP also functions as the spam-prevention fee token.
XRPL is the answer to a single question: what does a blockchain look like if you optimize exclusively for cross-border value transfer, FX-style market making, and tokenized issuance — and refuse to bolt on a general smart-contract VM? The result is a network that closes a ledger every 4 seconds with full, irreversible finality (no probabilistic confirmations like Bitcoin's 60-minute window, no 7-day optimistic-rollup challenge period). Throughput sits at ~100 TPS in typical mainnet load and ~1,500 TPS at theoretical max, all without sharding or off-chain rollups. The consensus mechanism — XRP Ledger Consensus Protocol — is a federated BFT system in which each validator chooses its own Unique Node List (UNL); agreement is reached through repeated proposal-rounds rather than PoW mining or PoS slashing. The trade-off is explicit: XRPL is not the chain you pick to deploy a Solidity DEX or a Move-based perp engine. It is the chain you pick when finality, predictable sub-cent fees, native order-book liquidity and 14 years of zero unplanned downtime are the requirements. The 2024 XLS-30 AMM amendment added constant-product liquidity pools natively at the protocol layer, narrowing the historical gap with Stellar's Soroban contracts while preserving XRPL's settlement-first design.
About XRP Ledger
XRP Ledger went live on 2 June 2012, making it one of the oldest continuously operating distributed ledgers — older than Ethereum, BNB Chain and every L2. It was built by Jed McCaleb, Arthur Britto and David Schwartz to solve a specific problem: settling cross-border value in seconds rather than days, with deterministic finality rather than probabilistic mining-based confirmations. Unlike Bitcoin, which copied a payments narrative onto a PoW base layer, XRPL was engineered from genesis as a settlement substrate — native multi-currency support, on-ledger order books, issued-currency primitives (IOUs) and a fee mechanism designed to burn rather than reward miners.
The consensus model is the defining technical choice. XRPL uses the XRP Ledger Consensus Protocol, a federated Byzantine fault-tolerant system in which each validator publishes a Unique Node List (UNL) of validators it trusts, and consensus is reached when supermajority overlap exists across UNLs. There is no mining, no staking and no native slashing — validators are not paid in protocol rewards. The closed ledger interval is 4 seconds, and finality is also 4 seconds: once a ledger closes with supermajority validation it is irreversible, with no rollback window. This makes XRPL conceptually closer to Stellar's SCP than to Nakamoto-style chains.
On the VM layer XRPL is deliberately constrained. There is no EVM, no Move VM, no Cairo or Sealevel. Instead the protocol exposes a fixed set of transaction types (Payment, OfferCreate, TrustSet, AMMCreate, AMMDeposit, etc.) plus an on-ledger central limit order book that has run since 2012. The XLS-30 AMM amendment, activated on mainnet 22 March 2024, added constant-product automated market makers as a native primitive — the first protocol-level AMM in any major settlement chain. General smart contracts are scoped to sidechain experiments such as the XRPL EVM sidechain and the Hooks amendment, keeping the L1 itself lean and audit-stable.
Economically, XRP supply is fixed at 100 billion units, all created at genesis — there is no inflation, no block reward and no proof-of-work emission. Transaction fees are burned, slowly reducing supply over time, and a per-transaction minimum (currently a fraction of a cent) plus reserve requirements (currently 1 XRP base reserve, 0.2 XRP per object) act as anti-spam mechanisms rather than economic incentives. This design eliminates the validator-subsidy treadmill that PoS chains depend on, but it also means XRPL has no native protocol revenue distribution — value capture for XRP holders is purely a function of fee burn and demand for the settlement layer.
XRP Ledger technical parameters
XRPL's technical stack is the antithesis of a maximal smart-contract platform: a fixed, audited set of transaction types running on a federated BFT consensus, closed every 4 seconds with no reorgs and no MEV auction. The result is a network with one of the simplest threat models in the L1 universe — at the cost of permissionless on-chain programmability.
| Consensus | XRP Ledger Consensus Protocol (federated BFT via UNL) |
|---|---|
| VM | Native (no general smart contracts; XLS-30 AMM, hooks via sidechain) |
| Block time | 4 s |
| Finality | 4 s |
| TPS | 100 typical / 1.5k max |
| Gas token | XRP |
| Launched | 2012-06-02 |
| Token standard | Native XRP + Issued Currencies (IOUs) |
| Address | Base58 (r-prefixed, classic) / X-Address (with dest tag) |
Consensus mechanism
The XRP Ledger Consensus Protocol (XRP LCP) replaces miners and stakers with a federation of validators each maintaining a Unique Node List (UNL) — the set of other validators they listen to. In each ~4-second round, every validator proposes the set of transactions it considers valid; nodes iteratively adjust their proposal toward what the UNL supermajority (typically >=80%) agrees on. When proposals converge, the round ends, the ledger closes and a hash chain is committed. There is no slashing because there is no stake; safety comes from UNL overlap and the assumption that >20% Byzantine validators across the overlapping UNL would break liveness rather than allow a double-spend. The trade-off versus PoS chains like Solana or Aptos is direct: XRPL gives up permissionless validator entry (you must earn UNL inclusion) in exchange for deterministic 4-second finality and zero fork-choice ambiguity. There is no probabilistic confirmation curve — a closed ledger is final.
Performance context
100 TPS typical and 1,500 TPS theoretical max is not impressive next to Solana's 3,000+ TPS or Sui's 1,500 TPS DAG throughput. The relevant comparison is the latency-finality product. XRPL closes and finalizes in 4 seconds with no rollback — versus Bitcoin's 3,600s (60-minute six-confirmation rule), Ethereum's 768s (two-epoch economic finality) or Arbitrum/Optimism's 604,800s (7-day optimistic challenge window). For correspondent-banking, FX settlement and stablecoin remittance, XRPL's 4s deterministic finality is functionally more useful than a high-TPS chain whose individual transaction may still be reorged. The 14-year operational record — zero unplanned mainnet halts since genesis — is also load-bearing context that benchmark TPS numbers ignore.
XRP Ledger ecosystem map
XRPL's ecosystem is narrower than a general-purpose L1's but deeper in its native verticals: native DEX trading, issued-currency stablecoins (RLUSD, EURØP) and the new XLS-30 AMM. There is no Aave fork, no Uniswap deployment and no perps DEX, because there is no EVM. What exists runs at the protocol layer.
DEX
The native XRPL DEX — a fully on-ledger central limit order book — has operated since genesis in 2012, making it the oldest continuously running decentralized exchange in crypto. Orders are first-class protocol objects (OfferCreate transactions) rather than smart contracts, so matching happens at ledger-close time with no MEV auction or sandwich risk.
Infrastructure
XLS-30 AMM, activated on mainnet 22 March 2024, introduced constant-product liquidity pools as a native amendment. LPs deposit dual-asset pairs (e.g. XRP/RLUSD) and earn fees on every swap routed through the pool, with the pool's auction mechanism partially rebating discounted trading to the highest LP-token bidder.
Wallet
Xaman (formerly Xumm) is the canonical XRPL self-custody wallet, handling sign-and-broadcast for Payment, OfferCreate, TrustSet and AMM transactions via QR-coded request payloads. Hardware support spans Ledger and Trezor; Crossmark and Trust Wallet round out the consumer-facing options.
Bridge
Cross-chain access to XRPL goes through wrapped XRP on EVM chains (via Multichain successors, Wormhole and Axelar) and through emerging native federations such as the XRPL EVM sidechain, which exposes Solidity contracts while settling final state back to mainnet XRPL via a federated bridge.
Infrastructure
XRPL EVM Sidechain (Peersyst/Ripple) gives developers an EVM-equivalent execution environment with XRP as the gas token, sharing security with XRPL mainnet via a federated bridge — the official answer to XRPL's lack of native smart contracts. Hooks (XLS-49) is a parallel approach exposing lightweight WebAssembly logic attached to accounts.
DEX
Sologenic and XPMarket build trading and tokenization UIs on top of XRPL's native order book and AMM, focusing on issued-currency markets (tokenized equities, RWAs, RLUSD pairs) rather than yield-farming primitives common on EVM L1s.
XRP Ledger vs peers
XRPL's only direct peer in the settlement-network category is Stellar (XLM). Both descend from the same intellectual lineage — Jed McCaleb co-founded both — and both reject general smart contracts as the L1's primary abstraction. The differences are sharper than the surface suggests.
| Chain | Block | Finality | TPS | TVL |
|---|---|---|---|---|
| xrpcurrent | 4 s | 4 s | 100 | $0.00 |
| Stellar | 5 s | 5 s | 100 | $206.47M |
Comparison insights
- Consensus design: XRPL uses the XRP Ledger Consensus Protocol (federated BFT via per-validator UNL); Stellar uses SCP (Stellar Consensus Protocol — Federated Byzantine Agreement via quorum slices). Both are federated, both reject PoW/PoS, but Stellar's quorum-slice model is more flexible at the cost of more complex safety analysis. XRPL's UNL model is simpler to reason about and operate.
- Latency and finality: XRPL closes ledgers every 4 seconds with 4-second finality; Stellar closes every 5 seconds with 5-second finality. The 20% latency edge for XRPL is real but small; both are deterministic-finality networks, an order of magnitude faster than Bitcoin's 3,600s and far ahead of Ethereum's 768s.
- Throughput: XRPL handles ~100 TPS typical and ~1,500 TPS theoretical; Stellar matches the 100 TPS typical figure but claims 5,000 TPS theoretical max — 3.3x XRPL's headroom. For current settlement volumes neither chain is throughput-constrained, but Stellar has more scaling rope.
- Programmability: This is where the chains diverge most. Stellar shipped Soroban — a WASM-based smart-contract VM — in 2024, giving it first-class general programmability while preserving fast finality. XRPL keeps general contracts off the mainnet, routing them through sidechains (XRPL EVM Sidechain) and Hooks. If you need on-L1 Turing-complete logic, Stellar wins; if you want a maximally simple settlement layer, XRPL wins.
- Ecosystem depth: Stellar reports ~$206M TVL via DefiLlama (Soroban-based DeFi is still early), while XRPL's DefiLlama TVL is not consistently tracked — most XRPL liquidity sits inside the native order book and XLS-30 AMM, which TVL aggregators historically under-counted. Both ecosystems are dwarfed by general-purpose L1s; the value proposition is settlement reliability, not DeFi yield surface.
XRP Ledger timeline
XRP Ledger went live on 2 June 2012, launched by Jed McCaleb, Arthur Britto and David Schwartz with a fixed pre-mined supply of 100 billion XRP — no mining, no PoW emission. Ripple Labs (then OpenCoin) received a large initial allocation to fund development and enterprise distribution, a decision that has shaped XRP's centralization debate ever since. The early years saw XRPL adopted by enterprise payment corridors (RippleNet, On-Demand Liquidity) rather than retail crypto users. In December 2020 the SEC sued Ripple Labs alleging that XRP sales constituted unregistered securities offerings; in July 2023 Judge Analisa Torres ruled that programmatic exchange sales of XRP were not securities transactions, a partial-win that re-opened US exchange listings. The litigation finally concluded in 2024 with a $125M civil penalty. Operationally, XRPL has run continuously since genesis with no unplanned mainnet halts — a 14-year uptime record matched only by Bitcoin and exceeded by no smart-contract chain. The 22 March 2024 XLS-30 AMM amendment was the most significant protocol upgrade in XRPL's history, adding native constant-product AMM pools as first-class ledger objects without breaking backwards compatibility for existing DEX traffic. Subsequent amendments (Clawback, DID, NFT XLS-20) extended tokenization primitives. The XRPL EVM Sidechain (Peersyst/Ripple) and the Hooks proposal (XLS-49) represent the network's parallel strategy for smart-contract capability — keeping the L1 lean while exposing programmability through bridged execution environments. Notably, XRPL has had no consensus-level hacks, no validator collusion incidents and no bridge-style fund losses on the base ledger, though sidechain and wrapped-XRP bridges remain external risk surfaces that operate under different security assumptions.
- 2012-06-02launchXRP Ledger genesis
- 2024-03-22upgradeXLS-30 AMM amendment activated on mainnet
Developer reference
Official documentation lives at https://xrpl.org/docs with full API references for rippled (the reference C++ node), the WebSocket JSON-RPC interface and Clio (the read-only API server). The canonical public RPC endpoint is https://s1.ripple.com:51234 (JSON-RPC) and wss://s1.ripple.com (WebSocket); a load-balanced public cluster also runs at s2.ripple.com. Block explorers: xrpscan.com (community, full transaction graph) and bithomp.com (account-focused). Address format is dual: classic Base58 r-prefixed addresses (e.g. rEXAMPLE...) and X-Addresses which encode the destination tag in a single string (X-prefixed) — exchanges should prefer X-Addresses to eliminate the destination-tag user-error class. SDKs: xrpl.js (TypeScript/JavaScript, official), xrpl-py (Python, official), xrpl4j (Java) and xrpl.swift cover the major language stacks. Wallets supporting XRPL include Xaman (Xumm) as the flagship mobile sign-and-broadcast app, plus Ledger, Trezor, Trust Wallet and Crossmark.
Assets swappable on XRP Ledger
Grouped by category. Click any asset to open its swap page for a live quote.
Majors
1 assets
XRP Ledger settle-time comparison
Shorter bars mean faster confirmations. Real settle time also depends on network congestion — figures are indicative.
XRP Ledger asset coverage comparison
Longer bars mean more assets are swappable on that chain.
Popular swap routes involving XRP Ledger
Routes below reflect actual user preference. Click to jump straight to the swap page.
XRP Ledger FAQ
01Is XRPL decentralized?
XRPL uses federated BFT consensus with a Unique Node List (UNL) model — validators are not permissioned by a foundation but UNL membership is curated by node operators, with Ripple, XRPL Foundation and major exchanges publishing recommended lists. There are ~150+ active validators globally and the default UNL has dozens of independent operators. It is more decentralized than commonly assumed but less permissionless than PoS chains like Ethereum or Solana, where any staker can become a validator.
02What is XRP Ledger's finality time?
4 seconds. XRPL closes a new ledger roughly every 4 seconds, and once a ledger receives supermajority validation (~80% UNL agreement) it is final — irreversible, with no rollback window. This is deterministic finality, not probabilistic like Bitcoin's six-confirmation rule. It is one of the fastest finality figures in production among non-PoH chains.
03Does XRPL support smart contracts?
Not on the L1. XRPL ships native primitives (Payment, OfferCreate, TrustSet, AMMCreate via XLS-30) but no general-purpose VM. For Turing-complete logic, developers use the XRPL EVM Sidechain (Solidity, federated bridge back to mainnet) or the Hooks amendment (XLS-49, lightweight WebAssembly attached to accounts). This is a deliberate design choice — keeping the settlement layer simple and audit-stable.
04How is XRP issuance handled? Is there inflation?
No inflation. XRP supply is fixed at 100 billion units, all created at genesis on 2 June 2012. There is no block reward, no staking emission and no mining. Transaction fees are burned (not paid to validators), which makes XRP marginally deflationary over time. Validators run nodes without protocol payment — their incentive is the utility of the network they participate in.
05What's the difference between XRPL and Stellar?
Both are federated-BFT settlement networks designed by the same architects (Jed McCaleb co-founded both). XRPL has 4s finality vs Stellar's 5s, 1,500 TPS theoretical max vs Stellar's 5,000, and rejects general smart contracts on L1 while Stellar shipped Soroban (WASM) in 2024. XRPL's design is more minimalist; Stellar's is more flexible. Both are non-custodial protocols suitable for cross-chain swap settlement of stablecoin and FX-style flows.