Skip to content

Commit

Permalink
Merge pull request #2502 from XRPLF/amm_status_blog
Browse files Browse the repository at this point in the history
Add AMM status update blog
  • Loading branch information
mDuo13 authored Mar 27, 2024
2 parents 8475fcc + 98a904d commit f34ad2d
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 0 deletions.
18 changes: 18 additions & 0 deletions blog/2024/amm-status-update.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
category: 2024
date: 2024-03-26
labels:
- Advisories
- Amendments
theme:
markdown:
editPage:
hide: true
---
# AMM Status Update

As [previously expected](./get-ready-for-amm.md), the AMM Amendment to the XRP Ledger went live on 2024-03-22. However, soon after, a community member identified a discrepancy in a few AMM pools which indicated transactions were not executing as intended. A team including RippleX, Orchestra Finance, tequ, and other members of the XRP Ledger community moved quickly to identify the source of the problem, which involves how the DEX payment engine routes liquidity through AMM pools and order books in some complex payment path scenarios.

A fix has been developed and [is being reviewed, tested, and prepared for release](https://github.com/XRPLF/rippled/pull/4968) as soon as possible. The fix requires an amendment to the XRP Ledger protocol, which must be voted in by network validators and maintain over 80% support for the normal 2-week period before activation. Until the fix is enabled on the network, it's best for users to redeem LP tokens and not deposit new funds into AMM pools.

Stay tuned for the release of `rippled` version 2.1.1.
1 change: 1 addition & 0 deletions blog/sidebars.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
- group: '2024'
expanded: false
items:
- page: 2024/amm-status-update.md
- page: 2024/get-ready-for-amm.md
- page: 2024/verifyed.md
- page: 2024/how-to-mint-nfts.md
Expand Down

0 comments on commit f34ad2d

Please sign in to comment.