Distributed MPC
For private computation.
Data enters as secret shares split across independent operators. Each performs computation on their share and arequest completes only when a threshold of them take part.
TACEO Network
The private execution layer for digital rails
The TACEO Network is a distributed MPC network.
Sensitive data is held as cryptographic shares by independent operators, so no single operator controls the data, the keys, or the outcome. Every output carries a proof, verifiable onchain.
How it works
Collaborate privately.
Prove publicly.
The TACEO Network runs computation on data that nobody can see.
Three pieces make that possible.
Oblivious map
For private storage and retrieval.
Private state lives in an encrypted key-value store. Reads and updates reveal nothing about which record was touched.
CoSNARKs
To provide verifiability.
Every output carries a zero-knowledge proof, verified onchain. Anyone can check the work was done correctly.
Operator-blind
No operator on the network,
including TACEO, ever sees the plaintext.
Shares without the rest are noise.
The protocol enforces it.
Cryptographic privacy
The alternatives keep someone who can see, or are too slow for real-world use.
Validiums and shielded pools still have an operator who can see. Enclaves put the trust in hardware, and hardware has been broken before. FHE avoids both, at a cost in overhead that rules out real-time settlement.
The TACEO Network is secret-shared across independent operators, so no party holds plaintext, and you choose how much is hidden: amounts alone, or the full graph.
Threshold MPC runs state lookups and updates at real-world latency.
Who runs the network
The TACEO Network runs across a curated group of independent operators.
A deliberate balance of professional infrastructure providers and academic and institutional partners. Operators are independent of one another, accountable in different jurisdictions, and answerable to different incentives. The threshold assumption holds because of who runs the network, not just the cryptography beneath it.
And you can be part of it. Customers can run their own node on the network, joining the operator set and holding part of the threshold that protects their own deployment. ZKPassport already does, helping operate the network it builds on.
Operators
Cryptography
Output
- Infra
provider Operator A - Infra
provider Operator B - AcademicOperator C
- AcademicOperator D
- Customer operated nodeCustomerOperator E
Private execution layer
Verified outputCoSNARK proof onchain
The operators running
the TACEO Network today.
Network operators
The teams running the protocols and the labs advancing the science operate the same network.
What runs on the networkExplore services
Four privacy services run on the network.
TACEO:Proof
CoSNARK generation, run by the network. Your application gets a verifiable proof; no single party sees the witness.
TACEO:OPRF
Unique, unlinkable nullifiers from a user's input, without anyone seeing the input. In production for World and ZKPassport.
TACEO:OMap
Private key-value state. Reads and updates reveal nothing, including the access pattern.
TACEO:Match
Biometric matching where no party ever holds a template.
Chain-agnostic by construction
The network does not pick a chain.
CoSNARK verifiers can be deployed to any chain with the relevant primitives. Current deployments run alongside the Base, Arc, Monad and Plasma testnets. New chains are integrated, not migrated to.
Live network
The network, live.
- ~8.4MPrivate requests processed
- 572 msSub-second MPC latency
- 18Decentralised MPC nodes
Building on the TACEO Network?
Let's talk about your workload.