XRP Ledger activates fixCleanup3_3_0 upgrade, putting outdated servers at risk
XRP Ledger activates fixCleanup3_3_0
The XRP Ledger activated a maintenance upgrade called fixCleanup3_3_0 on Sept. 11 at 11:29 UTC. The change went live in validated ledger 106,911,489, according to XRPSCAN. Ripple's public XRP Ledger endpoint showed the amendment enabled and supported on Sept. 12.
The upgrade bundles fixes for transaction handling, automated market makers (AMMs), vaults, lending, Checks, and pseudo-accounts. It is now part of the network's live rules.
Key facts
- fixCleanup3_3_0 fixes specific transaction and AMM errors.
- Servers that do not support it can become amendment blocked.
- The Lending Protocol and several other version 3.3.0 features remain disabled.
What the amendment changes
CheckCash and CheckCancel now reject an all-zero CheckID during preflight with temMALFORMED. A narrow divide-by-zero condition involving AMMWithdraw now returns tecAMM_FAILED instead of tefEXCEPTION.
Other fixes adjust freeze handling for transfers involving pseudo-accounts and tighten safeguards around AMMs, permissioned markets, and cleanup processes.
Outdated servers face consequences
The code behind the fixes has been available since xrpld 3.3.0 was released on Aug. 6. With activation, the fixes moved from optional software support into rules that servers must understand to stay compatible with the ledger.
XRPL documentation says an amendment-blocked server cannot determine whether ledgers are valid, submit or process transactions, or participate in consensus. The project recommends restoring compatibility by using the latest appropriate xrpld release.
XRPSCAN reported 31 of 35 validations supporting fixCleanup3_3_0 against a threshold of 28 at 01:45 UTC on Sept. 12, after the amendment completed its two-week majority period.
Lending protocol is not live yet
Activating these fixes does not mean every feature in version 3.3.0 is now live. Separate amendments for LendingProtocol, SingleAssetVault, BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, and Sponsor remained disabled on Sept. 12.
Ripple's public server reported support for those amendments, meaning the software can recognize them even though validators have not made them active network rules.
Why this matters
Businesses running their own XRP Ledger infrastructure, including exchanges, custodians, and payment companies, now face an immediate compatibility requirement. For users relying on maintained wallets or exchanges, the compatibility work largely sits with service providers.
What happens next
Operators need to keep their systems current as validator-approved amendments move from available code into the ledger's active rule set. The report does not give an activation date for the Lending Protocol or the other remaining amendments.
