0
0
RippleX Addresses Technical Issues with Automated Market Maker Pools on XRP Ledger
Ripple’s developer arm, RippleX, acknowledged that several Automated Market Maker (AMM) pools introduced on the XRP Ledger (XRPL) faced technical challenges hindering transaction processing. In a statement released on X, the developers highlighted a discrepancy impacting the DEX payment engine’s routing of liquidity through AMM pools and order books in complex payment path scenarios.
“The discrepancy affected how the DEX payment engine routes liquidity through AMM pools and order books in some complex payment path scenarios.”
David Schwartz, Ripple’s CTO, clarified that the issue was not linked to the single-sided deposit feature, which aligns with the intended AMM design functionality. He emphasized the importance of reviewing price impact before transaction submission, especially in pools with limited liquidity, advocating for transparent display of this information in user interfaces.
“Single-sided deposits allow for a more streamlined user experience, but can lead to price impacts when pools have less liquidity. It’s best for users to review the price impact in their tooling before submitting a transaction and front-end apps should display this information to users.”
AMMs were unveiled on XRPL on March 22 following a two-year anticipation within the community. The initiative aimed to enhance liquidity sources and trading prospects for XRPL users. Nevertheless, due to initial challenges, users are cautioned against depositing new funds into these pools until the technical hurdles are overcome.
RippleX disclosed that a potential solution is currently undergoing community evaluation and will soon undergo an amendment voting process.
‘Canary Network’ Proposal for XRPL
XRPL developer Wietse Wind proposed the concept of a Canary network for the blockchain ecosystem in response to the issues encountered during the AMM launch. Wind emphasized the necessity for thorough testing with real value on a separate network to address vulnerabilities before deploying changes on the mainnet.
“The recent finding of a bug in the freshly launched AMM on the XRP Ledger shows the need for better testing. Testing with real value, on a network that isn’t mainnet. Testing when an amendment is available, not when it was voted in and went live.”
The proposed Canary network would function autonomously with its native tangible asset, providing a practical environment for users and developers to test and identify weaknesses. This approach mirrors blockchain development practices, like Ethereum’s use of multiple testnets, such as Sepolia, to test upgrades and amendments prior to mainnet integration.
Image/Photo credit: source url
