infrastructure spotlight

TEEs Beat ZK for Live AI Agents as Verifiable Compute Goes Production

A four-step attested inference flow, backed by Nvidia Hopper and Intel TDX, is now production-ready across Marlin, Phala, Atoma, and Automata, while ZKML remains 10,000–100,000× slower. Chainlink's CRE and VeriLLM show how TEEs and blockchains compose for agentic DeFi.

3 min read 10 claims web-cited

In the year of our algorithm, the architecture of trust has shifted from cryptographic zero-knowledge proofs to the cold, hard silicon of hardware enclaves. TEE-based attested inference has become the production workhorse for AI agents that need to prove their behavior to smart contracts without re-running models. The flow is standardized: enclave provisioning, model and prompt loading over an attested channel, in-enclave inference and output signing, and verification of the attestation chain [^claim_1171]. This lets smart contracts or users trust the output without trusting the operator—a kind of digital escrow for machine reasoning.

Nvidia Hopper (H100) Confidential Computing, combined with Intel TDX or AMD SEV-SNP, now enables GPU-based confidential AI inference by encrypting PCIe link data and running kernels inside a hardware-isolated context [^claim_1176]. This matters because larger models require GPU support. The hardware stack determines the model size that can run inside the trust boundary—a constraint as old as the mainframe.

Projects like Marlin Oyster, Phala Network, Atoma Network, Automata, and Tinfoil have moved this pattern from concept to production over 2023–2025, offering confidential compute marketplaces, SGX-based agent meshes, confidential GPU inference settled in stablecoins, and EVM DCAP attestation contracts [^claim_1177]. These are not experiments—they ship. The market has spoken, and it prefers the latency of a hardware vault over the computational tax of a proof.

ZK proofs for LLM inference remain roughly 10,000–100,000× slower than native inference as of 2026 [^claim_1172]. RISC Zero and Succinct have published proving benchmarks confirming this gap. For live agent workloads where prompt and latency matter, TEEs are the practical choice. ZK is more appropriate for final settlement state than for live inference—like using a vault for a single transaction rather than for daily operations.

That said, ZKML has its place. It can prove that a specific model, given a specific input, produced a specific output without revealing model weights or the input itself [^claim_1180]. EZKL, Giza, and Ritual are the serious players in 2026, targeting credit scoring, prediction markets, and content authenticity where the proof’s financial or regulatory value exceeds its cost. The yield on compliance just went ex-dividend.

At the protocol layer, Chainlink’s verifiable AI stack uses offchain AI computation combined with either zkML or TEEs to produce cryptographically verifiable outputs, which are delivered onchain and checked by smart contracts before any state changes occur [^claim_1173]. Chainlink’s Runtime Environment (CRE) coordinates decentralized AI workflows where offchain models analyze data like market sentiment and multiple Chainlink node operators verify outputs, achieving nearly 100% data consensus agreement among AI models in a corporate actions processing demo with 24 major financial institutions and market infrastructures [^claim_1178]. The infrastructure is as cold as a Swiss bank vault.

VeriLLM goes further: it is a publicly verifiable, decentralized LLM inference framework built on a blockchain substrate, using a scheduler, homogeneous node groups, and on-chain verification contracts with collateral staking to achieve publicly auditable correctness, low verification overhead compatible with real-time inference, and incentive-enforced rewards and penalties [^claim_1175]. It’s a machine for producing trust, with the efficiency of a hedge fund.

On the agent framework side, the Model Context Protocol (MCP), launched by Anthropic in November 2024 and adopted by OpenAI, Microsoft, Google, and Amazon within 18 months, has become the de facto standard for connecting agents to tools, with over 6,400 MCP servers in the official registry and most modern agent frameworks supporting MCP natively [^claim_1174]. This consolidating standard makes it easier to swap in verifiable-compute backends underneath high-level agent SDKs while preserving interoperability across providers. The protocol is the new railroad gauge.

TEE-attested AI agents can bind decisions directly to on-chain actions via patterns such as agent-as-transaction-signer, agent-as-oracle, agent-as-intent-solver, and agent-as-compliance-gate [^claim_1179]. In each pattern, enclave-held keys sign transactions or oracle outputs, and smart contracts verify attestation measurements and model hashes before execution. The result: autonomous AI systems can act as first-class economic actors in DeFi, MEV markets, and cross-chain settlement while preserving trust-minimization and compliance-grade auditability. The market is bleeding red, but the architecture is solid.

