Block Gemini

Explore the connected ecosystem.

What does a verifier need to know before site entry?

A contractor presents a fictional site-induction credential. Compare a valid induction, an unrelated certificate and a revoked induction while keeping other personal information out of the check.

Scope my credential workflow

Interactive example · fictional records

Inspect a presented credential

Site induction · Access desk

Required claim
Induction for this site
Issuer and status
Equipment training · current
Access desk result
Site induction unconfirmed
Different certificate
Review decision

Ask for the credential the decision requires

The presented certificate may be genuine, but it covers equipment training. The desk needs a site-induction claim from an accepted issuer.

Scope my credential workflow

What we can build with you

An issuer, holder and verifier workflow with minimum required claims, status checks and an operator path for exceptions.

Bring to discovery
Bring one access decision, its accepted issuers, a status source and the person responsible for resolving failed checks.
How to test the pilot
Present a current, unrelated and revoked credential. Inspect exactly what the desk sees and the outcome for each.
Implementation details and questions

Organisations issuing, sharing or checking credentials as part of a defined business process.

Design issuer, holder and verifier experiences for digital credentials and controlled identity exchange. We connect credential lifecycle, status checking, consent and relying-party integration to the business process.

  • Workforce or partner credentials
  • Controlled onboarding and eligibility records
  • Issuer and verifier application integration
  1. Define the credential

    Agree issuer authority, claims, expiry and status rules. Identify the minimum information a relying process needs to receive.

    A credential schema and trust model
  2. Issue and present

    Build issuer and holder experiences with the agreed identity and consent flow. Integrate the chosen credential format and signing mechanism.

    A controlled issuance and presentation flow
  3. Verify the right context

    Check signature, issuer trust, status and the requirements of the receiving process. Route invalid or unclear cases to a defined review path.

    A verification decision with reasons

Issuer systems → signed credential → holder/presentation → verifier and status checks → relying workflow. Blockchain is optional; the trust and interoperability requirements determine the approach.

  • Issuer, holder and verifier journeys
  • Credential schema and lifecycle
  • Verification and status integration
  • Consent and recovery design

Start with the claim a verifier needs and the authority behind it. Minimise the information exchanged around that purpose.

  • Cryptographic verification confirms defined properties of a credential, not every underlying real-world claim.
  • Identity assurance, privacy and legal acceptance depend on the chosen ecosystem and business requirements.

Bring to discovery

  • Issuer, holder and verifier responsibilities
  • Credential claims and status requirements
  • Identity, consent and application interfaces
Is blockchain required for digital credentials?

No. Credential formats and verification flows can work with different trust registries and infrastructure. We choose the design around the required ecosystem.

Can a credential be revoked or expire?

The lifecycle defines expiry, status checking and replacement or revocation rules where supported. Verifiers must use that information in their decision.

Verify a credential at the point of access

For credential issuers and organisations that rely on another party’s evidence to grant access. Take a contractor arriving for their first shift.

How the work moves

The training provider issues a safety credential. The contractor agrees to share the required attributes. At check-in the site verifies the issuer, expiry and current revocation status before deciding whether to admit the holder. An unavailable status check goes to a supervisor.

What we connect and deliver

We map the issuer’s training register to the credential fields, design the holder’s consent screen and connect a verifier to the relying party’s access workflow. The site sets its admission rules and records the decision.

Where to start

Bring one credential, an issuer and a relying party. Together we define the data each party can see and specify tests for a valid, expired and revoked credential.

Scope a credential pilot