🛠️ DevLog – New RPC Servers Ordered, Infra Separation Comes Next A quick infra update. 🔹 Current progress - We’ve ordered a new server for the RPC path - It is now getting fulfilled, and we’re waiting on the data center response 🔹 What’s next - Later this week, we’ll start separating some of the infra across servers - This is also part of the earlier pre-prep work for Mainnet Lite 🔹 Why this matters - The main goal is to separate the RPC environments more cleanly - In practice, that means moving toward clearer separation between: - testnet RPC infra - mainnet RPC infra 🔹 Current takeaway - new RPC capacity is on the way - infra separation comes next - and this is part of the broader Mainnet Lite pre-prep path #Cortensor #DevLog #RPC #Infra #MainnetLite

⏰ Reminder – Testnet Phase #4 Wraps This Weekend A quick reminder on the near-term timeline. 🔹 Current phase - Testnet Phase #4 is expected to finish / wrap up this weekend 🔹 What comes with that - prize processing / follow-up comes after the wrap-up - then we move into the planning stage for Mainnet Lite prep 🔹 What happens next - More detailed Mainnet Lite prep plans will be shared after the planning period in the weeks following the Phase #4 wrap-up 🔹 Current takeaway - Phase #4 is almost done - wrap-up and prizes come next - then Mainnet Lite planning begins #Cortensor #DevLog #Testnet #Phase4 #MainnetLite

⏰ Reminder – Testnet Phase #4 Wraps in About a Week A quick reminder on the broader timeline. 🔹 Current phase - Testnet Phase #4 is expected to wrap in about a week 🔹 What comes after that - We’ll finish wrapping up Phase #4 fully - then shift more attention toward the planning and prep work for Mainnet Lite, as mentioned earlier 🔹 Current takeaway - about one more week for the current phase - then Phase #4 wrap-up - then more focused Mainnet Lite planning and prep from there #Cortensor #DevLog #Testnet #Phase4 #MainnetLite

Mainnet Lite is the controlled first step for bringing the Cortensor stack onto real mainnet conditions. The point is not to do everything at once. It is to start with a simpler, more productized L2 path first at @Arbitrum, validate the stack under real conditions, and then build outward from there. Q3 2026. #Cortensor #MainnetLite #Mainnet #Arbitrum

🛠️ DevLog – Portal Admin / Ops Visibility Keeps Getting More Useful A quick follow-up on the Portal admin / ops side. 🔹 Current progress - We’ve kept refining the admin / ops visibility surface so it is easier to understand what is happening across the Portal path - That includes broader improvements around metrics, hotspot visibility, and operational drilldowns 🔹 What improved - We added more triage-oriented views to help identify noisier or weaker paths faster - That includes triage around: - pool routes - model lanes - API Gateway instances - mapped sessions underneath 🔹 Why this matters - As traffic grows, it becomes harder to rely only on raw tables or broad summary metrics - These triage views make it easier to spot: - bad nodes - bad sessions - weaker model paths - noisier gateway instances 🔹 Current takeaway - Portal admin / ops is no longer only about broad observability - it is also becoming more useful for actual triage and follow-up when something starts degrading #Cortensor #DevLog #Portal #Observability #APIGateway #AIInfra

🛠️ DevLog – Portal Stress Tests Resumed, Monitoring Continues A quick follow-up on the current Portal testing path. 🔹 Current status - Portal stress tests have resumed - So far, things look good overall 🔹 Current issue - One model / node path still needs some attention from node ops - That has already been flagged and shared on our side 🔹 Visibility - The public Portal stats surface is reflecting the current state - The internal admin / ops pages are reflecting it as well 🔹 What’s next - We’ll keep these tests running through this week - and continue monitoring while we wrap up the current Testnet Phase #4 🔹 Current takeaway - stress tests are back in motion - overall path looks fine so far - one node/model path needs follow-up - monitoring continues across both public stats and internal ops surfaces #Cortensor #DevLog #Portal #StressTest #Observability #AIInfra

