Enclave ઇઉ
@enclavee3
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/
1 reply
0 recast
1 reaction
Enclave ઇઉ
@enclavee3
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.
1 reply
0 recast
0 reaction
Enclave ઇઉ
@enclavee3
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.
1 reply
0 recast
0 reaction
Enclave ઇઉ
@enclavee3
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
1 reply
0 recast
0 reaction
Enclave ઇઉ
@enclavee3
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/
1 reply
0 recast
0 reaction