Ripple has voted for the fixCleanup3_3_0 amendment as the proposal has secured support from 8 of 35 trusted XRP Ledger validators during its early voting stage. Summary Ripple has backed fixCleanup3_3_0, a package of fixes included with xrpld version 3.3.0. The amendment currently has 8 of 35 validator votes, leaving it below the activation threshold. Proposed changes cover vaults, lending, AMMs, Checks, the permissioned DEX, and pseudo-accounts. XRP traded near $1.06 as derivatives data showed uneven positioning across major exchanges. XRP Ledger fixCleanup vote remains below activation level XRPL validator voting data cited by community tracker CryptoRednirav shows that Ripple has cast a “yes” vote for fixCleanup3_3_0, taking support for the amendment to 8 of the 35 validators on the default Unique Node List. The vote gives the maintenance package an early endorsement from one of the XRP Ledger’s main contributors, but Ripple cannot approve the amendment alone. Validators make their own decisions, and the proposal must maintain support from more than 80% of trusted validators for two consecutive weeks before it can take effect on the mainnet. With 35 validators in the default configuration, more than 80% support would require at least 29 affirmative votes. The current eight votes do not start the two-week activation period, and no mainnet activation date has been set. Unlike a standalone feature proposal, fixCleanup3_3_0 groups several corrections under one amendment. The official XRPL release notes describe fixes involving Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned decentralized exchange, Checks, and pseudo-accounts. Among the proposed changes, developers have unified freeze and deep-freeze checks for transfers involving pseudo-accounts. The affected transaction types include VaultDeposit, VaultWithdraw, AMMDeposit, AMMWithdraw, LoanBrokerCoverDeposit, and LoanBrokerCoverWithdraw. Other corrections would change how CheckCash and CheckCancel handle an all-zero CheckID, prevent invalid actions involving pseudo-accounts, and fix hybrid offers that disappear from a permissioned order book when an account loses access to its permissioned domain. AMM-related changes address precision loss during deposits, withdrawals, and clawbacks. The package also prevents an AMM from being deleted through an unauthorized transaction type and changes the response produced by a specific AMMWithdraw calculation that would otherwise divide by zero. Version 3.3.0 places six amendments before validators Released on Aug. 6, xrpld version 3.3.0 contains the code needed for fixCleanup3_3_0 and five feature amendments, though installing the software does not activate any of them. As crypto.news reported on Aug. 7, the other proposals are ConfidentialTransfer, BatchV1_1, DynamicMPT, PermissionDelegationV1_1, and Sponsor. Each amendment has a separate function and must pass through the validator process before its rules become part of the mainnet. ConfidentialTransfer would add private transfers for Multi-Purpose Tokens by hiding balances and transfer amounts from the public while keeping them verifiable on the ledger. Authorized parties, including issuers or auditors, could still access information required for compliance under the proposal’s design. BatchV1_1 would let an account package as many as eight inner transactions together, supporting uses such as atomic swaps in which all transaction steps succeed or fail as a group. The revised amendment replaces an earlier Batch version that was disabled after developers found a security problem. PermissionDelegationV1_1 also replaces an earlier proposal. Its rules would let an account give another account limited transaction authority without sharing control of the main private key. DynamicMPT would allow issuers to designate selected Multi-Purpose Token properties as changeable when creating an asset. Sponsor, meanwhile, would let companies or other entities pay transaction fees and reserve requirements for users while leaving control of the users’ accounts and keys unchanged. Alongside the amendment code, version 3.3.0 has retired Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber. Retirement removes the older amendment gates after the underlying rules have operated for an extended period; it does not remove the user-facing functions from the ledger. The release also includes changes to node synchronization, online deletion, ledger-delta assembly, and subscription cleanup. Developers added more tests, adopted the C++23 standard, and changed the server’s system service settings to allow additional time for a controlled shutdown. Node operators have been asked to install version 3.3.0 to maintain service continuity. A server that does not recognize an activated amendment can become amendment-blocked, meaning it can no longer determine the valid state of the ledger. Vault and lending fixes accompany separate feature votes Precision and rounding corrections for Single Asset Vaults and the Lending Protocol form one part of fixCleanup3_3_0, while the vault and lending systems themselves remain subject to separate amendments. Ripple recently backed both proposals, voting in favor of XLS-65 for Single Asset Vaults and XLS-66 for the Lending Protocol. Voting data published on Aug. 10 placed support near 40% for XLS-65 and above 37% for XLS-66, leaving both below the required supermajority. Single Asset Vaults would pool one type of token, which could include XRP, Ripple USD, or another XRPL-issued asset. Depositors would receive shares representing their claims on the assets held by a vault. Liquidity from those vaults could then fund fixed-term loans through XLS-66. Rather than requiring every borrower to post assets worth more than the loan, the proposed framework would rely on off-chain credit checks, compliance reviews, and underwriting. XRPL would record and enforce the agreed loan terms, including interest, repayments, and defaults. Security firm Halborn completed a lending protocol re-audit in June. The firm reported no critical or high-risk findings after reviewing transaction checks, accounting rules, access controls, parameter limits, and state consistency. Halborn identified five findings: one medium-risk issue, two low-risk issues, and two informational items. Its report said Ripple had addressed, accepted, or acknowledged all five, including a vault asset-limit bypass involving loan interest and a missing freeze check in LoanBrokerSet. For U.S. institutions, ledger-level lending would not replace obligations arising from securities, lending, sanctions, consumer-protection, or anti-money-laundering rules. Participating firms would still need to conduct the legal and compliance checks applicable to their activities before using the ledger for execution and record-keeping. XRP rebounds as exchange positioning remains mixed XRP (XRP) traded near $1.06 at publication after recovering from the $1 area, according to current market data. The token had gained almost 3% over the preceding 24-hour period, while trading volume increased by about 16%. CoinGlass data showed a less uniform response in the derivatives market. Total XRP futures open interest fell by more than 0.65% within one hour after recently moving above $2.70 billion, indicating that some leveraged positions had been closed during the rebound. Exchange-level figures also differed. CME XRP futures open interest remained 1.31% higher over 24 hours, while open interest declined on Binance, OKX, Bybit, and several other crypto exchanges. The distinction is relevant to American investors who obtain XRP exposure through regulated products rather than holding the token directly. Recent XRP ETF figures covered by crypto.news showed that Canary’s U.S.-listed fund lost $81.6 million in net assets even as share activity added $82 million, with $159.7 million in unrealized XRP depreciation accounting for the difference.
