← Lesson 8: Building on the XRP Ledger

Education · 09

XRP Ledger Governance and Amendments

#XRPEducationMonth

We’ve covered Batch, liquidity pools and the permissioned DEX. All three started as proposed changes to the ledger’s rules. So how does an idea become a feature your wallet can actually use?

Let’s break it down with Bird.

First, what’s the difference between a node and a validator?

A node is a server running XRP Ledger software. It connects to other servers, checks transactions and keeps track of the ledger. Some nodes also give wallets and explorers a way to read balances or submit payments.

A validator is a node that also takes part in consensus. It proposes which transactions should go into the next ledger and sends a signed message confirming the ledger version it considers correct. Those messages help other servers decide when a ledger is final.

So whose votes count?

Each server has a Unique Node List, or UNL. That’s its list of validators whose signed messages it counts. Operators can use published lists or configure their own. Those lists need enough overlap for servers across the network to agree.

Anyone can run a validator. Its vote counts for a server when that server trusts it. Holding more XRP gives you no extra voting power, and Ripple can’t switch on a feature by itself.

How does an amendment go live?

1- Build it. Developers propose the change, write and test the code, and ship it in a server software release. The code can be installed while the feature is still off.

2- Vote on it. Validator operators can signal support and change their votes. The network checks support every 256 ledgers, usually about every 15 minutes, around what’s called a flag ledger.

3- Hold the majority. Support has to stay above 80% for two weeks. If the tally counts 35 trusted validators, 28 is exactly 80%, so it takes 29. If support falls back to the threshold during the voting window, the clock resets when the amendment regains its majority.

4- Activate it. Once the amendment is enabled, the next ledger starts using the new rules. A server running software that can’t understand those rules becomes amendment blocked until it upgrades.

What does that look like in practice?

In a 17 November 2026 snapshot, LendingProtocol had 22 yes votes out of 35 in the observed tally. It needed 29 to reach the majority threshold and start the two-week window.

So the next time you see “the upgrade has shipped,” ask one more question. Did the code ship, or did the feature actually switch on? That’s the difference between something developers can test and something your wallet can use on the live network.

Nothing Bird posts is financial advice. Beware of impersonators and scams. Always verify information through the official Bird account. Stay safe.