Fits in the README.
Fits on the slide.
Two letters, a dot, two letters. Keep the complete ZK name in a five-character address you can put on demos, docs and conference slides.
Give your prover, zkVM or privacy protocol a name that starts with its field. Read zk.cr as zero knowledge + cryptography. Four letters and one dot for what you’re building next.
ZK leads every link. CR completes a cryptography-inspired name. From your README to your launch announcement, zk.cr gives your work a concise identity you can build around.
// A name for your next buildconst identity = { zk: "zero knowledge", cr: "cryptography"}; const address = "zk.cr";Two letters, a dot, two letters. Keep the complete ZK name in a five-character address you can put on demos, docs and conference slides.
There is one zk.cr. Acquiring it gives your team control of what lives at this exact address, from the root site to its subdomains.
Point it to your first demo. Add your developer resources. Launch your product under the same compact ZK identity as your work evolves.
A home for your prover, zkVM or verification service. Put proof demos, API docs and integration guides under one name.
zk.cr/docsA dedicated place to explore identity proofs, private-data verification and credentials. Let the name introduce your ZK work.
zk.cr/verifyThe link on your next workshop slide. Bring papers, tutorials and events together, with a clear place for your community to return.
zk.cr/researchExample paths for a future owner’s website.
Give your next ZK product an address of its own. Start a conversation with the owner about acquiring zk.cr.
One exact domain. Offered directly by the owner.
Share your intended use, ask a question or make an offer.
Verify domain control. Agree the price, payment process, renewal costs and transfer details.
Complete the agreed ownership transfer and connect the address to your work.