Learn · Confidential computing

TEEs explained

A Trusted Execution Environment (TEE) is a hardware-isolated "secure room" inside a CPU. Code and data inside it are shielded — even from the operating system, the hypervisor, and the machine's own operator — and the chip can cryptographically prove what ran.

Two properties that matter

Isolation. The CPU encrypts the enclave's memory. A cloud admin with full root access still can't read what's inside or tamper with it undetected.
Remote attestation. The enclave produces a signed quote (rooted in a hardware key / virtual TPM) that proves which exact code is running on genuine hardware. Anyone can verify that signature chain before trusting the output.

Swipe the figure sideways to read its labels →Figure Schematic, not live data. Compute happens inside the enclave; it emits a signed attestation; a verifier checks the signature chain; the attested result is used on-chain.

Why oracles care

Oracles exist to bring trustworthy off-chain data on-chain. Today you largely trust operators to be honest. A TEE lets an operator prove that a price (or any computation) was produced by audited code, untampered — turning "trust me" into "verify the attestation." It also enables secure cross-chain signing: a key generated inside an enclave can sign only when consensus conditions are met, with no human able to extract it.

The hardware

Two technologies are in production today, both offered as confidential VMs by the major clouds:

AMD SEV-SNP — the older of the two, available on AWS, GCP and Azure.
Intel TDX — newer, with a richer attestation format; rolling out on recent Xeon hardware.

Next: how Flare turns this into a protocol feature. Flare Confidential Computing →

Last reviewed June 2026

Convinced by the data? Delegating takes two minutes. Delegate to Seraphim →