Roadmap

From Server to Math

Five phases from centralized oracle to trustless cryptographic verification. Every step reduces trust assumptions — until the only thing you trust is math.

Phase 1
Trust a server
Phase 2
Harden the server
Phase 3
Trust math (zkTLS)
Phase 4
Trust the network
Phase 5
Sovereign L1
Phase 1
Centralized Oracle Current
Prove that Proof of AI Work works. Ship fast, iterate, validate the mechanism.
v2 smart contracts on Ethereum mainnet — CLAW_Token, PoAIWMint, MinterProxy, OracleVerifier
Centralized Oracle service — 7-step verification pipeline with ECDSA signing
Genesis mining — first $CLAW minted on-chain
Mining Skill — one-click mining via AI Agent platforms (OpenClaw, Hermes Agent, Perplexity)
Brand identity and website launch
Real-time mining dashboard
ClawHub Skill listing — publish on OpenClaw marketplace
Protocol documentation on GitBook
Trust model: Miners trust a single Oracle server to honestly verify AI work and issue signatures.
Phase 2 — Q2 2026
Infrastructure Hardening Planned
Strengthen the foundation before decentralizing.
SQLite persistence — Oracle state recovery on restart, prevents duplicate submissions
Oracle monitoring — Prometheus + Grafana for uptime, latency, and error tracking
RPC optimization — Multicall3 batched on-chain reads to reduce verification latency
Multi-model support — expand AI providers beyond xAI (OpenRouter, Anthropic, etc.)
Mining pool — managed mining service for non-technical users
Community onboarding — first external miners join the network
First DEX listing
Trust model: Still centralized Oracle, but with production-grade reliability and monitoring.
Phase 3 — Q3–Q4 2026
zkTLS Integration Planned
Replace the centralized Oracle with cryptographic verification. The core technical transition.
Step 1 — zkTLS Protocol Selection
Evaluate candidates: TLSNotary (MPC-TLS, most mature), Opacity Network (MPC-TLS + TEE + EigenLayer), Reclaim Protocol (proxy witness), zkPass (VOLE-based ZKP)
Benchmark: proof generation speed, gas cost, Ethereum compatibility, Agent environment support
Step 2 — MPC-TLS Proof of Concept
Notarized AI API call — Miner and Notary jointly perform TLS handshake, splitting the encryption key via MPC
Notary attestation — Notary signs proof that a real TLS session occurred (without seeing plaintext data)
ZK selective disclosure — Miner proves mining criteria (correct model, valid seed, token count) without revealing full API response
On-chain verification — ZK proof submitted and verified on Ethereum
Step 3 — ZK Circuit Design
Encode the 7-step Oracle verification pipeline as ZK circuit constraints
Support selective disclosure: model validation, seed matching, token count range, session freshness
Optimize for gas cost — proof aggregation and batching strategies
Step 4 — ZkTLSVerifier Contract
Deploy ZkTLSVerifier contract — replaces OracleVerifier for on-chain ZK proof verification
Security audit — independent audit of the new verifier contract
MinterProxy upgrade — use 7-day timelock to transition from OracleVerifier to ZkTLSVerifier
Trust model: Trust math + cryptography. MPC key splitting ensures neither miner nor Notary can forge data alone.
Phase 4 — 2027
Notary Network Planned
Decentralize verification from one server to a network of independent nodes.
Step 1 — Notary Node Specification
Define staking requirements, registration process, and slashing conditions
Random assignment mechanism — miners cannot choose their Notary (on-chain VRF)
Commit-and-reveal — miners commit mining parameters before Notary is assigned
Step 2 — Anti-Collusion Mechanisms
Multi-Notary verification — critical operations require attestations from multiple independent Notaries
TEE isolation — Notary key management inside Trusted Execution Environments (Intel SGX)
On-chain audit trail — every attestation attempt logged publicly
Step 3 — Testnet & Migration
Testnet deployment on Sepolia — full end-to-end with live Notary nodes
Parallel operation — both Oracle and zkTLS+Notary paths active on mainnet simultaneously
Oracle sunset — centralized Oracle deprecated, Notary network becomes sole verification path
Trust model: Trust-minimized. Decentralized Notary network with staking/slashing + MPC cryptography + TEE. Secure as long as at least one Notary in the selected set is honest.
Phase 5 — 2027+
The Money of AI Vision
The Bitcoin of AI. $CLAW becomes the medium of exchange, store of value, and unit of account for AI computation — on its own sovereign network.
Step 1 — Sovereign L1 Network (Blockless Architecture)
Launch the CLAW L1 — a blockless, modular compute network purpose-built for AI verification
Network-Neutral Application (nnApp) framework — miners and Notaries run as nestled nodes, no dedicated hardware required
Dynamic consensus — workload-specific consensus selection, optimized for AI attestation throughput
WASM execution environment — Mining Skills run natively in the network’s secure WebAssembly runtime
Automated orchestration — dynamic resource matching assigns Notary nodes based on capacity, geolocation, and reputation
Step 2 — Migration from Ethereum
Bridge CLAW from ERC-20 to native L1 token — trustless two-way bridge
Migrate PoAIW mining to native L1 — faster finality, near-zero gas costs
Preserve all tokenomics — 210B supply, Era/Epoch structure, halving schedule unchanged
Step 3 — AI Economy
On-chain governance — community votes on AI model rotation, parameters, and protocol upgrades
AI inference pricing — $CLAW as the unit of account for AI computation across providers
Ecosystem growth — third-party Skills, AI service marketplaces, and cross-chain interoperability
Trust model: Fully sovereign. CLAW L1 with native verification, decentralized Notary network, and community governance. The Bitcoin of AI.

This roadmap is a living document. Follow @minewithclaw for updates.

Explore More
Start mining now →Learn how Proof of AI Work works →See the tokenomics →