We’re building .zkdns: a public network for decentralised DNS and private proof. With .zkdid, your digital root stays under your control. Share the proof that matters, keep your personal information private, and carry your trust beyond any single app.
Discover how a proof can answer a specific question—such as “over 18?”—without handing every service a copy of your identity document.
New to zero knowledge? Curious about sovereignty? Ask ZKdude to explain the project in your language, at your pace.
Today, one small question can mean handing over an entire identity document. Zero-knowledge proofs offer a different way: prove the relevant fact and keep the underlying evidence private. .zkdid® is being built to give that proof a root you control.
An age check can reveal far more personal information than the question requires.
Your wallet uses an accepted credential to answer the specific request.
Threshold proved · Source details private · Illustrative example
Every copied document creates another database that must be trusted, secured and governed fairly.
DNS helps you find a website. .zkdns™ is being developed to find and verify trust. A .zkdid® root provides continuity and control, so changing an app need not mean starting your digital life again.
.zkdid® aims to make trust reusable across services while keeping the person, not a platform, in control of the keys and evidence.
.zkdns™ is the decentralised DNS and trust-resolution protocol. .zkdid® is its identity namespace. Together, our aim is a public network where no single company or government can own the directory of who gets to exist online. Your root comes first. Optional assurance adds a claim; it must never become permission to exist.
Start with continuity and control. A passport, wallet provider or blockchain must not own your root.
.zkdns is being built to find and verify records without one company owning the directory.
Add a specific claim when it is useful. Root control and assurance remain separate.
Prove a defined requirement. The service applies its own access rules above the root.
Your root carries control. .zkdns resolves trust. Assurance supports a specific claim. Zero knowledge can keep the underlying evidence private. These are separate roles, working towards one open foundation.
Root creation, continuity and controller authority sit below optional assurance. External systems may support the protocol without becoming sovereign over it.
Compatible services should be able to find records and check their authority through .zkdns. Public-network operation is still being developed.
The Alpha can add passport assurance through ZKPassport. That is an optional claim, not a tradeable token or the source of your right to a root.
The network should carry what needs to be verified while the personal evidence stays under your control. Privacy belongs in the infrastructure.
The Alpha demonstrates a passport-assurance journey. It does not yet prevent every duplicate enrolment or establish one human, one root across providers. Those limits are part of the research.
.zkdns and .zkdid are protocol-native names under development, not delegated public Internet DNS top-level domains. The working Alpha is not yet a public production network.
Meet the native iPhone Alpha. Create your root, add optional passport assurance, see the separate checks, and save an encrypted backup. Tap through the app journey below. These are illustrative screens; your identity stays out of this website.
Create a root you control. In this Alpha, the iPhone guides you and the paired Mac holds the cryptographic keys. You can add passport assurance later; it is optional.
Tap or swipe the phone. Use the arrows to go at your own pace.
Root creation, passport assurance, resolution and encrypted backup now form a working iPhone journey. The next work takes privacy and resilience deeper into the network.
The documented assurance flow shares no civil or passport attributes with the .zkdid adapter. Resolver nodes still process the opaque root and controller public material. Network metadata is not hidden.
Cold recovery, global human uniqueness, duplicate-enrolment resistance and production security are not established. The current Mac bridge uses HTTP; the Alpha is for supervised private-lab use.
Root control, assurance and application permission do different jobs. A service may decide what you can do inside its app. It should not decide whether your underlying root may exist.
Tap a glowing node to explore its role. Keeping these boundaries separate helps stop one provider from becoming the owner of your whole digital life.
.zkdid®
trust root active
The root should remain resolvable as infrastructure, not become a switch one institution can use to erase participation.
Proofs should disclose only what a request needs. The Alpha keeps civil attributes out of its assurance result, while root and network-metadata privacy remain unfinished.
Apps and institutions can set access rules higher up, while the trust anchor itself stays neutral and auditable.
The mission is open-source public infrastructure with no protocol token and no founder, company or government holding a universal root override. The stewardship model still needs evidence and review.
The private-lab proof of concept is a milestone. The next direction is privacy beneath the app: how trust is resolved, how requests travel, and how continuity survives change.
The freedom to participate online should outlast any app, device, company or government. That is why we are building .zkdns and .zkdid as open-source public infrastructure: no protocol token, no single owner of the root, and privacy designed into the fabric. Build it for people. Give it to the public.
The holder controls the root. Tools and controllers should be replaceable.
Continuity and controller authority remain separate from service policy.
A service verifies the relevant proof and applies its own scoped rules.