- Explanation of the AMM amendment delay due to an edge case bug during integration testing.
- Details on the proposed fix to address the AMM bug and its integration into the upcoming Rippled 2.1 release.
- Divergent perspectives between Ripple CTO and XRPL community regarding the activation timeline post-fix.
In a recent development surrounding the anticipated activation of the Automated Market Maker (AMM) amendment on the XRP Ledger (XRPL), Ripple’s Chief Technology Officer, David Schwartz, has emerged to address the setbacks and potential solutions.
Unfortunately, that probably wouldn’t give people quite enough time to upgrade and would risk amendment blocking too many nodes. At least an extra week or two is probably going to be needed.
— David “JoelKatz” Schwartz (@JoelKatz) February 10, 2024
The AMM amendment, designed to introduce automated market maker capabilities to the XRPL, encountered a hurdle when certain validators withdrew their support due to a bug identified during extensive integration testing conducted by RippleX.
Schwartz shed light on the nature of the bug, clarifying that it pertains to an edge case effect within the AMM functionality, which could impede multiple AMM transactions from executing simultaneously on the ledger. However, he reassured the community that the bug does not compromise the stability of the ledger.
Efforts to resolve the issue have been underway, with a proposed fix aimed at eliminating the identified edge case. This fix, intended for both the core ledger and AMM code, has been incorporated into the upcoming Rippled 2.1 release.
Updates from XRPL validator ‘Vet’ indicate that the fix has been merged and is poised for publication in the Rippled 2.1 release candidate. Anticipation surrounds the release, with ‘Vet’ estimating one to two weeks of testing before the formal rollout.
Schwartz’s perspective diverges from some in the community regarding the timeline for AMM activation. While ‘Vet’ predicts that the activation timer may commence shortly after the release of Rippled 2.1, Schwartz believes additional time is needed to facilitate node upgrades and minimize disruptions. He suggests a delay of at least another week or two before restarting the activation timer.
Notably, XRPL amendments require sustained support from at least 80% of trusted validators over a two-week period for mainnet activation. Failure to maintain this threshold results in temporary rejection, with the two-week countdown resetting.
As stakeholders await further developments, attention remains focused on achieving consensus and navigating the complexities of integrating new features into the XRPL ecosystem.
Disclaimer: Please note that the viewpoints and perspectives expressed by the author, as well as any individuals referenced in this article, are intended solely for informational purposes. They should not be construed as financial or investment advice. It’s important to acknowledge that investing in or trading cryptoassets carries inherent financial risks.