Sabitlenmiş Tweet
PRIVACY in WEB 3 is infrastructure. Not a FEATURE!
(that's where @inconetwork, @zama_fhe @aztecnetwork @arcium comes in)
According to @DefiLlama, DeFi protocols hold a total of $142 billion in TVL. Only $796 million of that is private, just 0.56%. We are not going to onboard the next billion users to Web3 by leaking their information onchain, to do that privacy has to be default!
Privacy infra is the next stack war. Everyone talks about L2s, rollups, settlement layers and the likes but nobody wants to talk about the fact that the blockchain leaks everything: Identity, behavior, strategy and onchain history. These four projects are fixing that. Here's how:
Start with @inco_network
The goal: Confidential smart contracts using Fully Homomorphic Encryption (FHE).
FHE lets you run computations on encrypted data, no decryption, no exposure, no leaks.
You send data → contract executes in ciphertext → returns result.
With Inco you stay compliant, your data stays hidden and the contract stays auditable. They also built the Confidential ERC-20 Framework with Circle Research.
I wrote about it here: x.com/kamarlimaog/st…
Now look at @zama_fhe
Zama is building the FHE rails for the entire crypto space. You’ll see Zama’s stack behind Medical data sharing, private DeFi, secure AI inference and voting systems. FHE isn’t theory anymore, Zama makes it usable.
(Very detailed Zama guide by @morsyxbt here: x.com/morsyxbt/statu…)
I know you will be thinking, isn't this the same problem @inconetwork solves? The answer is NO! Look at it this way, Zama is the toolbox and Inco is the builder.
Zama focuses on low-level FHE primitives: TFHE, compilers, tooling while Inco uses those to create plug-and-play infra for developers using already existing tools and knowledge.
Now, unto @arcium
Arcium takes a different route, Trusted Execution Environments (TEEs). TEEs create secure enclaves inside CPUs.
You send data in → processor does the work → no one sees what happened. It’s encrypted compute at the hardware level. See it this way:
- ZK(@boundless_xyz ) proves.
- FHE(@inconetwork , @zama_fhe ) computes without decrypting.
- TEEs(@arcium, @tenprotocol ) isolate in a trusted execution environment .
TEEs offer speed and flexibility that ZK and FHE can’t always match. Arcium is building privacy-preserving execution layers using this stack, think of a secure off-chain compute with verifiable outputs.
Finally, @aztecnetwork
Aztec blends ZK and encryption. They’re building a ZK-encrypted L2, private state, private logic, composable apps. It’s not “hide your wallet" but more like "build dApps that don’t expose anything by default", developers chose what they allow the public to see. Aztec's tech is crucial because Ethereum doesn’t scale privacy, everything is public, trades, votes, DMs, DAO activity, token flows etc everything is public.
(Complete Aztec guide by @0xMoei here: x.com/0xMoei/status/…)
These projects aren’t competing, they’re building different layers of the privacy stack.
Inco → Confidential smart contracts using FHE
Zama → Core FHE infra for devs
Arcium → Secure execution via TEEs
Aztec → ZK-encrypted L2 for private DeFi
English
