Federated consensus (validator lists) · since 2012
XRP Ledger
A payments ledger with a built-in exchange; ledgers close every few seconds and are final.
Documented pace, live read missed
Live read:
Why people use it
How it works
Who agrees
Validators agree on each ledger using trusted lists (UNLs).
A shared clock, using numbers already on this site
Amendments
Features arrive as amendments that need 80% validator support.
Try it: how long until a payment counts?
The wide mark is when that network calls a payment settled.
Block paces use the live read when it answers.
Strengths and trade-offs
Strengths
- Final settlement in seconds
- Built-in DEX, AMM and payment features
- Over a decade of running
Trade-offs
- You choose validators to trust; no open mining or staking
- Supply was created at launch; most of Ripple’s RLUSD lives on Ethereum, not XRPL
- Production servers want 64 GB RAM
Design choices, next to Kaspa
Not a score. Every network picks a side on each of these. Filled: XRP Ledger. Outlined in blue: Kaspa. Tap a row for the trade-off.
Tap a row.
What its community is talking about
Paraphrased from X News story pages, which summarize public posts. Tap for the original thread.
Next to Kaspa
Generous where XRP Ledger leads, specific where Kaspa differs.
XRPL has deterministic finality, a built-in exchange and real institutional pilots that Kaspa does not have yet.
Kaspa is permissionless proof of work: anyone can mine, nobody picks the validators, and supply was not created at launch.
XRPL shows payments win with stable features, partners and stablecoins, not just block speed.
The facts
a few secondsto finality once a ledger is validated
100 billionXRP created at launch; each fee destroys a little
Recommended node, from official docs
| CPU | 8+ cores |
| Memory | 64 GB RAM (16 GB is test-only) |
| Disk | fast NVMe |
Old data
Servers keep recent ledger history by default; full history is optional.
Official site
Static facts checked Nov 15, 2026. Spotted something wrong? The official source wins.