🗓️ Weekly Focus – Phase #4 Wrap-Up & Mainnet Lite Preparation This week is mainly about wrapping up Testnet Phase #4. Most Phase #4 work is now complete, so the focus shifts toward final validation before entering the Mainnet Lite prep period, which is expected to last around ~6 weeks. 🔹 Phase #4 – Wrap-Up & Final Validation - Continue monitoring routing, miners, validators, dashboards, indexers, and L3 stats through the final week. - Run another overall validation pass to ensure Phase #4 closes with a clean baseline. 🔹 Portal V1 – Product Refinement - Continue polishing Portal V1 across auth, API keys, usage visibility, request logs, and overall UX. - Tighten the hosted product flow before shifting attention toward Mainnet Lite deployment. 🔹 Portal V1 – Public Stats Refinement - Continue refining the new public Portal stats page built on live production data. - Improve caching, observability, and overall UX while expanding useful public metrics. 🔹 Portal V1 – Final E2E Validation - With Testnet-1a nearly recovered, run another round of Portal E2E testing. - Validate the full hosted path across Gateway → router pools → router nodes under real conditions. 🔹 Mainnet Lite – Final Baseline Checks - Re-check the remaining Mainnet Lite baseline items before entering the prep period. - Confirm infra, RPC, contracts, dashboard, indexer, oracle, and application wiring are all ready. 🔹 Mainnet Lite – Prep Planning - Continue preparing the Mainnet Lite rollout plan, infrastructure, and application setup. - Mainnet Lite remains the controlled first mainnet step before the broader Mainnet Full/L3 direction. 🔹 PyClaw – Dev Path Progress - Continue PyClaw iteration toward the first public development release. - Keep improving workflow, tooling, and side packages before the initial public snapshot. This week is about closing Phase #4 cleanly, validating Portal V1 under real conditions, and preparing everything needed before transitioning into the Mainnet Lite preparation period. #Cortensor #Testnet #Phase4 #AIInfra #DePIN #Portal #PyClaw #MainnetLite #L3

🗓️ Weekly Focus – Phase #4 Wrap-Up & Mainnet Lite Preparation This week is mainly about wrapping up Testnet Phase #4. Most Phase #4 work is now complete, so the focus shifts toward final validation before entering the Mainnet Lite prep period, which is expected to last around ~6 weeks. 🔹 Phase #4 – Wrap-Up & Final Validation - Continue monitoring routing, miners, validators, dashboards, indexers, and L3 stats through the final week. - Run another overall validation pass to ensure Phase #4 closes with a clean baseline. 🔹 Portal V1 – Product Refinement - Continue polishing Portal V1 across auth, API keys, usage visibility, request logs, and overall UX. - Tighten the hosted product flow before shifting attention toward Mainnet Lite deployment. 🔹 Portal V1 – Public Stats Refinement - Continue refining the new public Portal stats page built on live production data. - Improve caching, observability, and overall UX while expanding useful public metrics. 🔹 Portal V1 – Final E2E Validation - With Testnet-1a nearly recovered, run another round of Portal E2E testing. - Validate the full hosted path across Gateway → router pools → router nodes under real conditions. 🔹 Mainnet Lite – Final Baseline Checks - Re-check the remaining Mainnet Lite baseline items before entering the prep period. - Confirm infra, RPC, contracts, dashboard, indexer, oracle, and application wiring are all ready. 🔹 Mainnet Lite – Prep Planning - Continue preparing the Mainnet Lite rollout plan, infrastructure, and application setup. - Mainnet Lite remains the controlled first mainnet step before the broader Mainnet Full/L3 direction. 🔹 PyClaw – Dev Path Progress - Continue PyClaw iteration toward the first public development release. - Keep improving workflow, tooling, and side packages before the initial public snapshot. This week is about closing Phase #4 cleanly, validating Portal V1 under real conditions, and preparing everything needed before transitioning into the Mainnet Lite preparation period. #Cortensor #Testnet #Phase4 #AIInfra #DePIN #Portal #PyClaw #MainnetLite #L3

