Flows

A flow page follows one feature end to end: who takes part, where it starts in the UI, each step with a sequence diagram, what goes on chain, to the server and stays in the browser, every wallet prompt, the real error messages, the variants and the code that implements it. This page lists them all, grouped by the role that starts them. The roles themselves are described in Roles.

By role

Verifier (no wallet)

Flow	One line
Verifying a credential	Look up an id, link or QR code, read the checks, and check a document or package the holder gave you
Verifiable credentials and Open Badges	Check a VC 2.0 or Open Badges 3.0 file against the chain
Selective disclosure	Issue a challenge and check a holder's disclosure file
Status lists	Read revocation and suspension bits as standard VC tooling does
Phone wallet and in-person checks	Scan a holder's phone at /present, online or offline

Holder (student)

Flow	One line
Enrolment and wallet linking	Accept an issuer's invitation so delivered credentials reach the wallet
Holder inbox	See every credential issued to the wallet, rebuilt from contract events
Document storage	Open the encrypted document with the credential package
Sharing documents	Give one wallet a sealed file, or anyone a link; apply a key update
Selective disclosure	Show chosen fields to one verifier in a challenge-bound file
Verifiable credentials and Open Badges	Export the credential in standard formats
Private access proofs (ZK)	Admit requesters to a credential's group; requesters prove access anonymously
Phone wallet and in-person checks	Carry credentials on a phone and present them as QR codes

Issuer (institution)

Flow	One line
Issuing a credential	Fill the four-part form, encrypt the document, sign, anchor, and hand on the package
Document storage	How documents are encrypted, uploaded behind sign-in, and reopened
Credential lifecycle	Suspend, reinstate, revoke and supersede, from the dashboard or the verify page
Enrolment and wallet linking	Invite a student's wallet, unlink it, cancel invitations
Record types	Register, switch off and use the institution's own record types
Bulk import	Issue a cohort from an export, repeat-safe, with a result file and package archive
Sharing documents	Replace a document's key and remove old copies
Selective disclosure	Add the disclosure attestation to a credential
Issuer key retirement	Hand an issuer's authority to a successor key

Guardian and admin

Flow	One line
Governance	The Safe, the timelock, the guardian's pause, admitting and removing issuers
Issuer key retirement	Retire a compromised or rotated issuer key through the admin
Credential lifecycle	Admin holds on one credential and issuer-wide suspension
Contract set upgrade	Deploy a new contract set beside the old one and make it active

Operator

Flow	One line
Monitoring and service reports	The read-only monitor, its checks, alerts and monthly report
Status lists	Configure and serve signed status lists

A credential's life

How the flows connect, from an institution joining to a verifier's check.

Conventions on flow pages

• UI labels are in bold exactly as the app shows them; routes are in backticks.
• "The issuer" means the issuer key in charge, which follows key retirements on sets that have them.
• "Signature" means a wallet signature that sends nothing; "transaction" means an on-chain write that costs gas.
• Unless a page says otherwise, a flow describes v0.3 with NEXT_PUBLIC_CONTRACT_VERSION=v03. Differences for the legacy v0.2 contract and for older contract sets are under each page's Variants heading.
• Time-sensitive facts (what is deployed or active on Sepolia) are as of 2026-10-24.