1/ Everyone's talking about programmable cryptography: FHE, ZKPs, MPC. But what about the environments where this cryptography actually runs?

TEEs vs E3s

Two models for secure computation, each with different trust assumptions, trade-offs, and use cases. 🔽

1/ Everyone's talking about programmable cryptography: FHE, ZKPs, MPC. But what about the environments where this cryptography actually runs?

TEEs vs E3s

Two models for secure computation, each with different trust assumptions, trade-offs, and use cases. 🔽 https://blog.enclave.gg/tees-vs-e3s-execution-environments/

2/ TEEs (Trusted Execution Environments) isolate computation in secure hardware enclaves.

They're widely used, but rely on vendor attestations, centralized supply chains, & specialized hardware.

@secretnetwork @oasisprotocolorg @nearprotocol and fireblocks all make use of TEEs.

The first decentralized smart contract network built on TEE technology, and the decentralized confidential computing hub of Web3.

The privacy? Unmatched. The tech? Secured. The
vibes? Confidential. oasisprotocol.org

A protocol for Encrypted Execution Environments

3/ E3s (Encrypted Execution Environments) take a different path.

They use programmable cryptography like FHE, ZKPs, and MPC to compute on encrypted data without relying on any single trusted party or machine.

Let's compare the two.

4/ In TEEs:

🔸Security comes from hardware isolation
🔸Data is decrypted during execution
🔸Trust is placed in vendors and proprietary attestations
🔸Optimized for low-latency, performance-heavy workloads

Examples: Intel SGX, AMD SEV, Nitro Enclaves, Apple Secure Enclave

5/ In E3s:

🔹Security comes from strong cryptoeconomic guarantees
🔹Data remains encrypted throughout execution
🔹Trust is distributed and enforced through verifiable computation
🔹Deployable on any machine, with modular cryptographic components

5/ In E3s:

🔹Security comes from strong cryptoeconomic guarantees
🔹Data remains encrypted throughout execution
🔹Trust is distributed and enforced through verifiable computation
🔹Deployable on any machine, with modular cryptographic components https://blog.enclave.gg/an-introduction-to-encrypted-execution-environments/

6/ These distinct execution environments aren't in opposition. They reflect different trust architectures.

🔸TEEs echo traditional governance: centralized, vendor-driven.
🔹E3s align with emerging preferences for decentralization, transparency, and modular infrastructure.

7/ Many use cases benefit from a hybrid approach:

🔸TEEs for real-time speed (e.g., trading systems)
🔹E3s for sealed-bid auctions, secret ballots, and secure multiparty analytics

The right approach depends on your stack and threat model.

8/ As computation increasingly underpins governance, economic coordination, and AI, the question is:

What are you willing to trust, and who (or what) gets to verify?

9/ Curious how E3s could fit into your stack? DM us!

Read our breakdown on TEEs vs. E3s:

9/ Curious how E3s could fit into your stack? DM us!

Read our breakdown on TEEs vs. E3s: https://blog.enclave.gg/tees-vs-e3s-execution-environments/