Government, distributed
What governments can do when credentials are cryptographic, portable, and selective.
Why you should care
Governments have always been in the identity business. Birth certificates, driver’s licenses, passports, voter rolls, professional licensure — issuing and verifying claims about people is a core function.
The digital version of this has taken two forms so far, and neither is working well.
One is the national ID database — a centralized record of every citizen, queried by every service. It’s efficient and breachable, and it makes “show me your papers” trivially easy to demand. The other is the per-agency silo — every department runs its own identity system, rebuilt each time, interoperable with nothing. Citizens prove the same facts over and over, to systems that don’t talk.
Decentralized Identifiers offer a third path: the government issues credentials, not accounts. The credential is cryptographically verifiable, held by the citizen, and revealed selectively. The database, such as it is, is the set of issuances and revocations — not a map of who did what.
Before
Today, the digital-identity landscape for governments is a set of tradeoffs, none of them great.
- Physical documents get photocopied. A driver’s license is a piece of plastic with a photo and a magstripe. Every bar, every rental counter, every pharmacy takes a copy of everything on it to verify one thing.
- Centralized identity databases get breached. When they do, the blast radius is every citizen at once.
- Cross-border recognition is manual. A degree from one country, a license from another, a voter registration moved across a state line — each involves paperwork, delays, and often redoing the underlying verification.
- Services get rebuilt per-agency, per-country, per-decade. Tax filing, benefits enrollment, vehicle registration, professional licensing — each runs on its own identity model, with its own login, its own assumptions about what a “person” is.
- Privacy erodes by default. Proving you’re over 18 requires handing over your birthdate, your name, your address, and often your photo. The system asks for everything because it doesn’t know how to ask for less.
After
With DIDs and the Verifiable Credentials that ride on them, each of these becomes tractable.
- A driver’s license becomes a credential in your wallet. Signed by the state’s DID. Verifiable offline. Presented in full, or sliced — “over 18, license valid, issued by this state” — without revealing the rest.
- The issuer runs the revocation list, not the identity store. Citizens hold their credentials. The government maintains a short, queryable status list. There’s no central map of “who used their license today.”
- Cross-border recognition becomes a resolver check. A license from one jurisdiction carries a credential signed by that jurisdiction’s DID. Another jurisdiction’s systems can verify it without a bilateral data-sharing agreement for every use case. eIDAS 2.0 in Europe is already building toward this shape.
- Services compose. Tax filing reads a credential from the census DID, a credential from your employer’s DID, a credential from your bank’s DID — each cryptographically verifiable, each under your control to present or withhold. No single system needs to hold all of you.
- Selective disclosure becomes routine. The pharmacy asks “over 18?” and gets a yes-or-no, signed by the state. Your birthdate stays home.
What fades
Some longstanding patterns start to look like historical artifacts.
- “Show me your papers” becomes thinner. The question becomes “can you present this specific claim?” — which is weaker by design.
- Credential re-issuance at every transition. Moving states, changing names, renewing licenses — these stop cascading across every service you use.
- Per-agency identity silos give way to a shared issuer/verifier model. Agencies issue credentials; the citizen’s wallet carries them; services verify them. Boring infrastructure instead of bespoke integrations.
- Breach-of-everything events. The blast radius of any single system compromise shrinks when there’s no central database of everyone’s everything.
- Vendor lock-in on identity. Governments stop being hostage to a single vendor’s “digital identity platform” and start publishing open, verifiable credentials that any compliant wallet can hold.
The new normal
By 2030, the better-governed jurisdictions will look something like this.
Every government-issued document — license, registration, certification, benefit eligibility — is available as a Verifiable Credential, signed by the issuing agency’s DID, held in a wallet the citizen chooses. Open standards, multiple implementations, no single vendor owns the stack.
Services don’t ask for copies of documents. They ask for claims, verifiably. “Resident of this state.” “Holds a current teaching license.” “Eligible for this benefit.” Each question gets the minimum answer the credential can give.
Cross-jurisdictional work gets easier. A nurse licensed in one state works in another by presenting a portable credential. A refugee arrives carrying signed credentials from home — education, professional qualifications, civil status — that the new country can verify without rebuilding them from scratch. The credentials don’t solve policy; they make policy choices visible instead of hidden behind administrative friction.
Government, in this model, is an issuer of truth — not a surveiller, not a database custodian. The role the public most wants it to play, and the one it’s been least well-equipped to play digitally.
This is the quietest transition of the three. Most citizens will never hear the word “DID.” They’ll just notice that renewing a license takes twenty seconds, that proving their age doesn’t require handing over their life, and that their credentials follow them across borders the way their passport used to promise but rarely delivered.
Want to see it in action? Install WeDID. Want to issue credentials yourself? Start here.