XRP Ledger Bug Fix Nears Activation as Lending Stalls 10 Votes Short

The XRP Ledger is about to switch on a bug-fix package for lending code that nobody can borrow against yet. The package, called fixCleanup3_4_0, has the 29 validator votes it needs and is in the 14-day countdown that would activate it around 09:34 UTC on Oct. 23, according to the XRPL amendments dashboard.

The code belongs to a system that is still off. Ripple's uncollateralized lending plan holds 19 of the 29 votes required; the vaults that would hold lenders' money hold 21. Neither has begun its countdown, so even if both cleared the bar today, lending could not go live before early November.

That gap is worth sitting with. The plumbing is being repaired before the feature can be used, because the fixes touch code that already exists but is not yet safe to run. The lending protocol and the vault and interest rules that come with it opened for a validator vote earlier, and it is still short.

A Change Needs 29 Votes Held for Two Weeks

Rules on the XRP Ledger move slowly on purpose. A change needs backing from more than 80% of the 35 validators the network trusts by default, which works out to 29, and that support has to hold for 14 straight days. If backing slips to 80% or below, the clock resets.

The dashboard paints the picture. It lists 97 amendments live on mainnet, 10 in flight, and one, fixCleanup3_4_0, in a countdown. That package holds exactly 29 of 35, so it has no votes to spare: one validator pulling support would restart its two weeks.

What the Fixes Change Before Lending Arrives

The xrpld 3.4.0 release introduces two amendments: LendingProtocolV1_1 and fixCleanup3_4_0. LendingProtocolV1_1 extends the vaults and lending protocol with closed-ended vaults that run through subscription, investment and redemption phases, plus cash-basis accounting that counts interest as income only when it is actually paid, rather than booking it all at the moment a loan is made.

fixCleanup3_4_0 bundles the safety work. Among the fixes, it closes a loophole that could let an account allowed only to burn tokens on an issuer's behalf create new ones under certain conditions, according to the release notes. Precision and rounding fixes run across VaultDeposit, VaultWithdraw and VaultClawback so a vault's tracked total assets, available assets and share supply stay consistent. Freeze, authorization and loan-default handling are refined too, including exempting loan defaults from asset freeze.

The same release retires fixAMMOverflowOffer, making it a permanent part of the protocol, and moves the xrpld DEB and RPM packages to packages.xrplf.org with an XRPLF signing key. Operators were told to upgrade to 3.4.0 as soon as possible to keep services running; the software shipped on Sept. 16.

How Lending Would Work if It Passes

The lending protocol docs describe an on-chain, fixed-term, uncollateralized system that pools funds from a Single Asset Vault, with credit decisions made off-chain. A lender deposits XRP or another token into a vault; a broker lends it out for a fixed term and decides, off-chain, whether a borrower qualifies. Borrowers post no collateral, so the broker's judgment is the only thing between the lender and a default.

The published design adds an optional buffer called first-loss capital, which a broker deposits in a separate pseudo-account to absorb losses from defaults. Ripple has pitched the setup to banks and payment companies since June, as a way to borrow cash while a cross-border settlement clears. A June re-audit of the lending changes reported no critical or high-risk findings.

Oct. 23 belongs to the patch, not the product. The lending system's own date stays unwritten until both amendments reach 29 votes and hold there for two weeks. Until then, the borrowing Ripple has been pitching since June is still a promise rather than something a payment desk can use.