Merces
- Name: Merces
- URL: https://docs.taceo.io/docs/finance-solutions/overview/
- Category: private-account payments middleware / confidential token transfer protocol / compliance-preserving finance rail
- Tags: ethereum-ecosystem
- Summary: Merces is best cataloged not as another privacy wallet, privacy chain, or generic stablecoin wrapper, but as a chain-local private-account rail for existing ERC-20 assets. Its official materials split the stack into ERC-20 wrapping on the EVM chain a team already uses, MPC-secret-shared balances and transaction history across TACEO Network operators, onchain CoSNARK-verified state transitions, per-transaction privacy-mode choice, and protocol-level selective-disclosure / wallet-registration compliance controls. That makes Merces a useful comparison point for privacy-preserving payment rails, shielded-intent systems, auditable privacy middleware, and private-finance infrastructure because the real control surface sits in account-state custody, gateway mediation, reveal-rights policy, and white-label issuer distribution rather than in one generic
private paymentslabel. - What it does:
- Wraps existing ERC-20 tokens such as USDC into a private form on the same EVM chain, so users get a private virtual account without migrating to a new chain or asset
- Keeps balances and transaction history in encrypted / secret-shared form across the TACEO Network while publishing only proof-checked commitment updates to the host-chain contract
- Supports two transfer modes selectable per transaction: confidential mode where amounts and balances are hidden but parties remain visible, and fully private mode where sender, receiver, amounts, and balances are hidden
- Exposes compliance primitives including scoped selective disclosure, wallet registration, optional policy checks at onboarding, and administrator-controlled restrictions or blocklisting
- Positions itself as API / SDK / white-label infrastructure for stablecoin issuers, fintechs, payment systems, and AI-agent payment flows rather than only as a direct retail wallet app
- Extends the same private-account model toward adjacent products such as confidential x402, private yield, and future private DeFi flows
- Key claims:
- Merces clears the bar because it does not flatten privacy into one generic
shielded transferfeature. The reviewed materials keep private-balance custody, proof-verified settlement, privacy-mode selection, and compliance reveal policy analytically distinct. - The strongest reusable mechanism is the private-account model. Merces argues that real financial privacy requires hidden persistent balances, history, and counterparties, not only hidden transaction amounts.
- The docs repeatedly emphasize that Merces comes to the chain an issuer or fintech already uses. That makes chain-local deployment and ERC-20 wrapping a meaningful design choice versus privacy-first alternative L1s or app-specific sidechains.
- The onchain contract remains the source of truth even though execution of private-state updates happens through the TACEO Network. That separation makes Merces a good comparison point for other systems that keep private state offchain while anchoring correctness onchain.
- Fully private mode introduces an extra control surface beyond confidential mode: the docs say a gateway service abstracts gas payment and submitter identity so the transaction graph itself stays opaque. That means graph privacy depends not only on cryptography, but also on relay / gateway design.
- Compliance is not an afterthought in the reviewed materials. Selective disclosure, wallet registration, blocklisting, and planned proof-of-compliance / MPKYC / Travel Rule flows show that Merces treats privacy and lawful reveal rights as co-designed protocol surfaces.
- Merces belongs in the active corpus because it makes a distinctive comparison layer visible between privacy infrastructure and payments infrastructure: issuer-facing private accounts on public EVM rails with scoped auditability and explicit white-label distribution.
- Merces clears the bar because it does not flatten privacy into one generic
- Whitepaper: The core protocol paper is
../whitepapers/merces-confidential-token-transfers-via-mpc-and-cosnarks-2026-850.pdf, with primary-source notes collected in../whitepapers/merces-primary-sources-2026-05-13.md. - Sources:
- https://docs.taceo.io/docs/finance-solutions/overview/
- https://docs.taceo.io/docs/finance-solutions/payments/introduction/
- https://docs.taceo.io/docs/finance-solutions/compliance/introduction/
- https://core.taceo.io/articles/merces-onchain-finance/
- https://merces.taceo.io/
- https://eprint.iacr.org/2026/850
Internal linkages
-
Stablecoin-issuer and reserve-policy contrast once private balances get packaged for fintech or issuer distribution: agora and m0.
-
Account-discovery and durable-authorization contrast: open-payments.
-
Keep the note on private account state, reveal rights, and gateway mediation. It is not just another privacy-wallet entry.
-
Last reviewed: 2026-06-01 UTC