Ripple, Pushing Further for XRP Ledger Security Improvements..."They said it was just the beginning, but 287 cases have poured out"

▲ XRP

As the XRP Ledger deployed the rippled 3.1.3 update to the mainnet after AI-assisted security checks, Ripple's core development team announced further improvements.

According to cryptocurrency media U.Today on May 30 (local time), RippleX Engineering Director Vijay Khanna shared the progress of the XRP Ledger AI Red Team via X (formerly Twitter), stating that the rippled 3.1.3 deployment was “just the beginning.” Khanna stated, “An enormous amount of effort went into safely deploying this release to the mainnet,” and that UNL operators upgraded at a record pace.

Version rippled 3.1.3 is an update focused on security and bug fixes. U.Today reported that this version includes bug fixes and improvements related to the fixCleanup3_1_3 amendment, along with a set of fixes related to NFTs, Permissioned Domains, Vaults, and the Lending Protocol.

Ripple launched an AI-assisted red team in March to continuously find vulnerabilities in the XRP Ledger. Two months later, the team, led by Ripple software engineer Mayukha Vadari, released a report detailing the inspection structure, types of bugs found, and lessons learned during the process.

To date, the team has disclosed 287 xrpld issues on GitHub, with 231 open and 49 closed. U.Today reported that these issues are primarily for improving code quality and strengthening defensive depth, and none have affected system stability, availability, or fund security. SDK checks also disclosed 44 issues for xrpl-py, 48 for xrpl.js, and 126 for xrpl-rust, some of which have already been patched.

rippled 3.1.3 has been recorded as the first dedicated security release resulting from the AI-assisted red team's activities. Future scheduled releases, including 3.2.0, are expected to incorporate more fixes from the backlog of identified findings, and Ripple plans to expand cross-functional interaction analysis, conduct Antithesis fault injection testing for new release branches, and perform more comprehensive attack checks on new fixes before mainnet activation.

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