Definition and scope
How XRPL Amendments Change the Protocol addresses a distinct part of validators and network governance. Explain the consensus-governed mechanism for activating transaction-processing changes.
XRPL governance is distributed across deterministic software rules, server operators, validator choices, amendment voting, and the consensus process. These topics clarify what validators can do, what they cannot do, and how protocol changes become active. No single validator or list publisher controls the ledger. Consensus claims must distinguish local trust configuration from network-wide results.
How it works
Amendments introduce consensus-rule changes. Validators signal support, and an amendment must hold more than 80 percent support for two weeks before an EnableAmendment pseudo-transaction activates it permanently.
- amendment: verify this field, object, or component against the cited protocol documentation.
- supermajority: verify this field, object, or component against the cited protocol documentation.
- EnableAmendment: verify this field, object, or component against the cited protocol documentation.
- feature method: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Operators compare their server's feature response with the official known-amendments registry, upgrade to software that supports expected changes, and monitor majority and activation dates.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
An amendment's documentation or presence in source code does not mean it is enabled. Mainnet, Testnet, Devnet, and sidechains can have different amendment sets.
No single validator or list publisher controls the ledger. Consensus claims must distinguish local trust configuration from network-wide results.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.