Skip to content
EnabledTier ADeFi & DEX

AMMClawback XLS-73

Tokens with clawback enabled can be used in AMM pools. AMMClawback is enabled on the XRP Ledger. xrpscan reports Jan 30, 2025 (UTC) as its activation date and rippled 2.3.0 as its first version.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Enabled
XLS
XLS-73
Enabled
Jan 30, 2025 (UTC)

What does this amendment change?

Why does this amendment exist?

Tokens supporting clawback needed a dedicated AMM recovery rule because a pool holds tokens from multiple participants together.

How does the mechanism work?

AMMClawback determines a holder's LP share and recovers the issuer's token from that share. If the issuer issues only one of the two pool assets, the holder receives the paired asset back. tfClawTwoAssets permits recovery of both sides only if the same issuer issued both assets.

What changes compared with the predecessor?

BeforeAfter
Accounts with clawback enabled could not create an ordinary AMM pool for their tokens because the original clawback covered only freely available balances.The issuer can recover its tokens from a holder's proportional pool balance, while AMMDeposit rejects frozen or unauthorized deposits.

Who is this change relevant to?

XRP holders and users

XRP itself remains outside clawback. A holder of LP tokens for an asset supporting clawback can lose their proportional pool balance of that token and receive the other asset back, depending on the pool configuration.

Wallets and app developers

AMM interfaces must check clawback, freeze, and authorization status before deposits and show how recovery affects LP tokens and pool balances.

Exchanges and issuers

An issuer can exercise compliance rights over tokens held in AMM pools. It may recover only its own assets; for trust line tokens, this requires the permanently enabled clawback account flag.

Node operators

Nodes calculate proportional pool shares, burn the corresponding LP tokens, and apply recovery to the AMM atomically.

What limitations and risks remain?

  • This feature cannot claw back XRP.
  • For trust line tokens, the issuer must have enabled lsfAllowTrustLineClawback.
  • Asset must identify a token issued by the executing Account.
  • tfClawTwoAssets is invalid unless the issuer issued both pool assets.
  • Clawback is not a general AMM withdrawal on behalf of an arbitrary holder.
Technical details: transactions, fields, codes and invariants

Transactions

  • AMMClawback
  • AMMCreate
  • AMMDeposit

Ledger objects

  • AMM
  • RippleState
  • AccountRoot

Fields and flags

  • Holder
  • Asset
  • Asset2
  • Amount
  • lsfAllowTrustLineClawback
  • tfClawTwoAssets 0x00000001

Result codes

  • tecNO_PERMISSION
  • temMALFORMED

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

AMMClawback is enabled on the XRP Ledger. xrpscan reports Jan 30, 2025 (UTC) as its activation date and rippled 2.3.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications