Handling the XRPL AMM (XLS-30) in Applications

New transaction types: AMMCreate, AMMDeposit, AMMWithdraw, AMMVote. Each has specific field requirements and fee structures distinct from Payment or OfferCreate.

Wallet providers, exchange deposit systems, DeFi interfaces

Update transaction construction libraries and signing flows to support the new canonical transaction types. Verify field validation logic.

New AMM ledger object type and modified trustline objects. AMM accounts hold the pool's asset pair. Metadata parsing must handle new node types for balance change calculation.

Custody platforms, accounting systems, block explorers, data indexers

Extend metadata parsers to correctly identify and process AMM-related AffectedNodes. Update balance calculation logic to attribute changes from AMM interactions.

Supports single-sided and double-sided deposits. Single-sided deposits can fail or result in a different LP token amount than expected due to slippage and pool ratio changes.

DeFi frontends, algorithmic trading bots, liquidity management dashboards

Implement pre-flight simulation using the amm_info API to calculate expected LP token returns. Display clear slippage warnings and handle the tec-class failure codes for single-sided deposits.

Liquidity Provider (LP) tokens are represented as a new fungible token type. The AMM account itself is the issuer. LP token balance changes must be tracked for user portfolio display.

Wallets, portfolio trackers, tax reporting tools

Update token indexers to recognize the AMM account as an issuer. Display LP token balances and their underlying asset composition. Ensure trustline logic does not incorrectly flag the AMM issuer.

AMMVote transaction allows LP token holders to vote on the pool's trading fee. Voting slots and fee governance are new on-ledger state that must be monitored.

Governance dashboards, LP analytics sites, community tooling

Parse AMM ledger objects to display current fee, voting slots, and voter participation. Build interfaces for constructing and submitting AMMVote transactions.

XRP Ledger's native pathfinding and auto-bridging can route payments through AMM pools. This changes the optimal path for cross-currency payments and can affect slippage.

Payment processors, wallets using ripple_path_find, arbitrage bots

Review pathfinding algorithms to ensure AMM pools are considered as potential liquidity sources. Test cross-currency payment outcomes with AMM routes enabled to verify cost and slippage assumptions.

AMMCreate requires a one-time special reserve. AMM transactions consume transaction fees. LP tokens do not carry the owner reserve burden of NFTs, but the AMM account itself has reserve requirements.

Infrastructure cost planners, exchange operations teams

Account for the higher reserve requirement when funding AMM creation operations. Monitor the transaction fee market to optimize AMM transaction submission costs during network congestion.

New transaction types and ledger objects introduce new failure modes. AMM pools can be drained, and LP tokens can become worthless if the underlying assets depeg or the pool is exploited.

Risk teams, security auditors, node operators

Implement monitoring for AMM-specific transaction failure codes. Set alerts for large, imbalanced AMMWithdraw transactions or rapid changes in pool composition that may indicate an attack or depegging event.

New AMM ledger object type with dynamic fields for LP tokens, asset balances, and trading fees. Incorrect parsing leads to incorrect pool state display.

Wallets, explorers, data aggregators, DeFi dashboards

Update ledger object parsers to handle the AMM object type and its fields. Validate parsing logic against devnet objects.

Single-sided deposits use an auction mechanism that can result in a different LP token amount than a double-sided deposit of equivalent value.

DeFi interfaces, liquidity management tools, wallets

Implement the auction logic for single-sided deposits in the UI. Clearly display expected slippage and LP token outcome before user confirmation.

New transaction types: AMMCreate, AMMDeposit, AMMWithdraw, AMMVote. Incorrect field construction can lead to transaction failure or unexpected economic outcomes.

Wallets, exchanges, custodial services

Add support for the new transaction types in transaction construction libraries. Validate all mandatory and optional fields against the XLS-30 specification.

AMMVote transactions allow LP token holders to direct protocol fees. Misinterpreting vote weight or epoch boundaries can cause governance display errors.

Governance dashboards, LP analytics tools, DeFi protocols

Implement correct vote-weight calculation based on LP token holdings. Monitor vote epochs and display active fee settings accurately.

AMM accounts require a higher base reserve. Failing to account for this can cause transaction failures due to insufficient XRP balance.

Wallets, exchanges, automated trading bots

Update reserve calculation logic to include the AMM account reserve. Ensure fee and reserve checks account for the higher requirement before transaction submission.

The continuous auction for arbitrage and single-sided deposits introduces a time-sensitive component. Stale data can lead to failed transactions.

Arbitrage bots, DeFi frontends, liquidity aggregators

Implement real-time or near-real-time data feeds for AMM pool states. Set appropriate transaction timeouts and handle tec-class failure codes gracefully.

LP tokens are represented as trustline balances. Standard token balance queries may not distinguish LP tokens from other IOUs.

Portfolio trackers, accounting systems, tax tools

Update balance scanning logic to identify LP tokens by their association with an AMM account. Ensure LP tokens are categorized correctly for reporting.