Update, Sept. 15, 2026: The fix did activate. fixCleanup3_3_0 went live on September 11, 2026, at 11:29 UTC, in validated ledger 106,911,489, with support at 88.57% — 31 of the network’s 35 trusted validators. Separate amendments bundled in the same 3.3.0 release (LendingProtocol, SingleAssetVault, BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor) remained disabled as of Sept. 12 — this update covers fixCleanup3_3_0 specifically, not the whole release.
A bundle of technical bug fixes for the XRP Ledger, known as fixCleanup3_3_0, had crossed the 80% support threshold on August 28, 2026, and stood at 82.86% as of September 6. If that support held through the required two-week window, the fix was projected to go live on the network around September 11.
The XRP Ledger runs on a rule, not a company decision: a proposed change, called an amendment, only takes effect once more than 80% of the network’s 35 trusted validators vote to support it, and keep supporting it, for 14 straight days. If support ever slips to 80% or below at any point in that window, the two-week clock resets and starts over. Ripple, the company behind XRP, operates just one of those 35 validators, and cast a “yes” vote on this amendment around August 12, when support stood at only about 23% — Ripple’s vote alone did not move the outcome; it took dozens more validator operators, acting independently, to carry the amendment past the threshold weeks later. Who operates the other 34 trusted validators — companies, exchanges, or individuals — is not identified anywhere in this reporting; Ripple is the only one of the 35 whose operator is named.
As of the most recent check on September 6, support stood at 82.86%, meaning 29 of the 35 validators were voting yes — just above the line, with five days left in the countdown toward the projected September 11 activation. Voting on the amendment had opened weeks earlier, in early August, and support climbed gradually. It stood at roughly 23% around August 12. By August 24 it had risen to about 69%, and it crossed 80% on August 28.
Key facts
- Support as of September 6: 82.86% (29 of 35 trusted validators)
- Threshold to activate: more than 80% support, held for 14 straight days
- 14-day window began: August 28, 2026
- Projected activation: around September 11, 2026
- Support climb: ~23% (Aug 12) → ~69% (Aug 24) → over 80% (Aug 28)
- Ripple’s role: operates 1 of the 35 trusted validators; voted “yes” around August 12
- Required software: xrpld version 3.3.0 or later
- Node-operator upgrade rate: over 60% as of August 24
What the fix actually changes
fixCleanup3_3_0 is not a new feature. It’s a bundle of roughly a dozen fixes correcting problems in systems the Ledger already has: Single Asset Vaults, the Lending Protocol, Automated Market Makers (AMM), the permissioned decentralized exchange, Checks, and “pseudo-accounts” (accounts the network itself controls for these features, rather than a person). Among the specific corrections: it stops a division-by-zero error that could occur when withdrawing funds from an AMM pool, it makes the network reject malformed Checks that carry an all-zero ID instead of processing them, and it fixes a bug where certain trading offers could vanish from the open order book if an account lost access to a permissioned trading domain on the Ledger. This is a bug-fix amendment, not a new user-facing feature; it corrects existing Ledger functionality. No source found in this reporting ties fixCleanup3_3_0 to any change in XRP’s price; it’s a protocol-reliability fix, not a monetary-policy or token-supply change.
This is a distinct, later amendment from an earlier one with an almost identical name, fixCleanup3_2_0, which already activated on July 29, 2026. The two are separate bug-fix bundles from different points in the Ledger’s release cycle; fixCleanup3_3_0 has not yet activated as of September 6, 2026.
What happens if support drops
Nothing about the September 11 date is locked in. It’s a projection that holds only if support stays above 80% every day through the full 14-day window that started August 28. Nothing in this reporting indicates support has fallen below that line since then — but the rule leaves no margin for error: even one dip to 80% or below restarts the countdown from zero.
For anyone running XRP Ledger server software, there’s a real deadline attached to this. Once an amendment activates, servers still running older software that doesn’t recognize it become “amendment-blocked” — they can no longer validate ledgers, process or submit transactions, or vote on future amendments until they upgrade. The fix requires xrpld version 3.3.0 or later, and as of August 24, more than 60% of node operators had already made that upgrade. That’s a different, larger population than the 35 trusted validators who vote on the amendment itself. “Node operators” means everyone running Ledger server software — a group that has numbered well into the hundreds before — though this reporting doesn’t say whether that 60% figure counts those 35 validators separately. A previous, unrelated amendment shows what missing the deadline can cost: when fixDirectoryLimit activated in December 2025, about 42% of tracked servers ended up amendment-blocked because their operators hadn’t upgraded in time.
Several other proposed amendments were also open for validator voting as of September 6, but all remained below the 80% activation threshold. BatchV1_1 was furthest along at roughly 65%; SingleAssetVault was around 37%; PermissionDelegationV1_1 and LendingProtocol were around 31%; DynamicMPT and ConfidentialTransfer were around 22%; and XChainBridge and Sponsor were around 14%. FixCleanup3_3_0 was the only amendment then meeting the threshold.