Skip to main content

Build your first use case on ISBE

This guide walks through the typical flow of an ISBE use case from start to finish, connecting the platform's two main layers: Identity and Smart Contracts. By the end you will have seen how all the pieces fit together:

This complete flow — decentralized identity, credential issuance and contract deployment with regulatory validity under eIDAS2 and MiCA — is ISBE's key differentiator compared to public networks.

Step 0 — Prepare your environment​

Complete the Onboarding Process and authenticate in the ISBE portal of the target environment (PRE for testing).

Step 1 — Register your did:isbe​

Your identity on the network. Generate secp256k1 keys, derive the DID and register it, either via the guided portal or directly against the DID Registry API.

Step 2 — Issue a verifiable credential​

ISBE's credentials layer issues W3C credentials via the OID4VCI protocol, which the user receives in their wallet.

Step 3 — Accredit the issuer in the Trust Chain​

For credentials to be verifiable by third parties, the issuer must be accredited (TAO or TI) in the TIR (Trusted Issuers Registry).

Step 4 — Deploy your smart contract​

If your use case requires its own logic on the network (tokenization, traceability, timestamping…):

  1. Choose a template and modality — Use the catalog decision tree and choose your deployment modality.
  2. Adapt and test your contract locally — Follow the Developer Guide and validate on a local ISBE network (npm install @red-isbe/isbe-contracts + Besu in Docker). You don't need to have completed the onboarding for this part.
  3. Request the deployment — In PRE and PRO you don't deploy directly: you register the contract in the Customer Portal and, after the technical review, the ISBE team orchestrates the deployment. See steps 4-5 of the Onboarding Process.

Step 5 — Inspect everything in Blockscout​

Your contract deployment and the transactions from the previous steps are recorded on the network and can be queried in the explorer. It is the most direct way to confirm that your contract is deployed and operational.

What's next?​