Amendment Idea: Permissioned AMM (domain-gated native AMM for KYC/FI liquidity)

[Grow420Crypto]

Summary

Vault Desk by AiVibes builds ops software for regulated desks that want gated RLUSD / XRPL flows (human dual-control + agent API). We are not asking for a private chain — we need the same credential / Permissioned Domain model that already works for order books to cover native AMM pools.

Why Permissioned DEX alone is not enough for large FIs

XLS-81 Permissioned DEXes correctly gate offers. Official docs also state permissioned trading cannot use AMMs, and AMM access cannot be restricted by a Permissioned Domain today.

Large FIs that require KYC/AML on every counterparty often want dual-asset liquidity provision (AMM-style LP), not only CLOB. Today the honest answer we have to give them is:

Permissioned order books: yes. KYC-gated AMM pools: not on ledger yet.

Depositing into an open AMM from KYC’d wallets (e.g. app-level KYC) does not make the pool KYC-only — strangers can still deposit/swap unless the AMM object itself enforces a domain.

Ask

Please advance a Permissioned AMM amendment (domain-gated AMMCreate / deposit / withdraw / optional swaps), reusing Credentials (XLS-70) + Permissioned Domains (XLS-80), complementary to XLS-81.

Useful properties for FI adoption:

• Pool-level DomainID (who may LP / govern; optionally who may swap)
• Withdrawal carve-out if credentials lapse (LP can exit)
• Clear incompatibility notes vs open AMM / hybrid routing
• Same credential issuers FIs already plan to use for Permissioned DEX + gated Single Asset Vaults (XLS-65) / Lending (XLS-66)

Context

We previously saw a draft “Permissioned AMM” direction in the ecosystem; the older discussion link we had (#566) now 404s. Happy to refine requirements with authors/validators from an ops-desk / FI tooling perspective.

Contact: support@everhostx.com — Vault Desk by AiVibes (anonymous-safe brand).