XRPL amendment voting: check the live status of every amendment
A change to the XRP Ledger's rules is called an amendment. It turns on only after the validators vote for it, and any server shows how that vote stands.
Below are the rule, three calls that read the live status, and what happens to servers that fall behind. You need curl and jq.
The rule
An amendment needs 80% of the validators on the trusted list, and it has to keep that support for two weeks. The XRPL docs: "If support drops below 80%, the amendment is temporarily rejected, and the two week period restarts."
Both numbers are constants in the server code: 80% (kAmendmentMajorityCalcThreshold) and two weeks (kDefaultAmendmentMajorityTime). When the two weeks pass, the ledger records an EnableAmendment and, in the docs' words, "the change applies permanently to all subsequent ledger versions."
1. List every open vote
feature returns every amendment the server knows, with the vote count for those not yet enabled.
Request:
curl -s https://api.xrpl.to/v1/rpc \
-H 'Content-Type: application/json' \
-d '{"method":"feature","params":{}}' \
| jq -r '.result.features[] | select(.enabled == false) | "\(.count)/\(.validations) votes, needs \(.threshold) \(.name)"' \
| sort -rn
Response:
25/35 votes, needs 28 SingleAssetVault
24/35 votes, needs 28 LendingProtocolV1_1
24/35 votes, needs 28 LendingProtocol
22/35 votes, needs 28 ConfidentialTransfer
17/35 votes, needs 28 DynamicMPT
11/35 votes, needs 28 Sponsor
11/35 votes, needs 28 fixXChainRewardRounding
4/35 votes, needs 28 XChainBridge
0/35 votes, needs 28 CryptoConditionsSuite
validations: the validators on the trusted list, 35 today.threshold: the votes needed, 80% of 35, so 28.- Nine amendments are open and none has 28 votes yet. The closest is
SingleAssetVault, three short.
2. Check one amendment
feature also takes one amendment's name or ID.
Request:
curl -s https://api.xrpl.to/v1/rpc \
-H 'Content-Type: application/json' \
-d '{"method":"feature","params":{"feature":"SingleAssetVault"}}' \
| jq '.result | to_entries[] | select(.value | type == "object") | {id: .key, name: .value.name, enabled: .value.enabled, count: .value.count, threshold: .value.threshold, validations: .value.validations}'
Response:
{
"id": "81BD2619B6B3C8625AC5D0BC01DE17F06C3F0AB95C7C87C93715B87A4FD240D8",
"name": "SingleAssetVault",
"enabled": false,
"count": 25,
"threshold": 28,
"validations": 35
}
The ledger stores amendments by that ID. The known amendments page lists each one with what it does.
3. See which votes are in their two weeks
The ledger keeps one Amendments entry: the IDs of the enabled amendments, and under Majorities, each amendment that reached 80% with the time it got there.
Request:
curl -s https://s1.xrpl.stream/ \
-H 'Content-Type: application/json' \
-d '{"method":"ledger_entry","params":[{"index":"7DB0788C020F02780A673DC74757F23823FA3014C1866E72CC4CD8B226CD6EF4","ledger_index":"validated"}]}' \
| jq '.result.node | {LedgerEntryType, enabled: (.Amendments | length), Majorities}'
Response:
{
"LedgerEntryType": "Amendments",
"enabled": 98,
"Majorities": null
}
98 amendments are on, and Majorities is empty: nothing will switch on in the next two weeks. When an amendment reaches 80%, it shows up here with a CloseTime, and it switches on two weeks after that time if it keeps its votes.
BatchV1_1, which lets several transactions succeed or fail together, was enabled in ledger 107,540,993 on 9 October 2026 at 14:47 UTC (the EnableAmendment).
Servers that fall behind
A server whose software does not know an enabled amendment stops following the ledger instead of guessing. The docs call this amendment blocked: "You can unblock amendment blocked servers by upgrading to the newest version of xrpld."
Until then, it answers calls like this:
{"error":"amendmentBlocked","error_code":14,"error_message":"Amendment blocked, need upgrade."}
If you run a server, upgrade before an amendment's two weeks end. If you only call servers, a sudden amendmentBlocked means that server is out of date: switch to another one.
Watch it
xrpl.to/amendments shows the same votes live, and XRPL amendments explained covers each one in plain words.
The calls above work on any public server; api.xrpl.to/v1/rpc and xrpl.stream need no key (docs). If you show data from api.xrpl.to in an app, put <a href="https://xrpl.to">Data by xrpl.to</a> on the same screen; the full reference is at xrpl.to/docs.
Comments
No comments yet. Start the discussion.