What Are XRPL Pseudo-Transactions?

Definition and scope

What Are XRPL Pseudo-Transactions? addresses a distinct part of xrp and ledger fundamentals. Understand consensus-generated transactions used for amendments, fee changes, and other network operations.

This collection establishes the language needed to evaluate every other XRP Ledger topic. It separates the asset from the network, explains the identifiers visible in explorers, and shows how individual transactions fit into an ordered ledger history. Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.

How it works

Pseudo-transactions are created by consensus rules rather than signed and submitted by an account. EnableAmendment and SetFee records make certain network-governance outcomes visible in ledger history.

• EnableAmendment: verify this field, object, or component against the cited protocol documentation.
• SetFee: verify this field, object, or component against the cited protocol documentation.
• pseudo-transaction: verify this field, object, or component against the cited protocol documentation.
• flag ledger: verify this field, object, or component against the cited protocol documentation.

Practical example and checks

When an amendment changes status around a flag ledger, an EnableAmendment pseudo-transaction records majority gained, majority lost, or final activation through its flags and amendment ID.

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.

Limits, risks, and common confusion

Users cannot submit pseudo-transactions and should not interpret their special Account or zero Fee fields as ordinary account activity. Their validity comes from ledger consensus.

Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.

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.