A Sept. 5 XRPL Standards discussion has introduced a proposal for a Permissioned AMM that would extend XRPL's existing Credentials and Permissioned Domains framework to native liquidity pools. The concept remains an XLS Idea rather than an approved amendment, and it has not been activated on the XRP Ledger.
The proposal targets a gap in XRPL's institutional DeFi infrastructure. XRPL's Permissioned DEX can already restrict order-book trading to wallets holding approved credentials, but official documentation states that permissioned trades cannot use AMMs and existing AMM access cannot be restricted through a Permissioned Domain. This matters because order books and AMMs provide liquidity differently: an order-book market matches buyers and sellers, while AMM users contribute two assets to a pool and trades execute against that pool's pricing mechanism.
The proposed design would attach a DomainID directly to an AMM pool, potentially determining who may deposit liquidity, participate in governance and optionally swap against the pool. A withdrawal exception would allow liquidity providers to retrieve assets if their credentials later expire, addressing a compliance lifecycle concern. The same credential and permissioned-domain architecture could eventually span the Permissioned DEX, Single Asset Vaults, lending and AMMs, reducing the need for separate institutional compliance systems.
Ripple's earlier institutional DeFi roadmap placed permissioned trading alongside lending and tokenization infrastructure, and Coinpaper has reported on how permissioned domains, credentials, vaults and lending are being combined for compliant institutional lending. However, the Permissioned AMM idea is currently only an early-stage proposal; no amendment has been activated on the XRP Ledger.
