Key XRP Fix Upgrade Eyes September Activation

The XRP Ledger is eyeing an important fix upgrade in September, as fixCleanup3_3_0, a bundle of amendment-gated bug fixes, reaches majority, with 82.86% in consensus.

The fixCleanup3_3_0 amendment introduced in the xrpld version 3.3.0 release entered voting on August 6 and secured majority today, August 28.

In a recent post, Hussein Zangana (Vet) highlighted this development, noting that the bundled fix amendment in XRPL 3.3.0 has entered a 2-week activation window with 29 Yes votes. The fix upgrade, according to Vet, further hardens existing XRP Ledger features, urging node operators to upgrade their nodes in time so they can keep operating once it activates.

According to XRPScan data, the fixCleanup3_3_0 amendment is expected to activate on the XRP Ledger mainnet on September 11, 2026. This earliest activation is a floor, not a promise. If its support falls to 80% or less at any point, the amendment is rejected and the 14-day period starts over.

fixCleanup3_3_0

The fixCleanup3_3_0 amendment is a collection of fixes for Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, Checks, and pseudo-accounts.

The fix upgrade unifies freeze and deep freeze checks for transfers to and from pseudo-accounts in the VaultDeposit, VaultWithdraw, AMMDeposit, AMMWithdraw, LoanBrokerCoverDeposit, and LoanBrokerCoverWithdraw transactions. It changes ‘CheckCash’ and ‘CheckCancel’ to reject an ‘all-zero CheckID’ with ‘temMALFORMED’ during preflight instead of ‘tecNO_ENTRY’ during processing.

fixCleanup3_3_0 also fixes hybrid offers being removed from the open order book when the account that placed them loses access to the permissioned domain and fixes Automated Market Maker liquidity being included in quality estimates for permissioned DEX order books.

The upgrade changes ‘AMMWithdraw’ to return ‘tecAMM_FAILED’ instead of dividing by zero for the one EPrice value at which the computation’s denominator becomes zero. It adds a precision loss check to AMMDeposit, AMMWithdraw, and AMMClawback when the fixAMMv1_3 amendment is also enabled.

The upgrade changes the ValidAMM invariant to ensure an AMM can only be deleted by an AMMWithdraw, AMMClawback, or AMMDelete transaction and adds an invariant ‘ObjectHasPseudoAccount’, which checks that deleting a ledger entry backed by a pseudo-account also deletes that pseudo-account. It adds further precision and rounding fixes for Single Asset Vaults and the Lending Protocol while changing transactions signed by a pseudo-account to fail with ‘tefBAD_AUTH’. This check also takes effect if the Lending Protocol or BatchV1_1 amendment is enabled.

fixCleanup3_3_0 changes ‘CredentialCreate’ to reject a pseudo-account in the Subject field with ‘tecPSEUDO_ACCOUNT’ and changes ‘DepositPreauth’ to reject a pseudo-account in the Authorize field with ‘tecPSEUDO_ACCOUNT’.