XRP Ledger · Mainnet

Every protocol change the ledger has voted on, from 2016 to this week.

Created by James Rule

Amendments are how the XRP Ledger upgrades itself. Validators must hold more than 80% support for two continuous weeks. Once enabled, the new rules apply forever — reversing them takes another amendment.

Tracked
112
Activated
94
Voting
10
In the 14-day window
1

Loaded from the last captured snapshot

How an amendment becomes law

01

Ship the code disabled

A change that affects transaction processing is compiled into xrpld as an amendment. Installing a release does not turn it on.

02

Validators vote

Every flag ledger — every 256 ledgers, about 15 minutes — trusted validators signal yes or no. Operators can change their vote at any time.

03

Hold 80% for two weeks

If support drops to 80% or below, the two-week clock restarts. Majority can be won and lost many times before enablement.

04

Enabled forever

An EnableAmendment pseudo-transaction is written. Servers without the code become amendment-blocked until they upgrade. After two years an amendment can be retired into core protocol.

Full specification: Amendments on xrpl.org.

Weekly briefing

Week of 15 Sep 2026

Drawn from the XRPL Foundation blog and live Mainnet votes. Check these sources each week — amendments move on a 14-day clock.

From inception

Every known amendment

112 tracked on Mainnet. Open any name for a plain-English explanation and source links.

Showing 112