For government & public sector

Digital identity that citizens hold, not a database you must defend.

Issue credentials and verify entitlement without building a honeypot of every citizen’s records.

BlockiDExample

My credentials · issued by an agency

Resident

Held on this phone · no central copy

Driving licencevalid
Benefit entitlementvalid

A service asks: “Is this person a resident?” — the answer is yes. Nothing else is shared.

The problem today

A central identity register is a single point of failure and a permanent political liability: it concentrates the entire population’s data in one place, it is a standing target, and citizens are asked to trust that it will never be misused or breached. Yet services still need to verify entitlement — age, residency, benefit status — reliably and at scale.

With BlockiD

Citizens hold their own credentials. Each service verifies the one fact it needs — with no shared mega-database to breach.

What you can do with it

Public services, proven. Not stockpiled.

Issue verifiable credentials

Issue a residency, licence or entitlement credential to a citizen’s own device. They present a proof of it; you hold no central copy to lose.

Entitlement without disclosure

A service confirms someone qualifies for a benefit without learning their full record. The proof answers one question and reveals nothing else.

Cross-agency, without a mega-database

Agencies verify the same credential independently. No shared central store is needed, so no single breach exposes everything.

Check a citizen at the desk

An officer shows a "Check a BlockiD" code. The citizen sees the office as a verified organisation, picks the facts and documents to share and approves with a fingerprint — nothing is shared without that step.

A shared document opens once

A shared document is fixed at the moment the citizen approves, opens once within 10 minutes, and the shared copy is erased afterwards. The citizen can also end a share at any time.

Inclusion and recovery

A lost phone does not mean a lost identity: a recovery phrase restores it on a new device, and a revoked device stops working immediately.

How it works for you

  • Citizens hold their own keys — the state does not custody them
  • Selective disclosure by default, so data minimisation is structural rather than a policy promise
  • Open standards (OpenID Connect, W3C DIDs, BIP-39 recovery) — no vendor lock-in
  • Every issuance and verification is auditable, on-chain where required

What you can rely on

  • Self-sovereign by construction: there is no central credential database to breach
  • Post-quantum cryptography for long-lived records
  • Deployable as a pilot within an existing agency before any wider rollout

Ready to start?

Creating a BlockiD takes seconds and needs no email. Your keys are generated on your device and never leave it.