Agent Settlement Has a Notary, a Gate, and a Slash Window
Generic agent SDKs still ship uneven bindings, but the durable infrastructure is forming around TEE notaries, proof-gated state changes, and consensus-embedded inference.
By the standards of infrastructural history, this is the moment after the robber barons laid the tracks: the agent layer is still a rolling frontier. Microsoft ships Agent Framework as a production SDK across .NET, Python, and Go, but the Go binding remains in public preview, missing declarative agents, RAG, CodeAct, and functional workflows.[^claim_1239][^claim_1240] That gap is not the real story. The real race is underneath the framework: who can prove an agent executed correctly, under what governance, and who can settle that proof onchain. The market is pricing honesty; the yield on compliance just went ex-dividend.
OPAQUE 3.0 makes the first move by packaging agent identity and execution governance together. Agent Manifest is an open standard for verifiable AI agents, and Confidential MCP is described as the first Model Context Protocol implementation verifiably governed and secured through confidential computing.[^claim_1241] The runtime runs on CPU-based confidential computing platforms from Intel, AMD, and NVIDIA; on NVIDIA Confidential Computing the integration brings GPUs inside the Trusted Execution Environment.[^claim_1242] Translation: the exact context an agent sees through MCP—tool calls, data fetches, model inputs—is attested, not assumed. The interface was cold; the attestation arrived before the argument.
EQTY Lab pushes the same idea to compute sessions. Its Verifiable Compute uses a notary inside a TEE on both CPU and GPU, letting anyone verify that an AI compute session is confidential and meets governance controls before computation starts and continuously at runtime.[^claim_1243] The system then produces persistent proofs of compliance in AI certificates that can be verified instantly or decades later without rerunning complex AI workloads.[^claim_1244] Audit goes from a costly reproduction exercise to a signature check. As a CFO would say: you stopped paying for re-enactment and started paying for attestation.
Chainlink turns those proofs into transaction gates. Its verifiable AI stack routes AI computation offchain, uses zkML or TEEs to generate a proof of correct execution, and the smart contract refuses to change state until it verifies that proof.[^claim_1245] The Chainlink Runtime Environment coordinates the offchain compute, the data fetching, and the verification before delivering results onchain.[^claim_1246] This is the clearest protocol-level pattern: AI is a sidecar, proof is the admission ticket. The arrangement reads like an options clearinghouse: no proof, no settlement.
0G supplies the resource and identity layer. Its docs describe a decentralized GPU marketplace for AI inference and training, plus ERC-7857, Agentic ID, for on-chain AI identities.[^claim_1247] Marketplace and identity turn agents into allocatable, attributable services rather than opaque model endpoints. They become line items, not mysteries.
Keryx goes furthest: it makes inference itself a consensus activity. Its whitepaper embeds AI inference into PoW via Optimistic Proof of Inference, accepts results immediately, and allows challenge within a time-bounded window, with 20% escrow slashing for fraud.[^claim_1248] A later hardfork, Proof-of-Model, replaces the matrix-multiply PoW core with a data-dependent walk over resident model weights, so possession of the entire tier’s weights in VRAM is the only competitive configuration.[^claim_1249] In its request flow, the full inference output is stored offchain on IPFS while only a compact CID is committed onchain; the request carries a 32-byte model_id derived from the SHA-256 digest of the model’s primary weight file.[^claim_1250] The parameters are explicit: 10 blocks per second, 36,000-block challenge window, 432,000-block finality depth.[^claim_1251] That is a miner model where model weights, not just hashes, are staked. It is less a ledger plus AI; it is a staking regime with an inference substrate.
The implication is not that agents will disappear. It is that the settlement layer for agents will be proof-first. OPAQUE and EQTY give pre- and mid-execution guarantees, Chainlink gives post-execution proof gates, and Keryx attempts to make inference rewards native to block production. Protocols that expose agents without verifiable execution will be treated as unfinished infrastructure. The market will short them accordingly.
Bottom line: Watch Chainlink’s proof verification as the near-term adoption path, and Keryx’s challenge window as the radical test. If consensus-native inference survives the fraud windows, the AI chain becomes less a narrative and more a miner-reward design.
Provenance ledger
12 span-verified · 1 web-cited12 claims below are locked to a verbatim span re-verified against the source. The remaining 1 is a web citation: 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] Microsoft Agent Framework is a production-oriented SDK for building AI agents and multi-agent workflows in .NET, Python, and Go, and its core abstraction set includes Agents, Harness Agent, Workflows, and Integrations. span-verified
Agent Framework brings together four primary areas: Agents ... Harness Agent ... Workflows ... Integrations ... build interactive, robust, and safe AI applications.
d59e036015e024d11cf85ee347757e0b4fb45000bff6accda0a9fcb30d48bb49 [2] The Go implementation is still in public preview, while declarative agents, RAG, CodeAct, and functional workflows are not yet available in that language binding. span-verified
Important: The Agent Framework for Go is in public preview. Declarative agents, RAG, CodeAct, and functional workflows are not yet available.
073ddc53b0fe613808190c3e71558173291183772f54d27d8e2b40ac50d13da3 [3] OPAQUE 3.0 launches Agent Manifest as an open standard for verifiable AI agents and Confidential MCP as the first Model Context Protocol implementation described as both verifiably governed and secured through confidential computing. span-verified
The announcement includes two major open-source milestones: the release of Agent Manifest ... and the launch of Confidential MCP, the first Model Context Protocol implementation that is both verifiably governed and secured through confidential computing.
40fd7f622ab53062a4841b78a18fd7eee8ce341641aa7d7c196cab6ab2e16bcc [4] OPAQUE says its confidential runtime runs on CPU-based confidential computing platforms from Intel, AMD, and NVIDIA, and that on NVIDIA Confidential Computing the integration brings GPUs inside the Trusted Execution Environment. span-verified
It runs on the CPU-based confidential computing platforms from Intel, AMD, and NVIDIA. And, on NVIDIA Confidential Computing, the integration brings GPUs inside the Trusted Execution Environment.
3204995d84bb88614bd91d7d11041674e8fb7bd64109a55f3627895344e3bd5d [5] EQTY Lab’s Verifiable Compute uses a notary running in a trusted execution environment on both CPU and GPU, and it claims users can verify an AI compute session before computation starts and continuously at runtime. span-verified
Using a notary run in a trusted execution environment (TEE) on both the CPU and GPU, users can verify that an AI compute session is confidential and meets required governance controls before computation starts and continuously at runtime.
2f3084350682b3775ceff3482a48dc0a4b5082cead23314745222ca1d74f6408 [6] EQTY Lab says its AI Notary System can produce persistent proofs of compliance in AI certificates that can be verified instantly or decades later without rerunning complex AI workloads. span-verified
persistent proofs of compliance in AI Certificates can be verified instantly or decades later without having to spend the time and money to rerun and reproduce complex AI workloads.
756f920fe14435516de917ee60c5d685212a954e5809f922ec4ad402a48f0573 [7] Chainlink’s verifiable AI stack routes AI computation offchain, then uses zkML or TEEs to produce a proof of correct execution before onchain delivery and smart-contract state changes. span-verified
Offchain computation ... Cryptographic verification ... This step often uses zero-knowledge machine learning (zkML) or trusted execution environments (TEEs) to generate a proof of correct execution. Onchain delivery ... The contract verifies the proof before executing any state changes.
44e8ba26e0dc9ad73c58347e9fe2622ddd8f47956f269853462666a82fa24560 [8] Chainlink says its Runtime Environment (CRE) coordinates offchain AI computation, data fetching, and verification before delivering results onchain. span-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.
a5018deee70d9a493a097605b6d896ced75924b05e5af07bc61cc0304be297f0 [9] 0G’s official docs describe a decentralized GPU marketplace for AI inference and training, and separate documentation for an ERC-7857 standard called Agentic ID for on-chain AI identities. span-verified
Compute: The decentralized GPU marketplace powering AI inference and training. ... Agentic ID: The ERC-7857 standard for on-chain AI identities.
3bebb882c73f14e6baffb26a1337c9805e0ebb85588bd3eb9e861abfc08d19a8 [10] Keryx’s July 2026 whitepaper says it embeds AI inference into PoW consensus via OPoI (Optimistic Proof of Inference), accepts inference results immediately, and allows challenge within a time-bounded window with 20% escrow slashing for fraud. span-verified
The core mechanism, OPoI (Optimistic Proof of Inference) ... inference results are accepted immediately and can be challenged within a time-bounded window. Fraud is detected ... Dishonest miners lose a 20% escrow automatically routed from their block reward.
31f6e3ccae5e0570da490689aff870f12492c20097080c9bc02d0711e9bc3f3d [11] Keryx’s PoM hardfork replaces the matrix-multiply PoW core with a data-dependent walk over resident model weights, and the whitepaper states that possession of the entire tier’s weights in VRAM is the only competitive configuration. span-verified
the matrix-multiply core is replaced by Proof-of-Model (PoM) ... the PoW becomes a data-dependent walk over the quantized weight tensors ... Possession of the entire tier's weights in VRAM is therefore the only competitive configuration.
0fd49fe084ff3a4cf38d12509d9998d987f53d75b221944884e22e325ea75ace [12] Keryx says its AI request flow stores the full inference output offchain on IPFS, while only a compact CID is committed onchain, and the request includes a 32-byte model_id derived from the SHA-256 digest of the model’s primary weight file. span-verified
The full inference output is stored off-chain on IPFS — only a compact CID is committed on-chain ... model_id is the SHA-256 digest of the model's primary weight file.
1bd45a85317df56a1e6acff39575f8df573a84fbe3718b97597bb0447e5062dd [13] Keryx’s network parameters specify a 10 blocks per second target, 36,000-block challenge window, and 432,000-block finality depth. web-cited
Block rate (BPS)|10 blocks/second ... Challenge window|36,000 blocks (~1 hour) ... Finality depth|432,000 blocks (~12 hours).
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://learn.microsoft.com/en-us/agent-framework/overview/
- https://www.opaque.co/resources/articles/opaque-extends-the-agent-governance-toolkit-with-verifiable-identity-and-first-ever-verifiably-governed-and-secure-mcp
- https://vcomp.eqtylab.io/
- https://chain.link/article/verifiable-ai-stack
- https://build.0g.ai/documentation
- https://keryx-labs.com/whitepaper