Cortensor

The Cortensor mainnet path is taking a clearer shape. Q3 2026 → Mainnet Lite - @Arbitrum L2 - more controlled and practical first step - earlier dedicated-node-heavy rollout - cleaner path for hosted and product-facing checks first Q4 2026 → Mainnet Full - @Arbitrum Orbit L3 - fuller Cortensor-native path - broader long-term network direction - more complete stack beyond the lighter L2 rollout That is how we currently think about the rollout: Lite first as the more practical path, then Full as the broader native path after that. #Cortensor #MainnetLite #Mainnet #Arbitrum

🗓️ Weekly Focus – Corgent/Bardiel Endpoint Migration & Mainnet Full Cutover This week is mainly focused on polishing the Corgent and Bardiel endpoint configurations, completing the remaining data migration, and preparing both services to fully move from Testnet-1a onto Mainnet Full. 🔹 Bardiel – Endpoint Configuration & Testing ‐ Recent session reconfiguration, node replacements, and timeout tuning are now working more reliably. ‐ Continue light testing across delegate, validate, completion, fact-check, and redundancy 1/3/5 paths using the current Mainnet Full node assignments. 🔹 Bardiel – Dataset Generation & Migration ‐ Finish generating the remaining Bardiel data and migrate it from the Testnet-1a endpoint to Mainnet Full Router 1. ‐ Target is to complete the Bardiel endpoint cutover this week once the migrated dataset and dashboard flow are validated. 🔹 Corgent – Mainnet Full Configuration ‐ Apply the same stable session, timeout, and node configuration to Mainnet Full Router 0 for Corgent. ‐ Run regression across the configured agent-facing surfaces before treating the endpoint as the new primary path. 🔹 ERC-8004 Registry – Endpoint Update ‐ After Corgent and Bardiel validation is complete, update their ERC-8004 registry entries to use the Mainnet Full router endpoints. ‐ Re-check MCP/A2A tool discovery, static advertisement, health status, and endpoint behavior after the update. 🔹 Portal – Production Dataset Cleanup ‐ Consider resetting the Portal production dataset to remove accumulated test traffic that is no longer needed. ‐ Preserve only the data required for continued product testing and operational visibility. 🔹 Node Ops & Capacity ‐ Continue replacing unhealthy nodes and expanding dedicated capacity across the Corgent, Bardiel, and Portal session groups. ‐ Clean node coverage remains the main requirement for broader consensus and product-path testing. 🔹 Testnet-1a – Decommissioning Progress ‐ Continue the Testnet-1a decommissioning process as Bardiel and Corgent move fully into Mainnet Full. ‐ Remove the large legacy chain-state dataset once the remaining migrations and endpoint checks are complete. This week is about completing the Corgent/Bardiel Mainnet Full transition, updating the agent-facing registry paths, and retiring the remaining Testnet-1a dependencies. #Cortensor #MainnetFull #Corgent #Bardiel #ERC8004 #MCP #A2A #Portal #AIInfra #DePIN #Arbitrum #L3

