๐งช Testnet Phase #1 Recap โ Integration, Load, and Engine Expansion
Phase #1 was the first structured Testnet week where we focused on one thing: break the pipeline, harden the pipeline, and prove the system scales under real usage across both Testnet-0 (Arbitrum Sepolia) and Testnet-1 (COR #L3).
๐น Incentivized Manual Testing (E2E + Payments)
- Daily manual testing by community testers across different models and task types
- End-to-end validation: routing โ miner execution โ validator checks โ results
- Exercised both Pay-to-Use (pay per task) and Stake-to-Use (stake-based access / rate-limits)
- General stress-testing across components to surface edge cases early
๐น Automated Load Testing โ 130K+ Tasks Executed
- Automated task jobs ran continuously during Phase #1
- 130,000+ tasks executed, validating stability and throughput under sustained traffic
๐น Dashboard UI Refinement
- Multiple rounds of UI polish across session/task views
- Improved navigation and usability during high-volume sessions
๐น #Ollama Engine Support + 65+ Models Live
- Added #Ollama LLM engine support across Testnet-0 and Testnet-1
- 65+ models are now supported (Q1 target: 100+)
- Current limitation is disk footprint: nodes need many models stored to serve on request
- Next up: network-driven model auto-assignment + model-usage-aware routing
- Also added additional embedding models via Ollama to support Validator v2/v3 tuning, since the current embedding stack shows GPU-specific issues on some setups
๐น SessionQueue Scaling โ Read Throughput & Pagination
- Phase #1 load exposed a read bottleneck at high task volumes
- Added missing foundations: precomputed task stats per session + scalable pagination
- Dashboard + Router can now handle large query/read workloads under single sessions
๐น Corgent Experimental โ /delegate + /validate
- First iterations to validate rough E2E behavior and clarify exact requirements
- Established what needs to be strict vs flexible for agent-facing flows
๐น Router Experiments: #MCP + #x402 + #ERC8004
- #MCP, #x402 and #ERC8004 components are functional inside Router Node today
- Still require refinement and full integration
- These will be re-iterated during Phase #3โ#4 to land as router-native primitives
๐น Roadmap 2026 Docs Ready (Cortensor Network + Corgent)
- Roadmap documentation is now published and aligned for 2026 planning
Phase #1 proved the pipeline can survive both real usage and sustained automated load. Next phases will build on this foundation toward SLA-driven routing, tighter payment flows, and deeper agentic integrations.
https://x.com/cortensor/status/2005225713801277648
https://farcaster.xyz/cortensor/0xc94e762e
Phase #1 was the first structured Testnet week where we focused on one thing: break the pipeline, harden the pipeline, and prove the system scales under real usage across both Testnet-0 (Arbitrum Sepolia) and Testnet-1 (COR #L3).
๐น Incentivized Manual Testing (E2E + Payments)
- Daily manual testing by community testers across different models and task types
- End-to-end validation: routing โ miner execution โ validator checks โ results
- Exercised both Pay-to-Use (pay per task) and Stake-to-Use (stake-based access / rate-limits)
- General stress-testing across components to surface edge cases early
๐น Automated Load Testing โ 130K+ Tasks Executed
- Automated task jobs ran continuously during Phase #1
- 130,000+ tasks executed, validating stability and throughput under sustained traffic
๐น Dashboard UI Refinement
- Multiple rounds of UI polish across session/task views
- Improved navigation and usability during high-volume sessions
๐น #Ollama Engine Support + 65+ Models Live
- Added #Ollama LLM engine support across Testnet-0 and Testnet-1
- 65+ models are now supported (Q1 target: 100+)
- Current limitation is disk footprint: nodes need many models stored to serve on request
- Next up: network-driven model auto-assignment + model-usage-aware routing
- Also added additional embedding models via Ollama to support Validator v2/v3 tuning, since the current embedding stack shows GPU-specific issues on some setups
๐น SessionQueue Scaling โ Read Throughput & Pagination
- Phase #1 load exposed a read bottleneck at high task volumes
- Added missing foundations: precomputed task stats per session + scalable pagination
- Dashboard + Router can now handle large query/read workloads under single sessions
๐น Corgent Experimental โ /delegate + /validate
- First iterations to validate rough E2E behavior and clarify exact requirements
- Established what needs to be strict vs flexible for agent-facing flows
๐น Router Experiments: #MCP + #x402 + #ERC8004
- #MCP, #x402 and #ERC8004 components are functional inside Router Node today
- Still require refinement and full integration
- These will be re-iterated during Phase #3โ#4 to land as router-native primitives
๐น Roadmap 2026 Docs Ready (Cortensor Network + Corgent)
- Roadmap documentation is now published and aligned for 2026 planning
Phase #1 proved the pipeline can survive both real usage and sustained automated load. Next phases will build on this foundation toward SLA-driven routing, tighter payment flows, and deeper agentic integrations.
https://x.com/cortensor/status/2005225713801277648
https://farcaster.xyz/cortensor/0xc94e762e
โค2๐1๐1
๐๏ธ 2025 Year-End Wrap - Cortensor
2025 was the year we proved a simple thesis: decentralized inference can be practical if you treat it like infrastructure - not a science project.
We focused on one thing: build the execution loop, validate it under load, and set the foundation for an agent-ready and developer-ready trust layer - so builders can ship reliable AI apps without a high cost barrier.
Minimal E2E MVP is live
We shipped a minimal but real end-to-end pipeline:
Router โ Session Queue โ Miners โ Validators
Payments: Pay-per-use + Stake-to-Use (still early, still needs tuning).
DevNets โ Testnet
We completed 6 DevNet phases, kicked off Testnet, and wrapped Testnet Phase #1.
Load testing reached 150k+ tasks executed, validating feasibility under sustained traffic.
Infra & Scaling Bpgrades
Core improvements landed:
- NodePool / NodePoolUtil refactors + data isolation (future SLA routing)
- Session Queue & SessionQueued scaling for high read-throughput + session-heavy workloads
- Dashboard polish for better NodeOps monitoring + rewards/performance visibility
Models + Validation Surfaces Expanded
We rolled out 64+ models (including embedding stacks for Validator v2/v3).
We iterated on /validate (multiple templates) and introduced /delegate as a thin agent-facing SDK surface.
Hackathons pushed the ecosystem forward
We ran 3 hackathons in 2025.
So far, 15+ apps were qualified/rewarded - not just demos, but real feedback loops that pressure-test the network.
Early Agent Rails: #ERC8004 + #x402 + #MCP (experimental)
We ran rough experiments on #ERC8004, #x402, and #MCP to surface blockers early.
Not fully integrated yet - but these are the rails weโll harden and fold in during 2026.
What Cortensor is becoming
Cortensor is shaping into an execution + trust layer for web3 agents and agentic apps - while staying practical for everyday developers building AI products.
Agents (and apps) delegate work โ Cortensor runs redundant inference + proofs โ validation/trust signals return โ results become usable, reliable, and affordable, without a high-cost barrier to enter the AI app market.
2026 North Star
Build the shared primitives that both agent economies and developers keep needing:
- Execution that scales (reliable inference under load)
- Validation you can verify (PoI/PoUW trust rails)
- Trust signals you can reuse (for routing, SLAs, and agent workflows)
- Low-friction payments (#x402 + agent-native integrations)
That's the path toward becoming the AWS for agent economies - and a builder-friendly execution layer where anyone can ship agentic apps with confidence.
https://x.com/cortensor/status/2006903828713713710
https://farcaster.xyz/cortensor/0x450ea4dc
2025 was the year we proved a simple thesis: decentralized inference can be practical if you treat it like infrastructure - not a science project.
We focused on one thing: build the execution loop, validate it under load, and set the foundation for an agent-ready and developer-ready trust layer - so builders can ship reliable AI apps without a high cost barrier.
Minimal E2E MVP is live
We shipped a minimal but real end-to-end pipeline:
Router โ Session Queue โ Miners โ Validators
Payments: Pay-per-use + Stake-to-Use (still early, still needs tuning).
DevNets โ Testnet
We completed 6 DevNet phases, kicked off Testnet, and wrapped Testnet Phase #1.
Load testing reached 150k+ tasks executed, validating feasibility under sustained traffic.
Infra & Scaling Bpgrades
Core improvements landed:
- NodePool / NodePoolUtil refactors + data isolation (future SLA routing)
- Session Queue & SessionQueued scaling for high read-throughput + session-heavy workloads
- Dashboard polish for better NodeOps monitoring + rewards/performance visibility
Models + Validation Surfaces Expanded
We rolled out 64+ models (including embedding stacks for Validator v2/v3).
We iterated on /validate (multiple templates) and introduced /delegate as a thin agent-facing SDK surface.
Hackathons pushed the ecosystem forward
We ran 3 hackathons in 2025.
So far, 15+ apps were qualified/rewarded - not just demos, but real feedback loops that pressure-test the network.
Early Agent Rails: #ERC8004 + #x402 + #MCP (experimental)
We ran rough experiments on #ERC8004, #x402, and #MCP to surface blockers early.
Not fully integrated yet - but these are the rails weโll harden and fold in during 2026.
What Cortensor is becoming
Cortensor is shaping into an execution + trust layer for web3 agents and agentic apps - while staying practical for everyday developers building AI products.
Agents (and apps) delegate work โ Cortensor runs redundant inference + proofs โ validation/trust signals return โ results become usable, reliable, and affordable, without a high-cost barrier to enter the AI app market.
2026 North Star
Build the shared primitives that both agent economies and developers keep needing:
- Execution that scales (reliable inference under load)
- Validation you can verify (PoI/PoUW trust rails)
- Trust signals you can reuse (for routing, SLAs, and agent workflows)
- Low-friction payments (#x402 + agent-native integrations)
That's the path toward becoming the AWS for agent economies - and a builder-friendly execution layer where anyone can ship agentic apps with confidence.
https://x.com/cortensor/status/2006903828713713710
https://farcaster.xyz/cortensor/0x450ea4dc
๐ฅ4๐2โค1