XRP Ledger's fix amendment: how the validator vote works

A package of bug fixes called fixCleanup3_4_0 is on track to switch on across the XRP Ledger this Friday, according to CoinDesk. Some of those fixes repair lending code that nobody can use yet, because the lending feature itself has not won approval. This article explains how an XRP Ledger rule change gets voted in, what the patch alters, and why the timing of these separate votes matters.

The change in one paragraph

The XRP Ledger changes its rules through amendments: named bundles of code that sit dormant in the server software until enough validators vote for them. fixCleanup3_4_0 is one such bundle. It closes a token-permission loophole, changes how vaults round amounts, and adjusts how lending code decides that a loan is late or in default. CoinDesk reported that it held exactly 29 votes on Monday, citing the XRPL Dashboard, and is expected to activate around 09:34 UTC on Oct. 23.

The unusual part is the order of events. Ripple has been marketing its lending design to banks and payment firms since June, yet that feature is still 10 votes short of approval. So the network is fixing that code before the code is ever turned on.

Under the hood: how an XRP Ledger amendment vote works

A validator is a server, run independently, that helps the network settle which transactions are valid. The network applies a simple, strict rule to rule changes.

• The reference group is a default trusted list of 35 validators.
• An amendment needs backing from more than 80% of that group, which means 29 validators.
• That support must hold without a break for two consecutive weeks.
• If support drops below the line at any point, the two-week clock resets and starts again from zero.
• Once the clock completes, the amendment activates.

This design trades speed for certainty. A change cannot slip in on a brief spike of support; it needs a sustained supermajority. The cost is that a narrow majority is fragile. fixCleanup3_4_0 sits at exactly the threshold, with zero margin, and its two-week clock had run nine days when CoinDesk checked. If even one validator withdrew support, the countdown would reset. For readers tracking an amendment, the useful number is not only the vote count but the margin above 29 and how long the clock has been running.

What the patch fixes in lending code that is not yet live

The planned lending design works like this. Money comes in when a lender places XRP or another token in a vault. From there, a loan broker extends it to borrowers for a fixed term. The ledger keeps the record of each loan and its repayments, but the credit check happens offchain, in the broker's hands. No collateral is pledged, so if a borrower fails, lenders are protected only by how carefully the broker assessed them. Ripple's target users are payment firms that need short-term cash while cross-border settlements finish.

Because the ledger itself tracks repayments and default status, the rules for rounding and lateness are not cosmetic. They decide when a loan officially counts as late or defaulted, and how amounts held in a vault are rounded. fixCleanup3_4_0 changes both. Fixing this logic while the feature is still switched off means it is corrected before any loan exists.

The package also carries a fix unrelated to lending. CoinDesk, citing the release notes for version 3.4.0 of the xrpld server software, said it shuts a gap where an account whose only permission was to burn, meaning destroy, an issuer's tokens might, in some conditions, mint fresh ones instead. That is a permission bug: a role meant to shrink supply could, in edge cases, expand it.

Who is affected

Token issuers that delegate burn rights to another account gain a tighter permission boundary once the patch activates. Validator operators carry the most direct weight, since any one of them can delay activation by changing a vote. Developers and firms planning to use XRP Ledger lending get corrected rounding and default rules before they write any production code against them.

Lenders in the future system should note the risk the design already states plainly: with no collateral, losses from a bad loan depend on how well the broker judged the borrower. A rule fix in the ledger does not change that, and lenders could lose money.

Status and next steps

CoinDesk reported that the lending amendment has 19 votes, while the vault amendment, which is a separate change, has 21. Neither has started its two-week countdown. So even if lending reached 29 votes immediately, it could not activate before early November.

The near-term item to watch is whether fixCleanup3_4_0 keeps all 29 votes until its scheduled activation on Oct. 23. After that, the question moves to the vault and lending amendments and whether either can build a sustained supermajority.

Sources

• CoinDesk, 19 Oct 2026

AI wrote this summary from the primary documents and reports cited above. It went live automatically after checks that figures match those sources and nothing is copied; there was no human review. It explains a protocol or rule change and is not investment advice.