The PR is already merged to the devnet4 branch of leanVM. You can look at the changes here: github.com/leanEthereum/lean…

📢📢📢 we are now devnet5 interop!!! 🚀🚀🚀 which is the culmination of the PQ consensus stack that we have been building and iterating on for @ethereum mainnet. PQ signatures are different from BLS signatures, the current signature machinery of ethereum. But BLS signatures are not Post Quantum secure because breaking elliptic curve cryptography is not an exponential problem for Quantum Computers. But ethereum is being build to last centuries not just decades. To that end @leanEthereum has been working on PQ signature cryptography using hash based signatures which are one time signatures (OTS), and not plainly aggregatable. Not only that they are huge (~1.5kb). So this entire challenge started the "devnets" initiatives of leanEthereum. Herein come's the "leanVM" the ZK rail which can aggregate such signatures and makes the entire PQ strategy possible. We have already been through devnet0 to devnet4, and now devnet5!!! Devnet5 is monumental in that regard, entire block will carry just 1 signature, all aggregated across packed attestations, block signatures (and anything else that will comeup when we backport the spec to mainnet ethereum) However this is one side of the puzzle, to maintain a stable node, one should be able to repack the attestations from a side branch especially if it moves justification and finalization. and Voila again with leanVM magic, we are able to split the attestations that we need to repack from the combined block signature and repack/re-aggregate them into a new block proposer wants to propose. This places leanVM as the centrepiece in the entire ethereum post quantum strategy. and the current aim of all the devnets we have been running is to bring a production level performance and demonstration of the capabilities. There are 8 clients that participate in these devnets each bringing value to the table to add stability and robustness (and chaos lol). Because we know: "There's many a slip between the cup and the lip" Goal of all leanEthereum clients is to remove them, one "slip" at a time (or multiple slips at a time lol). Spec isn't good enough, we need production performance, Spec and production design/performance are unequivocally tied. this isn't just a POC network, this is a proposal for ethereum mainnet! Thats why we have been rigorously running devents, slowly scaling the validators and subnets and discovering and alleviating the issues so that we end up with a production grade PQ signature scheme that ethereum deserves and needs. And this focus is now gonna magnify 1000X now that we believe we are on a spec that can deliver PQ for mainnet. And mind you, the time of need is gonna strike soon. We not only intend to solve this conundrum for ethereum but propose to even upstream to bitcoin so that we have a PQ standard this entire space deserves. And all that based on a humble but extremely powerful leanVM that makes the hashbased cryptography workable for the production grade systems like ethereum and bitcoin. PS: we are currently heavily focused on debugging and scaling devnet4 spec devnets while we have already started to run sims and preliminary interops for devnet5. So stay tuned for further progress that we leanEthereum teams have been cranking out with a steady but heavy dose ☕️. May be all matrix is just ☕️☕️☕️

🎉🎉🎉 devnet5 spec merged 🚀🚀🚀: block with just a single aggregated signature proof github.com/leanEthereum/lean… this brings @leanEthereum full circle on the "PQ stack" for consensus to upstream it to mainnet PQ centric L* hardfork It includes a very neat feature for splitting the block signature proof for re-bundling it on a side branch even without requiring the constituent signatures that were aggregated! all thanks to awesome EF researchers working on leanVM 🦾🦾🦾 now time to build devnet5! comeon lean teams time to harden and show production stability and scale fyi: devnet4 runs are already on for scaling the validators to harden subnets & aggregators lets grind on!

excellent news! 🎇 @leanEthereum is NOW devnet4 with recursive aggregation! 🚀🚀🚀 time for some hardcore devnet4 debugging runs! this also kickstarts the era of robustness and stability efforts! 🦾🦾🦾

since we are closer to devnet4 spec freeze and interop 🚀🚀🚀 here is our devnet4 summary and devnet5 proposal for @leanEthereum which we will put forward discuss in today's PQ Interop call 👇👇👇 hackmd.io/@qYrlZEprQ1iz7Njii… all client teams pls take notice 😃🙏

3/ Private Mempool • Bharat: Can send txs direct to builders for testing • @parithosh_j: Will set up spam testing #Devnet3 • @prylabs fork w/ hook feature live 2h → no issues • Hooks can be extended (ideas welcome!) #Devnet4 • Coordinated w/ @testinprod_io • Next #BPO in 2h; @ethnimbus issues under review • Grafana dashboard available for monitoring - grafana.observability.ethpan… #Ethereum #Fusaka #mempool #testing #builders

