"85% Validator Approval"...XRP Ledger, Security System Upgrade

▲ XRP

The XRP Ledger has ushered in the 3.2.0 era, with significant overhauls to its security system.

According to cryptocurrency media outlet U.Today on July 29 (local time), the XRP Ledger's fixCleanup3_2_0 amendment was activated on the mainnet on July 28. It secured 85.71% support, with 30 out of 35 validators voting in favor. XRPL 3.2.0 has been designated as the new minimum version required for mainnet operation.

Hussein Zangana, Community Manager at the XRP Ledger Foundation, stated via X (formerly Twitter), "The moment the switch was flipped, the XRP Ledger improved by a level." This amendment corrected precision and rounding errors in single-asset vaults and lending protocols. It also supplemented permissioned decentralized exchanges and permissioned domains. Additionally, it added non-standard multi-purpose token quantity verification and an immutability check function to inspect ledger states.

This upgrade is an extension of Ripple's ongoing efforts to strengthen XRP Ledger security. Last March, Ripple announced plans to form a dedicated red team to continuously explore network vulnerabilities using artificial intelligence. Subsequently, XRPL 3.1.3, including fixCleanup3_1_3, was distributed as the first security-only version. In June, XRPL 3.2.0, which further supplemented identified issues, was released.

XRPScan advised that nodes using versions 3.1.0 or lower might be in a state where the amendment is blocked. These nodes must upgrade to 3.2.0 to apply the new amendment. Upbit, an exchange holding over 6.4 billion XRP, has also begun supporting RLUSD deposits and withdrawals based on the XRP Ledger. The trading pairs consist of Korean Won, Bitcoin (BTC), and USDT.

[Article Key Summary]

-The XRP Ledger's fixCleanup3_2_0 amendment was activated on the mainnet, gaining 85.71% validator support.

-XRPL 3.2.0 reflects security and integrity improvements for key features such as lending protocols and permissioned decentralized exchanges.

-Nodes using versions 3.1.0 or lower must upgrade to 3.2.0 to apply the new amendment.

*Disclaimer: This article is for investment reference only, and we are not responsible for any investment losses based on it. The content should be interpreted for informational purposes only.*