On September 11, XRP Ledger validators flipped on fixCleanup3_3_0, a bundle of eleven small fixes touching automated market makers, lending vaults, checks, and the permissioned DEX. Validator support for this XRP Ledger security amendment cleared the required 80 percent threshold weeks earlier, in a vote most crypto news sites never mentioned. That silence is the point. The most important fixes are usually the ones nobody hears about until years later, when nobody manages to drain a liquidity pool because someone already closed the door.
Closing the Rounding-Error Loophole in AMMs
The headline fix targets Automated Market Makers, the pools that let people swap assets directly against a shared reserve instead of waiting for a matching buyer. Ripple’s engineers added a check for rounding losses that occur during deposits, withdrawals, and clawbacks inside AMM pools. Rounding sounds trivial, but in financial software it is a classic attack surface. Shave a fraction of a cent off thousands of transactions involving unevenly sized deposits, and an attacker can walk away with real value while the ledger’s books still appear to balance. This fix closes that gap before anyone gets the chance to test it in production, and it works alongside the existing fixAMMv1_3 amendment already running on the network.
Fixing Features Before They Even Launch
What makes this update unusual is its timing. Two of the systems it touches, Single Asset Vaults and the Lending Protocol, are not live on the XRP Ledger mainnet yet. Ripple’s developers are patching precision and rounding issues in code that ordinary users cannot touch, months ahead of launch. The amendment also introduces a new invariant called ObjectHasPseudoAccount, which forces the network to delete a pseudo-account automatically whenever the ledger entry tied to it gets removed. Skip that step, and the ledger accumulates orphaned accounts with no owner and no purpose, exactly the kind of loose end that turns into a support headache or an exploit down the line.
Why This XRP Ledger Security Amendment Sets a Pattern
This is the third cleanup amendment the XRP Ledger has activated in four months, and each one has passed without a contested vote. XRP Ledger developers aren’t alone in this kind of quiet maintenance: Injective patched a $4.9 million exploit earlier this year with a similar network upgrade, and Ledger closed a wallet signing flaw the same way. What sets the XRP Ledger apart is the cadence. Financial institutions weighing whether to build on it care less about any single patch and more about whether the network’s governance process works, quietly and on schedule, release after release. That consistency lands at a useful moment, too, with regulators paying fresh attention to XRP’s legal status. A boring, uncontested software update turns out to be oddly reassuring: the protocol keeps improving itself whether or not anyone is watching.
Ripple did not build this fix to grab a headline. It built it so the next time regulators or institutions look closely at the XRP Ledger, they find fewer rough edges, not more.