Proofs run in your browser today · group book not deployed yet
Prove More. Reveal Less.
Zekro is a zero-knowledge proof studio. Building a clearer way to review onchain access. Show that you belong to a group without saying which member you are, and let anyone check it.
secret stays in your browser · no accounts · no analytics
ProvingIn your browser, in a worker
CircuitNoir, group membership
Reused proofsOne nullifier per scope
NetworkRobinhood Chain 4663
live · Robinhood Chainchainlink + rpc · read from chain 4663
ETH···Chainlink ETH/USD
Block···chain head
Gas···what a proof submission pays for, nothing else
Two sides
What a proof says. What it never covers.
A proof is a narrow thing, and that is the point. Read both cards before you rely on one. The limit in the second card repeats in the footer of every page, because it is the part people skip.
Side 1 · the circuit
The statement
One sentence, checked by math: I know the secret behind a commitment in this root, here is its one nullifier for this scope, and this proof is tied to this message.
Which member you are stays out of the proof
A second proof in one scope is refused
Change a public value and the check fails
Side 2 · everything else
The limit
A zero-knowledge proof proves only the statement designed into the circuit. It does not make your activity anonymous. Your wallet address, IP, network metadata and transaction activity can stay visible through other layers.
The wallet that sends a proof is public
Your network can see that you visited
Timing and habits can link actions over time
How a proof runs
Five steps. One of them leaves your device as a proof.
Groups live in a public book on Robinhood Chain. Your secret never joins them. Only the commitment and, later, the proof and its public values do.
01
Make an identity
Your browser draws a secret and a salt and hashes them into a commitment. The secret stays on your device. The commitment is the only part you hand over.
02
Join the list
A curator adds your commitment to the group, in plain view. Nothing about the list says who stands behind each entry, unless you sent yours from your own wallet.
03
Publish the root
The curator publishes the Merkle root of the list and the digest it came from. Anyone can rebuild the tree from the same list and compare.
04
Prove
Your browser shows you hold the private values for some leaf, ties the proof to your message and derives one nullifier for this scope. It takes seconds, on your own machine.
05
Verify
Anyone runs the check: in a browser with the published key, or on chain through the verifier contract. A used nullifier is refused. The sending wallet remains public.
Why a circuit
A question you can check without asking us.
Membership checks usually mean showing a server who you are. A circuit moves the check to math that anyone can run, which also makes its limits easy to read.
01
A checkable statement
A signature says which key signed. A list check says which entry matched. A circuit lets a group ask one narrower question, whether this person belongs, and check the answer without the rest.
02
No one to ask
A gatekeeper server has to see who is asking, and you have to trust what it logs. A proof is checked with math and a public key, by anyone, with no account and no call back to us.
03
Written limits
The circuit is a short public file. What it does not state, it does not protect. That is why the wallet, the network and the timing are named on every page here, instead of hidden behind a word like private.
For developers
Zekro is an open circuit, a verifier and a group book.
Read the Noir source, rebuild the verifier, and call verify or submitProof from your own contract. Hosted proving and an API are planned, not live.
Zekro is a zero-knowledge proof studio on Robinhood Chain. A community keeps a list of members as commitments, publishes the Merkle root of that list, and a member proves in the browser that one of those commitments is theirs, without saying which one. Anyone can check the proof.
Does a Zekro proof make me anonymous?
No. A zero-knowledge proof proves only the statement written into the circuit. Your wallet address, IP address, network metadata and transaction activity can stay visible through other layers. If you submit a proof from your everyday wallet, that wallet is on the transaction for everyone to read. The proof hides which member of the list you are, and that is all it hides.
What ends up public on chain?
When a group is built: the admin's wallet, every commitment, and every root. When a proof is submitted: the sending wallet, the root it used, the scope, the nullifier, the signal, and the time. It does not see the secret, the salt or which leaf the proof belongs to. The review page lays out every value for a proof you paste in.
What stops one member from proving twice?
The nullifier. It is derived from the member's secret and the scope, so one identity produces one value per scope. The contract records it and refuses a second proof with the same value. In a different scope the value is different and cannot be linked to the first by the math alone.
What can go wrong?
Lose your identity backup and that membership is gone; nobody can restore it. A group admin decides who gets on the list and can pause the group, so a group is only as fair as its admin. A root is published by a curator, and the contract cannot recompute it; the review page rebuilds it from the list so you can compare. The circuit and contracts are new code and no outside firm has examined them. Use them for what you can afford to have go wrong.
Are the contracts live?
Yes. The group book and its verifier are live on Robinhood Chain. The stats page reads them directly. The circuit, the prover and the checks in your browser are the ones this site serves.
How do I get $ZEKRO?
$ZEKRO has not launched. When it does, it launches on Pons on Robinhood Chain and the only address is on the token page. The studio works without it. Any use for the token is planned, not live.
The studio is open
Make a real proof in the next minute.
No wallet needed to try it. A real circuit, a proof your own device computes, and a check that spells out what it covers and what it leaves out.