One XRP Ledger fix, one missed vote, and it gets “pushed” back by a month. The fix, fixCleanup3_4_0, was originally scheduled to activate on October 23 at 09:34 UTC. The rules are strict: more than 80% (29 votes) of the 35 default trusted validators must pass a check every roughly 15 minutes for 14 consecutive days. Miss just one check, and the countdown resets to zero.
At 12:54 UTC on Wednesday, support in one check plunged to 26 votes, wiping out the countdown on the spot. At 14:46 UTC, it returned to 29 votes, restarting a fresh 14-day countdown and setting the new activation time for November 4 at 14:46 UTC. The margin is also worth noting: the first activation attempt squeaked by with exactly 29 votes and no cushion; support has now recovered to 31/35, two votes above the threshold—but one lapse clears everything. The system allows no tolerance for error.
What does this fix actually do? It closes a real vulnerability: under certain conditions, an account authorized only to destroy an issuer’s tokens could create new tokens. It also adjusts how the whitelist library and lending code calculate when a loan becomes overdue or defaults (xrpld 3.4.0 release notes). This is part of the lending system Ripple has been pitching to banks and payment companies since June—and as of Thursday, that lending system itself was still about 10 votes short, so its countdown hadn’t even started.
One other thing to note: neither of the two tracking dashboards shows which validators went offline. Going offline or restarting a server is recorded the same way as voting against. So when you see the support rate “recover,” what you’re seeing isn’t necessarily genuine approval.
#XRP #XRPL #瑞波
At 12:54 UTC on Wednesday, support in one check plunged to 26 votes, wiping out the countdown on the spot. At 14:46 UTC, it returned to 29 votes, restarting a fresh 14-day countdown and setting the new activation time for November 4 at 14:46 UTC. The margin is also worth noting: the first activation attempt squeaked by with exactly 29 votes and no cushion; support has now recovered to 31/35, two votes above the threshold—but one lapse clears everything. The system allows no tolerance for error.
What does this fix actually do? It closes a real vulnerability: under certain conditions, an account authorized only to destroy an issuer’s tokens could create new tokens. It also adjusts how the whitelist library and lending code calculate when a loan becomes overdue or defaults (xrpld 3.4.0 release notes). This is part of the lending system Ripple has been pitching to banks and payment companies since June—and as of Thursday, that lending system itself was still about 10 votes short, so its countdown hadn’t even started.
One other thing to note: neither of the two tracking dashboards shows which validators went offline. Going offline or restarting a server is recorded the same way as voting against. So when you see the support rate “recover,” what you’re seeing isn’t necessarily genuine approval.
#XRP #XRPL #瑞波