Hope to see you around and listen to my talk: From Logical to Physical Trust: Extending the Foundations of Secure Execution Agents is one use case out of many that TEEs can support.

Co-founder of SpaceComputer @rezabfil will be grabbing the mic next, with a keynote on exploring the gap between theoretical trust models and the messy physical world where agents actually operate.

Research Day 🧑‍🏫 Nov 20th at Devconnect Privacy Community Hub Tune into @frezabek's research talk discussing recent TEE failures through the lens of “Proof of Cloud,” exploring data-center execution assurance for confidential VMs. 10AM to 11AM https://t.co/NKOzSS1bH3

We are co-sponsoring the Afternoon TEE Party! 🍵 Nov 19th at MUGSO Tune into @rezabfil's keynote "From Logical to Physical Trust: Extending the Foundations of Secure Execution" 4:45 PM to 5PM https://t.co/VXsFITMNDw

Practical Privacy Day 🔒 Nov 18th at Devconnect Privacy Community Hub Our Co-Founders @semicondurian & @rezabfil will lead an off-the-record after hour Q&A on TEEs with the Flashbots team. 4:45PM to 5:30PM https://t.co/tM495UXzEB

🧑‍🚀 Monday, 17 November Frontier Forum ~18:35 @shresth3103 @DistributedMarz @OrestTa and @rezabfil have an out-of-this world chat about the next 100x improvement in blockchain performance and throughput. We hear that a real-life moon man will be there. https://t.co/Jx4bYtHClh

A fantastic media partner @DefiantNews and amazing views on the Planetario for Frontier Forum✨🛰️ Imagine what the visuals are like inside👀

We don’t let just anyone on the stage at Frontier Forum. It’s high time we dive deeper into the brilliant minds setting the course for the frontier at DevConnect. Each speaker brings a unique set of expertise, offering new perspectives and moonshot ideas through various

@blocksec @Offchain @allred_chase @arbitrum @prabalbanerjee @AvailProject @matan_si @EO_Network @0xbowio @ameensol @auryn_macmillan @EnclaveE3 @jbaylina @ziskvm @Socrates @flashbots_x @Nethermind @mpfzajac @poddotnetwork @shresth3103 @kokebsolomon @gnosisdotio @hoprnet @SCBuergel @StoffelMPC @badcryptobitch @hashcloak @t1protocol @OrestTa @FireblocksHQ @arik_g Welcome Michał Zając as a speaker for Frontier Forum. CSO at @Nethermind, @mpfzajac works on formal verification of zkVMs and Ethereum-scale rollups, researching the primitives that make privacy scale in production. At Frontier Forum, Michał will speak on applied cryptography

7 Days until Frontier Forum in Buenos Aires. The launch date is approaching, and we have quite the lineup for you: 25+ Brilliant speakers 5 Keynotes from industry leaders 5 Debates on frontier topics 5 Lightning talks on moonshot ideas 1 Immersive planetarium experience And

We've given TEE Wiki a quick refresh with better flow including for contributors @PhalaNetwork @SecretNetwork @OasisProtocol @t1protocol and more A great starting point to understand TEEs as they become central to intelligent agents and verifiable AI → https://t.co/bq3JmHrgap

The final form of TEE haters: unpaid marketing department.

PSA: this is an application of the attack published a few weeks ago to newer chips It still doesn't apply to BuilderNet (or any Flashbots products) because of the physical access requirement but it *does* highlight some of the R&D we're doing [post below]

TLDR - TEEs broken again in a lab. - Doesn't affect BuilderNet or other Flashbots products, as we don't allow operators to run outside of vetted cloud environments. No user funds or data ever at risk. - Attack is nontheless very relevant for moving beyond the cloud model, our

To find out more, our papers: • https://t.co/Bflq3jxd4b • https://t.co/1ojjYScf2l

Notably, TEEs are not perfect, but they offer significant benefits when implemented properly. Issues like this move us forward and inspire new solutions - something we work on with @SpaceComputerIO, along with many other great initiatives, such as Trustless TEE.

DCEA bridges the missing link in TEE trust. We finally get an assurance where a secure enclave runs, not just what runs inside it. This enables high assurance for TEE applications.

Contributions: ✅ Formal threat model for “physical adversaries” in TEEs ✅ Design of DCEA architecture ✅ Feasibility evaluations

Threat model: Trust the CPU vendor’s root keys and the provider’s integrity (not confidentiality). Attackers may have full host access, but can’t forge DCEA proofs without breaking hardware measurements.

Bare-metal case: Use Intel TXT to extend trust from firmware → hypervisor → enclave, sealing the TPM to that chain. You get one continuous attestation from silicon to the guest.