Skip to content
EnabledTier ADeFi & DEX

PermissionedDEX XLS-81

Permissioned DEXes restrict trading to participants in an approved domain. PermissionedDEX is enabled on the XRP Ledger. xrpscan reports Feb 18, 2026 (UTC) as its activation date and rippled 2.5.0 as its first version.

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

Status
Enabled
XLS
XLS-81
Enabled
Feb 18, 2026 (UTC)

What does this amendment change?

Why does this amendment exist?

Some markets need on-ledger liquidity while admitting only verified participants.

How does the mechanism work?

OfferCreate can associate an offer with a permissioned domain's order book through DomainID. Only domain members may place orders there and execute them against each other. tfHybrid additionally lists an offer in the open order book while keeping execution in the two liquidity paths separate under the protocol rules.

What changes compared with the predecessor?

BeforeAfter
All fungible offers were in the open DEX and could generally execute against any matching counteroffer.A domain receives its own order books, whose offers and cross-currency payments can be used only by valid members.

Who is this change relevant to?

XRP holders and users

The open DEX remains available. Ordinary participants need an appropriate accepted credential for a domain order book; the domain owner is considered a member without that additional credential.

Wallets and app developers

Apps must distinguish open, permissioned, and hybrid offers, use DomainID in supported transactions, and pass domain in order book, pathfinding, and streaming API requests.

Exchanges and issuers

Regulated operators can restrict native liquidity to verified participants. They remain responsible for trusting credential issuers and domain rules.

Node operators

Nodes perform additional membership checks when placing, crossing, and traversing offers, and remove invalidated offers like unfunded orders.

What limitations and risks remain?

  • XLS-81 does not integrate AMMs into permissioned DEXes.
  • NFT offers do not support domains.
  • Open and permissioned offers must not fill each other. Only a hybrid offer can be listed in both books.
  • A payment's domain affects only cross-currency paths that touch an order book. It does not make direct token payments permissioned.
  • Expired credentials are not automatically deleted when traversing a payment path.
  • The specification lists additional failure conditions without assigning specific result codes, so no codes are added here.
  • The specification still treated the final throughput impact of additional checks as a subject for performance testing.
Technical details: transactions, fields, codes and invariants

Transactions

  • OfferCreate
  • Payment

Ledger objects

  • Offer (0x006F)
  • DirectoryNode (0x0064)
  • PermissionedDomain
  • Credential

Fields and flags

  • DomainID
  • AdditionalBooks
  • BookDirectory / BookNode
  • TakerGets / TakerPays
  • tfHybrid 0x00100000

API methods

  • book_offers
  • path_find
  • ripple_path_find
  • books subscription
  • book_changes

Invariants

  • A permissioned offer must not be filled by an open offer or by an offer from another domain.
  • An open offer must not be in a domain order book or be filled by a permissioned offer.

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?

PermissionedDEX is enabled on the XRP Ledger. xrpscan reports Feb 18, 2026 (UTC) as its activation date and rippled 2.5.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