A broad package of XRP Ledger protocol fixes is on course to activate on October 23, putting corrections for vault and lending code in place before the network's proposed lending system has secured approval. The amendment, called fixCleanup3_4_0, had the minimum validator backing required to remain in its activation window as of Monday, according to an independent review of the network's amendment status.

The package is expected to take effect at about 09:34 UTC on October 23 if support remains above the threshold through the full two-week period. CoinDesk reported that 29 of the 35 validators on the default trusted list supported the amendment, exactly the number needed for approval. Because there were no extra votes at that count, a validator withdrawing support could interrupt the process and restart the clock.

Related reporting: XRPL 3.4.0 adds closed-ended lending vaults

A cleanup across several protocol areas

The XRP Ledger Foundation's release notes describe fixCleanup3_4_0 as a collection of amendment-gated corrections spanning Single Asset Vaults, the Lending Protocol, automated market makers, the permissioned decentralized exchange, trust lines, NFTs, Multi-Purpose Tokens, escrow, sponsorship and transaction signing. The official amendment documentation lists the package under identifier 98433DD001A5737F773D74F8CA2A25A065089C73B2E611C760BAF369E4FECA76.

Among the changes, vault deposits, withdrawals and clawbacks would use more precise rounding so recorded assets are not over- or under-delivered. Loan lateness, impairment and default checks would require a due date to have strictly passed. The package also adds distinct signing prefixes for sponsor and counterparty signatures, closes a token-permission edge case involving payments that cross a zero balance, and tightens several checks around credentials and permissioned trading.

Lending is still waiting for separate approval

Activation of the cleanup package would not switch on the lending system. The underlying Lending Protocol and Single Asset Vault amendments require their own validator majorities and two-week approval periods. CoinDesk reported 19 votes for lending and 21 for vaults on Monday, both below the 29-vote threshold. The lending design would let a lender place XRP or another asset in a vault while a loan broker extends fixed-term credit and makes an offchain decision about the borrower's risk.

That separation is important for users and infrastructure operators. For holders, fixCleanup3_4_0 is a rules update rather than a token swap or a lending-product launch. For server operators, the XRPL Foundation's version 3.4.0 release notes advise upgrading to maintain service continuity as amendments become active. The newer 3.4.1 release also contains security and stability fixes, so operators should follow the current supported-release guidance rather than treat the cleanup amendment as a standalone software package.

Why the network uses an activation window

XRPL amendments do not become binding when code is first published. Validators signal support, and a proposed rule change must keep the required majority for two consecutive weeks before it activates. That delay gives infrastructure providers time to install compatible software and makes the change visible before it becomes part of consensus. Once enabled, an amendment permanently changes how subsequent ledgers interpret the covered transactions; reversing its effect would require another amendment. The process reduces surprise, but it also means a scheduled activation can move if the support level changes.

What remains uncertain

The verified development is that a comprehensive cleanup amendment is nearing activation while the features it partly repairs remain disabled. The October 23 timing still depends on validator support holding through the activation window. Even if lending and vault support rises later, each amendment would need to satisfy the network's governance process before the system could be used on the public ledger.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.