TACEO

"Private" and "compliant" are considered to be a tradeoff. They're not. Today we ship the proof. @0xPredicate is now the enforcement partner in the 𝐌𝐞𝐫𝐜𝐞𝐬 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐄𝐧𝐠𝐢𝐧𝐞. Gate and audit, both now in product. Compliance for private payments is two problems, and they sit on opposite sides of the transaction: - Before a transfer settles (should this happen at all?) - After it settles (what happened, when an auditor asks?) The "after" half has been live since March. Through the Compliance Dashboard, authorised parties can request to audit specific transactions for regulatory purposes. Nothing beyond those transactions is exposed. 𝗪𝗲'𝗿𝗲 𝘀𝗵𝗶𝗽𝗽𝗶𝗻𝗴 𝘁𝗵𝗲 "𝗯𝗲𝗳𝗼𝗿𝗲" 𝗵𝗮𝗹𝗳! Predicate now screens each confidential transfers against the operator's policy before they settle: sanctions, AML, CFT. Compliant transfers proceed. Non-compliant ones are rejected, with a reason returned to the user. The policy stays with the institution. Predicate enforces what the operator defines, on every transfer, and policies update as regulations change without touching the deployment. Clean division of labour: - @0xPredicate handles policy and enforcement. - @TACEO_IO handles private storage and controlled disclosure. Together: 𝐚 𝐟𝐮𝐥𝐥 𝐜𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐬𝐭𝐚𝐜𝐤 𝐰𝐢𝐭𝐡 𝐧𝐨 𝐩𝐥𝐚𝐢𝐧𝐭𝐞𝐱𝐭 𝐝𝐚𝐭𝐚 𝐭𝐫𝐚𝐢𝐥.

In the last hours people asked me what happens with the funds if the TACEO network is down. There is an built-in escape hatch. So user can directly withdraw funds. No need to wait or hope that the network is back again.

"Once everyone builds through one neutral layer, something interesting happens. The layer stops being just co-processing infrastructure and starts accumulating state."

@Cloudflare 🔥

We're opening the waitlist for our Monetization Gateway, which will allow you to charge for any web page, dataset, API, or MCP tool behind Cloudflare. The charges will settle in stablecoins over the x402 open protocol. cfl.re/4eUFdt6

4 years ago today: we founded TACEO 3 years ago: two months from running out of money 2 years ago: our first investment 1 year ago: our biggest R&D push Today: the TACEO network processes 100k+ requests a day All toward one goal: scaling privacy tech until it’s the default, not the exception.

@luhelminger 🎂

Just landed in London for the @lfdecentralized Privacy workshop. Will talk about Private Finance through the lens of MPC and CoSNARKs, and join a panel around cryptography for privacy tech. If you're in town the next days, let's meet! lfdecentralizedtrust.org/privacylondon

Prividiums (@zksync, @tempo) are a great way to add privacy on top of any public chain. But they share one design flaw that blocks widespread adoption.

I got the question: are requests similar to transactions? No, and a little bit yes. Let me explain what the TACEO network is: It's not a blockchain, it has no token. It's a set of distributed node operators that perform computations involving MPC and ZK. What kind of MPC+ZK computations? - OPRF: identity, authentication, and uniqueness on public chains - Merces: payments, yield, tokenization — this is the "little bit yes," closest to a transaction / state update - Match: machine learning inference for biometric data (face, palm, iris) - Proof: collaborative generation of ZK proofs: for example for custody of shielded assets.

@0xPredicate Glad to have you as part of Merces

@TACEO_IO Excited to support TACEO!

