The XRP Ledger (XRPL) has released version 3.3.0, introducing six amendments now subject to validator voting. The release centers on the fixCleanup3_3_0 package, which delivers essential bug fixes for mainnet stability, reduces node RAM usage by over 15%, and accelerates overall network synchronization. For a network that has been steadily expanding its native DeFi capabilities—including Automated Market Makers and a Lending Protocol added in recent versions—the maintenance release represents a key step in maturing those features for production use.

Version 3.3.0 is currently in the validator review stage following a high-profile Ripple vote that demonstrated strong community support for critical network maintenance.

The Ripple Vote and Core Technical Upgrades

The XRP Ledger is an open-source, distributed layer-1 blockchain optimized for low-cost, low-latency cross-border transfers. It relies on a Unique Node List (UNL) of trusted validators to reach consensus without energy-intensive mining. Unlike many blockchains that implement protocol changes through hard forks, XRPL uses an amendment system that activates upgrades only after sustained validator consensus, avoiding chain splits.

Version 3.3.0 adds six proposed changes that require network consensus before they can modify mainnet rules. A recent Ripple vote advanced the fixCleanup3_3_0 package into active validator evaluation across the network.

BREAKING: @Ripple votes 'YES' on fixCleanup3_3_0 amendment to advance @XRPLOperations XRP Ledger 3.3.0 Upgrade

fixCleanup3_3_0 is bundled fixes for Single Asset Vaults, Lending Protocol, Automated Market Makers, permissioned DEX, Checks and pseudo-accounts.

Other dUNL whi… pic.twitter.com/hEGTVsCdsz

— Rednirav (@CryptoRednirav) August 12, 2026

The fixCleanup3_3_0 maintenance package includes essential updates to protocols such as Automated Market Makers and permissioned order books. It also addresses edge-case issues involving Single Asset Vaults, the Lending Protocol, and pseudo-accounts.

On the infrastructure side, the update reduces RAM usage on nodes by more than 15%, which speeds up synchronization across all nodes and enhances long-term network stability. Lower memory requirements also lower the hardware barrier for prospective node operators, which can support broader network participation over time.

Institutional Features and Developer Proposals

Beyond core stability fixes, version 3.3.0 introduces features aimed at enterprise-grade decentralized finance. The ConfidentialTransfer amendment adds private multi-purpose token transactions and compliance-friendly view keys designed for regulators. Similar privacy-preserving features have been pursued by other layer-1 blockchains targeting regulated financial applications, where selective disclosure is a recurring requirement.

The DynamicMPT feature gives token issuers flexible, real-time control over custom asset properties. Ongoing developer support continues to expand the ecosystem, with additional proposals advancing through similar voting processes.

The update also reintroduces the BatchV1_1 amendment, enabling up to eight bundled transactions to execute as a single atomic operation. The PermissionDelegationV1_1 proposal allows account owners to delegate key transaction permissions securely without exposing their primary keys.

Additionally, the Sponsor feature enables a third-party entity to pay transaction fees and hold reserves on behalf of new users. Collectively, these proposals are intended to create a more scalable and accessible foundation for institutional adoption.

Mainnet Activation Thresholds

Any amendment activated for the first time on the XRP Ledger must pass through a transparent governance process. A proposal requires an 80% supermajority of trusted dUNL validators to approve it for two consecutive weeks.

Ripple's positive vote provides critical early support but is not, on its own, sufficient to deploy changes to mainnet. The fixCleanup amendment currently has 8 of the necessary 29 validator votes, meaning the remaining validators will determine whether the package advances to activation or the two-week consensus window resets.

If validator consensus falls below 80% at any point during the two-week period, the timer resets. Node operators who fail to upgrade to version 3.3.0 will become amendment-blocked once the features are activated.

As additional UNL validators cast their votes, participants are monitoring the results closely. This systematic governance process is designed to ensure that only thoroughly vetted software changes reach the mainnet environment.

Source: XRPL.org