Skip to content
Open for votingTier ATokens

DynamicMPT XLS-94

Issuers can update or permanently lock an MPT issuance's metadata, TransferFee, and certain capabilities. DynamicMPT is open for Mainnet voting but is not enabled yet. The latest response reports support from 16 of 35 tracked validators.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Open for voting
XLS
XLS-94
Enabled
Not enabled

What is the current Mainnet vote?

16 of 35 yes votes; minimum: 29 (current 45%; support >80%)

What does this amendment change?

Why does this amendment exist?

Issuers need controlled updates to selected MPT properties and a way to permanently lock properties that must remain fixed.

How does the mechanism work?

Without ImmutableFlags, an issuance's MPTokenMetadata and TransferFee remain mutable, and capability flags such as CanLock, CanEscrow, CanTrade, CanTransfer, or CanClawback can later be enabled once. MPTokenIssuanceCreate or MPTokenIssuanceSet can permanently lock individual fields or flags through ImmutableFlags; new bits can only be added, never removed. Enabled capability flags cannot be disabled again through MPTokenIssuanceSet.

What changes compared with the predecessor?

BeforeAfter
An MPT issuance's fields and behavior flags were generally immutable after creation.Metadata and TransferFee remain mutable, and capability flags can be enabled later, until the issuer permanently locks the relevant property through ImmutableFlags.

Who is this change relevant to?

XRP holders and users

Without ImmutableFlags set, the issuer can update metadata and TransferFee and later enable rights such as Clawback or RequireAuth. Before acquisition, users should be able to see which properties are already permanently locked.

Wallets and app developers

Wallets and explorers show active flags separately from ImmutableFlags and track metadata or TransferFee changes.

Exchanges and issuers

Issuers retain room for later updates by default and can give holders binding commitments by permanently locking individual properties.

Node operators

Nodes check bitmasks, issuer authorization, size and fee limits, and reject changes to properties already permanently locked.

What limitations and risks remain?

  • An ImmutableFlags bit cannot be removed once set.
  • Enabling a capability flag is a one-way operation; MPTokenIssuanceSet cannot disable it again.
  • MPTokenMetadata is limited to 1,024 bytes and TransferFee to 50,000 units.
  • A TransferFee greater than zero requires CanTransfer to be enabled already or enabled in the same transaction.
  • For MPT issuances with confidential balances, TransferFee must remain zero.
  • Holder and tfMPTLock or tfMPTUnlock cannot be combined with these updates in the same transaction.
Technical details: transactions, fields, codes and invariants

Transactions

  • MPTokenIssuanceCreate
  • MPTokenIssuanceSet

Ledger objects

  • MPTokenIssuance

Fields and flags

  • ImmutableFlags
  • MPTokenMetadata
  • TransferFee
  • tifMPTCanLock through tifMPTCanClawback 0x00000002 through 0x00000040
  • tifMPTCanHoldConfidentialBalance 0x00000080
  • tifMPTMetadata 0x00010000
  • tifMPTTransferFee 0x00020000
  • tfMPTSetCanLock through tfMPTSetCanClawback 0x00000004 through 0x00000080
  • tfMPTSetCanHoldConfidentialBalance 0x00000100

Result codes

  • temINVALID_FLAG
  • temDISABLED
  • temMALFORMED
  • temBAD_TRANSFER_FEE
  • tecOBJECT_NOT_FOUND
  • tecNO_PERMISSION

Invariants

  • A set ImmutableFlags bit is never removed, and its associated property cannot change afterward.

What does a concrete workflow look like?

An issuer creates an MPT issuance without ImmutableFlags and later updates its metadata. It then sets tifMPTMetadata, after which the ledger rejects any further metadata update with tecNO_PERMISSION.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

DynamicMPT is open for Mainnet voting but is not enabled yet. The latest response reports support from 16 of 35 tracked validators.

Activation requires support strictly above 80 percent for two uninterrupted weeks. A reported raw cutoff is not the minimum yes-vote count: with 35 tracked validators and a cutoff of 28, at least 29 yes votes are required.

Where does it sit within its amendment family?

Multi-Purpose Tokens: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  5. MPTokensV1Enabled · from rippled 2.3.0
  6. PermissionedDEXEnabled · from rippled 2.5.0
  7. TokenEscrowEnabled · from rippled 2.5.0
  8. PermissionDelegationDeprecated · from rippled 2.5.0
  9. fixTokenEscrowV1Enabled · from rippled 3.0.0
  10. fixMPTDeliveredAmountEnabled · from rippled 3.0.0
  11. fixCleanup3_2_0Enabled · from xrpld 3.2.0
  12. DynamicMPTOpen for voting · from xrpld 3.3.0
  13. SponsorOpen for voting · from xrpld 3.3.0
  14. ConfidentialTransferOpen for voting · from xrpld 3.3.0
  15. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  16. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  17. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications