Ripple's Chief Technology Officer, David Schwartz, responded to recent issues with Automated Market Makers (AMMs) on the XRP Ledger (XRPL), clarifying the situation and providing insights into Ripple's AMM functionality. Despite celebrating the launch of AMMs on Friday, a bug emerged shortly afterward, leading to their temporary suspension. The RippleX developer team is actively addressing this issue, identifying discrepancies in multiple AMM liquidity pools and working on solutions.
Schwartz emphasized that the AMM glitch was not caused by the single-sided deposit feature, reiterating his previous warning about potential price impacts and slippage during deposit transactions. He advised users to review price impacts before submitting transactions and recommended frontend apps to display this information for user awareness.
RippleX Developer Advocates for Canary Network on XRPL: Enhancing Testing and Deployment Processes
In response to the incident, RippleX developer Wietse Wind proposed the creation of a Canary Network on Ripple's layer-1 blockchain. This network would serve as a test-bed for major upgrades, tools, and products before deployment on the mainnet. Wind believes that such a testing ground would have prevented the recent AMM issue on XRPL.
The call for a Canary Network underscores the importance of rigorous testing and validation processes in the development and deployment of blockchain features. As Ripple continues to innovate on XRPL, implementing safeguards like Canary Networks may enhance the reliability and stability of its ecosystem.