PSA: There are NO official tokens for Bardiel or Corgent. No #BARDIEL token No #CORGENT token Any token claiming to be “Bardiel” or “Corgent” is not launched or endorsed by us – treat it as a scam. Always verify via official @Cortensor channels before interacting with anything on-chain. #Cortensor #Bardiel #Corgent #ScamAlert #AgenticAI

Cortensor Dashboard is the visibility and operations layer for the network. It is where you inspect sessions, tasks, nodes, rewards, config, and runtime state - all in one place. That is why the Dashboard matters: it turns raw infrastructure into something observable, operable, and easier to trust. #Cortensor #Dashboard #AIInfra #DePIN

🛠️ DevLog – Early Heads-Up on L3 Mainnet Infra Assessment A quick heads-up on another area we may start looking at a bit earlier. 🔹 Current direction We may do some earlier assessment on the L3 mainnet (@Arbitrum Orbit) infra side, mainly around: - infra shape - RPC path - baseline setup - supporting services and readiness 🔹 What this means This is not an execution/update post yet. It is more about starting to assess what the L3 mainnet baseline would require so we have a clearer picture earlier. 🔹 Why this matters The goal is to surface: - infra assumptions - RPC requirements - setup gaps - operational needs before those become heavier work later. 🔹 Current takeaway So for now, this is just an early signal that some L3 mainnet infra assessment may start sooner, even though there is nothing actionable from it yet. #Cortensor #DevLog #L3 #Mainnet #Infra #RPC

🗓️ Weekly Recap – Phase #4 Portal Progress, Mainnet Lite Validation & Infra Hardening This week was again heavily focused on Portal V1, with meaningful progress across product flows, API Gateway behavior, observability, and hosted inference readiness. 🔹 Phase #4 – Monitoring, Support & Stats - Continued monitoring across routing, miners, validators, dashboards, indexers, and L3 stats. - Phase #4 remained stable while Portal and Mainnet Lite workstreams continued to mature. 🔹 Portal V1 – Product Flow Maturing - Portal moved from rough MVP toward a more usable hosted product surface with cleaner auth, API keys, usage visibility, request logs, and UI/UX refinement. - Data consistency between web app, database, and API-key systems improved significantly. 🔹 Portal V1 – API Gateway & Quota Work - Sliding-window quota logic received deeper testing and fixes, including weekly-limit accounting improvements. - Usage counting became more accurate with better separation between successful requests, quota events, and real failures. 🔹 Portal V1 – Request Visibility & Analytics - Request visibility improved with better logs, filters, totals, and detailed request views. - Added richer usage analytics including trends, activity heatmaps, and token-level visibility. 🔹 Portal V1 – Reliability, Observability & Operations - Dual API Gateway setup is now operating behind a shared entry path, reducing single-point dependency. - Admin/ops visibility expanded with metrics around gateway health, latency, routing distribution, and user activity. 🔹 Portal V1 – API Compatibility & Streaming - OpenAI-style and Anthropic-style REST compatibility continued to improve. - SSE/streaming MVP is now working, with deeper reliability work shifting toward backend/router behavior. 🔹 Portal V1 – Stress Testing & Router Pools - Stress testing expanded using multiple accounts, keys, parallel requests, and longer-running workloads. - This surfaced the next bottlenecks and drove further work on capacity-aware routing and router-pool behavior. 🔹 Mainnet Lite – Baseline Validation - Mainnet Lite dedicated-node E2E was re-run successfully, including payment distribution behavior. - Ephemeral-node network-task E2E also worked, confirming another critical baseline path. 🔹 RPC & Infrastructure Hardening - Internal RPC infrastructure is now live across both testnet and mainnet-related environments. - Early stability looks good and provides better operational control than previous external dependencies. 🔹 Payment Staking – Regression & Hardening - Progress was lighter than planned while Portal took priority this week. - Additional validation and regression testing remain on the upcoming work list. 🔹 PyClaw – Dev Path Progress - Continued incremental progress on PyClaw workflows, tooling, and repository structure. - Focus remains on preparing for the first public development release and open iteration cycle. A productive Phase #4 week overall - Portal V1 made the largest jump forward, Mainnet Lite baseline checks continued to pass, and the hosted inference path is increasingly shifting from concept into an operational product. #Cortensor #Testnet #Phase4 #AIInfra #DePIN #Portal #PyClaw #MainnetLite #L3