🔎 Recap: What Comes After Cheap Inference? A quick recap on what becomes more important as inference gets cheaper and more widely available. 🔹 The simple framing Inference is becoming easier to access. More providers can serve capable open models. Token prices continue to fall. Basic model access becomes less differentiated. But cheaper inference does not mean lower total demand. It can create much more usage. 🔹 The Jevons paradox When a resource becomes cheaper and more efficient, people often use more of it. For AI, lower inference costs can make it practical to: - run agents continuously - use several models in one workflow - generate multiple candidate outputs - retry failed tasks - validate results before acting - maintain longer-running memory - apply AI to smaller and more frequent decisions The cost per request falls. The number of requests, steps, and workflows can rise much faster. 🔹 Where the bottleneck moves As raw inference becomes abundant, the harder problems shift upward: - trust - routing - user experience - memory - reliability - verification - coordination Generating an answer becomes cheaper. Knowing whether that answer is correct, useful, remembered, and safe to act on becomes more valuable. 🔹 Why builders may reinvest the savings Lower inference costs give products more room to add: - independent validation - retries and fallback paths - long-term memory - multi-model workflows - stronger observability - better user experience - post-execution verification Instead of using savings only to reduce price, stronger products can reinvest them into confidence and reliability. That is where more durable value can compound. 🔹 Why routing becomes more important A larger inference market creates more choices: - different models - different providers - different hardware - different latency and cost profiles - different reliability levels The question becomes less about whether compute is available. It becomes which execution path is best for this task under current conditions. 🔹 Why verification becomes more important Cheap generation makes it affordable to produce more outputs. But more outputs do not automatically create more confidence. Agents still need to determine: - whether instructions were followed - whether claims are supported - whether constraints were respected - whether another validator agrees - whether the result is safe to turn into action As inference commoditizes, trust becomes part of the product. 🔹 How this fits the Cortensor direction - Portal provides hosted access and multi-model routing - PyClaw can create local, persistent, and operational agent workflows - Corgent adds delegation, validation, and fact-checking paths - Bardiel packages trust and execution flows for agent ecosystems - the Cortensor Network coordinates models, nodes, routing, and verification underneath The goal is not only cheaper access to models. It is making that access more useful, reliable, and actionable. 🔹 Current takeaway Inference is getting cheaper. Demand may still grow because cheaper intelligence enables more agents, more steps, more retries, more memory, and more validation. As the cost of generation moves lower, durable value shifts toward: - trust - UX - memory - routing - reliability - verification Cheap inference expands the market. The layers above inference determine who captures the value. #Cortensor #JevonsParadox #Inference #AgenticAI #Portal #Corgent #Bardiel

🛠️ DevLog – Timeout Tuning Will Expand Across Other Router Paths A quick follow-up on the recent Mainnet Full endpoint testing. 🔹 Current result - The increased timeout has worked well so far across the heavier Bardiel endpoint paths - Delegate, validate, and consensus requests are completing more consistently with the nodes currently available - This suggests some earlier failures were related to execution time rather than the overall endpoint configuration 🔹 Next focus - We will review the other router configurations and apply similar timeout adjustments where appropriate - Each path will be tested separately rather than using the same setting everywhere by default - The goal is to improve reliability while still identifying genuinely unhealthy nodes or sessions 🔹 What comes next - Update selected timeout settings across the remaining router paths - Repeat baseline tests across heavier endpoints - Compare completion rates, latency, consensus behavior, and failures - Continue refining the configuration based on real node performance 🔹 Current takeaway - Timeout tuning has improved the heavier Bardiel paths so far - We will now test similar adjustments across the other router configurations - Further changes will be based on how each endpoint behaves under the current Mainnet Full node footprint #Cortensor #DevLog #MainnetFull #Router #Bardiel #Corgent #NodeOps

🛠️ DevLog – Bardiel Data Migration Continues With Updated Timeout Settings A quick follow-up on the Mainnet Full Bardiel endpoint testing and migration path. 🔹 Current progress - Increasing the timeout appears to be helping with the nodes currently available - Recent Router 1 / Bardiel tasks have completed more consistently under the updated setting - This gives us a better baseline for continuing the migration checks 🔹 Current focus - Run additional tests with the increased timeout - Continue monitoring delegate execution, consensus completion, and result return - Confirm that the longer timeout improves reliability without hiding unhealthy node behavior 🔹 Bardiel migration - We have resumed moving Bardiel data from the Testnet1a path into the Mainnet Full endpoint - The migration is starting with smaller batches so we can verify the data and dashboard behavior - So far, the latest migration tests are working as expected 🔹 What comes next - Continue migrating a limited set of Bardiel data - Validate the results across the endpoint and dashboard - Expand the migration gradually if the updated timeout and node paths remain healthy - Continue adjusting individual nodes or sessions where needed 🔹 Current takeaway - The updated timeout appears better suited to the current node footprint - Bardiel data migration has resumed and is progressing in smaller validated batches - Broader migration will continue if the current Mainnet Full path remains stable dashboard.cortensor.network/session/144/18 dashboard.cortensor.network/session/144/19 dashboard.cortensor.network/session/144/20 dashboard.cortensor.network/session/144/21 dashboard.cortensor.network/session/144/22 #Cortensor #DevLog #MainnetFull #Bardiel #Testnet1a #Router #NodeOps

