Last updated


An EnableAmendment pseudo-transaction marks a change in the status of a proposed amendment when it:

  • Gains supermajority approval from validators.
  • Loses supermajority approval.
  • Is enabled on the XRP Ledger protocol.

Example EnableAmendment JSON

  "Account": "rrrrrrrrrrrrrrrrrrrrrhoLvTp",
  "Amendment": "42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE",
  "Fee": "0",
  "LedgerSequence": 21225473,
  "Sequence": 0,
  "SigningPubKey": "",
  "TransactionType": "EnableAmendment"

EnableAmendment Fields

In addition to the common fields, EnableAmendment pseudo-transactions use the following fields:

FieldJSON TypeInternal TypeDescription
AmendmentStringHash256A unique identifier for the amendment. This is not intended to be a human-readable name. See Amendments for a list of known amendments.
LedgerSequenceNumberUInt32The ledger index where this pseudo-transaction appears. This distinguishes the pseudo-transaction from other occurrences of the same change.

EnableAmendment Flags

The Flags value of the EnableAmendment pseudo-transaction indicates the status of the amendment at the time of the ledger including the pseudo-transaction.

A Flags value of 0 (no flags) or an omitted Flags field indicates that the amendment has been enabled, and applies to all ledgers afterward. Other Flags values are as follows:

Flag NameHex ValueDecimal ValueDescription
tfGotMajority0x0001000065536Support for this amendment increased to at least 80% of trusted validators starting with this ledger version.
tfLostMajority0x00020000131072Support for this amendment decreased to less than 80% of trusted validators starting with this ledger version.