🛠️ DevLog – Testnet1a Is Back to Normal, Portal Stress Tests Resume Later Today A quick follow-up on the recent testnet1a recovery. 🔹 Current status - L3 / testnet1a is back to normal - All router endpoints are back to normal as well 🔹 Why this matters - This was a good recovery exercise for us on the infra / ops side - It gives more confidence that, with the current dataset and recovery path, we can rebuild and recover from this kind of disaster event more cleanly than before 🔹 What’s next - We’ll keep monitoring things further today - If everything continues to look stable, we’ll resume the Portal stress tests later today 🔹 Public stats - Public Portal stats is also reflecting again: - portal.cortensor.network/sta… 🔹 Current takeaway - testnet1a recovery looks successful - router endpoints are back - monitoring continues today - Portal stress testing should resume later today if things keep holding #Cortensor #DevLog #Testnet1a #Portal #Infra #L3

🛠️ DevLog – L2 / L3 RPC Upgrade Is Planned for Later Today A quick infra note. 🔹 Current update - The L2 / L3 RPC path will be upgraded later today - This is tied to a mandatory Arbitrum-side upgrade 🔹 Environments affected - Testnet0 - Testnet1a - Mainnet Lite 🔹 What this means - We expect these environments to be affected during the upgrade window - This is mainly part of keeping the RPC/base infra aligned with the required upstream changes 🔹 Current direction - We’ll work through the upgrade later today - then continue monitoring the affected environments after that #Cortensor #DevLog #RPC #Arbitrum #Infra

🛠️ DevLog – Testnet1a Recovery: L2 Batch + DA Rebuild Looks Good So Far A quick follow-up on the testnet1a recovery path. 🔹 Current progress - It now looks like the full blocks have been synced / rebuilt / reindexed successfully using the L2 batch path and the available DA dataset - That gives us a much better signal that the recovery path is holding up 🔹 What’s next - We’ll run more E2E checks later today through the Portal path - That should help confirm the broader product/API flow on top of the recovered chain state 🔹 Why this matters - This is useful not only for restoring testnet1a - It is also a good exercise for us on the infra / ops side around: - L3 recovery flow - edge cases - data recoverability - rebuild / reindex procedures under failure conditions 🔹 Current takeaway - testnet1a recovery looks much healthier now - Portal-side E2E checks come next - and the recovery process itself has been a useful infra / ops exercise for the longer-term L3 path #Cortensor #DevLog #Testnet1a #Infra #L3 #Portal

🛠️ DevLog – Testnet1a Recovery Is Still in Progress A quick update on the current testnet1a recovery path. 🔹 Current status - The sequencer is synced again - But there still appears to be some validation correction / cleanup happening on top of that - We have a few recovery steps lined up and will keep working through them today 🔹 What this means - The recovery is moving forward - But it is not yet at the point where we want to call it fully clean until those remaining checks are done 🔹 One lesson from this process - One clear takeaway from the testnet1a recovery process is that we should have additional sequencer backup coverage as well - Even though we had already planned to run multiple sequencers in production / mainnet, we were more relaxed on testnet because it is “just testnet” and the infra cost multiplies quickly 🔹 What changes from here - That backup / redundancy thinking is now more serious, even for environments where we previously accepted more risk for cost reasons - This is already under progress as part of the follow-up thinking from this incident 🔹 Current takeaway - testnet1a recovery is still ongoing - the sequencer is synced, but a few correction / validation checks remain - and this incident is reinforcing the need for stronger sequencer backup planning going forward #Cortensor #DevLog #Testnet1a #Infra #Sequencer

🛠️ DevLog – Portal Public Stats Prototype Is Now Live in Rough Form A quick follow-up on the public Portal stats direction. 🔹 Current progress - We’ve now pushed the rough shape / initial prototype live - It is reading from actual data rather than only static placeholders - Current ranges: - portal.cortensor.network/sta… - portal.cortensor.network/sta… 🔹 What this means - This is the first early public-facing stats surface for Portal - It gives a simpler public view into service status, request outcomes, latency, token throughput, request size, and recent status timeline 🔹 Performance follow-up - We also added a shared cache layer - That should help pages load faster - and reduce unnecessary load on query / summary / aggregation paths underneath 🔹 Current takeaway - Public Portal stats is no longer only an internal concept - the first rough prototype is now live - and we’ll keep refining it further from here #Cortensor #DevLog #Portal #Observability #Stats #AIInfra