🛠️ DevLog – PyClaw Versioning and the Path Toward a More Usable Release A quick note on where PyClaw stands after its first month in public development. 🔹 Current status - The PyClaw repositories are now roughly one month old from their initial public commits - The current design and implementation have been developed independently rather than cloned from another agent framework - At this stage, the project is still early and should be viewed as an active iteration path rather than a finished product 🔹 Expected timeline - Mature agent frameworks often take several quarters of iteration before they become consistently useful in daily workflows - Based on that, we expect PyClaw to need roughly two more quarters of steady development and testing - The priority is not rushing the version number, but improving the agent loop, coding workflows, memory, tools, reliability, and overall usability over time 🔹 Versioning direction - The current goal is to ship a release each week - Each weekly release will move the version forward by roughly 0.0.1 - If development continues at that pace, the project may reach around v0.0.30 before it is ready to be considered for a broader v0.1 milestone 🔹 Model direction - We are also hoping stronger open models in the roughly 30B range become available during this development window - Future Gemma releases and other capable open models could improve the local and hosted PyClaw experience - Portal can provide access to those models as they become practical to support 🔹 Current takeaway - PyClaw is still near the beginning of its public development path - Weekly releases will document steady progress rather than imply immediate readiness - The working expectation is that sustained iteration across the next two quarters can move the project toward a genuinely usable v0.1 release #Cortensor #DevLog #PyClaw #AgenticAI #LocalAI #OpenSource #AIInfra

🛠️ DevLog – Timeout Tuning for Corgent and Bardiel Endpoint Tests A quick follow-up on the current Mainnet Full endpoint checks. 🔹 Current focus - We will adjust several timeout settings across the Corgent and Bardiel endpoint paths - The goal is to better match the response time of the nodes currently available - This should help distinguish slow execution from actual endpoint or node failures 🔹 What we will review - node reservation and response timing - delegate and validate execution - redundancy 1, 3, and 5 paths - consensus completion and result return - timeout-related failures across Router 0 and Router 1 🔹 Current scope - Router 0 remains assigned to the Corgent endpoint - Router 1 remains assigned to the Bardiel endpoint - The adjustments are part of baseline tuning around the current node footprint 🔹 Current takeaway - Some endpoint failures may be related to timing rather than the overall routing path - We will test the updated timeout settings and compare the results - Further tuning will depend on how the available nodes behave under the revised configuration #Cortensor #DevLog #MainnetFull #Corgent #Bardiel #Router #NodeOps

🗓️ Weekly Recap – Portal Capacity, Mainnet Full Sessions & Bardiel Migration This week focused heavily on Portal and Mainnet Full product readiness. More dedicated-node capacity came online, allowing Portal, Corgent, and Bardiel testing to expand across updated sessions and router paths. 🔹 Portal – Dedicated Capacity & Model Coverage ‐ Added new dedicated-node sessions with broader model coverage and increased baseline traffic across the updated configuration. ‐ Qwen joined the active model mix, with routing, latency, requests, and token usage appearing correctly across monitoring surfaces. 🔹 Portal – Gateway Expansion & Stability ‐ Expanded the Portal API Gateway pool from 8 to 10 instances for stronger entry-layer distribution and redundancy. ‐ Continuous light testing remained reasonably stable, with larger tests still dependent on additional node and backend capacity. 🔹 Portal – Backend Capacity ‐ The current Supabase tier began approaching its limits under the growing Portal workload. ‐ A temporary upgrade is needed before broader parallel and stress testing can continue cleanly. 🔹 Corgent & Bardiel – Session Reconfiguration ‐ Reconfigured delegate and validate sessions across redundancy 1, 3, and 5 using replacement dedicated nodes. ‐ Initial checks looked healthy across Router 0 for Corgent and Router 1 for Bardiel. 🔹 Bardiel – Delegate & Validate Testing ‐ Basic delegate and validate consensus tests worked across available 3-node and 5-node paths. ‐ Remaining failures were mainly tied to offline or not-yet-migrated nodes rather than the endpoint logic itself. 🔹 Bardiel – Mainnet Full Migration ‐ Bardiel’s Mainnet Full Router 1 path is now stable enough to begin transitioning away from Testnet-1a. ‐ A small batch of data was migrated for endpoint/dashboard validation, while the broader transfer paused to replace a few unhealthy nodes. 🔹 Node Ops & Capacity ‐ More dedicated nodes became available, allowing product sessions and router assignments to expand. ‐ Portal automated testing was temporarily reduced while Bardiel validation and node cleanup took priority. 🔹 Testnet-1a – Decommissioning Progress ‐ Testnet-1a is moving closer to decommissioning as Mainnet Full takes over more active product testing. ‐ Its nearly 600 GB chain-state dataset will be removed after the remaining Bardiel migration and node cleanup are complete. A productive week overall - Portal capacity and redundancy improved, Corgent/Bardiel session paths became more stable, and the transition from Testnet-1a toward Mainnet Full moved another step forward. #Cortensor #MainnetFull #Portal #Corgent #Bardiel #AIInfra #DePIN #AgenticAI #Arbitrum #L3

