Bluefin_Crypto

🔎 Recap: Where Mainnet Prep Stands Now A quick recap on how the current Mainnet Lite → Mainnet Full transition has evolved and where the focus is moving next. 🔹 Mainnet Lite capacity shift - Mainnet Lite remains functional, with its routers, sessions, oracles, and broader configuration still in place - But under current market conditions, keeping both environments fully active adds recurring ETH gas and infrastructure cost - To stay conservative and use limited resources more efficiently, more node capacity has been shifted from Mainnet Lite into Mainnet Full - Lite can be brought back into a more active public-demo role whenever demand, exposure, and operating economics make sense 🔹 Mainnet Full baseline - Over the last few weeks, we have been running repeated light checks across Mainnet Full / mainnet1 - The L3, routers, sessions, node paths, network tasks, user tasks, dashboard, indexer, and related infrastructure have remained healthy at the current baseline - Node stats, reputation, levels, and quality sampling were also reset and tuned so the network can rebuild cleaner operational data under the latest configuration 🔹 Product paths - Portal, Corgent, and Bardiel are now all operating through their Mainnet Full paths - Portal has gone through repeated routing, model, gateway, session, and node E2E checks - Corgent and Bardiel have also been tested across delegate, validate, redundancy, consensus, MCP, and ERC-8004-facing paths - So far, these product configurations look workable under the current capacity 🔹 Where the focus is moving - With the basic Mainnet Full infrastructure and product paths in place, the next focus is improving Portal compatibility for agent runtimes - PyClaw is being used as the first practical integration target because it exercises OpenAI-compatible APIs, streaming, tool calling, and longer agent loops - If Portal works cleanly with PyClaw, much of that compatibility should also benefit other OpenAI-compatible agent frameworks 🔹 Current compatibility work - The rough PyClaw-side Portal integration foundation is already in the codebase - Portal-side compatibility changes have started as well - A new v4 completion path was introduced on the router / network side so newer tool-calling and agent-oriented behavior can be added without changing the existing v3 baseline - The Portal router pool has already been updated with the v4 completion path 🔹 Current dependency - We are still waiting for all miners to upgrade to the latest binary with v4 completion support - Once the miner side is aligned, we can run cleaner E2E checks across PyClaw → Portal → router → miner → model - From there, the remaining work should become a more iterative process of identifying smaller gaps, fixing them, and repeating the tests 🔹 Current takeaway - Mainnet Lite remains available, but more capacity is being concentrated into Mainnet Full for efficiency - Mainnet Full now has a healthy baseline across infrastructure, Portal, Corgent, and Bardiel - The next layer is making Portal a cleaner agent-compatible access surface - PyClaw is the first practical test case, but the broader goal is compatibility with OpenAI-style agent runtimes in general - This work is still in progress, with the immediate focus on completing the miner rollout and then iterating through the remaining Portal compatibility gaps #Cortensor #MainnetFull #MainnetLite #Portal #Corgent #Bardiel #PyClaw #AIInfra

🛠️ DevLog – Rough Portal V1 Mock Shared We shared a very rough Portal V1 mock in URL form on Telegram so it is easier to click through and get a better feel for the flow than from screenshots alone. 🔹 Current context This is still just a rough mock to help us understand the flow and the larger UI components better. It is not meant to represent the final implementation or final product polish yet. 🔹 Why this matters The goal right now is simply to understand the shape of the Portal surface more clearly: - auth / entry flow - usage / limits - API key flow - billing / plan surface - docs / quick-start path 🔹 Current direction This is more likely the basic UI direction we’ll keep iterating on next phase once implementation starts more seriously. 🔹 What’s next We’ll probably still do a bit more UI/UX iteration on this through the rest of this week, but this share is mainly to give a better feel for the current Portal direction in something more interactive than static screenshots. 🔹 Note We are not reposting the direct URL here for now - check Telegram if you want to click through and get a better feel for it - t.me/CortensorNetwork #Cortensor #DevLog #Portal #UIUX #ProductDesign #API