01
Sealed
submission
Every participant encrypts locally before anything is sent. Raw values never leave the machine that produced them, and nothing on the wire is readable on its own.
Coordination layer live · Robinhood Chain · chain 4663
Compute together.
Reveal nothing.
Infrastructure for multiplayer privacy, enabling independent parties to coordinate without revealing their inputs.
A different execution model
ZKCoord turns a group of unwilling-to-share parties
into one working computation.
Inputs arrive encrypted, the work happens over ciphertext, and the answer comes back with a receipt. What each side brought to the table stays theirs.
Sealed
02
Threshold
committee
A committee drawn for that round holds key shares between them. No operator, and no minority of operators, can unseal a round alone.
03
Checkable
result
What gets published is the outcome plus a proof it was computed correctly. Anyone can re-check the arithmetic without seeing a single input.
What it unlocks
Things that were impossible to arrange before.
Every one of these stalls on the same problem: somebody has to see everything first. Remove that requirement and the arrangement becomes practical.
Auctions that
cannot be read
Bids stay sealed through the whole round, so nobody — including whoever runs the venue — can price against an order book they alone can see. The clearing price still settles publicly.
Votes without
a vote reader
Ballots are counted without ever being opened individually. The tally is provable, the individual choices are not recoverable, and there is no trusted teller to compromise.
Shared numbers,
separate books
Rival firms can learn an aggregate they all need — exposure, reserves, overlap — without handing each other the underlying ledgers that produced it.
Participate
The network is assembled, not deployed.
It only works because independent people run independent pieces of it. There are three ways in.
Hold a key share
Run a node, sit on committees when you are drawn, and take your part of the decryption work. Hardware requirements are modest; the commitment is uptime.
Operator notesBuild against it
Wire an application to submit sealed inputs and read back verified outcomes. The interface is the same whether two parties are involved or two hundred.
Integration notesBring a hard case
If you have a coordination problem that keeps dying on the disclosure question, describe it. Pilots are how the protocol finds out what it is missing.
Start a threadExplore
Go a level deeper.
The short version is on this page. The long version, the running network, and the day-to-day are all somewhere below.
Protocol
How a round is opened, who is drawn into the committee, what the proof actually attests to, and where the trust assumptions really sit.
Read the write-upNetwork
Blocks, contracts and token movement on the chain the protocol settles against. Everything below is public and checkable by anyone.
Open the explorerUpdates
Release notes, committee changes and the occasional longer piece on why a decision went the way it did.
Follow along$ZKCOORD · token page