"Private" and "compliant" are considered to be a tradeoff. They're not. Today we ship the proof. @0xPredicate is now the enforcement partner in the 𝐌𝐞𝐫𝐜𝐞𝐬 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐄𝐧𝐠𝐢𝐧𝐞. Gate and audit, both now in product. Compliance for private payments is two problems, and they sit on opposite sides of the transaction: - Before a transfer settles (should this happen at all?) - After it settles (what happened, when an auditor asks?) The "after" half has been live since March. Through the Compliance Dashboard, authorised parties can request to audit specific transactions for regulatory purposes. Nothing beyond those transactions is exposed. 𝗪𝗲'𝗿𝗲 𝘀𝗵𝗶𝗽𝗽𝗶𝗻𝗴 𝘁𝗵𝗲 "𝗯𝗲𝗳𝗼𝗿𝗲" 𝗵𝗮𝗹𝗳! Predicate now screens each confidential transfers against the operator's policy before they settle: sanctions, AML, CFT. Compliant transfers proceed. Non-compliant ones are rejected, with a reason returned to the user. The policy stays with the institution. Predicate enforces what the operator defines, on every transfer, and policies update as regulations change without touching the deployment. Clean division of labour: - @0xPredicate handles policy and enforcement. - @TACEO_IO handles private storage and controlled disclosure. Together: 𝐚 𝐟𝐮𝐥𝐥 𝐜𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐬𝐭𝐚𝐜𝐤 𝐰𝐢𝐭𝐡 𝐧𝐨 𝐩𝐥𝐚𝐢𝐧𝐭𝐞𝐱𝐭 𝐝𝐚𝐭𝐚 𝐭𝐫𝐚𝐢𝐥.

Building payments, treasury, or settlement on stablecoins where compliance has been the blocker? Tell us what you're building! We'll get back with integration support & technical resources. Technical detail for builders: docs.taceo.io/docs/finance-s… Read the full announcement: core.taceo.io/articles/merce…

Live to try now in the Merces app: merces.taceo.io

... Just 2 weeks later and the number of requests processed on the TACEO Network crossed 2M !

Tune in tomorrow, Tuesday, June 16th @ 11:00AM ET!

@luhelminger @ethconf x.com/luhelminger/st…

@luhelminger and join @luhelminger tomorrow at the @ethconf main event to talk about the Custody Problem of Privacy.. >> 3:4PM on the Breakout Stage ethconf.com

Big week in NYC 🗽 @luhelminger and Filip will around @ethconf all week!

Permissioned blockchains are on the rise. People trade directly on CEXes. Institutions park assets with qualified custodians. Do we still need 'fancy cryptography privacy'? The answer is obvious when we look at how individuals, businesses and agents will transact onchain. Individuals * Self-custody is only 4-11% of crypto users today (roughly 30-80M people), and the power users are already here. * The next billion comes through neobanks, fintech apps and other types of CASPs. * Their assets are managed on hosted wallets in an omnibus structure; 1 wallet stores assets from multiple customers * Operator privacy is plausibly enough: the omnibus wallet sufficiently obfuscates individual onchain interactions Businesses * Far higher confidentiality bar: Payment flows, treasury positions and counterparty relationships are competitive intelligence. * Custody is the critical layer, with two models: → Qualified custodians (BitGo, Fidelity): omnibus wallets, segregation offchain. Operator privacy mostly covers you. → Self-custody (Fireblocks-style): segregated wallets, 1 wallet = 1 owner. Once a wallet is linked to an entity, the entire onchain history and live holdings are public. *Today, businesses that want self-custody pay for it with total transparency. That's a structural blocker for onchain B2B, and protocol-level privacy is the fix. Agents * Agents behave deterministically: timing patterns, predictable contract interactions, repeated flows. Trivially fingerprintable on a public chain. * Early on agents inherit their principal's operating model (individual/business). * The more autonomous they get, the more self-custody wins. Think one agent controlling multiple wallets directly, transacting with other agents. No omnibus pool absorbs that. * For autonomous agents, protocol-level privacy is a prerequisite. So, do we need 'fancy cryptography privacy'? The next billion individuals coming to crypto probably not. They'll get operator privacy through their CASP and be fine with it. Businesses that self-custody, and agents coming after them, get zero privacy without it. And that's where the actual economic activity will live.

Register here! luma.com/privacy-layer

As stablecoins become core infrastructure for payments, treasury, and financial operations, institutions are facing a new challenge: how to operate onchain without exposing sensitive financial activity in public. @gm_usi will be joining @utila_io's Stablecoin Builder Series to discuss how institutions are approaching confidentiality, selective visibility, and privacy-preserving infrastructure without compromising compliance, governance, or operational control.