XRP Ledger Prepares Oct. 23 Upgrade to Fix Minting Bug

The XRPXRP-0.46% Ledger is heading toward a key software upgrade on October 23, 2026. This upgrade addresses a software flaw that could allow delegated accounts to create new tokens instead of destroying them. At the same time, a long-awaited proposal to bring native lending features to the network remains waiting for validator approval.

What Is the XRPL Cleanup Upgrade?

The upcoming patch is officially known as fix Cleanup3_4_0. It is scheduled to go live at approximately 09:34 UTC on October 23, 2026, provided network validators maintain sufficient approval.

For any major change to take effect on the XRP Ledger, at least 80% of trusted validators must approve it. Once an amendment reaches that supermajority, a mandatory 14-day countdown clock begins.

This specific cleanup amendment secured its supermajority on October 9. Data from XRPSCAN shows that by mid-October, approximately 26 to 29 out of 32 to 35 active validators supported the change.

How the Validator Countdown Clock Works

The voting process on the XRP Ledger requires steady support. If validator approval drops to 80% or below at any point before the activation time, the countdown resets.

If a reset occurs, the proposal must secure 80% approval again and hold it for another uninterrupted two weeks before code activation.

Unlike updates that introduce consumer-facing trading products, this release focuses on code hygiene. Introduced in rippled version 3.4.0, the package cleans up logic across automated market makers, asset escrows, permission management, and lending framework infrastructure.

Fixing the Token-Burning Loophole

The primary bug addressed in this update relates to a feature called Permission Delegation V1_1, which was activated on October 8. This feature lets primary account holders grant specific, limited authority to secondary accounts without revealing main secret keys.

One delegate permission, named Paymentburn, was designed to let an authorized secondary account destroy specified tokens. However, developers uncovered a bug where, under specific conditions, the system did the exact opposite by minting tokens instead.

Official documentation for the XRP Ledger explicitly advised node operators and developers against assigning this specific permission until the cleanup update is fully active.

Additional Code Corrections Included

The fix Cleanup3_4_0 patch also contains several secondary repairs to improve overall system consistency:

• Vault calculations receive math adjustments to ensure correct withdrawal amounts.
• Rules determining overdue loan statuses are updated for strict accuracy.
• Automated market maker (AMM) routines are modified so liquidity tokens cannot be destroyed without returning underlying assets.

For everyday XRP users, these changes happen behind the scenes without altering basic wallet usage. Node operators, however, must run compatible server software to remain in consensus with the network after activation.

Native Lending System Remains Stalled

Ironically, while the October 23 patch fixes code related to lending infrastructure, the native lending product itself remains unapproved.

The proposed Native Lending Protocol would allow participants to pool assets and issue fixed-term loans directly on the ledger. Borrowers would not necessarily provide on-chain collateral, relying instead on off-chain credit evaluation by loan brokers.

To activate native lending entirely, three separate amendments must pass the validator voting process:

• Two core amendments defining loan terms and broker interactions.
• The Singleassetvault amendment managing vault mechanics.

As of mid-October, the two lending amendments held only about 17 to 19 supporting votes (roughly 53% approval). The Singleassetvault amendment had approximately 19 to 21 supporting validators. Because all three remain below the 80% threshold, no firm launch date exists for native lending.

Conclusion and Network Outlook

The contrast between the upcoming security patch and the stalled lending proposal highlights the XRP Ledger's governance model. Repairs that secure existing infrastructure gain validator consensus quickly, while major financial features take longer to achieve full agreement.

Past performance of digital assets or network upgrades is not indicative of future results. Holders and node operators should always verify official software updates directly through verified repository channels.