EN ▼
Favorites
My Favorites
View All
Market Cap Price 24h%

Disclaimer: Content does not constitute investment advice. Trading involves risks—please invest with caution!

XRP ledger upgrade is supported by Ripple's vote and includes bundled repairs

2026-08-13 15:46:04
Bookmark

Ripple voted for the fixCleanup3_3_0 amendment, which had 8 votes in support in the early voting phase

Summary

Ripple has voted for the fixCleanup3_3_0 amendment, which is included in xrpld version 3.3.0 and is a collection of fixes. Currently, the amendment has received 8 votes out of 35 verification nodes and has not yet reached the activation threshold. The proposed changes cover treasury, lending, automated market makers (AMM), checks, licensed decentralized exchanges (DEX), and pseudo-accounts. XRP is trading at close to $1.06, and derivatives data shows that positions are unevenly distributed among major exchanges.

XRP Ledger fixCleanup voting is still below the activation level

XRPL verification node voting data quoted by community tracking platform CryptoRednirav shows that Ripple has voted "yes" for the fixCleanup3_3_0 amendment, giving the amendment 8 votes in support of the 35 verification nodes in the default unique node list. The vote provided early recognition for the maintenance package from one of XRP Ledger's major contributors, but Ripple was unable to approve the amendment alone. Verification nodes make their own decisions, and the proposal must be supported by more than 80% of trusted verification nodes for two consecutive weeks before it can take effect on the main network. With 35 verification nodes in the default configuration, more than 80% support means at least 29 votes in favor are needed. Currently, the two-week activation period has not yet been launched for 8 votes, and the activation date for the main network has not yet been determined.

fixCleanup3_3_0 contains multiple fixes

Unlike stand-alone feature proposals, fixCleanup3_3_0 consolidates multiple amendments under one amendment. The official XRPL release describes repairs involving single asset vaults, loan agreements, automated market makers, licensed decentralized exchanges, checks and fake accounts. One of the proposed changes unifies transfer freezing and deep freezing inspections involving fake accounts. The transaction types affected include VaultDeposit, VaultWithdraw, AMMDeposition, AMMThithdraw, LoanBrokerCoverDeposit and LoanBrokerCoverWithdraw. Other fixes will change the way CheckCash and CheckCancel handle all-zero CheckIDs, prevent invalid operations involving fake accounts, and fix an issue where mixed orders disappear from licensed order books when accounts lose access to their licensed domains. AMM-related modifications address the issue of precision losses in the deposit, withdrawal and withdrawal processes. The package also prevents AMM from being deleted through unauthorized transaction types and changes the response generated by specific AMMThdraw calculations that would otherwise result in division by zero.

Version 3.3.0 Submit six amendments to the verification node

Version 3.3.0 of xrpld, released on August 6, contains the code required for fixCleanup3_3_0 and five feature fixes, but the installation software will not activate any of them. Other proposals include ConfidentialTransfer, BatchV1_1, DynamicMPT, PermissionDelegationV1_1 and Sponsor. Each amendment has independent functions and must pass the verification node process before it can become a main-network rule. ConfidentialTransfer will add a private transfer function to the multi-function token, making it verifiable but not public by hiding the balance and transfer amount. Authorizing parties (such as issuers or auditors) can still have access to information needed for compliance based on the proposal design. BatchV1_1 allows one account to package up to eight internal transactions together, supporting application scenarios such as atomic exchanges, where all transaction steps either succeed or fail. This revision replaces an earlier Batch version that was disabled due to security issues. PermissionDelegationV1_1 also replaces earlier proposals, with rules that allow one account to grant limited transaction rights to another without sharing control of the master private key. DynamicMPT allows issuers to designate selected multifunction token attributes as changeable when creating assets. Sponsor allows a company or other entity to pay transaction fees and reserve requirements for users while maintaining control of user accounts and keys. In addition to the amendment code, version 3.3.0 also removed Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversal Number. The removal operation eliminates old amendment gating after the underlying rules have been running for a long time, and does not remove user-facing functions from the ledger. This version also includes changes to node synchronization, online deletion, incremental ledger assembly, and subscription cleanup. Developers added more testing, adopted the C++23 standard, and changed the server's system service settings to allow more time for controlled shutdowns.

Node operators need to install version 3.3.0 to maintain service continuity

Servers that cannot identify the activated amendment may be blocked by the amendment, making it impossible to determine the valid status of the ledger.

Treasury and loan repair comes with independent function voting

Precision and rounding corrections to single-asset treasury and lending agreements are part of fixCleanup3_3_0, while the treasury and lending systems themselves still need to pass separate amendments. Ripple recently supported both proposals, voting in favor of XLS-65 (single asset vault) and XLS-66 (loan agreement). Voting data released on August 10 showed that XLS-65's support rating was close to 40%, and XLS-66 exceeded 37%, both failing to reach the required absolute majority. The single-asset vault will pool one type of token, including XRP, Ripple USD, or other XRPL issued assets. Depositors will receive a share representing their interest in treasury assets. The liquidity of these vaults can then be used to fund fixed-term loans through XLS-66. The proposed framework does not require every borrower to provide assets whose value exceeds the loan amount, but instead relies on off-chain credit reviews, compliance checks and underwriting. XRPL will record and enforce agreed loan terms, including interest, repayments and defaults. Security firm Halborn completed a re-audit of the loan agreement in June and found no serious or high-risk issues, reviewing transaction inspections, accounting rules, access controls, parameter restrictions and status consistency. Halborn identified five issues: one medium-risk issue, two low-risk issues, and two informational projects. Its report states that Ripple has resolved, accepted or confirmed all five issues, including a treasury asset limit bypass loophole involving loan interest and a missing freeze check in the LoanBroker Set. For U.S. institutions, book-level lending does not replace obligations arising from securities, lending, sanctions, consumer protection, or anti-money laundering regulations. Participating institutions still need to conduct legal and compliance inspections of their activities before using ledgers for execution and record-keeping.

XRP rebounded, with exchange positions in different directions

According to current market data, XRP traded close to US$1.06 at press time after recovering from the US$1 region. The token has risen nearly 3% in the past 24 hours, and transaction volume has increased by approximately 16%. Data from the derivatives market showed mixed reactions. The total open interest in XRP futures fell more than 0.65% in an hour after recently exceeding US$2.7 billion, indicating that some leveraged positions were closed during the rebound. Data at the exchange level also varies. Open interest in CME XRP futures still rose 1.31% in 24 hours, while open interest on Binance, OKX, Bybit and several other cryptocurrency exchanges fell. This difference is relevant for U.S. investors who gain XRP exposure through regulated products rather than directly holding tokens. Recent data showed that Canary's U.S. -listed funds lost $81.6 million in net assets, a difference caused by a $159.7 million unrealized XRP devaluation despite a $82 million increase in equity activity.

Disclaimer:

All content published on this website, including hyperlinks, related applications, forums, blogs, and other media accounts, originates from third-party platforms and their users. CoinMarketInsight makes no representations or warranties of any kind regarding the website or its content. All blockchain-related data and materials are provided for informational and research purposes only and do not constitute financial, legal, or investment advice. Users and third parties are solely responsible for the content they publish. CoinMarketInsight shall not be liable for any losses arising from the use of this website. You should exercise caution and conduct your own independent research, review, analysis, and verification before making any decisions.

Read Full Article
More News
TOP

TOP