Definition and scope
What Is an XRPL Flag Ledger? addresses a distinct part of validators and network governance. See how every 256th ledger anchors amendment voting and majority-status decisions.
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
Every 256th ledger is a flag ledger around which servers interpret amendment votes. Adjacent ledgers can record majority gained, majority lost, or activation through EnableAmendment pseudo-transactions.
- flag ledger: verify this field, object, or component against the cited protocol documentation.
- 256 ledgers: verify this field, object, or component against the cited protocol documentation.
- tfGotMajority: verify this field, object, or component against the cited protocol documentation.
- tfLostMajority: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A monitor watches validations before the flag ledger, then inspects pseudo-transactions and the Amendments ledger entry after it to update status without guessing from vote percentages.
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
A flag ledger does not contain user-controlled flags or special economic data. Reaching one flag ledger with high support is not the same as completing the required two-week majority period.
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.