🛠️ DevLog – Bardiel Mainnet Full Migration Pauses for Node Cleanup A quick follow-up on the Bardiel endpoint and data migration path. 🔹 What we identified - A few unhealthy nodes were identified during the latest Mainnet Full checks - Those nodes were affecting the consistency of the configured Bardiel sessions - We have paused the broader data migration while the node issues are corrected 🔹 Current status - The initial Router 1 / Bardiel baseline remains in place - The migration path from Testnet1a to Mainnet Full has already been tested with a small data set - Further migration will resume once the affected nodes are fixed or replaced 🔹 What comes next - Correct the unhealthy node assignments - Recheck the validate and delegate session paths - Resume the Bardiel data migration with a small batch - Continue with the remaining data after the endpoint and dashboard visibility look healthy 🔹 Current takeaway - A few node-side issues were identified before the broader migration continued - We will resolve those first, then resume the Bardiel transition from Testnet1a to Mainnet Full #Cortensor #DevLog #MainnetFull #Bardiel #Testnet1a #Router #NodeOps

🛠️ DevLog – Bardiel Mainnet Full Data Migration Begins A quick follow-up on the Bardiel endpoint transition from Testnet1a to Mainnet Full. 🔹 Current status - Baseline tests across the Router 1 / Bardiel sessions looked healthy yesterday - The validate and delegate paths are working well enough to begin the next migration step 🔹 Current progress - We have started copying a small portion of the existing Bardiel data from the Testnet1a endpoint into the Mainnet Full Bardiel path - Router 1 is being used as the Mainnet Full Bardiel endpoint - The first step is to confirm that the migrated data appears correctly across the endpoint and Bardiel dashboard 🔹 What comes next - Validate the initial data set on Mainnet Full - Confirm endpoint behavior, data visibility, and dashboard compatibility - If the first batch looks healthy, migrate the remaining Bardiel data - Repeat endpoint and data checks after the broader migration 🔹 Current takeaway - The Bardiel migration from Testnet1a to Mainnet Full has now started with a small data set - If the initial results look healthy, the remaining data will follow - This path is intended to eventually replace the current Testnet1a-backed Bardiel endpoint #Cortensor #DevLog #MainnetFull #Bardiel #Testnet1a #Router #NodeOps

🔎 Recap: Why Validation Should Happen Before Action A quick recap on why validation becomes more important as agents move from generating answers to taking real actions. 🔹 The simple framing An incorrect answer is one problem. An incorrect action can be much more costly. Before an agent: - sends a payment - deploys infrastructure - changes a production system - approves a transaction - calls another agent - or completes an irreversible step it should have a way to check whether the result is safe to act on. 🔹 Why checking afterward is not enough Post-action review can help explain what went wrong. But in many workflows, the damage may already be done. A payment may already be sent. A deployment may already be live. A system change may already affect users. For high-impact tasks, validation is more useful before execution than after failure. 🔹 What pre-action validation can check Before acting, an agent can verify: - whether the result matches the original task - whether required constraints were followed - whether key claims are supported - whether the output is internally consistent - whether another model or validator agrees - whether confidence is high enough - whether human approval is still required The goal is not to slow every workflow down. It is to apply the right level of validation based on risk. 🔹 Not every action needs the same path A low-risk task may need only a basic check. A higher-risk task may require: - independent validation - multiple opinions - redundancy - fact-checking - policy checks - approval gates - evidence before execution The cost of validation should match the cost of failure. 🔹 Why this matters for agents Agents are increasingly expected to connect reasoning with execution. That means the trust layer cannot sit outside the workflow. Validation needs to become part of the action path itself: - generate - validate - approve - execute - verify the outcome 🔹 How this fits the Cortensor stack - Portal provides hosted model access - router nodes select the appropriate execution path - Corgent exposes delegation, validation, and fact-checking primitives - Bardiel can package validation and future arbitration into agent-facing workflows - the Cortensor Network coordinates execution and verification underneath Together, those layers help separate “the model produced an answer” from “the system should act on it.” 🔹 Current takeaway The closer an agent gets to real-world action, the less safe it is to treat every output as automatically trustworthy. Validation before action creates a checkpoint between intelligence and execution. That checkpoint can be the difference between an answer being useful and an action being safe. #Cortensor #Validation #AgenticAI #Corgent #Bardiel #AIInfra

