🧪 Testnet Phase #4 Starts Now

Testnet Phase #4 is now live.

Phase #4 is less about adding isolated features and more about tightening the full pipeline under realistic conditions — data → quality → routing, reliability under load, and Mainnet Lite readiness.

🔹 E2E scope lock (Phase #3 → Phase #4)
Finalize the end-to-end test plan + order + pass/fail metrics (throughput/latency, recovery, drift, data integrity/offchain correctness)

🔹 Deeper stress testing (Data → Quality Path)
Longer, higher-volume runs that hit real failure modes (miner churn, partial outages, RPC degradation, queue spikes)

🔹 Privacy + offchain storage stress tests (optional / heavier)
Heavier testing where enabled: encryption paths, offchain correctness, and edge cases (timeouts, stale keys, partial writes)

🔹 SLA / quality signals – deeper validation (#3 signals)
Stress SLA signals under churn/load (drift detection, reliability weighting vs uptime, disagreement/arbitration behavior)

🔹 Portal V1 (design → early implementation) + product boundary
Portal becomes a real product layer: client → Portal backend → router pool → sessions
Scope: API keys, usage visibility, managed router pools, auth/rate limits, billing hooks + metering

🔹 Portal focus (gateway → router pool path)
Key issuance/consumption path is proven; Phase #4 drills into the hosted execution shape from Portal Gateway into managed router pools

🔹 PyClaw (early dev release track)
Move from design into early dev release: landing page + docs + initial runtime scaffolding aligned to router/session primitives

🔹 Mainnet Lite infra planning (execution readiness)
New RPC/server path is ready (L2 testnet/mainnet + L3 testnet/pre-mainnet)
Phase #4 begins bringing up Mainnet Lite pieces on top (dashboard, indexer, oracle-related path)

🔹 Core Docs
Testnet Phase #4: https://docs.cortensor.network/community-and-ecosystem/community-testing/testnet-phase-4

https://x.com/cortensor/status/2055830240958533777