The problem consensus solves
A decentralized payment network needs participants to agree on one ordered history. If two conflicting transactions attempt to spend the same funds, the network needs a deterministic way to decide what becomes part of the shared state without relying on a central database administrator.
XRPL's consensus protocol coordinates that agreement. Its documented priorities are correctness, agreement, and then forward progress. If conditions are unsafe, the intended behavior is to pause progress rather than let healthy servers validate incompatible ledger histories.
Proposals, ordering, and validation
Servers receive candidate transactions at different times. Validators exchange proposals describing the transaction set they believe should be considered. Through iterative rounds, proposals move toward a supermajority set. The final set is placed into a canonical order so every server applies it consistently.
Each server computes the resulting ledger locally. Validators then publish signed validation messages for the ledger they calculated. A server considers a ledger validated after observing the required agreement among the trusted validators it follows.
What a Unique Node List does
A Unique Node List, or UNL, is the set of validators a particular server trusts not to collude. The list controls whose validation votes that server considers. It does not grant validators control over account keys, and simply running a validator does not automatically give it influence over other servers.
Operators may configure their own lists, but high overlap is important so servers reach compatible conclusions. Recommended lists help operators begin with identified, reliable validators. The official documentation currently notes default list publishers associated with the XRP Ledger Foundation and Ripple, while making clear that server operators retain control over their own configuration.
Open the related live demo or evidence lab →What consensus does not mean
Consensus is not a vote to rewrite protocol rules, seize an account, or authorize an unsigned payment. Transactions still have to satisfy the deterministic rules implemented by the server software. Validators help coordinate which eligible transactions enter a ledger and confirm the resulting state.
It is also inaccurate to describe validators as earning the XRP transaction cost. That cost is destroyed. Validator operators participate for network reliability, their own infrastructure needs, or ecosystem reasons rather than protocol-issued rewards.