Intel SGX vs TDX for Block Building: Enclave or VM?

Intel SGX isolates a builder application inside an enclave, while Intel TDX isolates the full virtual machine running it, trading SGX’s narrower trust boundary and porting work for TDX’s larger trusted software base and simpler deployment.

What changes when you build inside SGX or TDX?

A builder takes transactions and bids as input, orders them into a candidate block, then returns the block and its bid to the proposer. A trusted execution environment (TEE) is meant to keep sensitive inputs and builder code private while they are in use. For more on how a blockchain TEE protects execution, see the related explanation; Flashbots uses TEEs as part of its work on private block building.

With SGX, the protected unit is an application enclave. The operating system and the rest of the machine remain outside it, so the builder must fit the enclave programming model. Gramine can help run Linux applications in SGX, but the team still has to configure and validate that path. Enclave memory limits and the work of moving a large client make this a poor fit for running a standard Ethereum client unchanged.

With TDX, the protected unit is a Trust Domain: a virtual machine whose private memory and CPU state are isolated from the host hypervisor. The builder can run with a stock guest OS and Ethereum client, which makes it easier to use normal software and allocate the memory a builder needs. Intel’s TDX Module Base Architecture Specification, Section 2, describes this VM-level isolation mechanism.

That convenience changes what you must trust and verify. In SGX, attention centers on the enclave and its interface with the untrusted host. In TDX, the guest OS, kernel, boot chain, and builder software all run inside the protected VM and become part of the workload’s trusted base. Remote attestation gives a verifier evidence about the platform and measured launch state; your deployment must define how it checks the kernel and userland image as well as the builder. TDX therefore trades enclave porting work for a wider software surface to audit.

Take a builder receiving private order flow. In an SGX design, you would package the builder for an enclave, then check that the enclave is running the expected code. In a TDX design, the client and builder run normally inside a confidential VM; you check the VM’s attestation and the measurements or image records that identify its software. The visible outcome is a private builder that can use standard client software, with the whole guest environment in scope for review.

SGX also has a record of attacks against enclave confidentiality, including Foreshadow, so an enclave is not a guarantee against every hardware attack or side channel. TDX changes the isolation boundary; it does not remove the need to assess side channels and the workload’s interfaces. Confusing an enclave with a whole VM can lead you to verify only the builder binary when the operating system around it matters too.

Flashbots’ earlier builder experiments used SGX; BuilderNet runs its builder on TDX, as described in the BuilderNet documentation. That choice suits a builder that needs standard client software and substantial memory, while placing more of the guest system inside the trust base.

Related questions

Can a cloud provider read memory inside a TDX VM?

TDX is designed to prevent the host hypervisor from reading a Trust Domain’s private memory. Data a VM deliberately shares with the host or sends through external interfaces is outside that private-memory boundary, and TDX does not make side-channel review irrelevant.

Why did Intel drop SGX from consumer CPUs?

Intel phased SGX out on client processor platforms beginning with 11th-generation Core processors, while SGX support remained available in some Xeon families. Intel’s public processor documentation describes where SGX is supported; it does not give one definitive reason for the client-platform change, so it should not be read as proof that SGX stopped working everywhere.

  • SGX isolates an application enclave; TDX isolates a full VM.
  • SGX requires enclave porting; TDX can run a standard client.
  • TDX widens the software base you need to attest and audit.

Comments

Popular posts from this blog

How to See How Large Sells Change a Token Chart

BNB Swap Verification: Confirm a Token Trade on BSC

How to Estimate Contract Energy Before a TRON Call