TL;DR
- fixCleanup3_3_0 reached 82.86% consensus with 29 Yes votes, starting a two-week activation window that could culminate on September 11 if support remains above 80%.
- The bundled amendment hardens Single Asset Vaults, the Lending Protocol, AMMs, permissioned DEX functions, Checks and pseudo-account behavior across multiple transaction paths.
- Additional fixes address hybrid offers, AMM pricing and precision, ledger invariants and malformed pseudo-account transactions, while validators must keep sufficient support through activation successfully.
XRP Ledger is approaching a significant September upgrade after the fixCleanup3_3_0 amendment secured majority support with 82.86% consensus. Introduced with xrpld version 3.3.0, the amendment entered voting on August 6 and reached majority on August 28 with 29 Yes votes, beginning a two-week activation window. The key development is that XRPL has crossed the threshold needed to begin the countdown toward activation. XRPScan data points to September 11, 2026 as the earliest activation date, although that timeline can reset if validator support falls to 80% or lower before completion for operators across the mainnet network.
The bundled fix amendment in XRPL 3.3.0 has entered 2 week activation window with 29 Yes votes. It further hardens existing XRP Ledger features.
Please upgrade your nodes in time so they can keep operating once it activates. https://t.co/dqVoKBkApw pic.twitter.com/mK4TuxLfW4
— Vet (@Vet_X0) August 28, 2026
fixCleanup3_3_0 hardens several XRPL systems at once
The fixCleanup3_3_0 package bundles corrections affecting Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, Checks and pseudo-accounts. Rather than introducing a new headline feature, the amendment focuses on hardening existing XRPL functionality across several interconnected components. Among its changes, it unifies freeze and deep-freeze checks for transfers involving pseudo-accounts in multiple vault, AMM and lending transactions. It also changes CheckCash and CheckCancel so an all-zero CheckID is rejected during preflight with temMALFORMED instead of failing later during processing with tecNO_ENTRY, tightening validation behavior before transactions advance before they reach ledger processing.
The amendment also addresses order-book and AMM edge cases. Hybrid offers will no longer disappear from the open order book when the account that created them loses access to a permissioned domain, while AMM liquidity will be incorporated into quality estimates for permissioned DEX order books. These fixes target subtle market-structure problems that could affect pricing, liquidity visibility and transaction reliability. AMMWithdraw will return tecAMM_FAILED instead of dividing by zero at a specific EPrice condition, while AMMDeposit, AMMWithdraw and AMMClawback gain additional precision-loss checks when fixAMMv1_3 is enabled, adding further safeguards around automated liquidity operations.
Additional protections tighten how pseudo-accounts and ledger objects behave. The ValidAMM invariant will ensure AMMs can only be deleted through AMMWithdraw, AMMClawback or AMMDelete, while a new ObjectHasPseudoAccount invariant checks that deleting a ledger entry backed by a pseudo-account also removes that pseudo-account. The remaining question is operational: validators must maintain sufficient support until the activation window closes. Transactions signed by pseudo-accounts will fail with tefBAD_AUTH, while CredentialCreate and DepositPreauth will reject pseudo-accounts in specified fields. If support holds above 80%, the bundled upgrade can activate on September 11 and harden several existing XRPL systems.
