🛠️ DevLog – Testnet-1a & Testnet-1b Status Quick #L3 self-managed check-in. 🔹 Testnet-1a – Load & Stability - 6 automated jobs are now running on Testnet-1a (self-managed $COR #L3). - So far, things look stable after the move to dedicated servers. - As this holds through the week, we’ll ask more node operators to migrate nodes over and gradually increase load. - Live stats: dashboard-testnet1a.cortenso… 🔹 Testnet-1b – Migration Ongoing - Testnet-1b (internal experimental #L3) is in the middle of its migration to the new dedicated setup. - This environment will stay our “breakable” lane for DA/Sequencer config experiments and ops playbook testing. For now, the main focus is soaking Testnet-1a under load and getting Testnet-1b fully settled on the new infra before we push harder. #Cortensor #TestnetPhase2 #L3 #DePIN #AIInfra

🛠️ DevLog – L3 Self-Managed: Temporary Fix → Path to Permanent Setup Quick follow-up on the self-managed COR L3 (Testnet-1a): 🔹 What We’ve Done - Moved the L3 stack off the throttled cloud instance onto a temporary dedicated server in the same data center zone. - All core L3 components (Sequencer, DA, RPC) are now running together on this temporary dedicated machine to eliminate cloud throttling as a factor. 🔹 What Happens Next (24–48h) - We’ll stress test this temporary dedicated setup over the next 24–48 hours with the same kind of network-task load as before. - If it stays stable under sustained traffic, we’ll treat it as confirmation that dedicated servers are the right baseline for self-managed COR L3. 🔹 Longer-Term Plan - Once validated, we’ll move L3 components onto permanent dedicated servers for the self-managed stack and formalize the recommended infra pattern (DA Sequencer RPC on dedicated / high-quality metal in the same DC). 🔹 Where To Watch - Testnet-1a Explorer: testnet1a-explorer.cortensor… - Testnet-1a Dashboard: dashboard-testnet1a.cortenso… #Cortensor #L3 #ArbitrumOrbit #SelfManaged #DePIN #AIInfra #DevLog

🛠️ DevLog – Self-Managed L3: Connectivity Findings & Next Steps Recent stress tests on Testnet-1a (self-managed $COR #L3) surfaced some very practical cross–data center connectivity limits in our setup. 🔹 What We’re Seeing - DA (Data Availability) & Sequencer are running in one data center - RPC is running in a different data center - Under sustained load, network hiccups between those DCs can: - Disrupt #L3 ↔ #L2 data sync - Occasionally force DA resyncs when connectivity between RPC and DA/Sequencer becomes unstable 🔹 What We’re Planning - Co-locate core L3 components - Move RPC into the same DC as DA and Sequencer - Keep the critical L3 path (Sequencer ↔ DA ↔ RPC) inside a single DC to reduce reliance on cross-DC links - Tighten recovery & redundancy - Run multiple DA nodes, with one configured for regular snapshots to speed up recovery - Apply similar snapshot/restore patterns to Sequencer storage for cleaner failover and resync Overall, Testnet-1a is still holding up well for network and user tasks - these are the kinds of operational details we expected to uncover once we pushed the self-managed L3 harder. The next few weeks will be about making this setup more predictable before we lean on it as the long-term $COR home. #Cortensor #L3 #SelfManaged #ArbitrumOrbit #DePIN #AIInfra #DevLog

Massive thanks to @_Nelly_London for sharing her abortion story with @CosmopolitanUK. The pain she describes is one of the reasons we want to make sure there are enough providers both pill and in clinic abortions 1/2 cosmopolitan.com/uk/reports/…