XRP Ledger Lines Up fixCleanup3_4_0 for 23 October as Lending Waits

A bundle of corrections to the XRP Ledger has held above the network's voting bar for nine days, which puts it five days from taking effect. fixCleanup3_4_0 reached its supermajority on 9 October and is scheduled to activate at 09:34 UTC on 23 October. Validators have to keep it there for the full two weeks. One dip below the line resets the clock to zero. Three amendments that would switch on lending and vaults are nowhere near the same position, and they sit roughly where they sat a week ago.

What the bundle repairs

Nothing in it is visible to a user. Its heaviest item is in permission delegation, the mechanism that lets one account hand a named power to another. An account granted the power to burn fungible tokens could, in some conditions, create new trust-line tokens or Multi-Purpose Tokens instead of destroying anything, and the fix rejects any payment using that permission where it would cross a zero balance. RippleX patched a separate path to unintended minting in the same 3.4 series. Until this one is live, the ledger's documentation tells operators not to delegate that power at all.

The rest is narrower. Rounding on Multi-Purpose Tokens could let an automated market maker clawback reclaim nothing while still burning the liquidity provider's tokens. Forged XRP-denominated offers on non-fungible tokens are rejected. Escrow restores the owner's reserve when a transaction is cancelled or completed. Vault deposits, withdrawals and clawbacks get precision corrections so that tracked assets, available assets and share supply stay consistent with each other. Several of these cover features that are not switched on yet.

Two counts, two denominators

How much support the amendment actually has depends on which account is read. Coinpaper, filing at 13:16 UTC on Sunday from amendment-tracking data, put it at 30 of 36 trusted validators against 29 required. A week earlier 36Crypto and a KuCoin news flash, both citing the XRPScan explorer, counted 26 of 32, or 81.25%. The sets differ by four. The trusted list is not fixed, so some of that is simply a week passing, but neither account acknowledges the other and we could not establish which set is current.

The countdown does not add up

There is a second gap in the published record, and it is arithmetical. 36Crypto on 11 October and the KuCoin flash a day later both say the activation window opened on 5 October, citing the same explorer. Fourteen days from 5 October lands on 19 October. Every account, those two included, gives 23 October at 09:34 UTC as the earliest activation, and fourteen days from 9 October lands exactly there. CryptoTicker, writing on Saturday, is the only one to timestamp the supermajority, at 09:34:30 UTC on 9 October. The two dates do not reconcile and nobody addresses it.

Lending is still short

The amendments behind the lending market have not moved into position. Coinpaper's Sunday snapshot has LendingProtocol and LendingProtocolV1_1 at 19 validators each and SingleAssetVault at 21, all against the same 29. CryptoTicker, reading an earlier count, put the lending amendment at 17 of 25 on 11 October. Those work out at 53% and 68% of their respective sets, which cannot be placed on one scale. The shape is familiar from last month, when the previous fixCleanup bundle cleared the bar on 11 September with the lending protocol still disabled behind it. This bundle repairs code that lending will run on once it is enabled, including how defaulted loans interact with asset freezes.

Friday is procedural rather than dramatic. If support holds through Thursday, servers apply the change at the scheduled ledger and any operator still on an older build becomes amendment-blocked, unable to validate or process transactions until it updates. If support slips once, the fourteen days start again from whenever it recovers. The lending vote has no clock running at all, and nothing in either published count suggests one starts this month.