BASICS / 04 OF 08
How the ledger works
A transaction is submitted, checked against network rules and included in a ledger result. A successful submission response alone is not proof of a validated outcome.
Three things to know
- Check the transaction result and whether it is validated.
- A ledger number identifies a version, not a price or a transaction count.
- An unavailable public server does not by itself prove the whole network stopped.
A practical example
Submitted → pending observation → validated result. The result may be success or failure; read the result and metadata instead of treating “sent” as “completed.”
Technical detail
The XRP Ledger Consensus Protocol coordinates agreement over transaction ordering and ledger state. A server’s trusted validator list and sufficient overlap matter. This is not proof-of-work mining, and a client-side animation is not a simulation of every consensus rule.
Common misunderstanding
A fast animation or an API acknowledgement does not establish final validation.
Check the original sources
Editorial review: October 28, 2026. Source content and network rules can change.
0 of 8 Basics read
Saved in this browser. No account needed. Clearing browser data removes this progress. Basics markers are separate from Academy completion and website backups.
Independent education. Not affiliated with Ripple. No wallet connection, recovery phrases or investment advice.