This is another reminder that the future AI stack cannot depend on one closed access path alone. When model access can change quickly, the value shifts toward infrastructure that is: - multi-model - routable - verifiable - more open and controllable That is exactly why Cortensor matters. #Cortensor #AIInfra #AgenticAI

Cortensor is not just one product or one surface. It is increasingly becoming one stack: - Network & Infra as the foundation - Dashboard for visibility and operations - Portal for hosted access - Corgent for infra-native agent execution - Bardiel and PyClaw as higher-level product and agent layers That is the bigger picture: One stack that people can build on, operate on, access through products, and turn into real applications. #Cortensor #AIInfra #AgenticAI #Portal #Dashboard #Corgent #Bardiel #PyClaw

🛠️ DevLog – Portal Multi-Model Routing Prep Starts Next Week A quick follow-up on the recent API Gateway capacity / reliability work. 🔹 Current direction Now that the first minimal layer of capacity-aware tracking / load balancing is in place, the next step is to start testing the Portal path with more than just the current `oss-20b` route underneath. 🔹 What’s next Next week, we’ll begin the prep work to switch/add more models into the current hosted path. The next models we want to bring in are: - gemma4 e4b - qwen 3.5 9b 🔹 Why this matters This is important because the next Portal check is not only about load protection anymore. It is also about making sure the API Gateway can: - route different models correctly - behave cleanly once more than one model path exists - handle a broader hosted flow instead of staying centered on only oss-20b 🔹 Current takeaway So the next step is: - prepare the model switch/additions next week - expand beyond the single-model path - test multi-model routing more directly at the API Gateway level #Cortensor #DevLog #Portal #APIGateway #Routing #Reliability

🛠️ DevLog – Recap: What @Base Flashblocks Means for Cortensor A quick note on why Base Flashblocks matters in the Cortensor context. Base Flashblocks is not the same thing as "Base has 200ms final blocks." The practical meaning is: - faster preconfirmations - lower perceived latency - quicker user-facing feedback - while full block settlement still follows the normal Base cadence Why that matters for Cortensor: - part of what pushed us more toward @Arbitrum earlier was responsiveness and execution behavior - Flashblocks makes the Base path more relevant now because it narrows part of that gap - that means Base becomes more interesting again for lighter Cortensor product and execution paths So the current thinking is still: - Arbitrum first for the main L2 / L3 Cortensor path - revisit Base more seriously after Mainnet Full is deployed and usable In simple terms: Flashblocks does not change the current stack direction today. But it does make Base much more worth revisiting later. #Cortensor #Base #Flashblocks #Arbitrum #AIInfra

🛠️ DevLog – Gateway Capacity Follow-Up: Next Focus Is Multi-Model Routing A quick follow-up on the recent API Gateway capacity / reliability work. 🔹 Current progress We’ve now added the first minimal layer of capacity-aware tracking / load balancing on the API Gateway side so the hosted path behaves a bit more safely under shared load. 🔹 What comes next From here, we’ll shift gears a bit and start reconfiguring the existing sessions so they can support more than just the current oss-20b path. The goal is to test: - model routing at the API Gateway level - how the gateway behaves when multiple model paths exist underneath - whether the current hosted flow still routes cleanly once the model mix becomes broader 🔹 Why this matters So the next step is not only “protect the gateway under load,” but also make sure the gateway can route correctly once the backend is no longer centered around just one model/session path. 🔹 Current takeaway The first capacity/reliability layer is in place. Next, we use that foundation to test the multi-model routing side more directly. #Cortensor #DevLog #Portal #APIGateway #Routing #Reliability

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 – Gateway Session Load Protection Is Now Live A follow-up on the capacity-aware gateway work from the last devlog. 🔹 Current progress We added session-capacity aware load protection to the API Gateway. The gateway can now track shared Cortensor session occupancy across multiple gateway instances using Redis, while keeping the routing flow simple and predictable. 🔹 What changed Core gateway updates: - Redis-backed shared session tracking - round-robin routing preserved, but full sessions are skipped - per-session in-flight limits - automatic capacity release after requests finish - short bounded-wait window during bursts Ops/admin updates: - capacity mode, Redis status, tracked sessions, limits, lease TTL, and wait timeout are now exposed - admin surfaces can show plain mode vs Redis-backed tracking mode - wait timeout can be tuned through env vars 🔹 Why this matters This helps the hosted API path behave more safely during traffic spikes. Multiple gateway instances can now coordinate against the same shared router pool instead of blindly sending more traffic to sessions that are already busy. This gives us: - smoother burst handling - better shared-session protection - clearer capacity visibility - safer multi-instance gateway behavior 🔹 Important note Plain/default mode still works as before. The new coordination behavior only activates when Redis-backed session tracking is enabled. This is not a full queue system yet, but the bounded-wait window gives requests a short chance to find open capacity before failing. #Cortensor #AIInfrastructure #DevLog #Inference #Gateway #DecentralizedAI