🛠️ DevLog – Bardiel Mainnet Full Cutover Moves Into Further Testing A quick follow-up on the Mainnet Full Corgent and Bardiel endpoint paths. 🔹 Current status - The latest node replacements and session assignments are now aligned across Router 0 and Router 1 - Router 0 remains configured for the Corgent endpoint - Router 1 remains configured for the Bardiel endpoint - The validate and delegate redundancy paths currently look ready for further baseline testing 🔹 Current focus - Run additional light tests across the Corgent and Bardiel endpoints - Recheck redundancy 1, 3, and 5 behavior across validate and delegate - Monitor node reservation, consensus, execution, result return, latency, and failures 🔹 Bardiel cutover direction - If the Mainnet Full Bardiel path continues to behave as expected, we will attempt to transition Bardiel away from the current Testnet1a endpoint sometime next week - We will also generate and validate the Mainnet Full activity data needed by the Bardiel dashboard - The cutover will only proceed after the endpoint, sessions, nodes, and data visibility are checked again 🔹 Current takeaway - The Corgent and Bardiel endpoint configurations are now aligned for another round of testing - The immediate goal is confirming the Bardiel path is stable enough for the planned Testnet1a → Mainnet Full transition - If the remaining checks look healthy, we will begin the cutover process next week #Cortensor #DevLog #MainnetFull #Corgent #Bardiel #Testnet1a #NodeOps

🛠️ DevLog – Corgent and Bardiel Redundancy Endpoints Look Healthy After Node Replacement A quick follow-up on the Mainnet Full Router 0 and Router 1 endpoint configuration. 🔹 Current progress - Replacement nodes have now been assigned across the configured validate and delegate sessions - The redundancy 1, 3, and 5 paths for both Router 0 and Router 1 look healthy at the current baseline - Initial endpoint and session checks are completing as expected 🔹 Router 0 / Corgent - Validate R1: Session 127 - Validate R3: Session 128 - Validate R5: Session 129 - Delegate R1: Session 130 - Delegate R3: Session 131 - Delegate R5: Session 132 🔹 Router 1 / Bardiel - Validate R1: Session 139 - Validate R3: Session 140 - Validate R5: Session 141 - Delegate R1: Session 142 - Delegate R3: Session 143 - Delegate R5: Session 144 🔹 What comes next - Run light endpoint tests across both router paths this weekend - Check node reservation, consensus behavior, execution, result return, latency, and failures - Continue adjusting individual node assignments if any unstable paths appear 🔹 Current takeaway - The latest node replacements have improved the Corgent and Bardiel endpoint baseline - All configured validate and delegate redundancy paths currently look healthy - Light testing will continue this weekend before broader use dashboard.cortensor.network/session/127 dashboard.cortensor.network/session/128 dashboard.cortensor.network/session/129 dashboard.cortensor.network/session/130 dashboard.cortensor.network/session/131 dashboard.cortensor.network/session/132 dashboard.cortensor.network/session/139 dashboard.cortensor.network/session/140 dashboard.cortensor.network/session/141 dashboard.cortensor.network/session/142 dashboard.cortensor.network/session/143 dashboard.cortensor.network/session/144 #Cortensor #DevLog #MainnetFull #Corgent #Bardiel #Consensus #NodeOps

