Skip to content
EnabledTier AIdentity & Oracles

Credentials XLS-70

On-ledger credentials represent authorization and compliance attestations. Credentials is enabled on the XRP Ledger. xrpscan reports Sep 4, 2025 (UTC) as its activation date and rippled 2.3.0 as its first version.

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

Status
Enabled
XLS
XLS-70
Enabled
Sep 4, 2025 (UTC)

What does this amendment change?

Why does this amendment exist?

Applications need reusable on-ledger attestations without implementing an identity check in every payment or access rule.

How does the mechanism work?

An issuer creates a credential for a subject. Credentials issued to another account need CredentialAccept; self-issued credentials are accepted at creation. DepositPreauth stores one to eight issuer/type rules that must all match. Supported transactions present the corresponding CredentialIDs as proof.

What changes compared with the predecessor?

BeforeAfter
DepositPreauth could approve individual sender accounts but could not verify reusable attestations from a trusted third party.Accounts can evaluate accepted on-ledger credentials to authorize groups of senders rather than only individual addresses.

Who is this change relevant to?

XRP holders and users

A user decides whether to accept a credential issued to them. The attestation and its association with the account are publicly visible.

Wallets and app developers

Apps must handle issuance, acceptance, expiration, and deletion separately and explicitly attach the required CredentialIDs to a transaction.

Exchanges and issuers

Exchanges and other institutions can use attestations from a selected issuer for deposit authorization or their own off-ledger workflows.

Node operators

Nodes store Credential objects in the issuer's and subject's directories and check validity, acceptance, and expiration for authorized deposits.

What limitations and risks remain?

  • A credential attests only to its issuer's statement. The ledger does not check whether that statement is substantively true.
  • A credential issued by another account requires explicit CredentialAccept before it is valid. A self-issued credential is accepted automatically at creation.
  • CredentialType must be nonempty and at most 64 bytes. URI is limited to 256 bytes and its content is not validated.
  • A credential list in DepositPreauth has at least one and at most eight entries. All entries are required together.
  • XLS-70 initially extends interactions covered by deposit authorization. Other protocol areas need their own integrations.
  • The ledger does not automatically search for matching credentials because an account may own many objects. Their IDs must be supplied.
Technical details: transactions, fields, codes and invariants

Transactions

  • CredentialCreate
  • CredentialAccept
  • CredentialDelete
  • DepositPreauth
  • transactions affected by DepositAuth

Ledger objects

  • Credential
  • DepositPreauth

Fields and flags

  • Subject
  • Issuer
  • CredentialType (at most 64 bytes)
  • Expiration
  • URI (at most 256 bytes)
  • CredentialIDs
  • AuthorizeCredentials / UnauthorizeCredentials
  • lsfAccepted 0x00010000

API methods

  • deposit_authorized
  • ledger_entry

Invariants

  • A Credential object's reserve allocation must match its acceptance status and the owner directories involved.

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?

Credentials is enabled on the XRP Ledger. xrpscan reports Sep 4, 2025 (UTC) as its activation date and rippled 2.3.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