The protocol’s priorities

The XRP Ledger’s consensus is built around three priorities, in order: correctness, agreement, and forward progress. A little chosen trust, the Unique Node List, replaces a mining race. One company does not run the ledger.

Marketing says “decentralized” and stops. The philosophy tells you what the network will protect first when something goes wrong.

Correctness means honest servers do not validate a ledger that breaks the rules. Agreement means they end up on the same ledger, so you are not paid on one server and unpaid on another. Forward progress means the network keeps closing ledgers even if some validators leave or misbehave. The docs put those three in that order on purpose. A fast wrong ledger is worse than a slow right one.

The trust idea is small on purpose. Each server listens hardest to a list of validators it has chosen, the Unique Node List. Those validators are assumed, as a group, not to collude. You can choose a different list. That is not the same as trusting no one, and it is not the same as trusting a single operator.

Ripple writes code and runs a validator. It does not own the rulebook. A change still has to pass the amendment vote. Payments were the original job: move value, in XRP or in issued assets, without a central desk in the middle.

Real example: the consensus docs name Correctness, Agreement, and Forward Progress, and say a little trust goes a long way. The FAQ says Ripple is one contributor, not the operator. Sources: Consensus Principles and Rules, FAQ.