The XRP Ledger activated the
fixCleanup3_3_0amendment on Sept. 11, bundling maintenance fixes for Checks, AMMs, pseudo-accounts and the incoming Lending Protocol into the network's live rules. Servers that don't support the update risk becoming amendment blocked, while the Lending Protocol itself still awaits separate validator approval.
Amendment goes live after two-week majority period
The XRP Ledger activated the fixCleanup3_3_0 amendment on Sept. 11 at 11:29 UTC in validated ledger 106,911,489, according to XRPSCAN. Ripple's public XRP Ledger endpoint showed the amendment enabled and supported on Sept. 12.
Bundled into the update are maintenance corrections touching Checks, automated market makers, pseudo-accounts, permissioned trading, Single Asset Vaults and the Lending Protocol into the network's live rules. Several fixes target transaction paths that could previously fail in edge cases: CheckCash and CheckCancel now reject an all-zero CheckID during preflight with temMALFORMED, and a narrow divide-by-zero condition involving AMMWithdraw returns tecAMM_FAILED instead of ending in tefEXCEPTION. Other fixes adjust freeze handling for transfers involving pseudo-accounts and tighten safeguards around AMMs, permissioned markets and cleanup processes.
Ripple had already made the underlying code available since xrpld 3.3.0 released Aug. 6, but this week's activation marks the point when the changes shifted from optional software support into rules servers must follow to stay compatible with the ledger.
Outdated servers risk losing consensus rights
XRPL's amendment system lets new code circulate before validators fold it into the network's consensus rules. Once an amendment secures the required majority for the prescribed period and activates, servers that don't support it can become amendment blocked — unable to determine whether ledgers are valid, submit or process transactions, or take part in consensus.
That creates an immediate operational issue for exchanges, custodians, payment companies and other businesses running their own XRP Ledger infrastructure. 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. The XRPL project recommends operators restore compatibility by running the latest appropriate xrpld release.
Lending Protocol still waits on its own amendment
Activation of fixCleanup3_3_0 doesn't mean every feature bundled alongside it in version 3.3.0 is now live. Separate amendments covering the Lending Protocol, Single Asset Vault, 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 haven't yet made them active network rules.
For users relying on maintained wallets or exchanges, the compatibility work largely sits with service providers. Firms running their own XRPL servers now face the more immediate task of keeping those systems current as validator-approved amendments move from available code into the ledger's active rule set.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