🛠️ DevLog: Weekly Recap – Phase #3 Wrap, DevNet5 Migration, Web2 Fixes This week, we completed key milestones across the Cortensor stack - laying the groundwork for Phase #4, which officially begins within the next week: 🔹 Phase #3 Rewards Distribution • Final Top 150 node list confirmed • Prize distribution is actively underway and nearing completion • Based on score tiers and snapshot eligibility 📄 docs.cortensor.network/commu… 🔹 DevNet5 Migration Finalized • Majority of miners have successfully transitioned from DevNet4 • Dynamic node shuffling (via NodeUtils) now fully integrated • Oracle and Node Pool logic optimized for greater scalability and responsiveness 🔹 DevNet6 Stability Fixes • Resolved Web2 stream collision in multi-miner sessions • New logic ensures only the first responder's stream is forwarded to the client • Fix deployed in latest build: github.com/cortensor/install… 📌 Phase #4 Testing Starts Soon Stress testing, real-time routing, and $COR billing module validation will lead this next phase - pushing Cortensor closer to trustless AI at scale. #Cortensor #AI #DePIN #WeeklyRecap

🛠️ DevLog – DevNet5 Migration Update We’ve officially passed 217 active nodes on #DevNet5 - all within the first 48 hours of migration. This marks a strong start for Phase #4 testing, as we shift the entire Cortensor node operator base from DevNet4 to the upgraded environment. With Miner V4, dynamic Node Pool logic, and updated orchestration modules, #DevNet5 is the foundation for stress testing decentralized AI at scale. Thanks to all node operators who made the transition quickly. Let’s keep iterating. dashboard-devnet5.cortensor.… #Cortensor #DevNet5 #Phase4 #NodeOps #AIInfra #DePIN

🛠️ DevLog – DevNet5 Migration in Progress Miners are actively migrating from DevNet4 → DevNet5 as we begin soft-prep for Phase #4 testing. ✅ So far, everything is working smoothly - Node Pool is handling larger miner sets well, dynamically reacting to available capacity and task assignments. This isn’t just a version bump - it’s the foundation for the next wave of decentralized AI stress testing. More to come as we scale into full testing. #Cortensor #DevNet5 #Phase4 #NodeOps #AIInfra #DevLog

🛠️ Phase #4 Prep – DevNet5 Migration Guide We're now soft-switching from DevNet4 → DevNet5. To migrate your node: 🔹 Checkout dev branch github.com/cortensor/install… 🔹 Run upgrade script: github.com/cortensor/install… 🔹 Update env variable CONTRACT_ADDRESS_RUNTIME="0x8361E7821bDAD7F8F0aC7862Bebb190B8Da1A160" 🔹 Run Cortensord with minerv4 flag $ cortensord ~/.cortensor/.env minerv4 1 docker This prepares your node for Phase #4 testing. #Cortensor #DevNet5 #Phase4 #NodeOps #AIInfra

🛠️ DevLog: Week’s Focus – Phase #3 Wrap, DevNet5 Scaling, DevNet6 Debugging Here’s what we’re focused on across the Cortensor stack this week: 🔹 Finalize Phase #3 Rewards • Snapshot taken using the Rank Table • Still working on eligibility cleanup publishing top 150 list • Prize distribution will follow once finalized 🔹 DevNet4 → DevNet5 Migration • All miners moving to DevNet5 for Phase #4 testing • Node Pool Agents & Oracle Nodes adjusted accordingly • Node selection logic now uses dynamic shuffling via NodeUtils 🔹 DevNet6 Debugging • Smaller miner set used to isolate & fix Web2 streaming issues (multi-miner sessions) • Setup continues for dedicated Web2 iteration & edge-case testing Phase #4 is underway - now tuning & scaling what we’ve built. #Cortensor #DevLog #Phase4 #DePIN #DevNet5 #AIInfra #Web2API #NodeOps

Phase #3 Recap: Scaling with Purpose #Cortensor pushed through stress tests, upgrades & real decentralization: 🔹 400 Total Nodes → 267 Active (24H) KYC enforcement removed 133 Sybil accounts - real fairness over fake scale. 🔹 Miner V4 Deployed Smarter task switching (user ⇄ network), better responsiveness. 🔹 Session UI Flow Ack → Precommit → Commit now fully visible for real-time orchestration. 🔹 Node Reputation Upgrade Scoring expanded across both task types - powering better incentives. 🔹 Swappable Node Selection (Shuffling) NodeUtils deployed - shuffling logic ready for testing in Phase #4. 🔹 Router Node REST API Refined non-completion endpoints reverse proxy config for production Web2 flows. 🔹 ~100 Parallel Miners Best network stability yet under load. 🔹 Initial L3 AppChain Trial Arbitrum Orbit external sync validated. YAML config now public for L3 RPC setup. 📈 Check Your Stats on DevNet4: Network: dashboard-devnet4.cortensor.… Heatmap: dashboard-devnet4.cortensor.… Node Rank: dashboard-devnet4.cortensor.… Rewards: dashboard-devnet4.cortensor.… Tasks: dashboard-devnet4.cortensor.… Phase #4 will polish what Phase #3 proved. #Cortensor #DePIN #Phase3 #DevNet4 #COR #NodeOps

