The XRP Ledger’s fixCleanup3_4_0 amendment lost its activation countdown less than two days before it was expected to take effect. Validator support fell to 26 of 35 at a Wednesday checkpoint, below the 29 votes required to maintain the network’s 80% approval threshold.
Support recovered within roughly two hours and later rose to 31 validators, but the XRP Ledger’s amendment process requires the threshold to hold continuously for 14 days. The interruption reset the clock and moved the expected activation from October 23 to November 4, based on the XRPL Dashboard and XRPLWin amendment tracker.
The amendment closes a token-creation loophole and adjusts calculations involving vault and lending functions. The broader lending-system amendments remain separate and have not gathered enough support to begin their own activation period.
No source reviewed for this scan identified the reason three validators stopped signaling support. Routine maintenance, configuration changes and deliberate vote changes remain possibilities, but none is established. The episode is a governance delay, not evidence that the loophole was exploited.
The patch is already available in node software. The delayed amendment concerns activation of consensus rules across the production ledger. Operators should distinguish running patched software from the network collectively enforcing the amendment.
TOKEN RECON ASSESSMENT
The safety mechanism worked as designed: insufficient continuous support stopped automatic activation. The weakness is operational coordination, because a fix with broad backing had no margin when three validators dropped out. November 4 remains conditional on uninterrupted support. A second reset, an explanation from affected operators or a change in the trusted-validator set would materially alter the risk picture.
Sources
XRPL Dashboard: Amendment voting status
