XRP Ledger tracks xrpld 3.2.0 bugs ahead of July 29 fixCleanup3_2_0 activation

The XRP Ledger is nearing activation of the fixCleanup3_2_0 amendment on July 29 after reaching 85.71% validator support, while RippleX developer Mayukha Vadari said transaction volume is not always the best measure of whether an XRPL amendment is being used. She pointed to the clawback feature, launched on XRPL in January 2025, arguing that its impact is better assessed through the liquidity or market cap of clawbackable tokens because some assets would not have launched without that capability. Vadari said cross-cutting features may be embedded inside broader transaction flows, making standalone transaction counts less informative. She gave Sponsored Fees and Reserves as an example, saying usage should be tracked through the sponsor field on transactions rather than only through the new SponsorshipSet and SponsorshipTransfer transactions, which may see limited direct use even if the wider feature is active. The planned fixCleanup3_2_0 change is expected to deliver fixes affecting Single Asset Vaults, the Lending Protocol, the permissioned DEX, Multi-Purpose Tokens and permissioned domains. RippleX developers have also said version 3.3.0 is expected in the coming weeks with Batch, Confidential Transfers, Sponsored Fees and Reserves, Permission Delegation and Dynamic MPTs amendments. The broader rollout comes as the XRP Ledger Foundation and XRPL Commons plan a 36-hour XRPL Hackathon in New York from October 24 to 25, the weekend before Ripple's Swell event. Participants will be able to compete across protocol innovation, agentic finance, lending and borrowing, and an open category.