XRPL's fixCleanup3_4_0 patch locks in October 23 as lending amendment stays 10 votes short

XRPL's fixCleanup3_4_0 amendment is set to activate around 09:34 UTC on October 23, after reaching the minimum 29 validator votes needed to pass without any spare support. The bundle, shipped in the xrpld 3.4.0 release, repairs issues across the ledger's new Lending and Vault amendments — neither of which has yet cleared the vote threshold itself, per CoinDesk citing the public XRPL Dashboard tally.

What's in the patch

Three fixes bundled under one amendment name:

• Burn-permission loophole. An account authorized only to burn tokens could, under specific conditions, create new units of that token. The fix tightens the authorization check.
• Vault rounding. Amounts moved into and out of Single Asset Vault accounts rounded in a way that could accumulate error over many operations.
• Loan default rules. Rules governing when a loan in the Lending amendment counts as late or in default are rewritten.

The patch sits in the xrpld 3.4.0 release notes alongside the two amendments it partly repairs. The release packages are now served from packages.xrplf.org and signed with an XRPL Foundation key, per the Foundation's release post.

Where the votes stand

Per the XRPL Dashboard tally as of Monday, October 19:

• fixCleanup3_4_0: 29 of 29 trusted validators voting yes. No spare votes. The two-week countdown started October 9.
• LendingProtocolV1_1 (XLS-66): 19 of 29 validators. 10 short.
• SingleAssetVault (XLS-65): 21 of 29 validators. 8 short.

Neither Lending nor Vaults has started a two-week countdown of its own, so even if both reach 29 votes today, mainnet activation would land no earlier than early November.

Validators have to opt in to the fix amendment — it ships with a DefaultNo vote under the newer governance convention, unlike the earlier default-yes rippled 3.1.3 patch. A single validator dropping back to no would stall the countdown and push the October 23 target.

The lending protocol context

XLS-65 and XLS-66 went to validator vote in July after a devnet opening. The Lending amendment is Ripple's pitch to banks and payment firms building fixed-term loan products directly on the ledger; the Vault amendment holds lenders' funds. The amendments' slow progress through the 29-validator threshold is the pattern — XRPLF's October 9 overflow disclosure in rippled 3.4.1 is the second time in two weeks the ledger has needed a validator-signed fix for amendments shipped but not yet activated.

What to watch

1. The October 23 activation. Any validator dropping support between now and ~09:34 UTC Thursday would push the date. Watch the Dashboard tallies for the fix amendment specifically.
2. Lending/Vaults countdown trigger. Neither has hit 29 yet. If both do before early November, mainnet activation lands roughly two weeks after that vote threshold holds continuously.
3. A second patch bundle. The pattern of ship-then-patch argues for a third fix amendment before Lending goes live, if any issue surfaces in the next two weeks.

Context

Ripple's pitch for Lending on XRPL is a payments-and-banking play — fixed-term loans issued and settled on an L1 that already processes institutional stablecoin flow. The validator-vote threshold has slowed every non-trivial amendment for months. Lending has now been in validator vote since July 2026 without crossing the finish line; today's 19/29 is below the 85% ratio fixCleanup3_3_0 needed in April to activate.

The three bugs this amendment addresses were caught in validator and third-party review before mainnet activation of the amendments they fix. That is the governance system working as intended — slow, but with a working feedback loop between amendment authors and the validator set.