RippleX Alerts Users Against a Technical Glitch Affecting AMM Pools

Last Updated:
RippleX Alerts Users Against a Technical Glitch Affecting AMM Pools
  • RippleX reveals a technical issue that affects the Automated Market Maker (AMM) pool on the XRPL.
  • David Schwartz comments that the issue is not caused by the single-sided deposit feature.
  • The team urges users to stop depositing new funds to the AMM pool and redeem LP tokens.

Ripple’s development division, RippleX, has recently disclosed a technical glitch that affects the Automated Market Maker (AMM) pool on the XRP Ledger. Providing more clarity to the matter, Ripple CTO David Schwartz shared an X post, asserting that the technical issue was not caused by the single-sided deposit feature.

Schwartz’s post came in response to RippleX’s official message revealing a “discrepancy” that led to the disruption of transactions and liquidity pools on XRP Ledger. RippleX cited, “The discrepancy affected how the DEX payment engine routes liquidity through AMM pools and order books in some complex payment path scenarios.”

On March 22, the Ripple team announced the successful integration of AMM on XRPL. Schwartz also joined the celebration by acknowledging the team’s two-year-long efforts to bring  “AMM live on XRPL.”

Notably, AMM pools are the liquidity pools used in decentralized exchanges (DEXs). They focus on facilitating trading without traditional order books.

In his recent X post, Schwartz elaborated on the single-sided deposit feature of AMM. According to his post,

“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.”

Further, RippleX cautioned its users to stop depositing new funds to the AMM pools. In addition, the team also requested that the users holding LP tokens redeem them. Moreover, the platform assured its community that the issue would soon be fixed as the “engineering team is working to resolve the issue alongside community participants.”

Disclaimer: The information presented in this article is for informational and educational purposes only. The article does not constitute financial advice or advice of any kind. Coin Edition is not responsible for any losses incurred as a result of the utilization of content, products, or services mentioned. Readers are advised to exercise caution before taking any action related to the company.