Historical Roadmaps¶
Last updated: 2026-06-28
Historical roadmap context explains where the project came from. Current setup and launch instructions live in the active getting-started and roadmap pages.
Original Comprehensive Roadmap¶
The original roadmap was organized around broad phases from Q3 2024 through Q4 2026 and beyond.
| Phase | Period | Historical theme |
|---|---|---|
| Phase 1 | Q3 2024 to Q1 2025 | Foundation, L2/L3 architecture design, early Web2/Web3 interfaces, staking dApp, community setup. |
| Phase 2 | Q4 2024 to Q1 2025 | Alpha/devnet launch, PoW refinement, user-serving work, router direction, early synthetic-data ideas. |
| Phase 3 | Q2 2025 to Q3 2025 | Testnet launch/refinement, developer docs/tools, hackathons, bug bounty direction. |
| Phase 4 | Q4 2025 to Q1 2026 | Testnet refinement, security audits, performance optimization, mainnet preparation. |
| Phase 5 | Q1 2026 | Mainnet preparation, final testing, docs/tools/resources. |
| Phase 6 | Q1 to Q2 2026 | Original mainnet launch framing. Superseded by the newer Mainnet-Lite/Mainnet-Full framing. |
| Phase 7 | Q3 2026 and beyond | Feature expansion, privacy, more models, enterprise, interoperability, governance. |
| Phase 8 | Q4 2026 and beyond | Scaling, global expansion, R&D, ecosystem maturity, continuous improvement. |
Technical Roadmap 2025¶
| Period | Historical theme | Current interpretation |
|---|---|---|
| Q3 2024 | Launch and genesis; staking dApp; early community support. | Historical community/token context. |
| Q4 2024 | Closed alpha focused on mining/network task validation and hardware compatibility. | Historical miner/operator evolution. |
| Q1 2025 | Open alpha, points, airdrop planning, broader testing. | Historical unless a current campaign exists. |
| Q2 2025 | User-request testing phase for Layer 2/user serving. | Conceptual predecessor to router/API/user-serving work. |
| Q3 2025 | Full user-request and mining integration. | Historical path toward router/miner/session architecture. |
| Q4 2025 and beyond | Testnet and mainnet launch preparation. | Superseded by current 2026 testnet/Mainnet-Lite/Mainnet-Full plan. |
Community Testing Archive¶
The historical archive also contains closed alpha phases, testnet phase pages, DevNet mapping, DevNet modules/parameters, Discord role and privilege notes, contests, and readiness memos.
| Historical content | Status |
|---|---|
| Closed Alpha phases | Community testing history. |
| DevNet module/address pages | Superseded by active deployment matrices. |
| Discord roles/mainnet privileges | Community program history unless active terms are published. |
| Product demo contests | Community/contest history. |
| Testnet readiness memos | Architecture context, not live deployment values. |
What Changed¶
| Area | Change |
|---|---|
| Router/API | The current router direction includes separate /api/v1, /api/v2, and /api/v3 route families for completions, delegate, and validate, plus factcheck, trial, x402, A2A, MCP, privacy, and off-chain flows. |
| Products | Portal and API gateway became a distinct hosted product plane. |
| Agent surfaces | Corgent/Bardiel emerged around delegate, validate, factcheck, policy tiers, and arbitration direction. |
| Network strategy | Mainnet-Lite and Mainnet-Full are now the launch framing. |
| Setup guides | Public node setup uses packaged cortensord commands rather than source entrypoints. |