Skip to content

feat: add PermissionedDomains support (XLS-80)#157

Draft
e-desouza wants to merge 6 commits intomainfrom
feat/xls-80-permissioned-domains
Draft

feat: add PermissionedDomains support (XLS-80)#157
e-desouza wants to merge 6 commits intomainfrom
feat/xls-80-permissioned-domains

Conversation

@e-desouza
Copy link
Copy Markdown
Collaborator

@e-desouza e-desouza commented Apr 3, 2026

Summary

Implements XLS-80 (PermissionedDomains) support for xrpl-rust.

New transaction types

  • PermissionedDomainSet — Create or update a permissioned domain with a list of AcceptedCredentials
  • PermissionedDomainDelete — Delete an existing permissioned domain by DomainID

New ledger entry type

  • PermissionedDomain (LedgerEntryType = 0x0082) — On-ledger permissioned domain object with Owner, AcceptedCredentials, Sequence, and audit fields

Shared types

  • Credential — Nested STObject (via serde_with_tag!) with required Issuer and CredentialType fields

Validation

  • Credential.issuer and Credential.credential_type are required (non-optional String fields)
  • PermissionedDomainSet.get_errors() rejects empty issuer or credential_type values

Registration

  • TransactionType::PermissionedDomainSet, TransactionType::PermissionedDomainDelete added to enum
  • LedgerEntryType::PermissionedDomain (0x0082) added to enum
  • Module re-exports and integration tests included

Test plan

  • Serde roundtrip tests for PermissionedDomainSet, PermissionedDomainDelete, PermissionedDomain
  • Builder pattern and new() constructor tests
  • get_transaction_type() variant tests
  • Validation: empty credential fields rejected
  • Multiple credentials in AcceptedCredentials array
  • Integration tests in tests/transactions/
  • cargo fmt, cargo clippy --all-features, cargo test --release all pass
  • All 9 feature-matrix builds compile cleanly

…r XLS-80

Add the Credential serde_with_tag type for wrapping issuer/credential_type
pairs, and add PermissionedDomainSet and PermissionedDomainDelete variants
to the TransactionType enum. Module declarations for the new transaction
types are included.
Implement the PermissionedDomainSet transaction for creating and updating
permissioned domains. Supports optional DomainID for updates, a list of
accepted Credential entries, and the full CommonTransactionBuilder pattern
with builder methods for domain-specific fields.
Implement the PermissionedDomainDelete transaction for removing an
existing permissioned domain from the ledger. Takes a required DomainID
field identifying the domain to delete.
Add the PermissionedDomain ledger object representing a permissioned
domain on the XRP Ledger, with owner, accepted_credentials, sequence,
owner_node, previous_txn_id, and previous_txn_lgr_seq fields. Register
as LedgerEntryType 0x0082 and add the LedgerEntry enum variant.
Add integration test stubs for PermissionedDomainSet and
PermissionedDomainDelete transactions. These tests verify transaction
construction, signing, and submission against a running XRPL node,
accepting temDISABLED when the amendment is not yet enabled.
Copy link
Copy Markdown
Collaborator Author

@e-desouza e-desouza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a read through

Required Credential fields typed as Option without validation — flagged inline.


Review by ReviewBot 🤖

Review by Claude Opus 4.6 · Prompt: V12

The XLS-80 spec requires both `issuer` and `credential_type` on every
Credential entry.  Having them typed as `Option<String>` allowed callers
to construct silently invalid transactions.

- Change `Credential.issuer` and `Credential.credential_type` from
  `Option<String>` to `String`, matching the Signer struct pattern.
- Add `get_errors()` validation in `PermissionedDomainSet` that rejects
  empty issuer or credential_type with `MissingField`.
- Add two tests covering the new validation paths.
- Update all call sites (unit tests, integration test, ledger object
  tests) to use non-optional field construction.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant