Key takeaways
- XRPL upgrade loses its two-week validator approval countdown
- November 4 becomes the new conditional activation date
- Native lending proposals remain below the required voting threshold
The XRP Ledger's latest network upgrade has missed its expected October 23 activation after validator support briefly dropped below the required 80% threshold, resetting a two-week approval countdown just before completion.
The affected amendment, fixCleanup3_4_0, is now projected to activate on November 4 at approximately 14:46 UTC, provided sufficient validator support continues uninterrupted.
According to the XRPL amendment tracker, the proposal regained its required majority on October 21 after a short interruption. The delay is particularly notable because the upgrade includes corrections to token permissions, lending-related infrastructure and other network functionality.
Why the XRP Ledger Upgrade Was Delayed
The amendment had been approaching its October 23 activation target before support dropped to 26 of 35 trusted validators at approximately 12:54 UTC on October 21. It needed at least 29 votes to maintain the required supermajority.
Support recovered to 29 votes by 14:46 UTC, but the interruption had already reset the mandatory 14-day countdown. Subsequent October 22 readings showed backing recovering to 31 or more validators.
Unlike ordinary software releases, XRP Ledger amendments must maintain more than 80% support for two consecutive weeks before activation. A single checkpoint below that threshold restarts the process, even if support quickly returns.
The setback follows an earlier Batch upgrade delay, when another temporary decline in validator support disrupted the network's approval schedule.
As explained in our XRPL governance breakdown, protocol changes cannot be activated unilaterally by Ripple. They depend on sustained support from the validators trusted by participating servers.
What the Delayed XRPL Upgrade Actually Fixes
The fixCleanup3_4_0 amendment is primarily a collection of technical corrections introduced through xrpld version 3.4.0 rather than a completely new feature.
One important correction addresses an unintended token-creation possibility associated with delegated PaymentBurn permissions. The patch also improves automated market maker operations, escrow handling, transaction signatures and calculations involving Single Asset Vaults.
These changes build on XRPL's earlier permission delegation rollout, which introduced more granular account controls for payments and other operations.
The broader security implications also follow the network's recent emergency release, which introduced separate protections ahead of the Batch upgrade.
XRP Ledger Lending Still Faces a Separate Approval Barrier
The delayed cleanup amendment should not be confused with the proposed native lending system, which remains outside the network's activated feature set.
Recent validator data showed LendingProtocol and LendingProtocolV1_1 receiving 19 votes each, while SingleAssetVault had 21. All three remained below the required threshold.
The proposed lending architecture would allow pooled assets to finance fixed-term loans, while the newer lending revision introduces closed-ended vault structures and updated interest-accounting rules.
