Skip to the article
Crypto Daybook

Markets, chains and policy news

Threshold Encryption and TEE Mempool Privacy

Threshold encryption vs TEE for encrypted mempools: keyholders decrypt after ordering, while trusted hardware decrypts early enough for simulation and filtering.

Crypto Daybook Newsroom3 min read

Threshold Encryption and TEE Mempool Privacy

Threshold encryption and a TEE hide pending transactions in different ways: keyholders decrypt after ordering, while trusted hardware decrypts inside an enclave so a builder can simulate first. The choice depends on when plaintext is exposed and which trust assumption fits the design.

Which trust model fits your mempool?

Trust assumption: Threshold encryption relies on fewer than the required threshold of keyholders colluding. A TEE, or trusted execution environment, relies on hardware keeping data inside a protected enclave. The first distributes trust across keyholders; the second places it in hardware and its vendor.

When plaintext appears: Threshold-encrypted transactions are ordered before keyholders release the decryption key. Shutter Network uses a keyper committee: keypers release keys once a threshold agrees. A TEE decrypts transactions inside the enclave before ordering, so the builder can inspect them while building a block.

Pre-ordering simulation: Threshold encryption cannot simulate transactions before ordering because their contents are still hidden. That means failing or spam transactions may take block space. A TEE can simulate in plaintext and drop invalid transactions, helping it build more efficient blocks. BuilderNet runs block builders inside Intel TDX trusted execution environments.

For someone choosing where to send a transaction, flashbots protect makes the submission route part of the decision alongside the mempool’s trust model. Flashbots is an MEV research and infrastructure organization, so its relevance here is how private transaction submission fits into the path to a builder.

Failure mode: Threshold encryption can fail if enough keypers collude and reveal keys early. A TEE can fail through hardware side-channels or vendor compromise. The risk is different: committee behavior in one design, hardware security in the other.

Liveness: Threshold decryption can stall when too few keypers respond to release a key. A TEE-based builder depends on one operator’s uptime. The first needs enough committee members available; the second needs its operator and enclave to stay online.

Choose threshold encryption when hardware trust is unacceptable and the design can tolerate waiting for committee key release. Choose a TEE when block efficiency and filtering invalid transactions matter, and the hardware trust assumption fits. Flashbots’ BuilderNet example shows where TDX enters the second design.

Related

What is Shutter Network?

Shutter Network uses threshold encryption for transaction privacy. Its keyper committee releases decryption keys once enough keypers agree, so ordering happens before plaintext is available.

Can Intel SGX enclaves be broken?

Intel SGX has the TEE trust model: it depends on hardware security. Side-channels or vendor compromise are failure modes to consider when deciding whether that trust is acceptable.