XRP Wiki
REF · 13.04 / Reference

XRP Ledger Technical Specifications Reference

A quick-reference table of the XRP Ledger's core technical parameters — consensus, timing, fees, and transaction limits.

A condensed reference table of the XRP Ledger's core technical parameters, for readers who want the numbers without re-reading the full Consensus Protocol write-up. Where a value is not a fixed protocol constant, this is noted — some parameters can change via the amendment process or fluctuate with network conditions.

Consensus and timing

Parameter Value
Consensus mechanism XRP Ledger Consensus Protocol (federated Byzantine agreement) — see Consensus Protocol
Typical ledger close time ~3–5 seconds
Finality Deterministic and immediate once a ledger version is validated — no probabilistic confirmations or block-depth waiting
Energy model No mining; validators do not compete on computational work

Supply and fees

Parameter Value
Total XRP supply 100,000,000,000 (fixed at genesis; see Total Supply and Issuance)
Smallest unit 1 drop = 0.000001 XRP
Typical base transaction fee A small fraction of a cent, dynamically adjustable under network load (see Inflation vs. Deflation Mechanics for how fees are burned rather than paid to validators)
Minimum account reserve A base reserve plus a small additional reserve per owned ledger object (trust lines, offers, etc.); exact amounts are protocol parameters that can change via amendment

Transaction and object limits

Parameter Value
Native decentralized exchange Built into the base protocol — see Decentralized Exchange (DEX) and Trading Use Cases
Multi-signing Up to 32 signer entries per account — see Multi-Signature and Advanced Account Security
Smart contract model No general-purpose on-chain smart contracts on the base ledger; programmability is delivered via native protocol features (escrow, DEX, AMM) and sidechains/EVM-compatible extensions rather than an on-ledger VM
Issued currencies Represented via trust lines between accounts and issuers, not a separate token standard

Governance parameters

Parameter Value
Amendment activation threshold ~80% of trusted validators (by each operator's UNL), sustained for two weeks
New feature proposal process XLS standards process, open and not gated by a single company

A note on precision

Several of the values above (reserve amounts, exact fee levels) are protocol parameters that have changed via amendment in the past and could change again. For current, authoritative values, consult the official XRPL documentation rather than treating this page as a live technical spec — it is a conceptual orientation reference, not a substitute for rippled's own documentation.