"Validators 100% Unanimous"...XRP Ledger, What amendment received unprecedented approval?

▲ XRP/ChatGPT generated image

The XRP Ledger (XRPL) is nearing the activation of a new amendment. The XRP Ledger ecosystem has entered the process of implementing a key amendment within days, accompanied by an unprecedented record of 100% validator consensus.

U.Today reported on May 24 (local time), citing XRPScan data, that the fixCleanup3_1_3 amendment for XRP Ledger version 3.1.3 has entered a two-week activation period. The estimated activation time is May 27, 2026. Unlike most amendments that only just exceed the 80% passing threshold, this amendment achieved 100% consensus.

The XRP Ledger's amendment system is a procedure to approve changes that affect transaction processing. Fully functional transaction processing changes are introduced as amendments, and validators vote on these changes. If an amendment receives more than 80% support for two weeks, it passes, and the changes are then permanently applied to all ledger versions. A new amendment is required to deactivate an already passed amendment.

fixCleanup3_1_3 is a default pro-amendment that does not require manual voting and achieved 100% consensus. This amendment is a package of fixes related to NFTs, permissioned domains, vaults, and lending protocols. XRP Ledger version 3.1.3 only contains bug fixes and improvements and does not include new features requiring a vote.

This amendment comes as Ripple is overhauling the XRP Ledger's security architecture using artificial intelligence. In March, Ripple announced a revamp of the XRP Ledger's security approach, presenting an AI-centric strategy. The AI-powered red team focuses on continuously analyzing the XRP Ledger codebase and how each feature interacts in a real-world environment.

Ripple also stated that it is investing in modernizing and improving the alignment of the XRP Ledger codebase, along with active testing. It explained that various types of bugs occurring in long-running systems stem not only from individual mistakes but also from structural issues such as limited type safety, inconsistent interaction patterns between functions, insufficient enforcement of immutability, and undocumented or unenforced assumptions. The XRP Ledger 3.1.3 amendment was presented as a step to reflect bug fixes and improvements as an extension of these security enhancement efforts.

*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.*