XRP Ledger fixCleanup3_3_0 Secures Majority Ahead of September Activation

2 hour ago 2 sources neutral

Key takeaways:

  • XRP Ledger's 82.86% consensus signals robust validator alignment, yet activation remains conditional until September.
  • Protocol cleanup addressing DeFi edge cases suggests preparation for institutional-grade lending and AMM adoption.
  • Node operators must upgrade promptly; support below 80% resets the two-week clock.

The XRP Ledger is moving toward a significant protocol amendment as fixCleanup3_3_0 has secured 82.86% consensus and entered its two-week activation window. The amendment, introduced in the xrpld version 3.3.0 release, began voting on August 6 and achieved majority on August 28 with 29 Yes votes.

According to XRPScan data, the fix is expected to activate on the XRP Ledger mainnet on September 11, 2026. This date is the earliest possible activation, not a guarantee; if support falls to 80% or lower at any point, the amendment will be rejected and the 14-day period restarts.

Hussein Zangana, known as Vet, highlighted the milestone and urged node operators to upgrade their nodes in time so they can keep operating once it activates.

The bundled amendment includes a collection of fixes for Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, Checks, and pseudo-accounts. It unifies freeze and deep freeze checks for transfers to and from pseudo-accounts across several transaction types, and changes CheckCash and CheckCancel to reject an all-zero CheckID with temMALFORMED during preflight instead of tecNO_ENTRY during processing.

Other fixes include removing hybrid offers from the open order book when an account loses access to a permissioned domain, correcting AMM liquidity quality estimates for permissioned DEX order books, and changing AMMWithdraw to return tecAMM_FAILED rather than dividing by zero. The upgrade also adds precision loss checks to AMMDeposit, AMMWithdraw, and AMMClawback when fixAMMv1_3 is enabled, and strengthens invariants to ensure an AMM can only be deleted by specific transactions. Additional checks ensure deleting a ledger entry backed by a pseudo-account also deletes the pseudo-account, and transactions signed by a pseudo-account fail with tefBAD_AUTH.

Finally, fixCleanup3_3_0 changes CredentialCreate to reject a pseudo-account in the Subject field with tecPSEUDO_ACCOUNT and DepositPreauth to reject a pseudo-account in the Authorize field with tecPSEUDO_ACCOUNT.

Disclaimer

The content on this website is provided for information purposes only and does not constitute investment advice, an offer, or professional consultation. Crypto assets are high-risk and volatile — you may lose all funds. Some materials may include summaries and links to third-party sources; we are not responsible for their content or accuracy. Any decisions you make are at your own risk. Coinalertnews recommends independently verifying information and consulting with a professional before making any financial decisions based on this content.