Ripple has cast its vote in favor of the fixCleanup3_3_0 amendment on the $XRP Ledger, giving the XRPL 3.3.0 upgrade its first significant endorsement from one of the network's primary contri
Ripple has cast its vote in favor of the fixCleanup3_3_0 amendment on the $XRP Ledger, giving the XRPL 3.3.0 upgrade its first significant endorsement from one of the network's primary contributors.
The fixCleanup3_3_0 proposal is a bundled maintenance package that addresses targeted fixes across several protocol areas, including Single Asset Vaults, the Lending Protocol, Automated Market Makers (AMMs), Checks, and pseudo-accounts. It is one of six amendments introduced alongside the 3.3.0 release, which also includes Confidential Transfer, BatchV1_1, DynamicMPT, PermissionDelegationV1_1, and Sponsor.
Beyond the amendments themselves, the 3.3.0 release brings meaningful performance improvements. Developers have flagged a reduction in memory usage of between 10% and 15%, better online delete and node sync performance, and roughly 60 bug fixes identified through an internal AI red team process.
Ripple's vote carries weight as an early signal, but it does not determine the outcome alone. Eight of the 35 Unique Node List (UNL) validators currently support the fixCleanup3_3_0 amendment. Mainnet activation requires the proposal to hold more than 80% validator support, equivalent to at least 28 of 35 UNL validators, for two consecutive weeks before the changes take effect permanently on the network.
That governance structure is standard for the XRP Ledger. Once an amendment clears the 80% threshold for the required two-week period, the change applies permanently to all subsequent ledger versions. Validators make independent decisions, and the proposal can fail or be delayed if support drops below the threshold at any point during that window.
Node operators face a practical deadline tied to the process. Any server that has not upgraded to xrpld 3.3.0 before the amendments activate risks becoming amendment-blocked, a status that cuts the node off from consensus and prevents it from reading or submitting new transactions.
The broader 3.3.0 upgrade is positioned as a step toward institutional readiness for the XRP Ledger, with features spanning privacy for tokenized assets, atomic transaction batching, delegated account permissions, and sponsored network fees.
Sources:crypto.news: XRP Ledger upgrade gains Ripple vote for bundled fixesXRPL.org: Amendments documentationCoinGape: Ripple votes in favor of fixCleanup proposal
