local PDF: merces-confidential-token-transfers-via-mpc-and-cosnarks-2026-850.pdf
Key takeaways from primary sources
Merces is best understood as a private account system for existing ERC-20 assets, not merely as a one-off hidden-transfer gadget. The docs are explicit that private balances, counterparties, and transaction history matter as much as hiding amounts.
The system wraps tokens on the EVM chain a team already uses instead of asking users or issuers to migrate to a new privacy chain. That makes deployment location a central analytical distinction.
Private state sits with the TACEO Network: balances are maintained as secret shares and encrypted history, while the host-chain contract only accepts updates when CoSNARK-backed state transitions verify.
The docs separate two privacy modes that should not be flattened together: confidential transfers hide amounts but keep sender/receiver visible, while fully private transfers also hide sender and receiver.
Fully private mode adds a meaningful operational dependency. The payments docs say a gateway service abstracts gas payment and submitter identity so the transaction graph remains opaque.
Compliance is built into the reviewed product story rather than added later. Selective disclosure, wallet registration, optional policy checks, and blocklisting are already part of the current materials, with proof-of-compliance bundles, MPKYC, and Travel Rule flows framed as next steps.
Distribution matters. Merces is positioned as SDK / API / white-label infrastructure for stablecoin issuers, fintechs, payment infrastructure teams, and AI-agent flows, not only as a retail application.
The paper adds the lower-layer mechanism detail missing from product pages: Merces translates existing ERC-20 tokens into confidential versions by storing secret shares in a decentralized MPC network, publishing commitments onchain, and proving valid state transitions with collaborative SNARKs, with the implementation benchmarked at more than 300 TPS.
Specific source signals worth retaining
finance-solutions/overview: strongest compact source for Merces as TACEO’s finance-layer product, the two payment/privacy modes, compliance positioning, confidential x402, and current testnet / throughput claims.
payments/introduction: best concise source for the white-label distribution model, the two privacy modes, host-chain deployment without migration, and the gateway dependency in fully private mode.
compliance/introduction: clearest source for scoped decryption, wallet registration, administrator restriction / blocklist policy, and the future MPKYC / Travel Rule direction.
core.taceo.io/articles/merces-onchain-finance/: strongest narrative source for the shift from private transactions to private accounts, plus the shared encrypted-ledger framing and how Merces II extends Merces I.
merces.taceo.io: minimal but useful confirmation that the live demo is framed as private onchain accounts rather than only confidential transfers.
eprint 2026/850: strongest source for the exact cryptographic architecture — decentralized MPC network, commitments onchain, CoSNARK state-transition proofs, Groth16 / BN254 / Poseidon2 instantiation, UC formalization, and end-to-end benchmark claims.
Why this entry belongs in the corpus
It gives the corpus a concrete comparison point for chain-local private-account finance rails rather than only privacy pools, privacy chains, or generic confidential-compute infrastructure.
It exposes a reusable split between private-state custody, onchain validity enforcement, gateway-mediated graph privacy, and protocol-level lawful reveal rights.
Keeping Merces distinct from TACEO is analytically valuable because otherwise the corpus would preserve the network/service layer but lose the issuer-facing confidential-finance control plane built on top of it.