SPICE, 0G, and Origins Forge a Verifiable Trinity for Agentic DeFi
Three projects formalize a stack for AI-agent provenance and execution, with TEEs handling real-time inference and ZKML reserved for settlement.
The infrastructure for verifiable AI inference is crystallizing around a three-layer stack: identity and provenance, verifiable compute, and on-chain settlement. Three projects—SPICE, 0G, and Origins—each contribute a critical piece, and together they define how autonomous agents will prove their execution in DeFi and beyond. It’s like watching the early days of the internet’s TCP/IP stack, but with more cryptographic firepower and less optimism about human nature.
SPICE, an IETF Internet-Draft, formalizes the provenance layer. Its core innovation is the inference_root claim: a Merkle root of an append-only inference registry embedded in an OAuth token [^claim_2025]. This keeps large proof payloads off the token while enabling audit-plane retrieval. The draft supports two proof types: ZKML proofs for mathematical certainty and TEE attestation quotes for hardware-rooted proof [^claim_2026]. Critically, it quantifies the tradeoffs: ZKML is currently limited to ~100M parameters, while TEE attestation scales to 100B+ parameters [^claim_2027]. Proof sizes range from ~200 bytes (Groth16) to ~50KB (STARKs) for ZK, and ~2KB (Intel TDX) to ~4KB (NVIDIA) for TEE [^claim_2027]. Think of it as the difference between a Swiss watch and a tank—both reliable, but one is for precision, the other for brute force.
The threat model is concrete: model substitution, weight tampering, environment spoofing, and replay of stale proofs [^claim_2028]. SPICE mitigates these by binding proofs to model_fingerprint, input_hash, output_hash, and iat timestamp [^claim_2028]. For real-time applications like chat or interactive agents, the draft recommends TEE attestation quotes exclusively; ZKML is reserved for batch/offline or high-stakes cases [^claim_2030]. This maps directly to DeFi agent risk controls: a trading agent must prove model identity and fresh execution before touching wallets. It’s like a bouncer checking ID and breathalyzer before letting you into the club.
0G provides the execution layer. Its Aristotle Mainnet, live since September 2025, offers verified compute, persistent memory, and onchain settlement [^claim_2031]. Every inference call runs inside a TEE and is cryptographically verified [^claim_2031]. The project claims its DA layer is 50,000x faster and 100x cheaper than Ethereum’s [^claim_2032]—a claim that, if true, changes the economics for agent logs and proof posting. It’s the kind of performance that makes traditional blockchains look like dial-up modems in a fiber-optic world.
Origins Network adds a modular settlement layer. It raised $8 million to build a chain where heavy AI inference runs off-chain on GPU infrastructure from AWS, Tencent Cloud, and Alibaba Cloud, while succinct proofs are verified on-chain [^claim_2033][^claim_2034]. This is a hybrid Web2/Web3 compute market: cloud GPUs execute, blockchain governs verification and settlement. It’s the financial equivalent of short-selling the cloud oligopoly while going long on cryptographic trust.
Finally, the DeFi-ML paper provides the threat data. Its curated dataset includes 298 distinct exploits, 402 exploit transactions, and $3,735,630,450.52 in total losses [^claim_2035]. Classifiers like CNN(F4, K4) achieve 0.9004 accuracy and 0.8200 F1 on unseen exploits [^claim_2036]. These benchmarks show that transaction-level classifiers can be both accurate and gas-feasible, enabling on-chain threat scoring. The numbers are cold, but the losses are real—like reading a balance sheet after a market crash.
The synthesis is clear: TEE-first for latency, ZKML for high-assurance settlement, and a compact provenance token to tie it all together. For DeFi, this means agents can prove their reasoning without revealing it, and protocols can audit execution without re-running it. It’s a stack built for speed, trust, and the cold logic of capital markets.
Provenance ledger
12 claims web-citedEvery 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] The SPICE Internet-Draft defines an **inference_root** claim that stores the Merkle root of an append-only inference registry, and it uses that root to keep large proof payloads out of the token while still enabling audit-plane retrieval. Crypto implication: this is directly relevant to **agent identity / provenance layers** for DeFi agents because the token can carry a compact commitment while the full proof log lives off-chain or in a transparency log. web-cited
"Only the Merkle root is included in the OAuth token"; "The resulting root hash is included in the OAuth token as the inference_root claim."
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[2] The SPICE draft says the inference-chain design supports two proof types: **ZKML proofs** and **TEE attestation quotes**. It states that ZKML provides mathematical certainty, while TEE quotes provide hardware-rooted proof, and it explicitly frames them as complementary proof systems. Crypto implication: this maps to a **verifiable compute primitive** for on-chain inference providers that need either privacy-preserving proofs or production-scale latency. web-cited
"The inference chain supports two primary proof types"; "ZKML proofs provide mathematical certainty"; "TEE attestation quotes provide hardware-rooted proof"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[3] The SPICE draft gives concrete trust/scale tradeoffs: **ZKML is currently limited to ~100M parameters**, while **TEE attestation is described as production-scale for 100B+ parameters**. It also lists proof-size guidance of **~200 bytes (Groth16)**, **~50KB (STARKs)**, **~2KB (Intel TDX)**, and **~4KB (NVIDIA)**. Crypto implication: protocol designers for **on-chain inference marketplaces** can use TEE for real-time agent execution and ZKML for high-assurance settlement or post-trade audit. web-cited
Table 3: "Currently limited (~100M parameters)" vs "Production-scale LLMs (100B+ parameters)"; proof sizes listed as "~200 bytes", "~50KB", "~2KB", "~4KB"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[4] The SPICE draft’s threat model explicitly names **model substitution**, **weight tampering**, **environment spoofing**, and **replay of stale proofs** as concrete attacks against AI-agent inference provenance. It proposes binding proofs to `model_fingerprint`, `input_hash`, `output_hash`, and `iat` to mitigate these attacks. Crypto implication: this is a direct fit for **DeFi agent risk controls** where a trading or underwriting agent must prove both model identity and fresh execution before acting. web-cited
"Concrete threats: Model Substitution... Weight Tampering... Environment Spoofing... Replay of Stale Proofs"; mitigation fields include "model_fingerprint", "input_hash", "output_hash", and "iat timestamp"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[5] The SPICE draft specifies a **TEE verification flow** that requires validating the platform certificate chain against the manufacturer root CA, checking revocation, verifying the quote signature, and ensuring `report_data` binds the quote to specific input/output hashes. Crypto implication: this is the sort of attestation pipeline a **confidential-agent execution layer** would need before allowing an agent to touch wallets, approve swaps, or sign transactions. web-cited
"Validate the platform certificate chain against the manufacturer's root CA"; "Verify report_data binds the quote to the specific input/output hashes"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[6] The SPICE draft says deployments SHOULD use **TEE attestation quotes exclusively** for real-time applications such as chat, interactive agents, and API serving, while **ZKML proofs** are recommended for batch/offline applications and high-stakes cases. Crypto implication: this gives a concrete architecture for **agentic DeFi front-ends** where low-latency inference runs under TEE and final settlement can be audited with zk proofs later. web-cited
"Real-time applications (chat, interactive agents, API serving): Use TEE attestation quotes exclusively"; "Batch/offline applications ... ZKML proofs provide mathematical certainty"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[7] 0G says its Aristotle Mainnet has been live since **September 2025** and provides three core capabilities for autonomous agents: **verified compute**, **persistent memory**, and **onchain settlement**. The announcement further states that every inference call in its Sealed Inference system is executed inside a **TEE** and cryptographically verified. Crypto implication: this is a direct **agent execution + settlement stack** for AI-native DeFi bots that need compute, state, and payments in one protocol. web-cited
"Aristotle Mainnet, live since September 2025, provides ... verified compute, persistent memory, and onchain settlement"; "Every AI inference call is executed inside a hardware enclave (TEE) and cryptographically verified."
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[8] 0G’s announcement claims **Data Availability is 50,000x faster and 100x cheaper than Ethereum’s DA layer**. Crypto implication: if true, that changes the economics for **agent logs, proof posting, and state updates** in AI-heavy rollups and agent networks that need frequent attestations or memory writes. web-cited
"0G’s DA layer is 50,000x faster and 100x cheaper than Ethereum’s DA layer"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[9] Origins Network says it raised **$8 million** to build a modular blockchain for AI agents and that its **Proof of Computation** design keeps heavy inference off-chain on GPU infrastructure while verifying succinct proofs on-chain. Crypto implication: this is a concrete **verifiable-compute / settlement** pattern for agentic workloads, especially for DeFi automation where the chain only needs to verify execution, not re-run it. web-cited
"raised $8 million"; "heavy AI inference runs offchain on GPU-rich infrastructure, while succinct proofs of that work are verified and settled onchain"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[10] The Origins article says the network’s off-chain execution layer can tap infrastructure from **AWS, Tencent Cloud, and Alibaba Cloud**, then post cryptographic evidence back to its chain. Crypto implication: this is a **hybrid Web2/Web3 compute market** design where cloud GPUs do execution but blockchain consensus still governs verification and settlement. web-cited
"can tap infrastructure from partners like AWS, Tencent Cloud, and Alibaba Cloud"; "post cryptographic evidence of the computation back to Origins’ chain"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[11] The on-chain DeFi-ML paper reports **298 distinct exploits**, **402 exploit transactions**, and **$3,735,630,450.52** in total losses in its curated dataset. Crypto implication: it supports using **on-chain transaction classifiers** as a DeFi firewall because the training set is built from real exploit behavior across multiple EVM chains. web-cited
"298 unique attack vectors"; "402 exploit transactions"; "Total exploits loss ... $3,735,630,450.52"
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[12] That same paper reports that **CNN(F4, K4)** achieved **0.9004 accuracy** and **0.8200 F1**, while **SVM** reached **0.8814 accuracy** and **0.8000 F1** on unseen DeFi exploits. Crypto implication: these are practical benchmarks for **transaction-level threat scoring** in a state-modifying DeFi contract or pre-execution router. web-cited
Table 12: "CNN(F4, K4) 0.9004 ... 0.8200"; "SVM 0.8814 ... 0.8000"
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://datatracker.ietf.org/doc/draft-mw-spice-inference-chain/
- https://www.globenewswire.com/fr/news-release/2026/03/21/3260008/0/en/0G-Positions-as-the-Blockchain-for-AI-Agents-as-Industry-Moves-Toward-1-Trillion-Agentic-AI-Economy.html
- https://crypto.news/origins-network-raises-8m-to-build-modular-ai-chain-with-verifiable-compute/
- https://arxiv.org/html/2510.16024v1