@cortensor

🧪 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.

1 reply

1 recast

1 reaction