Skip to content
EnabledTier AIdentity & Oracles

PermissionedDomains XLS-80

Permissioned domains represent controlled participant groups on the XRPL. PermissionedDomains is enabled on the XRP Ledger. xrpscan reports Feb 4, 2026 (UTC) as its activation date and rippled 2.4.0 as its first version.

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

Status
Enabled
XLS
XLS-80
Enabled
Feb 4, 2026 (UTC)

What does this amendment change?

Why does this amendment exist?

Several protocol features need a reusable definition of which credentials authorize participation.

How does the mechanism work?

PermissionedDomainSet stores accepted credential types and issuers in a domain object. Holding an appropriate valid, accepted credential makes an account a member. Only the domain owner may change the rules or delete the object.

What changes compared with the predecessor?

BeforeAfter
The XRPL had no shared PermissionedDomain object that multiple protocol features could reference as an access policy.Multiple protocol features can use the same DomainID as an on-ledger access layer.

Who is this change relevant to?

XRP holders and users

A domain moves no assets. It determines only whether an account's credentials qualify it for membership in a feature built on that domain.

Wallets and app developers

Apps must check the domain object, credential issuer, credential type, acceptance status, and expiration together.

Exchanges and issuers

Institutions can centrally define up to ten alternative credential rules and reuse the domain in supported DEX or vault workflows.

Node operators

Nodes validate the domain owner, array limits, and referenced issuers and keep the reserve-requiring domain object in the owner directory.

What limitations and risks remain?

  • A domain itself performs neither trading, payments, nor lending.
  • AcceptedCredentials contains at most ten rules.
  • The rules are alternatives. Complex AND combinations or freely programmable rules are outside XLS-80's scope.
  • Security depends on the credential issuers and the domain owner.
  • The domain owner cannot modify other parties' credentials but can change its domain's accepted list.

What fee and performance figures does the specification provide?

  • The PermissionedDomain object requires one owner reserve from the domain owner.
Technical details: transactions, fields, codes and invariants

Transactions

  • PermissionedDomainSet
  • PermissionedDomainDelete

Ledger objects

  • PermissionedDomain
  • Credential

Fields and flags

  • DomainID
  • Owner
  • Sequence
  • AcceptedCredentials
  • Issuer
  • CredentialType (at most 64 bytes)

Invariants

  • A domain must not exist without rules.
  • When present, AcceptedCredentials must contain between one and ten entries.

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?

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

Identity and Permissions: protocol progression

  1. DepositPreauthEnabled · from rippled 1.1.0
  2. DeletableAccountsEnabled · from rippled 1.4.0
  3. TicketBatchEnabled · from rippled 1.7.0
  4. DisallowIncomingEnabled · from rippled 1.10.0
  5. DIDEnabled · from rippled 2.0.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixEmptyDIDEnabled · from rippled 2.2.0
  8. CredentialsEnabled · from rippled 2.3.0
  9. fixInvalidTxFlagsEnabled · from rippled 2.4.0
  10. PermissionedDomainsEnabled · from rippled 2.4.0
  11. PermissionedDEXEnabled · from rippled 2.5.0
  12. PermissionDelegationDeprecated · from rippled 2.5.0
  13. SponsorOpen for voting · from xrpld 3.3.0
  14. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  15. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  16. fixCleanup3_4_0Enabled · from xrpld 3.4.0

Which primary sources support this information?

← All XRPL amendments and XLS specifications