TACEO primary sources — 2026-05-13

What I reviewed

• Docs entrypoints:
  • https://docs.taceo.io/
  • https://docs.taceo.io/docs/
• Network docs:
  • https://docs.taceo.io/docs/taceo-network/
  • https://docs.taceo.io/docs/taceo-network/network/
  • https://docs.taceo.io/docs/taceo-network/governance/
  • https://docs.taceo.io/docs/taceo-network/node-operators/
• Service / product docs:
  • https://docs.taceo.io/docs/services/overview/
  • https://docs.taceo.io/docs/taceo-proof/overview/
  • https://docs.taceo.io/docs/finance-solutions/compliance/introduction/
  • https://merces.taceo.io/
• Repository context:
  • https://github.com/TaceoLabs/co-snarks
• Research paper saved locally:
  • merces-confidential-token-transfers-via-mpc-and-cosnarks-2026-850.pdf from https://eprint.iacr.org/2026/850.pdf

Key takeaways from primary sources

• TACEO is best understood as a private-execution stack rather than a single product. The docs separate the underlying committee-based MPC network from the individual services that run on it and from the application-layer products built on top.
• The service decomposition is the main analytical value. TACEO:OPRF, TACEO:Proof, OMap, Match, and Merces are not presented as one monolith; they are workload-specific services with their own coordination and integration surfaces.
• TACEO:Proof is an especially useful comparison point because it keeps several usually-flattened layers distinct: blueprint admission, voucher authorization, node-set selection, encrypted-share submission, MPC execution, and standard-proof output.
• The docs make governance and operations explicit. TACEO currently coordinates service approval, node participation, software upgrades, and incident response together with curated independent operators. That means the control plane is visible rather than hidden behind generic decentralization language.
• Merces pushes TACEO into the finance/compliance layer rather than stopping at outsourced proof generation. The reviewed docs emphasize encrypted transaction graphs, scoped decryption requests, wallet registration, blocklisting, and privacy-preserving compliance queries as first-class design goals.
• The Merces paper is useful because it shows TACEO is publishing a proper research artifact for at least one major application layer, not only marketing pages and developer docs.

Specific source signals worth retaining

• docs/taceo-network/network: best explanation of TACEO’s private shared state framing and service-instance / committee execution model.
• docs/taceo-network/governance: clearest statement that TACEO still coordinates approvals, node participation, upgrades, and incident response in the current phase.
• docs/taceo-network/node-operators: best concise articulation of the committee trust model and current permissioned operator posture.
• docs/services/overview: best compact map of the current service family and how TACEO wants applications to integrate it.
• docs/taceo-proof/overview: strongest mechanism page for blueprint / voucher / node-provider / CCL structure and for standard-Groth16 output compatibility.
• docs/finance-solutions/compliance/introduction: strongest source for why TACEO belongs in the onchain-finance privacy cluster rather than only in proving infra.
• co-snarks repository: best evidence that TACEO is shipping concrete coSNARK tooling for Circom and Noir rather than only operating hosted APIs.

Why this entry belongs in the corpus

• It gives the corpus a concrete MPC private execution as shared service infrastructure comparison point.
• It bridges several clusters that would otherwise stay too separate: privacy-preserving identity infrastructure, outsourced proof generation, confidential shared state, and regulated private payments.
• The durable insight is that TACEO should be analyzed as a network-and-service control plane for private computation, not just as a proving company, not just as Merces, and not just as World-adjacent MPC infrastructure.