By The XRP Ledger is approaching a significant protocol upgrade as its fixCleanup3_4_0 amendment prepares to complete the required two-week validator approval period on November 4, 2026.
The amendment is scheduled to become eligible for activation at 14:46:22 UTC, following a restart of its governance countdown on October 21. According to XRPLWin’s amendment tracker, 33 of 35 trusted validators supported the proposal, representing approximately 94.3% approval.
The XRP Ledger requires more than 80% validator support maintained continuously for 14 days before a protocol amendment can activate. Although the approval period is expected to conclude at 14:46 UTC, the actual change will take effect at a subsequent flag ledger, the network’s periodic amendment voting checkpoint.
The update introduces corrections affecting issued tokens, automated market makers, escrow transactions and proposed lending infrastructure. It does not introduce a new cryptocurrency or change XRP’s maximum supply.
Validator Support Dip Delayed Upgrade by Nearly Two Weeks
The amendment was originally expected to activate on October 23 after receiving sufficient validator support earlier that month. However, on October 21, the number of supporting validators temporarily declined to 26 out of 35, falling below the required threshold of 29.
The reduction occurred during a roughly two-hour period before support recovered at 14:46 UTC. Under the XRP Ledger’s governance rules, any interruption in the required majority automatically resets the entire 14-day approval period.
Consequently, the amendment’s activation window shifted from October 23 to November 4. The mechanism is designed to prevent protocol changes from activating without sustained agreement among trusted validators. Support subsequently strengthened, reaching 33 validators ahead of the revised activation date.
The amendment was introduced in version 3.4.0 of the XRP Ledger server software, released in September. Its corrections address several technical issues, including a permissions vulnerability affecting tokens issued on the network.
Under certain conditions, an account authorised only to destroy issued tokens could potentially create additional tokens without separate issuance permission. The update closes that loophole, strengthening controls relevant to stablecoin issuers and other organisations managing tokenised assets.
There have been no publicly confirmed cases of the vulnerability being exploited. Importantly, the issue does not affect the native XRP cryptocurrency’s supply.
Amendment Strengthens Token Security but Does Not Launch Lending
Beyond token issuance permissions, fixCleanup3_4_0 introduces corrections to automated market maker operations and token recovery procedures. It addresses calculations involving Multi-Purpose Tokens, including circumstances where rounding could interfere with recovering assets from liquidity pools.
The amendment also corrects escrow processing under specific account reserve conditions. Additional fixes relate to proposed Single Asset Vaults and the XRP Ledger’s upcoming lending functionality. One correction prevents lending transactions from being incorrectly classified as overdue or in default before their contractual deadlines.
However, these changes do not mean the XRP Ledger’s lending protocol will become operational on November 4. The separate LendingProtocol and SingleAssetVault amendments have not yet secured the required validator approval. Recent governance data showed 19 validators supporting LendingProtocol and 21 supporting SingleAssetVault, both below the 29-vote threshold.
Those proposals must independently maintain sufficient support for two consecutive weeks before activation. For financial institutions and developers building on the XRP Ledger, the cleanup amendment represents an infrastructure maintenance upgrade rather than the launch of a new financial product.
Its significance lies in strengthening existing transaction rules and preparing components for future functionality. Once activated, the amendment’s rules will apply across the network, and server operators running incompatible software will need to upgrade.
The final confirmation will come from the XRP Ledger’s validated transaction history rather than the projected activation timestamp alone.