Definition and scope
XRPL Liquidity-Provider Tokens Explained addresses a distinct part of dex, amms, and native defi. Understand the pool-ownership tokens minted when assets are deposited into an AMM.
The XRP Ledger includes exchange and liquidity functions at the protocol layer. These topics explain how order books and AMMs interact, how users express prices and limits, and where liquidity, slippage, fees, and smart operational controls matter. Protocol liquidity does not guarantee price, depth, returns, legality, or issuer performance. Examples are mechanical, not trading advice.
How it works
An XRPL AMM issues a pool-specific LP token proportional to deposited liquidity. Holding LP tokens represents a claim on the pool's changing asset balances, and withdrawal burns them for underlying assets.
- LPTokenBalance: verify this field, object, or component against the cited protocol documentation.
- AMMDeposit: verify this field, object, or component against the cited protocol documentation.
- AMMWithdraw: verify this field, object, or component against the cited protocol documentation.
- pool share: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Record the exact AMM asset pair and LP token issuer, compare LP share before and after deposit, and calculate withdrawal outcomes from current reserves rather than the original deposit.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
LP tokens are not fixed-value receipts. Their redemption composition changes with trading and fees, and underlying issued assets retain issuer and freeze risks.
Protocol liquidity does not guarantee price, depth, returns, legality, or issuer performance. Examples are mechanical, not trading advice.
Current network status
Enabled on XRPL Mainnet. AMM was enabled on XRPL Mainnet in feature responses from both official public servers at review time. Client and service support can still vary.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.