🛠️ DevLog – Gateway Capacity Tracking Is Now in Testing A quick update on the capacity-aware gateway work from the last devlog. 🔹 Current progress The first version is now implemented and being tested across the hosted API path. The gateway can now coordinate shared router-session usage through Redis, so multiple gateway instances have better awareness of which sessions are already busy before routing more traffic. 🔹 What changed Core gateway updates: - Redis-backed session capacity tracking - per-session concurrency limits - existing routing flow preserved - capacity/runtime status exposed through management endpoints Ops UI updates: - admin view for capacity mode, tracked sessions, lease TTL, and Redis state - dedicated Sessions view for live Cortensor session usage - visibility into live occupancy, recent traffic, labels, latency, token usage, and gateway hit distribution 🔹 Why this matters This helps the hosted API path handle bursts more safely. With multiple gateway replicas, traffic can now be coordinated against the same shared session pool instead of blindly overloading the same router session. This gives us: - better load protection - clearer real-time session visibility - easier debugging during stress tests - more predictable hosted inference traffic distribution 🔹 What comes next This is not full queue-based admission control yet. Next, we’ll also be looking into the queue layer so overload behavior is safer when sessions are busy or all sessions are at capacity. The goal is: - stronger backpressure - clearer overload handling - more predictable burst behavior #Cortensor #AIInfrastructure #DevLog #Inference #Gateway #DecentralizedAI

🛠️ DevLog – Stress Tests Are Surfacing the Next API Gateway Improvement A quick follow-up on the current Portal / API Gateway stress tests. 🔹 What we’re seeing As we push the hosted path harder, one of the clearer gaps showing up is around how the API Gateway should handle load when multiple requests arrive faster than shared router sessions can process them. When that happens: - some router sessions can get overloaded - response times become less predictable - failures increase more easily under bursts 🔹 What we plan to add The next improvement we’re planning is capacity-aware routing inside the API Gateway. The idea is simple: - keep the current round-robin routing shape - but make it aware of whether a router session is already busy - skip sessions that are already at capacity - move to the next available one instead of sending too much work to the same node 🔹 Why this matters This should help with: - smoother request handling - better stability during spikes - more predictable performance - safer behavior when multiple gateway instances share the same router pool 🔹 Current status This is the direction we’re moving toward based on what the stress tests are surfacing, but it is not implemented yet. #Cortensor #DevLog #Portal #APIGateway #StressTest #Reliability

🛠️ DevLog – Small Ops UI/UX Refinements While Stress Tests Continue A quick follow-up on the Portal admin / ops side. 🔹 Ops UI/UX refinement We’ve been adding a number of smaller refinements to the ops/admin surface while doing the current stress tests: - more small graphics / visual cues - clearer metric blocks - cleaner request / fleet / event views - better readability for operational monitoring So this is mostly a polish pass, but it helps the admin/ops side feel more usable as the Portal path gets more real. 🔹 Stress-test constraint One thing we also realized during testing is that the current testnet1a router pool only has 8 nodes behind it. That means even something like 3 parallel tests can already start to overwhelm the pool. 🔹 What this means So from here, we’ll decide whether: - we can keep pushing with more stress tests on the current pool or - it makes more sense to pause/postpone until the pool is better populated 🔹 Current takeaway So this is both: - a small admin/ops UI refinement pass - and a useful signal that the current router-pool size is still a limiting factor for heavier stress testing #Cortensor #DevLog #Portal #Observability #StressTest #UIUX