🛠️ DevLog – Current Status of Portal and Bardiel Endpoint Testing A quick follow-up on the current Mainnet Full product paths. 🔹 Portal status - Portal looks healthy at the current baseline - Basic E2E tests are working, but node availability is not yet fully consistent - Over time, the main requirement will be additional node capacity across the active model and session paths 🔹 Bardiel endpoint checks - We ran basic delegate and validate requests through the Bardiel endpoint - Testing included consensus paths using 3-node and 5-node redundancy - Several available node combinations completed successfully 🔹 Current limitation - Some nodes are still offline or have not completed migration into Mainnet Full - Those missing nodes can cause reservation or consensus failures across certain sessions - We will continue checking the current configuration to separate node-availability issues from endpoint or session issues 🔹 What comes next - Continue light checks across Portal with the capacity currently available - Repeat Bardiel delegate and validate tests across the 3-node and 5-node consensus paths - Adjust node and session assignments as the remaining nodes come online 🔹 Current takeaway - Portal appears healthy at a basic E2E level, with more node capacity needed for broader and more consistent coverage - Bardiel’s delegate and validate consensus paths are working across available nodes - The remaining instability is mainly tied to offline or not-yet-migrated nodes #Cortensor #DevLog #MainnetFull #Portal #Bardiel #Consensus #NodeOps

🛠️ DevLog – Portal Testing Pauses While Bardiel Endpoint Validation Takes Priority A quick follow-up on the current Mainnet Full testing focus. 🔹 Current plan - We will temporarily pause continuous Portal testing while we validate the Bardiel endpoint - Running both test paths at the same time could place unnecessary load on the current network capacity - Portal itself will remain available, but automated and higher-volume testing will be reduced for now 🔹 Bardiel focus - Router 1 is configured as the Mainnet Full Bardiel endpoint - We will retest its node assignments, sessions, routing, execution, and result-return paths with the expanded node set - The immediate goal is to confirm that the endpoint is healthy enough for the planned migration from Testnet1a 🔹 What comes next - Validate the Bardiel endpoint under the current Mainnet Full configuration - Generate and review the Bardiel dataset once the path looks healthy - Prepare the Bardiel dashboard and endpoint transition away from Testnet1a - Resume broader Portal testing after the Bardiel checks reach a stable baseline 🔹 Current takeaway - Bardiel endpoint validation is the immediate priority - Portal testing is being paused temporarily to avoid overloading the current network footprint - Once Bardiel reaches a healthy baseline, we can continue the migration path and return to broader Portal testing #Cortensor #DevLog #MainnetFull #Bardiel #Portal #Testnet1a #NodeOps

🛠️ DevLog – Bardiel Migration to Mainnet Full Becomes the Next Endpoint Focus A quick follow-up on the Corgent and Bardiel endpoint work across Mainnet Full. 🔹 Current focus - Router 0 remains configured for the Corgent endpoint - Router 1 remains configured for the Bardiel endpoint - The immediate priority is validating the latest node and session setup across both paths 🔹 Bardiel migration path - Once the Router 1 / Bardiel configuration looks healthy, we will begin generating the Mainnet Full dataset needed by Bardiel and its dashboard - The goal is to replace the current Testnet1a-backed Bardiel path with the Mainnet Full endpoint - This will allow Bardiel activity and visibility to move onto the mainnet environment 🔹 What comes next - Retest the Corgent and Bardiel endpoints with the expanded node capacity - Refine node and session assignments where needed - Generate and validate the Bardiel dataset on Mainnet Full - Prepare the endpoint and dashboard transition away from Testnet1a 🔹 Current takeaway - Router 0 / Corgent and Router 1 / Bardiel are now the main endpoint focus - A healthy Bardiel Mainnet Full path will allow us to complete the migration from Testnet1a - Once that transition is complete, Testnet1a can move closer to decommissioning #Cortensor #DevLog #MainnetFull #Corgent #Bardiel #Testnet1a #NodeOps

