Key takeaways
- XRPL cleanup amendment holds 30 trusted validator votes
- October 23 activation depends on sustained majority support
- Lending Protocol remains below its required approval threshold
The XRP Ledger is approaching another network upgrade, with 30 trusted validators supporting the fixCleanup3_4_0 amendment ahead of a projected October 23 activation.
However, the network's proposed native lending system remains well short of the approval threshold, highlighting the different stages of XRPL's ongoing development.
According to XRPL amendment tracking, fixCleanup3_4_0 has received 30 votes from 36 trusted validators, exceeding the 29 required for approval. The amendment first secured a supermajority on October 9, placing it on course for activation around 09:34 UTC on October 23 if sufficient support continues uninterrupted.
Unlike major feature upgrades, this amendment primarily addresses technical issues affecting existing and proposed XRPL functionality, including token permissions, automated market makers, escrow transactions and lending-related infrastructure.
XRP Ledger's October 23 Upgrade Addresses Token Permission Flaw
One important correction involves the PaymentBurn permission introduced through XRPL's recently activated permission delegation framework.
Under certain circumstances, an account granted permission to burn fungible tokens could also create new trust-line tokens or Multi-Purpose Tokens. Official XRPL documentation recommends against delegating PaymentBurn until fixCleanup3_4_0 becomes active.
The amendment changes validation behavior to prevent payments exercising that permission from crossing a zero balance, closing the unintended token-creation possibility.
The cleanup package also includes corrections for automated market maker clawbacks, token authorization, escrow reserve handling, transaction signatures and calculations involving Single Asset Vaults.
Some fixes concern functionality that has not yet been activated on the public network. Their inclusion in the software release does not mean the corresponding features are already available to users.
XRPL amendments require more than 80% validator support maintained for two consecutive weeks. If backing drops to 80% or below, the activation countdown resets, as happened with an earlier Batch upgrade.
XRP Lending Protocol Still Needs More Validator Support
While the cleanup amendment approaches activation, XRPL's proposed lending infrastructure remains below its required voting threshold.
As of the October 18 snapshot, LendingProtocol and LendingProtocolV1_1 each had 19 supporting validators, while SingleAssetVault had 21. All three remained below the 29 votes required in the 36-validator snapshot.
The proposed lending framework would introduce fixed-term loans funded through pooled assets, with credit assessment and underwriting conducted off-chain.
Single Asset Vaults would allow participants to pool funds, while LendingProtocol would support loan creation and management. The V1_1 amendment adds closed-ended vault structures and accounting changes for interest recognition.
Coinpaper's earlier validator analysis showed the lending proposals already trailing the approval threshold on October 15. Their continued shortfall means there is still no confirmed activation date.
Why the Difference Matters for XRPL
The contrast illustrates how XRPL's amendment process separates technical readiness from network approval. Developers can release code containing new functionality, but trusted validators must independently approve the relevant amendments before those changes become operational.
Recent network upgrades have already introduced additional account permissions and transaction batching, expanding the tools available to developers and financial applications.