ryanwold.net - Civic Tech, Bitcoin, and Open Government Innovation

Title

Text

https://afomi.github.io/did-page/

Decentralization is an important concept and pattern unfolding as information networks take shape in the form of software shaped hardware and signal networks across the planet, and above, in space.

Decentralized Identifiers, or DID's, for short are a way to establish identity at the edge of networks, and then have interactions with those identities rollup or sum to meaning or legitimacy in some respect --- just like a reputation is based on a series of interactions.

DID Page was created to demonstrate how DIDs can:

* create a Decentralized Identifier (DID)
* using a DID, issue a Credential
* as a Verifier, request to see a Credential and have it authorized
* as a User, be able to present my Credential to a Verifier, when queried
* as a Verifier, be able to verify the credential's validity (authentication) **and optionally** be able to determine the credential's timeliness (authorization)

----

#### What is a DID in plain language?

Think of a driver’s license or employee badge — it proves who you are so you can access services, sign documents, or enter places.
A Decentralized ID is like that, but digital, and you (not a government office, not a tech company) hold it directly — usually in a secure app on your phone or computer.

Instead of a central database that can be hacked or shut down, DIDs work like a unique web address that points to secure proof of your identity, controlled by cryptography.
Others can check that proof without calling a central office, and you can prove things about yourself without oversharing personal data.

Why it’s important

Data control: You decide what information to share and with whom.

Privacy & security: No big central “honeypot” of personal data for hackers to target.

Interoperability: One ID works across many services — no need to re-prove who you are each time.

Trust at scale: Communities, agencies, and organizations can verify claims instantly, even across borders.

Responsibilities it implies

For the holder:

Keep your digital wallet/keys safe — losing them is like losing your passport.

Keep your information current and revoke outdated credentials.

For the issuer (agency, nonprofit, business):

Issue credentials honestly and accurately.

Maintain the ability to revoke or update credentials when needed.

For the verifier (anyone checking credentials):

Verify only what’s needed — don’t collect more personal info than necessary.

Respect privacy rules when storing or acting on credential data.

What it will enable easier and cheaper than today

Proof of service eligibility (e.g., “I’m a resident of this county” or “I qualify for this benefit”) without scanning ID cards or keeping paper copies.

Cross-organization verification without faxing, emailing, or calling other offices.

Fast onboarding for programs, volunteers, or contractors without repeated background checks.

Digital signatures on forms and agreements without mailing or in-person visits.

What it will enable that cannot be done today

Selective disclosure: You can prove “I’m over 18” without showing your birth date or address.

Instant, cross-border recognition: A credential issued by one organization can be recognized anywhere in the world, without new integration.

Portable reputation: Volunteers, professionals, or vendors can carry a verifiable record of their skills, certifications, or good standing from place to place — even if an issuing organization shuts down.

Offline verification: Credentials can be checked without internet access, useful in disaster response or rural areas.

If you like, I can follow this with three short, concrete real-world scenarios — one in local government, one in nonprofit aid delivery, and one in cross-agency emergency response — to make the benefits vivid. That would make this explanation even more compelling for your audience.

An entry