Ripple Backs fixCleanup3_3_0 as XRPL 3.3.0 Upgrade Advances

Ripple casts early vote for XRPL maintenance package

XRPL validator records tracked by community monitor CryptoRednirav show that Ripple has voted yes on the fixCleanup3_3_0 amendment, bringing support to 8 of the 35 validators on the default Unique Node List (dUNL) during the amendment's initial voting phase. The endorsement is an important early signal from one of the ledger's primary contributors, but it falls well short of the supermajority needed for activation on mainnet.

What fixCleanup3_3_0 includes

fixCleanup3_3_0 is not a single new feature but a maintenance package that consolidates numerous corrections across core XRPL systems. The fixes target areas that developers say improve safety, prevent edge-case failures, and close subtle logic gaps. Key areas addressed include:

Vaults and Lending

• Precision and rounding corrections for Single Asset Vaults and the Lending Protocol. These changes help avoid accounting inconsistencies when depositors receive share tokens representing claims on pooled assets.
• Fixes related to vault deposit and withdrawal logic, and to loan broker cover transactions. These adjustments reduce the risk of incorrect state changes when interest calculations or asset limits interact with lending flows.

Automated Market Makers (AMMs)

• Corrections to prevent precision loss during AMM deposits, withdrawals, and clawbacks.
• Protection against AMM deletion via unauthorized transaction types and fixes to calculations that previously risked division-by-zero outcomes during AMMWithdraw operations.

Checks, Permissioned DEX, and Pseudo-Accounts

• Changes to how CheckCash and CheckCancel treat an all-zero CheckID, preventing invalid states.
• Unified freeze and deep-freeze checks for transfers involving pseudo-accounts, covering transaction types such as VaultDeposit, VaultWithdraw, AMMDeposit, AMMWithdraw, LoanBrokerCoverDeposit, and LoanBrokerCoverWithdraw.
• A fix for hybrid offers that could vanish from a permissioned order book when an account lost access to its permissioned domain.

Collectively, these repairs aim to make multi-feature interactions on XRPL more robust as the network evolves to support more complex tokenization, lending, and AMM use cases.

xrpld 3.3.0 bundles six amendments

The server release xrpld 3.3.0, published on Aug. 6, contains the code necessary for fixCleanup3_3_0 and five other amendments. Installing xrpld 3.3.0 enables node operators to recognize these amendments when they are activated, but installation alone does not flip any amendment on the ledger. The other amendments in the release are:

• ConfidentialTransfer: Introduces private transfers for Multi-Purpose Tokens by concealing balances and transfer amounts from the public ledger while allowing authorized parties (issuers, auditors) to view data for compliance.
• BatchV1_1: Enables bundling up to eight inner transactions into a single atomic package, supporting multi-step operations that must all succeed or fail together. This revision replaces a previous Batch version disabled after security concerns.
• DynamicMPT: Lets issuers mark selected Multi-Purpose Token properties as mutable at issuance time.
• PermissionDelegationV1_1: Allows account-level delegation of limited transaction authority without sharing the main private key; this replaces an earlier delegation proposal.
• Sponsor: Enables external entities to pay transaction fees and reserve requirements for users while leaving user account keys intact.

Version 3.3.0 also retires a set of older amendments — Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber — a housekeeping step that removes their amendment gates after the community has operated under those rules for a significant period.

The release includes operational improvements too: node synchronization changes, online deletion refinements, ledger-delta assembly updates, subscription cleanup, expanded test coverage, adoption of C++23, and server shutdown timing adjustments for safer controlled stops.

Validator process and activation threshold

Amendment activation on XRPL requires sustained support from validators. For fixCleanup3_3_0 to activate on mainnet, it must maintain affirmative votes from more than 80% of the trusted validators for two consecutive weeks. With the default dUNL set at 35 validators, that threshold translates to at least 29 yes votes. At the time of reporting, the amendment had eight yes votes and therefore has not started the two-week activation countdown.

Validators are independent operators and will evaluate the amendment code, effects on ledger state, and operational risks before changing their vote. Ripple's yes vote is influential, but it cannot unilaterally force activation; community and institutional validators will weigh the package against their risk and compliance needs.

How fixCleanup3_3_0 relates to vault and lending enhancements

While fixCleanup3_3_0 corrects precision and logic issues, the fundamental feature amendments for Single Asset Vaults (XLS-65) and the Lending Protocol (XLS-66) are separate votes and remain under review by validators. Ripple has voted in favor of both XLS-65 and XLS-66, but voting data showed support near 40% for Single Asset Vaults and roughly 37% for the Lending Protocol at the last update — still well below the supermajority.

Single Asset Vaults aim to pool a single token type (for example XRP or an issued stablecoin) and issue shares representing depositor claims. XLS-66 would permit fixed-term loans funded by vault liquidity, where underwriting, compliance checks, and credit decisions could be performed off-chain while loan terms are recorded on-ledger. The proposals include governance and accounting rules to enforce interest, repayments, and defaults.

Security firm Halborn's re-audit of the lending protocol in June found no critical or high-severity issues, reporting one medium, two low, and two informational findings. Halborn noted that Ripple had addressed or acknowledged these items, including a vault asset-limit bypass related to loan interest and a missing freeze check in LoanBrokerSet. These audits are part of the due diligence as the XRPL treasury of features expands.

Network operations and upgrade guidance

XRPL developers have urged node operators to install xrpld 3.3.0 to maintain service continuity. A server that does not recognize an activated amendment can become amendment-blocked and lose the ability to validate the ledger state accurately. Operators who wish to participate in the validator decision process should run the updated software and test their environments against the new rules in staging before switching votes on mainnet.

Market reaction and derivatives positioning

At publication, XRP traded near $1.06 after recovering from the $1 region, gaining roughly 3% over 24 hours with about a 16% increase in trading volume. The derivatives market showed mixed behavior: CoinGlass data reported a modest decline in total XRP futures open interest shortly after a rebound above $2.7 billion, suggesting that some leveraged long positions were trimmed as prices moved.

On an exchange-by-exchange basis, CME's XRP futures open interest ticked up by 1.31% over 24 hours, while major crypto venues including Binance, OKX, and Bybit showed declines in open interest. These divergences matter for institutional investors who obtain XRP exposure via regulated futures or ETFs rather than holding spot tokens.

Recent U.S. ETF flows for XRP-based products revealed discrepancies between net asset changes and share activity: for example, Canary's U.S.-listed fund recorded $82 million in share activity but a net asset loss of $81.6 million, driven by $159.7 million in unrealized XRP depreciation. Those figures underscore how market structure and product wrapper mechanics can produce different outcomes for regulated products versus spot holders.

Implications and next steps

fixCleanup3_3_0 is an important maintenance step that reduces risk as XRPL grows its tokenization, AMM, and lending functionality. However, the amendment's current level of support is insufficient to trigger activation. Validators will continue to review code and operational impacts, and node operators are being advised to upgrade to xrpld 3.3.0 to avoid potential amendment-blocking.

If the amendment reaches the 80%+ threshold and sustains it for two weeks, the fixes would become active and help stabilize interactions among vaults, lending, AMMs, checks, permissioned DEX flows, and pseudo-accounts. Until then, the vote reflects an incremental but cautious progression toward a more feature-rich XRPL ecosystem.

For traders and institutional participants, the ongoing amendment process and protocol audits are signals that XRPL is preparing for broader decentralized finance use cases, but market participants should continue to monitor validator votes, security audits, and derivatives positioning to assess risk around network upgrades and token exposure.