Callers
open the round
Somebody has to say what is being computed and on whose behalf. A caller fixes the program, the participant set and the rule for releasing the answer — then the terms are locked for that round.
Coordination layer live · Robinhood Chain · chain 4663
Different jobs.
One computation.
A round on ZKCoord is not one party running software for everyone else. It is three separate roles that only produce an answer when they are held by different hands.
The three roles
Contributors
supply the secrets
Contributors put in the values the computation is actually about. A bid, a ballot, a balance. It is encrypted before it is sent and it is never decrypted individually, only folded into the result.
Keepers
hold the shares
Keepers are drawn into a committee for a given round, jointly produce the round key, and later combine partial decryptions. One keeper holds nothing useful. A threshold of them holds the answer.
Participate
Pick the part you can actually carry.
Three tracks, no ranking between them. The network needs all three filled before a round means anything.
01
Run
a keeper
Keepers are the reason no single party can unseal a round. You provide a machine that stays up, answers when your committee is drawn, and contributes its share of the decryption on schedule.
A keeper handles:
- committee selection
- joint key generation
- partial decryption
- round attestations
02
Build
on top
If your product keeps running into a step where somebody would have to trust somebody else with raw data, that step is the one to move here. The submission interface does not change with the number of parties.
Common starting points:
- sealed-bid markets
- private governance
- cross-firm analytics
- agent-to-agent deals
03
Pilot
something real
Protocols get sharpened by awkward real deployments, not by demos. Bring a case with actual counterparties and actual consequences, and we will work through it in the open.
Useful shapes:
- consortium reporting
- public-sector ballots
- research collaborations
- supply-chain matching
$ZKCOORD
What the token is actually for.
Three jobs, all of them load-bearing. None of them is a claim on anything the protocol does not control.
Heads up — the contract address has not been published yet, so the address shown around this site is a placeholder and the market links below are inactive. Treat any figure on this page as sample data until that changes.
Acquire
The token is how the network prices the work of keeping it honest. Holding it is the precondition for the other two rows, and nothing more than that on its own.
Token pageChain explorer
Bond to keep
Keepers post a bond before they can be drawn into committees. It is the thing at risk if a node goes dark mid-round or misbehaves during decryption, which is what makes the threshold assumption worth anything.
Lock to steer
Locked balances carry proposal and voting rights over the parameters that actually matter: committee size, threshold ratio, release rules. Governance votes run through the protocol itself, so the ballots are sealed too.
Settles on Robinhood Chain · chain 4663 · ETH gas
Where the network is now
01
Closed devnet
02
Open testnet
03
Live rounds
Rounds are running on Robinhood Chain.
The committee set is still small and deliberately so. It grows as keepers come online, applications start opening rounds of their own, and parameter changes move to on-protocol votes.