Zero-knowledge decentralised DNS Humans, agents and devices Self-sovereign identity roots

Private proof for a world of humans, agents and devices.

.zkdid™ is a proposed zero-knowledge decentralised DNS trust layer for proving uniqueness, continuity and integrity without exposing raw identity data, surrendering sovereignty, or depending on closed registry power.

See how it works View grant proposal
Verify without disclosure Resolve without capture Prove without profiling Own keys, own identity
What it is

Identity should not live inside someone else’s database.

.zkdid™ is zero-knowledge decentralised DNS for identity: a neutral naming and trust root that helps humans, agents and devices prove continuity without handing over raw data or depending on one platform’s closed registry.

Plain-English idea
“Not your keys, not your identity.”

If one company controls the account, the recovery path and the resolver, then your digital identity still lives on someone else’s terms.

Today

Identity can become a kill switch.

When identity lives inside one platform account, access can be disabled, frozen, profiled or pressured.

  • A lost login can mean lost services, reputation and proofs
  • Copied documents create permanent exposure and data trails
  • Central recovery becomes a pressure point for platforms, attackers or states
  • The danger is not verification, it is central control over existence
  • Traditional DNS was not built for W3C DID trust anchors; decentralised DNS is
Why decentralised DNS matters

A public trust root below apps.

Instead of every app owning identity, a neutral root can anchor names, continuity and proof while your keys stay with you.

Keys stay local Proof instead of oversharing One root, many services
With .zkdid™

Equal power at the root.

.zkdid™ aims to make trust portable, public and harder to capture, useful to apps, but not owned by them.

  • Individuals keep keys and prove only what is needed
  • No king registry: open rules, public artefacts and auditable roots
  • Continuity can move across wallets, services and ecosystems
  • A public-good layer can serve humans, agents and devices equally
No kings. No silent capture. Proof without ownership.
Human continuity Agent accountability Trusted devices Wallet-ready Zero-knowledge proof
Storyboard proof flow

A private proof journey, shown as a device-native flow.

The storyboard turns the architecture into a human-readable journey: keys stay hardware-bound, credentials remain local, the registry receives commitments rather than identity data, and verifiers receive fresh scoped proofs.

Local firstKeys and raw credentials remain on the device.
Proof basedCommitments and nullifiers reduce duplicate or synthetic actors.
Resolver awarePublic verification material is exposed without raw identity.
Lifecycle safeRecovery and credential updates preserve continuity without exposing the person.
Step 01 / 10

Private onboarding on a sovereign phone root.

The user begins locally. Keys stay device-bound, and no raw biometrics or personal documents leave the phone.

Swipe or tap the phone to move through the steps.

Discuss the flow
Architecture direction

Built as a public-good trust substrate, not a platform trap.

The architecture keeps identity existence separate from service-level authorisation, so policy can sit above the root without one actor becoming the power to erase participation.

ApplicationsWallets, services, agents, IoT networks
Zero-knowledge dDNS trust layerNames, roots, proof, continuity, verification
Open rootsCryptographic proofs, decentralised state, standards mapping
Trust boundary explorer

See what .zkdid™ keeps separate.

Tap a node in the diagram to open the matching layer below. The point is simple: sovereignty improves when existence, proof, policy and governance are not collapsed into one controllable chokepoint.

.zkdid™ trust root active
Identity existence

The root should remain resolvable as infrastructure, not become a switch one institution can use to erase participation.

Scoped proof

Services receive fresh proof material for the interaction, not a reusable identity profile or raw biometric record.

Policy above the root

Apps and institutions can set access rules higher up, while the trust anchor itself stays neutral and auditable.

Capture resistance

Open standards, public artefacts and decentralised governance reduce the risk of platform or registry capture.

Next step

From concept, to lab, to public protocol identity.

This root site frames .zkdid™ as a living public-interest protocol initiative rather than only a funding document.

01ConceptPublic thesis, trust model and visual explanation.
02LabResearch, review and architecture hardening.
03Open artefactsReusable documents, prototypes and standards notes.
04Public protocolCommunity-governed identity-root infrastructure.
Grant ask Contact
Visual sovereignty map

Trust should move as proof, not as control.

A visitor should be able to see the core principle: the person keeps secrets local, the trust layer anchors proof, and the service verifies only what it needs.

01

Private holder

Human, agent or device keeps keys and sensitive source material local.

02

.zkdid™ root

Commitments, resolver material and continuity live below service policy.

03

Scoped verifier

The service checks proof without taking ownership of the underlying identity.