Skip to content
EnabledTier BSecurity

fixCleanup3_3_0

The bundled fix for xrpld 3.3.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, checks, and pseudo-accounts. fixCleanup3_3_0 is enabled on the XRP Ledger. xrpscan reports Sep 11, 2026 (UTC) as its activation date and xrpld 3.3.0 as its first version.

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

Status
Enabled
XLS
No separate XLS
Enabled
Sep 11, 2026 (UTC)

What does this amendment fix?

Which failure case does this fix correct?

fixCleanup3_3_0 bundles the amendment-gated corrections in xrpld 3.3.0. It standardizes freeze and deep-freeze checks for transfers to and from pseudo-accounts, excludes AMM liquidity from permissioned DEX quality estimates, and makes transactions signed by pseudo-accounts fail with tefBAD_AUTH.

Who is affected?

Holders need to take no action. Users of vaults, AMM pools, and permissioned markets receive earlier or clearer result codes in some failure cases, such as tecAMM_FAILED instead of tefEXCEPTION for AMMWithdraw.

What changes compared with the predecessor?

BeforeAfter
Hybrid offers could disappear from the open order book when their account lost access to the permissioned domain. At a particular EPrice, AMMWithdraw could divide by zero and fail with tefEXCEPTION.Hybrid offers remain in the open order book. CheckCash and CheckCancel reject an all-zero CheckID during preliminary checks with temMALFORMED, and CredentialCreate and DepositPreauth reject pseudo-accounts with tecPSEUDO_ACCOUNT.

Who is this change relevant to?

XRP holders and users

Ordinary XRP payments retain their behavior. In permissioned markets, hybrid offers remain in the open order book when domain access ends.

Wallets and app developers

Apps account for tecAMM_FAILED, tefBAD_AUTH, and tecPSEUDO_ACCOUNT as possible results and expect temMALFORMED for checks with an all-zero ID.

Exchanges and issuers

Permissioned market operators receive quality estimates that exclude AMM liquidity. Vault and lending providers receive additional precision and rounding corrections.

Node operators

Nodes check two additional invariants and need xrpld 3.3.0 or later to recognize the bundled fix.

What limitations and risks remain?

  • The precision check for AMMDeposit, AMMWithdraw, and AMMClawback applies only when fixAMMv1_3 is also enabled.
  • According to xrpl.org, rejection of transactions signed by a pseudo-account also applies when LendingProtocol or BatchV1_1 is enabled.
  • The documentation describes vault and lending precision and rounding corrections only in summary form.
Technical details: transactions, fields, codes and invariants

Transactions

  • VaultDeposit
  • VaultWithdraw
  • AMMDeposit
  • AMMWithdraw
  • AMMClawback
  • LoanBrokerCoverDeposit
  • LoanBrokerCoverWithdraw
  • CheckCash
  • CheckCancel
  • CredentialCreate
  • DepositPreauth

Ledger objects

  • Vault
  • LoanBroker
  • AMM
  • Offer
  • Check
  • Credential
  • AccountRoot of pseudo-accounts

Fields and flags

  • CheckID
  • EPrice
  • Subject (CredentialCreate)
  • Authorize (DepositPreauth)

Result codes

  • temMALFORMED
  • tecAMM_FAILED
  • tefBAD_AUTH
  • tecPSEUDO_ACCOUNT

Invariants

  • ValidAMM: An AMM may be deleted only through AMMWithdraw, AMMClawback, or AMMDelete.
  • ObjectHasPseudoAccount: Deleting a ledger object with a pseudo-account also deletes that pseudo-account.

How does this amendment relate to others?

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

bundles fixes for

Checks

The bundled fix for xrpld 3.3.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, checks, and pseudo-accounts. The documented bundled fix covers Checks.

Check the relationship in the primary source

bundles fixes for

DepositPreauth

The bundled fix for xrpld 3.3.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, checks, and pseudo-accounts. The documented bundled fix covers DepositPreauth.

Check the relationship in the primary source

bundles fixes for

fixAMMv1_3

The bundled fix for xrpld 3.3.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, checks, and pseudo-accounts. The documented bundled fix covers fixAMMv1_3.

Check the relationship in the primary source

What happens next for this amendment?

fixCleanup3_3_0 is enabled on the XRP Ledger. xrpscan reports Sep 11, 2026 (UTC) as its activation date and xrpld 3.3.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications