The Yield on Verifiable Inference: How TEEs and AVSs Built a Trust Stack
TEEs handle privacy and speed; on-chain attestations and slashable validators supply the audit trail. Together, they give smart contracts a concrete path to consume AI outputs with explicit trust assumptions.
The architecture of trust hasn’t changed much since the Phoenicians stamped clay seals on amphorae. You need a secure container, a tamper-proof mark, and a ledger of who’s allowed to stamp what. In the age of AI agents that trade autonomously, the container is a Trusted Execution Environment (TEE), the mark is an attestation transcript, and the ledger is an on-chain registry slashing misbehavior.[^claim_207] The emerging stack—TEEs for privacy, Attestation Verification Services (AVSs) for accountability, and protocols like VeriLLM for cheap public validation—is the digital equivalent of a notary who works for gas money, not a percentage.[^claim_214]
OpenGradient’s private LLM inference demonstrates the physicality of this trust. Requests travel via Oblivious HTTP (OHTTP), split through a relay that sees the IP but not the payload, while the enclave sees the prompt but not the sender—a split trust as deliberate as a dead drop.[^claim_207] Inside the enclave, two keypairs are minted: an RSA-2048 signing key and an X25519 HPKE key, both bound to a single AWS Nitro attestation like a passport riveted to a diplomatic pouch.[^claim_208] The signed response—hashed over requestHash, outputHash, and timestamp with RSA-PSS-SHA256—then lands on-chain, where a smart contract can verify the TEE’s registration and the freshness of the timestamp, making the enclave’s output as auditable as a bank vault’s camera footage.[^claim_209]
The relay-enclave split isn’t a bug; it’s the feature that kills a single point of compromise. The relay could collude with the enclave, but the protocol demands non-collusion: the relay knows the IP but not the plaintext, the enclave knows the plaintext but not the IP. It’s a trust model built like a spy exchange, where each party holds half a secret, and the final handshake is verified on a public blockchain.[^claim_210] Even streamed responses are sealed per SSE event, with a final chunk using AAD=‘final’ so that any truncation by the relay is detectable—like a courier who must deliver the sealed package or get shot by the protocol’s slashing conditions.[^claim_211]
EigenLayer scales this architecture into a verification layer for entire agent stacks, calling AVSs the infrastructure for ‘Level 1 Agents’—verifiable tool calling, memory availability, and runtime integrity.[^claim_212] EigenDA becomes a cheap memory store at ‘15 MBps, and increasing,’ enabling agents to dump encrypted state and respawn anywhere, their memory cryptoeconomically secured without leaking content.[^claim_213] This is the equivalent of a mercenary army that remembers its contracts from battle to battle, because forgetting means slashing.
VeriLLM goes after the verifier bottleneck directly, rerunning only the autoregressive decoding phase to slash verification costs to ~1% of inference—a volatility index for truth that makes challenging a false output as cheap as querying an oracle.[^claim_214] Its isomorphic architecture multiplexes inference and verification on the same GPU workers, improving utilization and making task indistinguishability a countermeasure against targeted collusion.[^claim_215] In practice, a DAO could run a large model where any skeptical node can cheaply re-run and challenge results, with slashing settling on-chain like a lien on a defaulted bond.
Nesa’s ongoing work adds VRF-based committee selection and threshold decryption inside TEEs, though the mechanisms are still in beta—financial products, after all, don’t ship with ‘under evaluation’ stamped on the prospectus.[^claim_216] The pattern is the same: TEEs do the heavy lifting, on-chain attestations supply the collateral.
For DeFi and agent developers, the takeaway is that on-chain logic doesn’t need to run the model; it just needs to verify a signature over the output, check the attester’s stake, and optionally challenge with a lightweight protocol like VeriLLM. This stack—privacy via TEEs, auditability via registries, and cheap validation—is what lets autonomous agents sign trades, rebalance portfolios, and report data feeds with provable execution paths. The trust model is no longer a trust me; it’s a short-sellable claim, and the market is already pricing the risk.
Provenance ledger
5 span-verified · 5 web-cited5 claims below are locked to a verbatim span re-verified against the source. The remaining 5 are web citations: the URL was checked, but the excerpt is the researcher's summary and was not re-derived from the page. Citation markers in the text jump here.
[1] OpenGradient’s private LLM inference uses Oblivious HTTP (OHTTP) plus hardware-attested TEEs, with prompts and completions end-to-end encrypted to an attested enclave and the request path split through a relay to anonymize the network path. span-verified
“combines Oblivious HTTP (OHTTP) with hardware-attested Trusted Execution Environments (TEEs)” and “Prompts and completions are end-to-end encrypted to an attested enclave ... the entire request is anonymized.”
7b09082a22624a8da548298d98297959ce083e6067977977804f04242089ec6d [2] OpenGradient’s enclave startup generates two keypairs inside the TEE: an RSA-2048 signing keypair for responses and an X25519 HPKE keypair for OHTTP request encapsulation, and both public keys are bound to a single AWS Nitro attestation transcript. web-cited
“An RSA-2048 signing keypair” and “An X25519 HPKE keypair” are generated inside the TEE, and the attestation user_data “commits to a transcript” containing both keys.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[3] OpenGradient’s response signature scheme hashes requestHash, outputHash, and timestamp with keccak256, then signs with RSA-PSS-SHA256 using salt_len=32; clients verify tee_signature, tee_id, tee_request_hash, and timestamp against the on-chain TEE registry. span-verified
“msg_hash = keccak256( abi.encodePacked(requestHash, outputHash, timestamp) )” and “sig = RSA-PSS-SHA256(..., salt_len=32)” plus the client verification steps for tee_signature, tee_id, tee_request_hash, and timestamp.
165e722ac4416315f343324c56dd49028760ca61d66291e788ba8ae6b5fd2499 [4] OpenGradient’s private inference threat model explicitly requires non-collusion between relay and gateway; the relay sees client IP and sealed bytes, while the enclave sees plaintext prompt and completion but not client IP. web-cited
The trust model table states the relay sees “Client IP” and “OHTTP ciphertext” but not prompt/completion, while the TEE gateway sees request/response but not client IP; the page says the privacy guarantee is “non-collusion between relay and gateway.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[5] OpenGradient’s streaming mode uses Chunked OHTTP so each SSE event is sealed individually, and the final chunk uses AAD="final" so truncation by the relay is detectable by the client. span-verified
“Each SSE event is sealed individually” and “The final chunk uses the AAD 'final' so a truncation by the relay is detectable by the client.”
52bc44f7ed5c677e97277360e4237b3be15466120451ff10cf6396aecb1ae26c [6] EigenLayer positions AVSs as a way to verify off-chain activity or inference, and explicitly frames them as the infrastructure for “Level 1 Agents” with verifiable tool calling, memory availability, and agent runtimes. web-cited
“developers on EigenLayer can use the cryptoeconomic security of Ethereum to build cloud services (AVSs) to verify any off-chain activity or inference” and “AVSs also enable verifiability across the rest of the AI stack.”
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[7] EigenCloud’s post says EigenDA provides a cheap memory store for agents at “15 MBps, and increasing,” intended for encrypted long-term state that can be fetched from anywhere the agent respawns. web-cited
“a data availability service such as the EigenDA AVS offers agents a cheap, fast (15 MBps, and increasing) memory store” and it can be used to dump encrypted memory and fetch it later.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[8] VeriLLM proposes a publicly verifiable decentralized LLM inference protocol that validates results at approximately 1% of underlying inference cost by exploiting the separation between prefill and autoregressive decoding. span-verified
The abstract says VeriLLM uses “lightweight empirical rerunning with minimal on-chain checks” and allows verifiers to validate results at “approximately 1% of the underlying inference cost” by exploiting the structural separation between prefill and autoregressive decoding.
2f469e06b0e5c8d3b2ce464e8707ea06257608d9fd8cf1d56dc39baff6d4c67e [9] VeriLLM multiplexes inference and verification roles across the same GPU workers in an isomorphic inference-verification architecture, with the stated goals of improving GPU utilization, enlarging the validator set, and enforcing task indistinguishability. span-verified
The abstract describes “an isomorphic inference–verification architecture that multiplexes both inference and verification roles across the same GPU workers” and lists improved utilization, larger validator set, and task indistinguishability as benefits.
3cf63d019635c57eb2dd0a26eefd29114a7552203fc99fc7abfbdae52a36e6f7 [10] Nesa’s TEE-based inference design uses encrypted user input, VRF-based committee selection, threshold decryption inside secure enclaves, and then re-encrypts the output for the user; the docs explicitly note the mechanisms are still under evaluation. web-cited
The page opens with “Evaluation in Progress” and describes encrypted inference requests, committee selection using the VRF technique, threshold decryption within TEEs, and result encryption back to the user.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
Sources
- https://docs.opengradient.ai/learn/onchain_inference/private_inference.html
- https://blog.eigencloud.xyz/introducing-verifiable-agents-on-eigenlayer/
- https://arxiv.org/abs/2509.24257
- https://docs.nesa.ai/nesa/major-innovations/private-inference-for-ai/background-and-exploratory-notes/hardware-side-trusted-execution-environments-tees/trusted-execution-environments-tees