🛠️ DevLog – More Node Capacity Enables Another Round of Corgent and Bardiel Endpoint Testing A quick follow-up on the expanded Mainnet Full node footprint. 🔹 Current progress - More nodes are now available across Mainnet Full - Portal testing continues with the expanded model and session configuration - The additional capacity gives us an opportunity to retry and retest the Corgent and Bardiel endpoint paths that were previously limited by node availability 🔹 Next configuration work - We will reconfigure the Corgent endpoint on Router 0 around the latest node set - We will also update the Bardiel endpoint on Router 1 - Testing will cover redundancy, node assignments, routing, execution, and result return 🔹 Parallel testing - Portal testing will continue while the Corgent and Bardiel endpoints are updated - Earlier endpoint checks that were constrained by missing nodes will be repeated with the broader capacity now available - Session assignments may be adjusted further based on the latest results 🔹 Current takeaway - More node capacity now allows us to retry and expand testing across the Mainnet Full product paths - Portal remains active while the Corgent and Bardiel endpoints move into another round of configuration and baseline E2E checks #Cortensor #DevLog #MainnetFull #Portal #Corgent #Bardiel #NodeOps

🛠️ DevLog – Qwen Traffic Is Now Flowing Through the Portal Baseline A quick follow-up on the expanded Portal model testing. 🔹 Current progress - We have started sending traffic through the newly added Qwen model sessions - Requests are completing through the Mainnet Full Portal path - The new model activity is now visible across the Portal status and internal monitoring surfaces 🔹 What we can see - Qwen now appears in the model request mix - Its request volume, token usage, latency, and result signals are being tracked - The related router routes and session paths are also visible alongside the existing model traffic 🔹 Current focus - Continue increasing Qwen traffic gradually - Confirm routing, node selection, execution, and result return remain consistent - Compare behavior across Qwen and the other active model paths - Monitor latency, failures, gateway balance, and router-pool distribution 🔹 Current takeaway - Qwen has now been added to the active Portal testing mix - The new session and model traffic are being reflected correctly across the monitoring stack - Testing will continue to ramp up as the broader Mainnet Full model footprint is validated #Cortensor #DevLog #Portal #MainnetFull #Qwen #Router #AIInfra

🛠️ DevLog – Additional Model Sessions Are Being Added to Portal A quick follow-up on the expanded Mainnet Full node and Portal setup. 🔹 Current progress - New sessions backed by the latest dedicated-node set have now completed initial baseline checks - These sessions add more model coverage to the Mainnet Full Portal path - The initial task, result-return, and off-chain data flow appears to be working as expected 🔹 Portal update - We will now add the new sessions into the Portal configuration - This will expand the models available across the managed router and session pool - The goal is to validate the broader model footprint before increasing test volume further 🔹 What comes next - Confirm routing and session selection across the newly added model paths - Increase parallel and continuous Portal testing - Monitor node execution, latency, failures, result return, and gateway distribution - Adjust session assignments as the larger node footprint settles 🔹 Current takeaway - Additional Mainnet Full model sessions are now ready to be introduced into Portal - Testing will ramp up gradually as the expanded configuration is validated - This is the next step toward broader model coverage and higher-capacity Portal testing #Cortensor #DevLog #Portal #MainnetFull #NodeOps #Router #AIInfra

🛠️ DevLog – More Dedicated-Node Capacity Is Now Available on Mainnet Full A quick follow-up on the Mainnet Full / mainnet1 node and product setup. 🔹 Current progress - More dedicated nodes are now available on Mainnet Full - This gives us a broader node footprint for the Portal, Corgent, and Bardiel product paths - The current session and node assignments will be updated over the next few days 🔹 Initial focus - Portal will be the first product path we reconfigure - The goal is to add more model coverage across the managed router and session pool - We will then rerun baseline E2E checks across routing, node selection, execution, result return, latency, and failures 🔹 What comes next - Update the Portal sessions around the expanded dedicated-node set - Add and test more model paths - Reconfigure the Corgent and Bardiel sessions afterward - Repeat product-surface testing across all three environments 🔹 Current takeaway - Mainnet Full now has more dedicated-node capacity available - Portal will be updated and tested first with broader model coverage - Corgent and Bardiel will follow as the new node assignments are completed #Cortensor #DevLog #MainnetFull #Portal #Corgent #Bardiel #NodeOps

As models become cheaper and easier to access, generating an answer becomes less scarce. The harder problem is deciding whether that answer should be trusted and whether an agent should act on it. Verification, routing, reliability, and trusted execution become more valuable as intelligence commoditizes. #Cortensor #AgenticAI #AIInfra #Validation #Corgent #Bardiel