Last updated



The Amendments ledger entry type contains a list of Amendments that are currently active. Each ledger version contains at most one Amendments entry.

Example Amendments JSON

    "Majorities": [
            "Majority": {
                "Amendment": "1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146",
                "CloseTime": 535589001
    "Amendments": [
    "Flags": 0,
    "LedgerEntryType": "Amendments",
    "index": "7DB0788C020F02780A673DC74757F23823FA3014C1866E72CC4CD8B226CD6EF4"

Amendments Fields

In addition to the common fields, the Amendments ledger entry has the following fields:

NameJSON TypeInternal TypeRequired?Description
AmendmentsArrayVector256NoArray of 256-bit amendment IDs for all currently enabled amendments. If omitted, there are no enabled amendments.
FlagsNumberUInt32YesA bit-map of boolean flags enabled for this object. Currently, the protocol defines no flags for Amendments objects. The value is always 0.
LedgerEntryTypeStringUInt16YesThe value 0x0066, mapped to the string Amendments, indicates that this object describes the status of amendments to the XRP Ledger.
MajoritiesArraySTArrayNoArray of objects describing the status of amendments that have majority support but are not yet enabled. If omitted, there are no pending amendments with majority support.

Each member of the Majorities field, if it is present, is an object with one field, Majority, whose contents are a nested object with the following fields:

NameJSON TypeInternal TypeDescription
AmendmentStringHash256The Amendment ID of the pending amendment.
CloseTimeNumberUInt32The close_time field of the ledger version where this amendment most recently gained a majority.

In the amendment process, a consensus of validators adds a new amendment to the Majorities field using an EnableAmendment pseudo-transaction with the tfGotMajority flag when 80% or more of validators support it. If support for a pending amendment goes below 80%, an EnableAmendment pseudo-transaction with the tfLostMajority flag removes the amendment from the Majorities array. If an amendment remains in the Majorities field for at least 2 weeks, an EnableAmendment pseudo-transaction with no flags removes it from Majorities and permanently adds it to the Amendments field.

Note: Technically, all transactions in a ledger are processed based on which amendments are enabled in the ledger version immediately before it. While applying transactions to a ledger version where an amendment becomes enabled, the rules don't change mid-ledger. After the ledger is closed, the next ledger uses the new rules as defined by any new amendments that applied.

Amendments Flags

There are no flags defined for the Amendments entry.

Amendments Reserve

The Amendments entry does not require a reserve.

Amendments ID Format

The ID of the Amendments entry is the hash of the Amendments space key (0x0066) only. This means that the ID is always:


(Don't mix up the ID of the Amendments ledger entry type with the Amendment ID of an individual amendment.)