TL;DR
- XRPL’s fixCleanup3_4_0 activation moved from October 23 to November 4 after validator support briefly dropped below the required threshold and reset its 14-day countdown.
- Support fell to 26 of 35 validators before recovering, while a later dashboard reading showed 31 votes, two above the minimum needed to maintain majority.
- The amendment bundles technical fixes across tokens, AMMs, vaults, lending and escrow, but does not activate XRPL’s broader native lending protocol.
The XRP Ledger’s fixCleanup3_4_0 amendment is now projected to activate on November 4 after a temporary drop in validator support reset its mandatory two-week countdown. The XRPL amendments dashboard shows that backing fell to 26 of 35 trusted validators on October 21 before recovering above the required threshold about two hours later. The brief loss of majority erased nearly two weeks of accumulated approval despite support returning quickly. The episode highlights the mechanics behind XRPL’s validator-based amendment process.
XRPL Bug Fix Restarts Its Two-Week Activation Window
The amendment originally reached majority status on October 9 and had been projected to activate on October 23. XRPL requires amendments to maintain support from more than 80% of trusted validators continuously for 14 days, which currently means at least 29 of 35 votes. Dropping to 80% or below even once resets the activation window rather than merely pausing it. That governance rule has also affected previous XRPL amendment activation windows.
According to the dashboard, support fell to 26 validators at 12:54 UTC on October 21 and returned to the required majority at 14:46 UTC. A later reading on October 22 showed 31 of 35 validators supporting fixCleanup3_4_0, giving the amendment two votes above the minimum. If that majority holds continuously, activation is projected for November 4 at approximately 14:46 UTC. The timeline remains conditional because another decline to 80% or less would restart the countdown again.
fixCleanup3_4_0 bundles corrections introduced with xrpld 3.4.0 rather than launching a new standalone feature. The package addresses issues affecting tokens, automated market makers, the permissioned exchange, NFTs, vaults, lending and escrow. Its purpose is maintenance and bug remediation across existing and developing XRPL functionality, not the immediate activation of native lending. The amendment follows other technical work delivered through xrpld 3.4.1 and its Batch-related fixes.
The distinction matters because XRPL’s broader lending stack remains below the voting threshold required to begin its own activation countdown. In the later dashboard snapshot, LendingProtocol and LendingProtocolV1_1 each had 19 of 35 votes, while SingleAssetVault had 21. The November projection therefore applies only to fixCleanup3_4_0 and should not be interpreted as a launch date for XRPL lending. The separate lending amendments still require additional validator support before their own two-week approval periods can begin under the network’s existing consensus rules for future protocol changes.