Cortensor Announcements

🧪 Testnet Phase #4 – Wrap-Up Recap Testnet Phase #4 is wrapping up over the next 48 hours. Phase #4 focused on tightening the full Cortensor stack under more realistic conditions - network execution, Portal, router pools, observability, L3 recovery, and Mainnet Lite readiness. Core Infra: 🔹 Mainnet Lite baseline validation - Mainnet Lite moved from rough setup into real E2E baseline checks under actual mainnet conditions - Dedicated-node user tasks, ephemeral-node network tasks, and ephemeral-node user-task → node-pool flows all worked end to end 🔹 Mainnet Lite infra readiness - Contract/module deployment, RPC/server setup, oracle/indexer/dashboard setup, explorer checks, and chain-side validation reached rough baseline form - Heartbeat/ping timing was adjusted around real Arbitrum mainnet gas-cost assumptions 🔹 RPC / environment separation - Internal RPC infrastructure was refreshed and migrated toward newer internal/community-backed paths - Testnet and mainnet RPC separation started on newly provisioned servers as prep for Mainnet Lite and later Mainnet Full 🔹 Testnet1a / L3 recovery - Testnet1a went through a real sequencer / local Nitro DB recovery exercise using L2 batch data plus DAS/DA-backed data - The recovery helped validate L3 rebuild flow, edge cases, and future sequencer backup/redundancy planning 🔹 Cortensor L3 progress - Cortensor L3 closed Phase #4 in a much stronger operational position - The network has processed over 8M blocks and over 16.5M transactions 🔹 Mainnet Full early tryouts - Very early Mainnet Full infra work started across rough server setup, bridge flow, contract deployment, explorer checks, and connectivity validation - This remains early, but helped prepare the path beyond Mainnet Lite Products / Stack: 🔹 Portal V1 – hosted API layer - Portal stress tests expanded into larger prompts, heavier token-size requests, longer-running hosted API calls, and multi-model testing across oss-20b, gemma4, qwen 3.5 9b, and oss-120b - API Gateway → router pool → session routing was validated in rough form, including dynamic model reconfiguration, capacity-aware routing, and multi-instance gateway deployment 🔹 Portal V1 – metering + observability - OpenAI-style and Anthropic-style REST compatibility advanced, with SSE / streaming MVP support added at the gateway level - Usage tracking moved toward token-based metering, while public stats and admin/ops views expanded across usage, latency, route health, gateway health, tokens, heatmaps, and model/session triage 🔹 Portal auth + control-plane direction - Portal auth matured with prod OAuth setup for Google, X, and Discord, while wallet login was de-emphasized because of spam/abuse concerns - Backend planning advanced toward a future API/control-plane path beyond the current Supabase-style pattern 🔹 Docs V2 - Docs V2 progressed in rough form with cleaner structure, updated diagrams, and clearer operator/developer paths - Current direction is to preview the new docs website during Q3 between Mainnet Lite and Mainnet Full 🔹 PyClaw - PyClaw early WIP direction continued with a public early snapshot/repo push - Framing became clearer: local-first agent/app layer now, with future connection into remote delegation and agent-cloud-like flows 🔹 Stack messaging - Public stack messaging expanded across Network & Infra, Dashboard, Portal, Corgent, @BardielTech, and PyClaw - Mainnet Lite vs Mainnet Full was clarified further: Lite first as the controlled L2 rollout path, Full later as the fuller Arbitrum Orbit L3 path Phase #4 tightened the path from network execution to hosted access, routing, metering, observability, L3 recovery, and Mainnet Lite readiness. After Phase #4 wraps, the next focus is detailed planning and execution toward Mainnet Lite. https://x.com/cortensor/status/2073337304278843903