Back

Identity · Admin portal

Inscribing a DID on the Blockchain

User story

As an administrator, I want to monitor and manage the DID inscription process, ensuring that users can batch inscriptions efficiently while preventing duplicate transactions, so that the system remains secure, transparent, and optimized for blockchain processing.

Acceptance criteria

  • The administrator can view all pending and completed DID inscriptions.
  • The administrator can set and adjust fee parameters for inscriptions.
  • The administrator can track users’ inscription requests and monitor their status.
  • The system prevents duplicate DID inscriptions by marking them as pending for all users once they are batched.
  • The administrator can access logs of completed inscriptions for auditing purposes.
  • The administrator receives error or failure notifications for failed transactions.
  • The system automatically updates the status of inscriptions once they are confirmed on the blockchain.
01

The inscribe view

01Pending DIDs, fee selector and block previewThe starting view: a grid of pending DIDs, a fee selector for transaction cost, and a block preview summarising how the inscription will be processed.
02Block preview collapsedThe preview collapses for a cleaner working surface, leaving the DID list and fee selection in focus.
02

Selecting fee and DIDs

03Step 1 — Select feeThe administrator picks a fee band based on urgency and network conditions.
04Step 2 — Select pending DIDsOne or many pending DIDs are selected; bulk selection batches multiple identifiers at once.
03

Confirming and processing

05Step 3 — Confirm inscriptionA last checkpoint: the selected DIDs and fee are reviewed before the batch is submitted.
06Status updateSubmitted DIDs are marked pending until the transaction confirms on-chain, and disappear from every other administrator’s available list — preventing duplicate inscriptions.
All projectsNext projectCreating Python Script in Python Editor