Skip to main content

DID in ISBE

The Spain Blockchain Services Infrastructure (ISBE) offers a decentralized identity layer based on the W3C standards of Decentralized Identifiers (DIDs) and Verifiable Credentials. Any entity — private company, public administration, or agency — joining the network can:

  • Register its own digital identity as a did:isbe.
  • Publish the cryptographic keys with which it will sign credentials and authorizations.
  • Build trust chains to issue verifiable credentials.

This section documents the concepts, onboarding flows, and in particular, how to manage the complete lifecycle of a DID through the DID Registry API exposed by ISBE in each environment.

What is a did:isbe?​

A did:isbe is a decentralized identifier registered on the ISBE blockchain. It has the following format:

did:isbe:<modelDeploy>:<identifier>

Where:

  • <modelDeploy> indicates the environment and network (uc for production, uc-pre for pre-production).
  • <identifier> is the unique identifier of the entity, cryptographically derived.

Each DID resolves to a DID Document, a JSON-LD document describing the public keys of the entity and the associated verification relationships (what can be done with each key: authentication, issuing credentials, etc.).

Example:

did:isbe:uc:z12kVar5p6bD5WCjEJcQ18Zyt8XV

Identity Stack Components​

ISBE divides identity management into several services. This section focuses on the first one:

ServicePurposeDocumented in
DID Registry APIRegister, update, rotate, and resolve DIDs.This section
Trusted Issuer Registry (TIR)Publish accreditations and trust chains.Trust chain section
Issuer / IDPIssue verifiable credentials to end users.Credentials section
ISBE WalletStore credentials on the user side.Wallet section

Structure of this section​

  1. Key concepts — DID, DID Document, keys, verification relationships, trust chain.
  2. Environments — URLs and trust anchors for PRE and PRO.
  3. DID Onboarding — Complete tutorial: generate keys, register the first DID Document.
  4. Key Management — Add, revoke, expire, and rotate verification methods.
  5. DID Resolution — Query the current or historical state of a DID Document.
  6. Trust Chain — Generate RTAO, TAO, and TI accreditations.
  7. DID Registry API Reference — Detailed documentation for each endpoint.
  8. Troubleshooting — Common errors and how to resolve them.
Prerequisites

Before starting, it is convenient to have:

  • Access to the ISBE portal for the target environment (with a Legal Representative Certificate or a Verifiable Credential).
  • The CLI isbe-identity-did-gen installed to generate the DID and, optionally, an EVM transaction signing library (ethers.js, eth_account) to sign transactions returned by the API.
  • Funds in the EOA associated with your control keys (if you are going to register or modify a DID).
Conventions

Throughout this section, placeholders such as <PRIVATE_KEY>, <DID>, or <RESPONSE_BODY> are used. Replace them with actual values before running the commands.