🗓️ Weekly Recap – Phase #4 Portal Maturity & Mainnet Lite Baseline Complete This week Portal V1 continued to mature into a real hosted product, while Mainnet Lite closed out nearly all remaining baseline validation work. 🔹 Phase #4 – Monitoring, Support & Stats - Continued monitoring across routing, miners, validators, dashboards, indexers, and L3 stats. - Phase #4 remained stable while Portal V1 became the primary engineering focus. 🔹 Portal V1 – Product Refinement - Portal continued evolving with improvements across auth, API keys, request visibility, usage reporting, and overall UI/UX. - The hosted product flow now feels much closer to a practical MVP than an early prototype. 🔹 Portal V1 – Token Metering & Multi-Model Routing - Token-based usage metering moved into rough implementation across the Gateway, Portal, and admin surfaces. - Multi-model routing expanded into live testing across oss-20b, Gemma4, Qwen, and oss-120b. 🔹 Portal V1 – Gateway, Stress Tests & Operations - Portal stress tests expanded into heavier workloads and multi-hour runs. - API Gateway scaled to three instances while admin/ops metrics and token-level observability continued improving. 🔹 Mainnet Lite – Baseline Validation Complete - Dedicated-node user-task, ephemeral-node network-task, and ephemeral-node user-task → node-pool flows were all validated successfully. - With payment distribution revalidated, the Mainnet Lite baseline checklist is now largely complete. 🔹 Mainnet Lite – Infrastructure & Operations - Additional ephemeral nodes were added for cleaner validation, while internal RPC infrastructure remained stable. - A sequencer recovery exercise on Testnet-1a also highlighted the need for stronger backup/redundancy planning going forward. 🔹 Payment Staking – Regression & Hardening - Additional regression and hardening checks looked good on Testnet-1a. - Follow-up validation will continue, but no major issues have surfaced. 🔹 PyClaw – Dev Path Progress - Prepared the first public development version (early 0.0.1-style snapshot) for release. - Iteration continues toward a more usable framework during Q3 while remaining open for public feedback. A productive Phase #4 week overall - Portal V1 made another significant step toward a real hosted inference product, while Mainnet Lite baseline validation is no longer the primary blocker and attention is steadily shifting toward product refinement and operational maturity. #Cortensor #Testnet #Phase4 #AIInfra #DePIN #Portal #PyClaw #MainnetLite #L3

🧪 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: docs.cortensor.network/commu… #Cortensor #Testnet #Phase4 #DevUpdate #Portal #PyClaw #InferenceQuality #AIInfra #DePIN #L3

Monthly Node Rewards – May 2026 We've now sent out the May 2026 $COR node rewards to 24 nodes as part of our monthly node reward program. 🔹 Rewards sent to 24 nodes total 🔹 Includes dedicated nodes + ephemeral nodes 🔹 Recognizing uptime, stability, and contribution 💬 Join our Discord to set up a node or get involved: discord.gg/cortensor Thanks to all node operators pushing decentralized AI forward - it’s $COR or nothing. #Cortensor #AI #DePIN #NodeRewards #COR

🛠️ DevLog – Public-Facing Portal Stats Is Moving Into Early Prototype A quick follow-up on the public Portal stats direction we mentioned earlier. 🔹 What it is - We now have a rough prototype for a public-facing stats surface on Portal - The goal is to give people a simpler, higher-level view of how the hosted path is behaving without exposing all the deeper internal admin / ops detail 🔹 What it shows - aggregate service status - request outcomes and completion rate - latency trends - token throughput - average request size - a recent status timeline with more customer-visible service notes 🔹 Why this matters - Until now, most of the richer observability has lived inside internal admin / ops panels - This public stats surface is meant to turn part of that into something easier to follow from the outside 🔹 Current status - This is still an early prototype - But we expect to release this early prototype later today on both: - Prod Portal - Dev0 Portal 🔹 Current takeaway - public-facing Portal stats is now moving from internal concept into actual product surface - the first version will be simple and early - then we’ll expand it further from there over time #Cortensor #DevLog #Portal #Observability #Stats #AIInfra