Provenance ledger

10 claims web-cited

Every claim below cites a source URL, and each URL was checked for validity before publish. The excerpt shown is the researcher's own summary of the page — it is not re-derived from the source, so it is not a verified verbatim quote. Follow the link to confirm any claim against the original. Citation markers in the text jump here.

[1] TEE-based attested inference for AI agents uses a four-step flow—enclave provisioning, model and prompt loading over an attested channel, in-enclave inference and output signing, and verification of the attestation chain—to produce verifiable compute that smart contracts or users can trust without trusting the operator. web-cited
Excerpt reported by researcher (not re-verified)
“TEEs for AI agents combine a hardware-isolated execution environment with remote attestation… The mechanics of attested inference follow a four-step pattern… Step 1: Enclave provisioning… Step 2: Model and prompt loading… Step 3: Inference and signing… Step 4: Verification… Verifiable compute is computation whose result can be checked by an outside party without re-running the computation. For AI, this typically means proving that a specific model ran on a specific input, producing a specific o

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[2] ZK proofs for LLM inference remain roughly 10,000–100,000× slower than native inference as of 2026, making TEE-attested inference the practical choice for live agent workloads that require low latency while still providing verifiable compute. web-cited
Excerpt reported by researcher (not re-verified)
“ZK-proving an LLM is technically possible but currently runs 10,000–100,000× slower than native inference; RISC Zero and Succinct have published proving benchmarks confirming this gap… For workloads where the prompt and the latency matter, TEEs are the practical choice. ZK is more appropriate for… final settlement state, than for live inference.”

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[3] Chainlink’s verifiable AI stack uses offchain AI computation combined with either zero-knowledge machine learning proofs or trusted execution environments to produce cryptographically verifiable outputs, which are then delivered onchain and checked by smart contracts before any state changes occur. web-cited
Excerpt reported by researcher (not re-verified)
“The verifiable AI stack… allows smart contracts to securely consume AI outputs while guaranteeing the integrity of offchain model execution… Models execute offchain… Cryptographic verification… often uses zero-knowledge machine learning (zkML) or trusted execution environments (TEEs) to generate a proof of correct execution… The verified output and its accompanying cryptographic proof are submitted to a smart contract. The contract verifies the proof before executing any state changes.”

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[4] The Model Context Protocol (MCP), launched by Anthropic in November 2024 and adopted by OpenAI, Microsoft, Google, and Amazon within 18 months, has become the de facto standard for connecting agents to tools, with over 6,400 MCP servers in the official registry and most modern agent frameworks supporting MCP natively. web-cited
Excerpt reported by researcher (not re-verified)
“As of early 2026, MCP (Model Context Protocol) has become the de facto standard for connecting agents to tools. Anthropic launched it in November 2024, and within 18 months, OpenAI, Microsoft, Google, and Amazon all adopted it… There are now 6,400+ MCP servers in the official registry… Most modern frameworks support it natively. If a framework doesn’t support MCP yet, that’s a yellow flag.”

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[5] VeriLLM is a publicly verifiable, decentralized LLM inference framework built on a blockchain substrate, using a scheduler, homogeneous node groups, and on-chain verification contracts with collateral staking to achieve publicly auditable correctness, low verification overhead compatible with real-time inference, and incentive-enforced rewards and penalties. web-cited
Excerpt reported by researcher (not re-verified)
“We introduce VeriLLM, a publicly verifiable protocol for decentralized LLM inference that achieves security with incentive guarantees while maintaining practical efficiency… VeriLLM is… built atop a blockchain substrate. The system targets three objectives: publicly auditable correctness, low verification overhead compatible with real-time inference, and transparent incentive enforcement via smart contracts… VeriLLM consists of three core components: a scheduler, a set of homogeneous node group

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[6] Nvidia Hopper (H100) Confidential Computing, combined with Intel TDX or AMD SEV-SNP, enables GPU-based confidential AI inference by encrypting PCIe link data and running kernels inside a hardware-isolated context, allowing large LLMs to run inside an attested boundary suitable for TEE-based verifiable AI agents. web-cited
Excerpt reported by researcher (not re-verified)
“Nvidia’s Hopper architecture includes Confidential Compute mode, which encrypts data on the PCIe link between CPU and GPU and runs the GPU’s compute kernels inside a hardware-isolated context. Combined with Intel TDX or AMD SEV-SNP on the host, this lets a model run inside a confidential VM with the GPU compute also attested… The hardware stack matters because it determines the model size that can run inside the trust boundary… Larger models require GPU support.”

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[7] Projects like Marlin Oyster, Phala Network, Atoma Network, Automata, and Tinfoil have moved TEE-based attested AI inference from concept to production, offering confidential compute marketplaces, SGX-based agent meshes, confidential GPU inference settled in stablecoins, EVM DCAP attestation contracts, and enclave-backed LLM APIs that produce onchain-verifiable outputs. web-cited
Excerpt reported by researcher (not re-verified)
“This pattern has moved from concept to production over 2023–2025. Marlin's Oyster, Phala Network's worker mesh, Atoma Network, Automata's verifiable AI service, and Flashbots' work on attested inference all ship in some form… Marlin's Oyster is a marketplace for confidential compute… Phala has positioned its SGX-based worker mesh as a host for AI agents… Atoma… focused exclusively on confidential AI inference… Automata's DCAP attestation contracts let any EVM smart contract verify Intel SGX/TDX

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[8] Chainlink’s Runtime Environment (CRE) coordinates decentralized AI workflows where offchain models analyze data like market sentiment and multiple Chainlink node operators verify outputs, achieving nearly 100% data consensus agreement among AI models in a corporate actions processing demo with 24 major financial institutions and market infrastructures. web-cited
Excerpt reported by researcher (not re-verified)
“The Chainlink Runtime Environment (CRE) enables developers to build custom workflows that coordinate offchain AI computation, fetch necessary data, and verify the results before delivering them onchain… If an AI model analyzes market sentiment to trigger a trading strategy, Chainlink infrastructure ensures the model's output is verified by multiple independent operators… This was demonstrated by Chainlink and 24 of the world’s largest financial institutions and market infrastructures… with thei

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[9] TEE-attested AI agents can bind decisions directly to on-chain actions via patterns such as agent-as-transaction-signer, agent-as-oracle, agent-as-intent-solver, and agent-as-compliance-gate, where enclave-held keys sign transactions or oracle outputs and smart contracts verify attestation measurements and model hashes before execution. web-cited
Excerpt reported by researcher (not re-verified)
“Agent as transaction signer… The enclave holds a private key that signs Ethereum transactions. The smart contract verifies the signing key was generated inside an enclave with a known measurement… Agent as oracle… The contract verifies the attestation before accepting the value… Agent as intent solver… computes the optimal execution plan, and signs the resulting transaction batch… Agent as compliance gate… The compliance attestation accompanies the transaction onchain… Each pattern depends on t

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text
[10] Zero-knowledge machine learning (ZKML) can prove that a specific model, given a specific input, produced a specific output without revealing either the model weights or, optionally, the input, enabling privacy-preserving verifiable AI for applications like credit scoring, prediction markets, and content authenticity where proof value exceeds computation cost. web-cited
Excerpt reported by researcher (not re-verified)
“Zero-knowledge machine learning (ZKML) lets you prove that a specific model, given a specific input, produced a specific output — without revealing the model weights or, optionally, the input itself… useful for credit scoring, prediction markets, and content authenticity where the proof’s financial/regulatory value exceeds its cost… EZKL, Giza, and Ritual are the serious players in 2026.”

This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.

↩ back to text

Sources

  1. https://eco.com/support/en/articles/14796365-tees-for-ai-agents-verifiable-compute
  2. https://chain.link/article/verifiable-ai-stack
  3. https://sidsaladi.substack.com/p/agent-frameworks-101-the-complete
  4. https://arxiv.org/html/2509.24257v4
  5. https://www.agilesoftlabs.com/blog/2026/05/ai-blockchain-in-2026-5-onchain
teeattested-inferenceverifiable-computezkmlchainlinkverillmmcpai-agentsdeficonfidential-computing
AUTOMATED

Get the synthesis

AI×crypto research, repackaged with every claim hash-locked to its source. New arXiv → analysis in ~3 hours.