An XRP Ledger cleanup patch has lost its earlier October activation timetable after a temporary drop in validator support restarted the required two-week waiting period.
The fixCleanup3_4_0 amendment was projected to activate on October 23 if its majority held. XRPLWin now lists a conditional November 4 activation at 14:46 UTC, with 31 of the 35 validators in its tracked set supporting the change.
The revised countdown is a fresh development since our report on the patch’s earlier progress toward activation. That report distinguished the cleanup work from separate proposals to enable lending, which still lack sufficient support.
A short interruption can restart a long waiting period
The XRP Ledger’s amendment process requires more than 80% support for two consecutive weeks. With the tracked set of 35 validators, at least 29 need to support the change.
The network checks amendment status periodically through flag ledgers. Losing the required majority resets the waiting period even if support returns soon afterwards. Recovering the votes does not restore the time already accumulated.
CoinDesk reported that support briefly fell to 26 on Wednesday before recovering. The current trackers corroborate the later activation estimate; they do not establish the identity or motivation of each validator missing from an earlier count.
That distinction matters because an observed reduction in support is not automatically evidence of a coordinated policy decision. A snapshot of counted votes alone cannot explain every server’s circumstances.
The new estimate remains conditional
The current 31 supporting votes leave the tracked amendment above its threshold. They do not remove the requirement to maintain sufficient backing throughout the new waiting period.
A calendar date shown by an explorer is therefore an estimate based on the present majority state. Another loss of support could change it again before activation.
For operators, installing software and activating its transaction-rule changes are separate steps. Software can include support for an amendment while the network continues enforcing the older rules until the voting process completes.
That process gives participants time to prepare for a consensus change. It also means that an amendment approaching the end of its waiting period can still be delayed without the network itself having stopped processing transactions.
Lending has not acquired approval through the cleanup vote
XRPLWin separately showed 19 of 35 votes for LendingProtocol and 21 for SingleAssetVault. Those entries remained in voting status, below the majority needed to start their own activation periods.
Support for a cleanup amendment cannot be counted as approval for those features. Each amendment has its own voting and activation state, even where their code or intended uses are related.
The immediate news is a delay in the patch’s deployment, not the launch of a lending service or evidence of a successful attack. The next milestone is whether its renewed majority survives the waiting period and the network reaches the revised activation point.