2026 Network Launch¶
Last updated: 2026-06-28
The 2026 roadmap moves Cortensor from a testnet-focused inference network into agent-ready decentralized AI infrastructure. The plan joins router evolution, validation primitives, agent ecosystem integration, and staged network launch.
Objectives¶
Agent-ready router
Upgrade Router Node into Router Agent with stable completions, validation, delegation, MCP, A2A, and x402 surfaces.
Reusable validation
Turn PoI and PoUW into validation primitives that agents and applications can use before accepting outputs or taking action.
Virtual ecosystem integration
Embed Cortensor agents and Corgent inside Virtual, ACP, and ERC-8004-style ecosystems.
Network launch
Complete the four-phase testnet path, then launch Mainnet-Lite on Arbitrum L2 Alpha and Mainnet-Full on COR L3 Beta.
Phase Timeline¶
Testnet phases 1-2: Router v1.5 foundations
System-wide regression, end-to-end application testing, NodePool and SLA routing groundwork, validator v2/v3 stabilization, dual-testnet routing, and dashboard telemetry.
Testnet phases 3-4: validation layer
/validate, PoI/PoUW integration, embedding-distance checks, LLM verifier scoring, scorecards, attestations, optional IPFS evidence bundles, and Router v1.6 / COR Prover direction.
Mainnet preparation
Stake-to-use, pay-per-use, x402 receipts, service metadata, Virtual/ACP/dApp testing, audits, routing stress tests, session stability, bridge, RPC, explorer, and indexer preparation.
Mainnet-Lite: Arbitrum L2 Alpha
Production-oriented agent workloads, stable Router Agent, live inference and validation endpoints, COR bridging, explorer integration, and L2 telemetry.
Agentic integration
Cortensor agents operate inside Virtual/ACP ecosystems, while Corgent becomes a verification oracle for task delegation, validation, recursive reasoning checks, and dispute workflows.
Router v2.0 and network scaling
Hardened MCP/x402 stack, public validation attestations, ERC-8004 registry participation, score-distribution telemetry, SLA reporting, and multi-agent load profiles.
Mainnet-Full: COR L3 Beta
COR-native payments, low-cost high-volume agent execution, recursive tasks, metadata rollup, miner/oracle-backed security, and agent-to-agent adjudication.
Router Capability Map¶
| Capability | Role in the 2026 roadmap |
|---|---|
/completions |
Base inference primitive for hosted API users, direct router users, Portal, and agents. |
/delegate |
Sends work to Cortensor miners under policy and redundancy settings. |
/validate |
Checks outputs, claims, or actions before an agent or application relies on them. |
/factcheck |
Claim-checking and evidence-oriented validation surface where configured. |
| MCP | Tool and agent protocol surface layered over router capabilities. |
| A2A | Agent metadata and discovery direction for agent-to-agent ecosystems. |
| x402 | Pay-per-call route family for agent and application usage. |
| Privacy and off-chain payloads | Encrypted sessions, URN references, private inference, and evidence-bundle storage. |
Agentic Lifecycle¶
sequenceDiagram
participant Agent as External Agent
participant Router as Router / Corgent
participant Miners as Miner Sessions
participant Validators as Validators
participant Verdict as Verdict / Evidence
Agent->>Router: completions / delegate / validate / factcheck
Router->>Miners: route task by session and policy
Miners-->>Router: outputs, hashes, or URNs
Router->>Validators: PoI / PoUW / scoring flow
Validators-->>Verdict: score, reasons, references
Verdict-->>Agent: output, verdict, retry, or escalation
How This Connects To Products¶
| Product area | Roadmap connection |
|---|---|
| Router Node | Router Agent v1.5 through v2.0, MCP/x402, route families, sessions, and metadata. |
| Portal and API gateway | Hosted access, API keys, usage metering, billing, model aliases, and managed router pools. |
| Corgent | Virtual-native delegation, validation, arbitration, and trust-oracle surface. |
| Bardiel | Productized ecosystem agent using delegate, validate, factcheck, and staking/product surfaces. |
| Dashboard | Network telemetry, session visibility, node/model status, and operator controls. |