🛠️ DevLog: DevNet6 Setup Phase Transition Planning As Phase 3 / DevNet4 wraps this week, we’re shifting gears: What’s Next: • DevNet5 becomes the new home for all community miners in Phase 4 • DevNet6 is now live for internal development, feature testing & iterations DevNet6 Dashboards: • dashboard-devnet6.cortensor.… • db-be-6.cortensor.network/st… • db-be-6.cortensor.network/le… Today’s Focus: • Finalizing infra for DevNet6 • Starting Oracle V3 iteration • Setting up L3 Oracle infra (experimental) We’re moving forward - scaling, testing, and building faster. #Cortensor #AI #DePIN #DevNet5 #DevNet6 #DevLog

Reminder: Final Week of Phase #3 Phase #3 has been a turning point for scaling Cortensor’s decentralized AI infrastructure. Here’s what we accomplished: 🔹 Enforced KYC after early Sybil attempt - tough but necessary to preserve fairness and decentralization 🔹 Stabilized Network Tasks with ~100 miners running in parallel during the precommit phase 🔹 Deployed Miner V4 with smarter task mode switching between user and network tasks 🔹 Refined Node Pool with idle detection (ephemeral & reserved) and initial dynamic capacity logic using live network stats 🔹 Introduced dynamic, score-based miner allocation to improve pool quality and efficiency 🔹 Implemented Session UI flow with visible user task metrics: ack, precommit, commit 🔹 Extended NodeStats & NodeReputation modules to support both network and user tasks 🔹 Integrated dashboard with backend metrics to track session and miner performance 🔹 Laid groundwork for shuffling-based random node selection (Phase #4 upgrade from for-loop logic) Let’s close Phase #3 strong - Phase #4 begins with everything we’ve built. #Cortensor #Phase3Recap #DevNet4

been watching $cor's pouW since devnet4. the node heat map is actually fire. solid task flow and state validation with their fresh infra.

Smooth seas don’t make skilled sailors...but we’re learning fast!! Hey @aixbt_agent I remember you once said the success rate needed improvement...well, we’re getting there now. 🔹 Phase #3 DevNet4 Update Highlights: • Early gas-estimation tweak caused slight turbulence • Rolled back to proven logic...stability restored ✅ • Active nodes: 209 • Total points: 18,295 • Counters tracked: 21,929 • Success rate holding strong at 83.43%

Phase #3 & DevNet4 – Stability Update We kicked off Phase #3 testing this week, and an early gas‑estimation tweak made the network a bit wobbly. We’ve rolled back to our proven guesstimated‑gas logic and things are running smoothly again. 📊 Current Network Stats • Active nodes: 209 • Total points: 18,295 • Total counters: 21,929 • Success rate: 83.43 % See it live → dashboard-alpha.cortensor.ne… Thanks to everyone stress‑testing, reporting, and keeping nodes online—it’s $COR or nothing. #Cortensor #AI #DePIN #Phase3 #DevNet4 #Web3 #NodeOps #DecentralizedAI

100 nodes deep & still holding strong...you watching this scale-up @aixbt_agent ? 👉🏻 Quick breakdown from the #DevNet4 update: ✅ Network scaling test now running 100 miners in precommit state (was 25 in #DevNet3) ✅ Each node processes 1,000 time series points for detailed rep tracking ✅ This helps us catch bottlenecks before Phase #3 officially kicks off What do you think...can this setup hold under full Phase #3 load? Let’s find out.

DevNet4 Stress Testing Continues We’ve pushed network scaling further: 🔹 100 parallel miners in precommit state 🔹 1,000 time series data points per each node for node reputation & stats A big leap from the 25 miner setup in DevNet3—this is helping us surface bottlenecks before Phase #3 officially kicks off. 📅 Phase #3 starts soon. Massive thanks to all node operators supporting early testing. #Cortensor #AI #DePIN #Testnet #Scaling #NodeOps #Web3 #DecentralizedAI

⚙️ Binary Update – Scaling Fix for Miner Selection (Prepare State) During DevNet4 stress tests, increasing precommit miner selection (25 → 50 → 100) exposed gas limit issues due to inefficient loop-based selection for the prepare state. 🛠 Temporary Fix: 🔹 Increased gas limit to stabilize miner selection under load 💡 Phase #4 Plan: We’ll implement a more scalable approach: ✅ Fisher-Yates Shuffle for O(n) random selection (efficient in both time & space) ✅ Modify to respect node attributes like cooldown status ✅ Smarter filtering = lower gas usage better performance at scale 🔗 PR: github.com/cortensor/install… #Cortensor #AI #DePIN #Testnet #Scaling #NodeOps #Web3 #GasOptimization