🔎 Recap: Mainnet Lite Is Coming in Q3 2026 A quick recap on what Mainnet Lite is and why it matters. 🔹 What Mainnet Lite is Mainnet Lite is the more practical and controlled #L2 rollout path for Cortensor. It is taking shape around: - @Arbitrum L2 - more dedicated-node-heavy serving in the earlier stage - a simpler and more productized rollout shape - the earlier hosted / demonstration-style path before broader expansion 🔹 Why it matters Mainnet Lite is important because it is the more controlled first step for bringing the Cortensor stack onto real mainnet conditions. It gives us a path to validate: - execution - routing - sessions - dashboard / infra visibility - product-facing surfaces on top without treating the fuller long-term path as the first rollout step. 🔹 How to think about it The simple framing is: - Mainnet Lite = L2-first, simpler rollout, more dedicated-node-heavy path - Mainnet Full = fuller L3-native Cortensor path later 🔹 Timing The current direction is that Mainnet Lite is coming in Q3 2026. #Cortensor #MainnetLite #Mainnet #Arbitrum

This is directionally why we think execution infrastructure matters. As AI access becomes more metered and less subsidized, the winning stack is not just "best model." It is: - which model runs where - at what cost - with what trust level - on what execution layer That is exactly the kind of future Cortensor is built for.

🛠️ DevLog – Portal Usage Heatmap Got a Small UI/UX Refinement Pass A quick Portal UI/UX follow-up. 🔹 What improved We refined the usage heatmap experience a bit more so the section reads more cleanly and feels more intentional. That includes: - filling future heatmap cells farther out so the calendar grid looks more complete - adding a small reading guide for: - date coverage - successful requests only - dashed cells = future days - adding matching light/dark mode styling for those guide chips 🔹 Why this matters This is a small refinement, but it makes the usage-trend area easier to read at a glance and helps the heatmap feel less ambiguous. #Cortensor #DevLog #Portal #UIUX #ProductDesign

🛠️ DevLog – Dashboard → Explorer Verification Links Are Now Live on Testnet0 and Testnet1a A quick follow-up on the earlier dashboard verification update. 🔹 Current progress We’ve now pushed this feature into both: - testnet0 - testnet1a 🔹 What changed Task/session views can now link more directly into the explorer, so actions and state changes are easier to verify without doing manual lookup first. Example flow: - Dashboard task view → dashboard-testnet1a.cortenso… - Explorer tx view → testnet1a-explorer.cortensor… 🔹 Why this matters This makes it much easier to: - inspect what happened from the dashboard - jump straight into the underlying transaction/state change - verify task/session activity with less friction 🔹 Current takeaway So this is a useful refinement for both dashboard usability and verification flow: - less manual explorer searching - more direct traceability from dashboard views - cleaner inspection of task/session state changes #Cortensor #DevLog #Dashboard #Verification #Explorer

🛠️ DevLog – Dashboard Verification Links Are Coming A quick follow-up on the Dashboard side. We’ll likely release a small dashboard update later today focused on verification and traceability. 🔹 What’s changing The main improvement is that each: - action - session - state change will start linking more directly to the explorer, so people can verify the underlying tx / state transition more easily. 🔹 Why this matters Right now, some of this still requires manual lookup through the explorer. With these links added directly into the dashboard, it should become easier to: - verify what happened - inspect state transitions - trace actions more quickly - connect dashboard views to onchain/explorer data with less friction 🔹 Current direction So this is mainly a dashboard verification refinement pass: - less manual explorer lookup - more direct verification from the dashboard - cleaner traceability for sessions and state changes #Cortensor #DevLog #Dashboard #Verification #Explorer

🛠️ DevLog – Portal Stress Tests Are Now Starting A quick follow-up on the Portal V1 stress-testing path. 🔹 Current progress We’ve now started running the first round of: - parallel API calls - repeated request patterns - broader hosted-path checks through the Portal API Gateway flow 🔹 What this means This is the next step beyond simple single-request validation. The goal is to see how the hosted path behaves under: - more realistic usage - concurrent requests - multi-account / multi-key activity - longer-running API calls 🔹 What’s next We’ll keep running more of these tests today and use them to surface: - weaker points in the hosted path - routing / pool behavior under load - request/accounting consistency - areas that still need hardening before broader usage 🔹 Current direction So this stress-test phase is now in motion, and it should give us a clearer signal on how the Portal path behaves under more realistic usage patterns. #Cortensor #DevLog #Portal #Gateway #API #StressTest

This is directionally why Cortensor matters. If more of the market is moving toward cheaper models, then the real challenge is no longer just model quality by itself. It becomes: - routing workloads to the right cost/quality tier - using lower-cost capacity where it is good enough - reserving premium capacity where it actually matters - making that whole path observable, verifiable, and programmable That is exactly the layer Cortensor is building.