> For the complete documentation index, see [llms.txt](https://docs.cortensor.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortensor.network/community-and-ecosystem/community-testing/testnet-phase/testnet-phases-and-focus-areas-structured-plan.md).

# Testnet Phases & Focus Areas (Structured Plan)

**Status:** Active Planning (Mid Q4 2025 → Mid Q2 2026)\
**Duration:** \~4–6 weeks per phase (4 phases total)\
**Networks:** DevNet7 (Internal R\&D) | Testnet-0 (Arbitrum Sepolia) | Testnet-1 (COR L3 Rollup)\
**Reference:**\
<https://docs.cortensor.network/technical-architecture/testnet-and-mainnet-strategy>

***

### **Overview**

The Testnet Phase transitions Cortensor from controlled prototype environments to full-scale, real-world validation.\
\
Unlike DevNet cycles — where data resets were frequent — Testnet data persists across all four phases, allowing long-term analysis of validator accuracy, node reliability, and gas optimization.\
Only major systemic failures will trigger resets.<br>

Each phase lasts roughly 4–6 weeks, and builds incrementally toward Mainnet deployment, emphasizing stability, verification, and ecosystem maturity.

***

### **Network Roles**

| **Network**                      | **Role**                       | **Description**                                                                             |
| -------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------- |
| **DevNet7**                      | Internal Development Network   | Used for rapid module iteration, regression testing, and contract debugging. Internal-only. |
| **Testnet-0 (Arbitrum Sepolia)** | Public L2 Validation Ground    | Main environment for node operators and stress tests under real gas conditions.             |
| **Testnet-1 (COR L3 Rollup)**    | Sovereign AppChain Environment | Long-term validation of COR-as-gas economics, validator feedback loops, and scalability.    |

Most external node operators and miners will run on **Testnet-0** and **Testnet-1**, while **DevNet7** remains internal for core development and regression debugging.

***

### **Phase 1 — System Integration & Regression Validation**

**Timeline:** *Mid Q4 → End of Q4 2025*

**Goal:** Restore stability and ensure all node roles and modules function cohesively after recent feature integrations.\
**Focus:** Regression recovery, full E2E validation, and system-wide observability.

**Scope**

* Comprehensive regression testing across Router, Miner, Validator, Oracle, and Dashboard Indexer nodes.
* Full E2E flow validation: task creation → routing → validation → payment → reputation update.
* Cross-module integration checks for Cognitive, Session, Validator, Runtime.
* Dashboard baselines: latency, throughput, validator sync, miner precommit stats.
* Node infrastructure review: NodePool, NodeSpec, heartbeat, uptime tracking.
* Code cleanup + unit testing: regression fixes and interface harmonization.
* Initial gas benchmarking: identify high-cost paths in Session, Payment, and Validation.
* Developer docs: REST API + on‑chain interfaces with Python/TS/JS examples.

**Outcome:** Stable, integrated environment ready for scalable validation and optimization work.

***

### **Phase 2 — Validation Refinement & Infrastructure Hardening**

**Timeline:** *Early Q1 → Mid Q1 2026*

**Goal:** Strengthen validator logic, expand redundancy, and begin formal gas optimization.\
**Focus:** Accuracy, trust stability, and infrastructure robustness.

**Scope**

* **Validator v2/v3 refinement:** Deep PoI (quantitative) & PoUW (qualitative) validation.
* **QuantitativeStats / QualitativeStats:** expand datasets for threshold calibration and LLM-verifier scoring.
* **Oracle & internal service reliability:** router APIs, indexers, dashboard feeds.
* **Infrastructure redundancy:** multiple RPC endpoints, failover mechanisms, validator backups.
* **Gas optimization & runtime tuning:**
  * Profile Cortensord parameters and on-chain execution paths.
  * Optimize SessionQueueValidation, SessionPayment, and Validator storage for L2.
  * Reduce log events and nested calls to minimize gas costs.
* **Dashboard expansion:** real-time PoI/PoUW analytics and validator health views.

**Outcome:** Redundant, cost-efficient, and fully instrumented trust layer.

***

### **Phase 3 — Privacy, Payments & Incentive Mechanics**

**Timeline:** *Mid Q1 → End of Q1 2026*

**Goal:** Deploy privacy-preserving sessions and finalize economic mechanisms.\
**Focus:** Confidentiality, sustainability, and incentive fairness.

**Scope**

* **Privacy integration:**
  * Implement three-party encryption (User ↔ Miner ↔ Oracle).
  * Benchmark latency and select default scheme (Session V3).
* **Payment flow refinement:**
  * Tune unit costs, rebates, and surcharge parameters.
  * Expand SessionPayment metadata and gas tracking.
* **Staking-to-Use feature:**
  * Extend SessionPayment to support stake-based free inference quotas.
  * Enable auto-deduction from user stake balances.
* **Node reward automation:**
  * Dynamic rewards linked to NodeReputation and Validator feedback.
  * Pilot GPU/CPU reward balance curves.
* **Gas profiling iteration:**
  * Measure gas after privacy integration; compare vs Phase 2 baseline.

**Outcome:** Secure, privacy-preserving sessions with efficient and transparent economic flows.

***

### **Phase 4 — Agentic Integration & Mainnet Preparation**

**Timeline:** *End of Q1 → Mid Q2 2026*

**Goal:** Align Cortensor’s decentralized inference with the agent economy and initiate Mainnet transition.\
**Focus:** ERC-8004 and x402 integration, SDK design, and Mainnet L2 readiness.

**Scope**

* **Agentic Hackathons:**
  * Continuous rounds focused on agentic apps built with Cortensor SDK.
  * Collect developer feedback on API ergonomics and missing hooks.
* **Basic Agent SDK Design:**
  * Define session routing, proof generation, validation APIs.
  * Map ERC-8004 Identity / Validation / Reputation linkages.
  * Integrate x402 for pay-per-call and stake-to-use top-ups.
* **x402 + ERC-8004 Phase 1 (COR Prover MVP):**
  * Delegated sessions with k-redundant PoI consensus.
  * v3 LLM evaluation + signed attestations (JWS/EIP-712).
  * Register COR Prover identity under ERC-8004 Validation Registry.
  * [x402 & ERC‑8004 - Three‑Phase Integration Plan](https://docs.cortensor.network/technical-architecture/designs-wip/early-wip-x402-and-erc-8004-three-phase-integration-plan)
* **SessionQueueValidation Extensions:**
  * Implement TaskRoot and SessionRoot Merkle structures for proof anchoring.
  * Map SessionID ↔ ValidatorID for cross-agent reputation tracking.
* **Node Ops Tooling:**
  * Enhanced CLI and dashboard for GPU nodes and cluster monitoring.
* **Mainnet Preparation:**
  * **L2 Mainnet (Lite)** launch first on Arbitrum Mainnet for lower cost and partner access.
  * **L3 Mainnet (Full/GA)** follows after ecosystem traction to avoid premature rollup maintenance costs.
  * Begin partner onboarding via hackathons and early SDK adoption.
* **Dashboard Upgrades:**
  * Network-wide agent analytics and cross-chain validation views.

**Outcome:** Agent-ready SDK, ERC-8004 & x402 compatibility, and Mainnet L2 infrastructure ready for launch.

***

### **Post-Testnet Feature Phases (After Q2 2026)**

Following the 4-phase Testnet, Cortensor enters the **x402 + ERC-8004 feature expansion track**, aligned with Mainnet iterations:

| **Integration Phase**                           | **Timing**                  | **Focus**              | **Description**                                                                                          |
| ----------------------------------------------- | --------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------- |
| **x402 Phase 2 — Passes & Expansion**           | Post-Testnet / Mainnet-Lite | Feature Iteration      | Introduce x402 passes, quotas, idempotent invoices, ERC-8004 Validation writes by default.               |
| **x402 Phase 3 — Core Inference & Agent Flows** | Mainnet-Full / L3 Rollup    | Agentic Infrastructure | Implement one-shot x402 for `/v1/infer`, agent-bound flows over MCP, and cross-agent 8004 registrations. |

These phases are **feature releases**, not Testnet extensions, and will be tracked under the Mainnet Roadmap series.

***

### **Phase Continuity & Data Policy**

* **Persistent data:** No routine resets; continuous tracking of validators, nodes, and gas efficiency.
* **Selective resets:** Only for breaking migrations or corrupted state.
* **Cross-phase analytics:** Aggregate feeds for NodeReputation, Validator scores, SessionPayment economics, and gas usage over time.

***

### **Summary**

By mid-Q2 2026, Cortensor will have:

* Validated PoI and PoUW at scale.
* Implemented privacy-preserving sessions.
* Achieved significant gas optimization for L2/L3 deployment.
* Refined staking and reward systems.
* Released Agent SDK spec and ERC-8004 alignment.
* Deployed Mainnet L2 as the first production environment, with L3 to follow post-traction.

Cortensor’s Testnet Phases lay the foundation for a **trustless, verifiable, and gas-efficient AI execution network**, evolving seamlessly into the Mainnet era of decentralized and agentic AI infrastructure.