A Sept. 5 XRPL Standards discussion proposes a Permissioned AMM that would extend XRPL's existing Credentials and Permissioned Domains architecture to native liquidity pools. The concept is currently an XLS Idea, not an approved amendment, and has not been activated on the XRP Ledger.
The proposal targets a specific gap in XRPL's institutional DeFi infrastructure. Its Permissioned DEX can restrict order-book trading to wallets holding approved credentials, but official XRPL documentation says permissioned trades cannot use AMMs, and access to an existing AMM cannot currently be restricted through a Permissioned Domain.
Banks Can Use Permissioned Order Books, but Not Permissioned Pools
That distinction matters because an order-book market and an AMM provide liquidity differently.
XRPL's existing permissioned exchange lets a domain owner specify acceptable credentials. Only accounts meeting those requirements can place or interact with qualifying offers. This builds KYC or other eligibility controls directly into the trading environment.
Coinpaper previously covered the arrival of the Permissioned DEX as part of XRPL's broader institutional infrastructure push. Ripple's earlier institutional DeFi roadmap also placed permissioned trading alongside lending and tokenization infrastructure.
AMMs are different. Rather than requiring buyers and sellers to post matching orders, users contribute two assets to a liquidity pool and trades execute against that pool's pricing mechanism.
Under the current architecture, however, putting assets into an ordinary XRPL AMM from a KYC-verified wallet does not make the pool KYC-only. Other wallets can still interact with it. That is precisely the problem the new proposal is trying to address.
A Permissioned AMM Would Put Credentials at the Pool Level
The idea proposes attaching a DomainID directly to an AMM pool.
That could determine who is allowed to deposit liquidity, participate in governance and, optionally, swap against the pool. The proposal also calls for a withdrawal exception so liquidity providers could retrieve assets if their credentials later expire.
The same Credentials and Permissioned Domains framework could then potentially span the Permissioned DEX, Single Asset Vaults, lending and AMMs rather than forcing institutions to maintain separate compliance systems.
That direction fits the wider institutional architecture developing around XRPL. Coinpaper recently covered how permissioned domains, credentials, vaults and lending are being combined for compliant institutional lending.
| Feature | Open XRPL AMM | Proposed Permissioned AMM |
|---|---|---|
| Liquidity providers | Open | Credential-gated |
| KYC enforcement | No pool-level requirement | Proposed through DomainID |
| Swaps | Open | Potentially restrictable |
| Credential expiry | Not relevant | Exit mechanism proposed |
| Status | Existing | Early-stage idea |
