wei rong

🇸🇬 RECAP: TEE (Trusted Execution Environment) Wei Rong | Singapore | 20 Aug | Recap 🧵 Thank you @wr1159 for leading the discussion and @stablebunny for hosting us at the @AlliumLabs office! Shout-out to @tomespel and Dom for asking the key questions, and to @dhattarwalmohit from @karnotxyz for helping us understand zkTLS and TEEs and some how they are using it. Great to see @luminoir @cryptoecongames after all this time, @marcuspangeth (@monad, who lead our session on VerkleTrees) and our friends from @nus_blockchain ! Discussion Highlights: 1️⃣ How do TEEs enable private computation? TEEs isolate code and data from the surrounding system, allowing private computation to run at near-native speed. Remote attestation lets others verify which code is running without seeing the private computation itself. 2️⃣ TEEs change the trust model Blockchains normally rely on many nodes repeating and verifying the same computation. With TEEs, that verification is replaced by trust in hardware, attestation services, operators, and integration code. 3️⃣ What can go wrong? Even if an enclave remains secure, the wider system may still fail through compromised keys, side channels, stale state, rollback attacks, enclave cloning, or faulty blockchain integration. 4️⃣ How does zkTLS work? zkTLS can prove that information came from an authenticated HTTPS session—and prove selected facts about it—without revealing all the underlying data. The implementation may involve a browser extension, notary, proxy, MPC, or zero-knowledge proofs. 5️⃣ How do zkTLS and TEEs relate?\ Both help connect private offchain information with publicly verifiable systems, but they rely on different security assumptions. The key question is not only “Can it be verified?” but also “Who or what must be trusted?” Good sessions always raise more questions than answers ;) Full summary: docs.google.com/document/d/1… Thank you @wr1159 for putting this together! Stay Up to date: Website: wprc.club Events: luma.com/whitepaper CV: linkedin.com/company/whitepa…