@cortensor Avatar @cortensor Cortensor

Cortensor posts on X about the new, core, testing, $cor the most. They currently have [-----] followers and [---] posts still getting attention that total [-----] engagements in the last [--] hours.

Engagements: [-----] #

Engagements Line Chart

Mentions: [--] #

Mentions Line Chart

Followers: [-----] #

Followers Line Chart

CreatorRank: [---------] #

CreatorRank Line Chart

Social Influence

Social category influence finance 12.61% stocks 11.76% technology brands 8.4% cryptocurrencies 5.88% social networks 3.36%

Social topic influence the new 16.81%, core 15.97%, testing 11.76%, $cor #7, ai 10.92%, module 10.92%, network 10.92%, status 9.24%, the first 8.4%, metrics 8.4%

Top accounts mentioned or mentioned by @el_cano498 @cryptonormie50 @family_hedge @bozdemir5269 @cryptoninjapro @01_choose @almamy1217047 @0xtwilty @djgriffith @mickey_tmnt @astr0_peng @bardieltech @volkerts_trades @indespensionnl @01choose @itsmecryptality @8004xbt @aixbtagent @ryanis999 @sundardharan3

Top assets mentioned Cencora, Inc. (COR) Alphabet Inc Class A (GOOGL)

Top Social Posts

Top posts by engagements in the last [--] hours

"🛠 DevLog PyClaw Agent Experiments on Testnet-1A We've started using a dedicated set of Cortensor sessions on Testnet-1A to iterate on the lightweight PyClaw agent framework (inspired by OpenClaw and being ported into Python for tighter Router integration). 🔹 Where Were Testing - Session #44 (main playground): - Session #45: - Session #46: 🔹 Whats Running There - End-to-end PyClaw unit tests and orchestration flows wired into Cortensor sessions. - Mix of raw completion traffic and early tool-call tests running on OSS 20B-class models. 🔹 Why It Matters - Gives us a repeatable sandbox to"
X Link 2026-02-15T23:54Z [----] followers, [---] engagements

"🗓 Weekly Focus Phase #2 Hardening Agent Surfaces & Data Mobility This week continues the Phase #2 push with stability first deeper Testnet-1a iteration and follow-up work on agent-facing endpoints. 🔹 Testnet Phase #2 Stability & Support - Ongoing monitoring across routing miners validators oracles indexers and dashboards. - Fast follow-ups on abnormal node states and performance regressions. 🔹 Testnet-1a (Self-Managed L3) Ops + Load - Completed the full operational checklist for Testnet-1a (baseline stability capacity monitoring). - Move into replay / break-testing mode: intentionally"
X Link 2026-02-09T08:29Z [----] followers, [----] engagements

"🛠 DevLog Prepping Arbitrum Mainnet #L3 Dry-Runs & Experimental (With Data Mobility in Place) Quick snapshot as we get ready for real #L3 experiments on #Arbitrum mainnet. 🔹 Current Cost Snapshot (#Arbitrum #Sepolia) - Approx deploy cost per L3: [------] ETH + [---] $COR - Latest reference deployment tx: 🔹 Why This Matters - #L3 deployment itself is relatively cheap; the main capital cost is validator staking which is fully configurable. - Now that we have basic data mobility across the key modules (Session Session Queue/Task Payment plus NodePool/NetworkData) we can safely: - Exercise the full"
X Link 2026-02-14T10:54Z [----] followers, [----] engagements

"Weve been quietly calling Cortensor AWS for agents for a while now not as a slogan but because the pattern really does rhyme with how AWS changed web apps. Back then AWS basically said: Dont http://x.com/i/article/2022653474115317760 http://x.com/i/article/2022653474115317760"
X Link 2026-02-14T13:37Z [----] followers, [----] engagements

"🗓 Weekly Recap Phase #2 Hardening L3 Ops Progress & Data Mobility Milestone This week we completed most planned Phase #2 work with /delegate and /validate iteration rolling over. 🔹 Testnet Phase #2 Stability & Support - Continued active monitoring across routing miners validators oracles indexers and dashboards. - Followed up on abnormal node states and kept Phase #2 environments stable. 🔹 Testnet-1a (Self-Managed L3) Ops + Replay/Break Testing - Completed replay/break-testing and recovery validation on Testnet-1a. - Ran base fee adjustment exercises and captured learnings into the L3 ops"
X Link 2026-02-14T23:02Z [----] followers, [---] engagements

"🛠 DevLog #Arbitrum #L3 Dry-Run Experiments (Data Mobility Ops & Cost Probing) 🔹 Why Were Doing This - Self-managed #L3 on Testnet-1A has been stable for a few weeks so were confident enough to rehearse the same flows on Arbitrum mainnet. - #L3 deployment costs on #Arbitrum (from #Sepolia tests) are low enough that a few dry-runs are reasonable. - This is not a mainnet launch - just early experiments to build real-world ops + cost data. 🔹 What Well Test - Spin up short-lived #L3s on #Arbitrum mainnet and run through our L3 ops playbook: - Measure gas usage for sequencer batch posting and"
X Link 2026-02-15T09:27Z [----] followers, [---] engagements

"🛠 DevLog Router v2 Agentic Stack: Smoke Tests Passed Weve finished iterating and smoke-testing the full router agentic surface on Testnet-1A and everything is now behaving as expected. 🔹 What Was Tested - Generalized #MCP (stream + SSE) #A2A agent card and both v1/v2 of /delegate + /validate. - #x402 payments vs API key usage for REST endpoints. - #MCP + #x402 paths for agents coming in through #MCP instead of raw REST. - All test traffic is visible here: 🔹 New Trial Endpoint - Introduced a trial mode where payment is not required but rate-limited so external users can try /delegate +"
X Link 2026-02-18T04:48Z [----] followers, [---] engagements

"🛠 DevLog How Were Using Pre-Mainnet [--] / 1A / 1B To keep our mainnet dry-runs clear were standardizing the naming: 🔹 Environment Mapping - Pre-Mainnet [--] #Arbitrum #L2 (full Cortensor stack like a mainnet version of Testnet-0). - Pre-Mainnet 1A #Arbitrum #Orbit #L3 (self-managed L3 similar to Testnet-1A). - Pre-Mainnet 1B #Arbitrum #Orbit #L3 (second lane for alternate configs / hardfork drills). 🔹 How This Differs From Testnets - Testnets (Testnet-0 / Testnet-1A) mostly use test ETH + test $COR to validate logic and behavior. - Pre-Mainnet environments use real ETH + real $COR for validator"
X Link 2026-02-17T08:05Z [----] followers, [---] engagements

"🛠 DevLog Cortensor /delegate vs #Google DeepMinds Intelligent AI Delegation Paper: We spent some time going through #Google #DeepMinds new Intelligent AI Delegation paper and sanity-checked how Cortensors /delegate + /validate stack lines up with where the research world is heading. The paper basically says: delegation isnt just call another model its a sequence of decisions that must include task decomposition capability matching transfer of authority/responsibility clear specs trust mechanisms and verifiable completion especially in future agentic web economies. 🔹 1) Contract-First"
X Link 2026-02-18T06:12Z [----] followers, [---] engagements

"🗓 Weekly Recap Mini Hackathon Ready + Core Improvements As we close out the week Cortensor is now better prepared for real usage - just in time for the first Mini Hackathon. 🔹 Hackathon Infrastructure Ready - Finalized internal hackathon structure & async submission via Discord - Integrated initial tools into: 🔹 Session & SessionQueue Fixes - Resolved key bugs in Oracle v3 affecting task timing & state sync - New Router Node API endpoint /api/v1/create added - enables session creation via RESTful calls - Web3 SDK already supports session creation 🔹 API & SDK Enhancements - Web2 API and"
X Link 2025-06-28T06:30Z [----] followers, [---] engagements

"🛠 DevLog Dynamic Pricing Ready Across All Testnets Dynamic pricing is now wired up end-to-end on Testnet-0 Testnet-1 and Testnet-1a. 🔹 SessionPaymentTable per-network Global Pricing Table and Session Pricing Breakdown UIs are all deployed on Testnet-1 / Testnet-1a matching Testnet-0. 🔹 Well run manual user task e2e tests on Testnet-1 and Testnet-1a to confirm everything behaves as expected under real sessions. 🔹 Dynamic pricing is not yet "turned on" globally - we can flip a single switch and adjust the pricing tables during Testnet Phase #2 and Phase #3 to tune rates weights and behavior"
X Link 2026-01-10T09:48Z [----] followers, [----] engagements

"💡 Community Spotlight - Monthly Reward: Tools & Infrastructure Each month we reward community members who maintain and improve the critical tools and infrastructure that keep Cortensor's decentralized network running. This month's recipients: 🔹@01_choose Community RPC Node 🔹@ItsMeCryptality Node Monitoring Bot These contributions help node operators and developers onboard monitor and maintain reliable performance - making the network more resilient accessible and efficient. 📌 Access these tools or contribute your own: Thank you to all builders driving the decentralized AI movement"
X Link 2026-01-12T10:31Z [----] followers, [----] engagements

"🛠 DevLog Self-Managed L3: Connectivity Findings & Next Steps Recent stress tests on Testnet-1a (self-managed $COR #L3) surfaced some very practical crossdata center connectivity limits in our setup. 🔹 What Were 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 Were Planning - Co-locate core L3 components - Move RPC into the same DC"
X Link 2026-01-21T05:16Z [----] followers, [---] engagements

"🔹 DevLog Data Mobility & Data Module Import/Export (Early Design Thoughts) As we see real data growth on the self-managed #L3 its becoming clearer that storage growth itself isnt the real problem - data mobility is. 🔹 What Were Thinking About - Instead of worrying only about raw disk size were focusing on how to move and reshape state cleanly over time. - The idea is to support import/export for core data modules so we can migrate or hardfork infra without losing the logical network state. Target data modules for import/export design: - Session Data user sessions configs runtime state -"
X Link 2026-01-25T23:11Z [----] followers, [----] engagements

"Monthly Node Rewards January [----] (Initial Batch Sent) We've just sent out the first round of $COR rewards to [--] active nodes as part of our monthly node reward program. 🔹 Rewards will be distributed in batches 🔹 More batches rolling out over the next few days 🔹 Recognizing uptime stability & contribution 💬 Join our Discord to set up a node or get involved: Thanks to all node operators pushing decentralized AI forward - it's $COR or nothing. #Cortensor #AI #DePIN #NodeRewards #COR https://discord.gg/cortensor Monthly Node Rewards December [----] (last Batch Sent) Another [--] active nodes"
X Link 2026-01-26T08:55Z [----] followers, [---] engagements

"Monthly Node Rewards January [----] (Batch [--] Sent) Another [--] active nodes have just received their $COR rewards - bringing the total to [--] rewarded nodes so far this month. 🔹Rewards will be distributed in batches 🔹More batches rolling out over the next few days 🔹Recognizing uptime stability & contribution Join our Discord to set up a node or get involved: Thanks to all node operators pushing decentralized AI forward - it's $COR or nothing. #Cortensor #AI #DePIN #NodeRewards #COR https://discord.gg/cortensor Monthly Node Rewards January [----] (Batch [--] Sent) Another [--] active nodes have just"
X Link 2026-01-27T20:30Z [----] followers, [---] engagements

"Staking APR Adjustment Reminder (Feb 28) Quick reminder that the next scheduled APR step-down for $COR staking goes live on Feb [--] [----] as part of the long-term sustainability plan. 🔹 New APR (from 2/28/2026) - Pool 3: 10% APR - Pool 2: 5% APR - Pool 1: 2% APR Lock periods + all other staking conditions stay the same. This follows the gradual schedule as the network matures and we move into the next phases of Testnet Mainnet. More details: #Cortensor #Staking #COR #DePIN https://docs.cortensor.network/community-and-ecosystem/staking-pool-overview#apr-breakdown Staking APR Adjustment Reminder"
X Link 2026-01-28T09:43Z [----] followers, [---] engagements

"🛠 DevLog #L3 Ops: Gas Fees Playbooks & Next Steps 🔹 What We Just Did - Ran a base fee / gas fee collection exercise on the self-managed #L3 (Testnet-1A) to make sure accounting + ops flow are sane. - Updated the #L3 execution fee collector to a new address and verified balances before/after the switch: - New fee collector: - Confirmed that #L3 execution fees are accumulating correctly even with a very low base fee right now. - Started drafting internal L3 ops docs around: - changing fee recipients - adjusting base fee / gas params - and doing basic key/collector rotations as part of a"
X Link 2026-01-30T07:46Z [----] followers, [----] engagements

"🛠 DevLog Testnet Node Capacity Market Conditions & Next L3 Steps 🔹 What Were Doing - Based on community feedback + current market conditions were keeping testnet node capacity intentionally moderate and adjusting it gradually instead of pushing for max scale right now. - Upscaling isnt the bottleneck - spinning up more capacity is straightforward once the timing + market are right. 🔹 What Weve Learned So Far - Last phases (plus current Phase #2) showed the stack can scale: more nodes + more traffic mostly surfaced minor bugs and SLA tuning gaps not hard infra limits. - That means the best"
X Link 2026-02-01T03:49Z [----] followers, [---] engagements

"The quiet lesson from #OpenClaw / #Moltbook-style agent stacks: inference is getting cheap but running agents 24/7 is not. As we spin up fleets of always-on agents Jevons kicks in: lower per-call cost more calls more tools more orchestration and suddenly the real bottlenecks are: - Infra bills (API + hosting + storage) - Trust in what agents did while you werent watching - Long-term memory + state you dont want to recompute every time Cheap inference doesnt end demand it moves value from raw tokens to: ✅ verification / proofs ✅ scheduling & routing ✅ durable memory + context sharing. Thats"
X Link 2026-02-01T08:28Z [----] followers, [----] engagements

"🛠 DevLog CorClaw Agent Economy Experiment (#OpenClaw + #Moltbook + #Clawnch) 🔹 What Were Actually Testing - OpenClaw is the local agent stack were experimenting with. - Moltbook is the agent social network where CorClaw / Cortensor agents can post follow and be discovered: - CorClaw profile: - Cortensor community: - Clawnch is a separate agent-powered launchpad that CorClaw used to deploy a small test token on Base as an on-chain fee stream: - Clanker view: 🔹 Why This Matters - Always-on agents are fun in theory but in practice 24/7 inference is still expensive especially at scale. -"
X Link 2026-02-01T23:36Z [----] followers, [----] engagements

"🗓 Weekly Focus Phase #2 Hardening SLA Filters L3 Ops & Agent Surfaces This week continues the Phase #2 push with stability first deeper self-managed L3 iteration and prep work for SLA-driven routing. 🔹 Testnet Phase #2 Stability & Support - Continue active monitoring across routing miners validators oracles indexers dashboards. - Fast follow-ups on abnormal node states and performance regressions. 🔹 Testnet-1a (Self-Managed L3) Iteration + Ops Playbook - Keep iterating Testnet-1a from an operational perspective (reliability throughput failure modes). - Expand and refine the L3 operational"
X Link 2026-02-02T08:36Z [----] followers, [----] engagements

"🛠 DevLog Multi-RPC Core Implemented Now in Wiring & Testing Phase 🔹 Status - The core multi-RPC Web3 client (supporting multiple hosts with round-robin rotation) is roughly implemented. - Its not tested end-to-end yet and were in the process of updating the modules that currently rely on the old singleton Web3 instance. 🔹 What This Means - We now have a clear direction: Web3 is effectively becoming an injectable multi-endpoint dependency rather than a single global client. - The remaining work is mostly about wiring and regression: - Swap existing callsites to the new multi-RPC abstraction"
X Link 2026-02-03T07:31Z [----] followers, [---] engagements

"🛠 DevLog Multi-RPC Support: First Attempt & Next Steps 🔹 We tried the first pass of wiring multi-RPC into cortensords core Web3 layer but it didnt stick - once we started plugging it into real modules a few assumptions about single RPC only broke flows. 🔹 The good news: that attempt clarified what we actually need next: - update call-sites module by module - run proper regression tests on each flow - and treat multi-RPC as an incremental rollout not a one-shot refactor. 🔹 Current direction: - keep the new multi-RPC client concept - gradually thread it through the main components (router"
X Link 2026-02-03T12:00Z [----] followers, [---] engagements

"🛠 DevLog Corgent & Bardiel Docs Live (Answering the Whats the Difference Question) A few people have been asking how Corgent and Bardiel differ so weve shipped clearer docs to make the split explicit. 🔹 New / Updated Docs - Corgent overview: - Corgent vs Bardiel comparison: 🔹 TL;DR on the separation - Corgent Infra-native trust & execution oracle for ERC-8004 agents and agent frameworks. Lives closest to the Router + validation stack. Minimal policy-driven /delegate / /validate / arbitration surface. - Bardiel Virtual-first service agent that runs on Cortensor (and often Corgent) but plugs"
X Link 2026-02-03T22:26Z [----] followers, [---] engagements

"🛠 DevLog Integrating Multi-RPC Core Changes into cortensord 🔹 Weve started wiring cortensord into the new multi-RPC Web3 core swapping a small set of calls one by one to make sure behavior stays stable. - The new core supports round-robin rotation across configured endpoints; the rpc_instance: n log line shows which endpoint index is active. - For now were using two test RPC URLs repeated into a 10-endpoint list to verify rotation and basic reliability under real network tasks. 🔹 Early tests look OK but theres still a lot of replacement + regression work ahead. - Most modules still use the"
X Link 2026-02-04T12:41Z [----] followers, [----] engagements

"🛠 DevLog Multi-RPC Integration Progress in cortensord Were mid-way through wiring cortensord into the new multi-RPC Web3 core and testing it in small steps. 🔹 Whats In Place - Web3 now supports round-robin RPC rotation (rpc_instance: n in logs). - A simple config/keystore cache makes sure shared system config (contract addresses versions etc.) is fetched once and reused across all RPC instances. 🔹 What Were Doing - Gradually replacing call sites to use the new multi-RPC helper instead of the old singleton Web3. - After each swap we run light regressions (task metrics errors lag) to catch"
X Link 2026-02-04T23:11Z [----] followers, [---] engagements

"🛠 DevLog Multi-RPC Wiring Pass Mostly Complete 🔹 Most of the web3 call sites in cortensord are now migrated to the new multi-RPC core (round-robin + shared config cache). - Old single-RPC paths are still kept around for safety but the primary codepath is now using the new helper. - Next step: run targeted tests later today (network tasks error rates lag) to make sure behavior matches the previous version under real load. If things look stable well start cleaning up the legacy paths and then roll this into broader testnet usage. #Cortensor #DevLog #RPC #AIInfra #DePIN #NodeOps 🛠 DevLog"
X Link 2026-02-05T05:18Z [----] followers, [---] engagements

"🛠 DevLog Multi-RPC Round-Robin Support for cortensord (PR #211) 🔹 Whats New - Added optional multi-RPC support to cortensord via env flags with simple round-robin rotation across configured endpoints. - New config knobs: - ENABLE_MULTIPLE_RPC_HOST turn multi-RPC mode on/off. - NUM_RPC_HOST how many RPC slots to read. - RPC_HOST_0 . RPC_HOST_N-1 the actual RPC endpoints to rotate through. - When enabled cortensord will cycle through the configured RPC hosts instead of hitting a single endpoint every time. 🔹 Why This Matters - Lets node ops spread load across multiple public / free RPCs"
X Link 2026-02-05T10:08Z [----] followers, [---] engagements

"🛠 DevLog #MCP HTTP Stream Adjustments for Corgent & Bardiel (#ERC8004 Mainnet) 🔹 What We Found - Our current #MCP HTTP stream setup for Corgent and @BardielTech works fine with #OpenAI / #Claude tools discovery. - However some other #MCP clients (including the #ERC8004 scan UI) expect more static advertised agent metadata than we currently expose. - As a result our mainnet #ERC8004 agents are showing up as unhealthy on 8004scan even though the underlying MCP servers are actually functional. - Corgent (mainnet): - Bardiel (mainnet): 🔹 What Well Change - Update the #MCP HTTP stream"
X Link 2026-02-05T11:03Z [----] followers, [----] engagements

"🛠 DevLog Additional SLA Filter (PoI/PoUW) Wiring & Tests Today 🔹 Were spending today iterating on the new additional SLA filter that uses validator-derived PoI/PoUW ranks alongside the existing node-spec SLA. - The first rough implementation is already hooked into NodePool utils; now were focusing on wiring it cleanly through the selection path and making sure it plays nicely with the current SLA levels. - Goal for this round: verify that the new filter can narrow candidates using Quantitative/Qualitative ranks without breaking existing routing or starving valid nodes. - Well run a few"
X Link 2026-02-05T23:05Z [----] followers, [---] engagements

"🛠 DevLog Additional SLA Filter (PoI/PoUW) Moving to Testnet-0 for testing 🔹 Status - The new additional SLA filter is now wired into NodePool utils behind a separate path. - It keeps the existing SLA (spec / capabilitybased) then adds a second pass using Quantitative (PoI) + Qualitative (PoUW) rank data. 🔹 Next Steps - Well deploy this on Testnet-0 and run small controlled traffic slices through the new method. - Main checks: - Routing stays sane vs. the old SLA-only path. - PoI/PoUW filtering narrows candidates without starving good nodes. This is the first step toward SLA that reflects"
X Link 2026-02-06T13:10Z [----] followers, [---] engagements

"🛠 DevLog PoI/PoUW-Based SLA Filter Now Live on Testnet-0 The new additional SLA filter (using validator PoI/PoUW ranks) is now deployed on Testnet-0 and running in the real routing path for controlled traffic. 🔹 Whats Happening Now - Weve started end-to-end testing of the new SLA method on Testnet-0. - Flow: existing spec-based SLA then PoI/PoUW rank filter as an extra pass. - During this phase well: - Tune thresholds / buckets for the rank bands. - Watch node selection patterns and task success rates. - Confirm it behaves as intended before considering wider rollout. Goal: make SLA reflect"
X Link 2026-02-07T07:59Z [----] followers, [---] engagements

"🛠 DevLog PoI/PoUW SLA Filter Now Active on Testnet-0 & Testnet-1A Weve now rolled out the additional SLA filter (PoI/PoUW-based) to both Testnet-0 and Testnet-1A. 🔹 Current Status - Testnet-0: initial e2e tests are running with the new flow - existing spec-based SLA extra PoI/PoUW rank filter. - Testnet-1A: the same logic is now live and will be our main playground for tuning since it has more capacity and traffic. From here well: - Observe how node selection changes under real load. - Adjust rank bands / thresholds to avoid over-filtering while still rewarding consistently good validators."
X Link 2026-02-07T11:07Z [----] followers, [---] engagements

"🗓 Weekly Recap Phase #2 Hardening L3 Ops Progress & SLA Prep This week we completed nearly all planned focus items for Phase #2 with one item rolling over into next week. 🔹 Testnet Phase #2 Stability & Support - Continued active monitoring and support across routing miners validators oracles indexers and dashboards. - Follow-ups on abnormal node states and performance regressions helped keep Phase #2 stable. 🔹 Testnet-1a (Self-Managed L3) Iteration + Ops Playbook - Further iteration on Testnet-1a from an operational perspective (reliability throughput failure modes). - Expanded and refined"
X Link 2026-02-07T22:35Z [----] followers, [---] engagements

"🛠 DevLog Data Mobility & Import/Export: From Idea Next Steps Last week we outlined data mobility as the real problem to solve on self-managed #L3s not raw disk size. The focus is still on import/export for core data modules (Session Session Queue Session Payment Node Pool) so we can move state cleanly across infra or L3 instances when needed. 🔹 Whats Next (Early Next Week) - Well start mapping concrete import/export shapes for: - Session / Session Queue data - Session Payment balances - Node Pool metadata + reputation - Run small migration drills on testnet/L3 setups to see how cleanly we"
X Link 2026-02-08T02:44Z [----] followers, [---] engagements

"🛠 DevLog SaltStack Infra for cortensord Fleets Weve just open-sourced our SaltStack-based infrastructure for managing cortensord fleets at scale: 🔹 What It Is - A full SaltStack repo for provisioning configuring and upgrading cortensord across many servers from a single control plane. - Repo: 🔹 Key Features - Centralized node registry to track all your keys configs and roles in one place while still letting you assign specific instances per server. - 3-layer config hierarchy Global Server Instance so you can precisely control everything from chain IDs and RPC URLs to GPU settings and model"
X Link 2026-02-08T07:28Z [----] followers, [---] engagements

"🛠 DevLog L3 Testnet-1A Fee Experiments (Base Fee [--] Stepping) 🔹 This week were starting structured base fee experiments on the self-managed L3 (Testnet-1A) to better understand fee economics vs miner capacity. - Current fee collector (L3 execution fees): - Until now the base fee has been set very low mainly to validate infra + routing under load. - Next step: well increase the base fee by [--] this week and monitor: - Miner/node behavior - Effective weekly fee totals - Relationship between network task volume and L3 fee accumulation - Plan is to repeat the [--] step-up week over week (within"
X Link 2026-02-08T11:29Z [----] followers, [---] engagements

"🛠 DevLog SaltStack Infra: First End-to-End Miner Tests Weve now run end-to-end tests of the new SaltStack setup - not just in theory but all the way through to real miner management: 🔹 What We Just Verified - Brought up a full cortensord miner setup via Salt: install configure systemd service start/stop. - Confirmed the Global Server Instance config hierarchy works as intended for basic flows (chain IDs RPC models GPU flags etc.). - Validated that upgrades + config changes can be pushed centrally without manual SSH. 🔹 Whats Next - This week well start using the SaltStack stack to manage"
X Link 2026-02-08T22:24Z [----] followers, [---] engagements

"🛠 DevLog #L3 Fee Experiment & Deflationary $COR Mechanics (Testnet-1A) 🔹 Week [--] Base Fee Bump (0.01 Gwei) - L3 base fee on Testnet-1A set to [----] Gwei (Feb [--] 7:55 PM PST). - Fee collector were using as the main gauge: - Balance so far: - Start: [----------] $COR - 5h later: [----------] $COR 🔹 What This Experiment Is For - Use the next [--] days to see how much L3 execution can earn in fees at this base fee level (with [---] nodes active). - Each week well 10x the base fee on testnet then measure again rough curve of: - L3 fee generation - Per-miner economics - How sensitive behavior is to base fee"
X Link 2026-02-09T11:20Z [----] followers, [---] engagements

"🛠 DevLog SaltStack RPC Support for Self-Managed L3 🔹 Weve added RPC setup/management modules to the SaltStack repo so node ops can eventually run their own #L3 RPC endpoints. Salt states: Pillar config: 🔹 Design Notes From last weeks tests an L3 RPC node only needs a relatively small disk since L1/L2 data can come from remote RPCs (e.g. Alchemy). This keeps self-managed L3 more affordable while still giving operators local control over their L3 read/exec path. 🔹 Whats Next Not fully tested in the wild yet - this week well use these RPC modules to stand up an L3 stack via Salt. Goal: once"
X Link 2026-02-09T12:31Z [----] followers, [---] engagements

"🛠 DevLog MCP + ERC-8004 Interop Patch Live on Corgent & Bardiel Weve now applied the MCP + ERC-8004 interop patch to the mainnet Corgent/Bardiel agents and started testing it in-place. 🔹 What Changed - Tweaked MCP stream + metadata behavior so clients that expect more static agent/tool info (like 8004scan) can read health status cleanly. - Redeployed the router nodes behind the mainnet agents with the updated MCP behavior. 🔹 Where Its Live Corgent (mainnet): Bardiel (mainnet): 🔹 What Were Testing Now - Verifying theres no regression with standard MCP clients (OpenAI Claude Tools etc.)"
X Link 2026-02-09T22:53Z [----] followers, [---] engagements

"🛠 DevLog #MCP + #ERC8004 Interop Patch: Testing Regression Monitoring Weve enabled the new #MCP static advertisement payload on the router endpoints behind the mainnet Corgent and Bardiel #ERC8004 agents and are now focused on testing + monitoring rather than adding new behavior. 🔹 Whats Under Test New MCP discovery response that advertises tools categories and protocol info up front so 8004scan can read agent health correctly. Config-gated behavior on the mainnet router nodes backing Corgent and Bardiel (no change to core routing logic or task execution). 🔹 Where Its Running Corgent"
X Link 2026-02-10T02:26Z [----] followers, [---] engagements

"🛠 DevLog Corgent & Bardiel #MCP / #ERC8004 Interop Confirmed Healthy 🔹 Whats Now Working 8004scan now shows both mainnet agents as Healthy and fully MCP-compatible. MCP static advertisement payload is live and tool discovery works as expected (10 tools exposed per endpoint). 🔹 Where You Can See It Corgent (mainnet agent): Bardiel (mainnet agent): Corgent MCP: Bardiel MCP: 🔹 What We Verified Standard MCP clients (OpenAI-style Claude tools) still discover and call completions / validation / sessions without regressions. 8004scans endpoint test view can list and ping all tools confirming the"
X Link 2026-02-10T06:40Z [----] followers, [---] engagements

"🛠 DevLog #MCP/#ERC8004 Looking Solid Shifting Focus to Data Mobility + /delegate 🔹 MCP / ERC-8004 Status Looks Solid Corgent and Bardiel #MCP endpoints are now showing Healthy on 8004scan and tool discovery works end-to-end. Standard MCP clients (OpenAI / Claude tools) are behaving as expected so were moving MCP to monitor only for now. 🔹 Data Mobility Designing Export/Import for Core Modules Focus this week: admin-level import/export for key data modules so L3s can be migrated or hard-forked cleanly: - Session data - Session queue data - Payment data Node Pool data is largely"
X Link 2026-02-10T10:44Z [----] followers, [---] engagements

"🛠 DevLog Secondary #MCP Endpoints for /delegate Work 🔹 New MCP iteration endpoints (Testnet-1A) Corgent: Bardiel: 🔹 Why Keep the primary MCP endpoints focused on ERC-8004 agents + 8004scan health. Use these secondary endpoints for /delegate experiments breaking changes and fast iteration. 🔹 Whats next Continue expanding the static MCP advertisement (tools + params). Start wiring /delegate as an MCP tool on these endpoints before mirroring anything back to the main surfaces. #Cortensor #DevLog #MCP #Delegate #Corgent #Bardiel #AgenticAI https://router1-t1a.bardiel.app/mcp/messages"
X Link 2026-02-10T22:42Z [----] followers, [---] engagements

"🛠 DevLog #L3 Self-Managed Status Disk Growth & Mock Mainnet Dry Run 🔹 Self-Managed L3 Holding Up (RaaS Paused for Now) - Were decommissioning the RaaS L3 track for the moment the self-managed L3 (Testnet-1A) is stable enough to be our primary focus. - If/when we need it again spinning up a fresh RaaS L3 only takes a few minutes so this is a pause not a permanent removal. 🔹 Real Disk Growth Numbers (Sequencer Focus) - Sequencer disk usage went from [--] GB (Jan 26) to [---] GB (Feb 10). - Thats roughly +100 GB over [--] days [--] GB/day with [---] active miners. - For now the sequencer (plus"
X Link 2026-02-11T04:05Z [----] followers, [---] engagements

"Staking APR Adjustment Reminder (Feb [--] 2026) Quick reminder that the next scheduled $COR staking APR step-down goes live on Feb [--] [----] as part of the long-term sustainability plan. 🔹 New APR (effective 2/28/2026) - Pool 3: 10% APR - Pool 2: 5% APR - Pool 1: 2% APR Lock periods and staking mechanics stay the same - only the reward rates are adjusting along the previously published curve as the network matures. More details here: #Cortensor #Staking #COR #DePIN https://docs.cortensor.network/community-and-ecosystem/staking-pool-overview#apr-breakdown Staking APR Adjustment Reminder (Feb 28)"
X Link 2026-02-11T06:04Z [----] followers, [---] engagements

"🛠 DevLog Session / Task Data Mobility (First Contract Sketch) Weve started wiring the data mobility layer on the contract side for Session + Session Queue / Task data. 🔹 Whats In Rough Shape - Session Data module - Admin getters with pagination (e.g. getUserSessionsCount getUserSessionsBatch getNodeLastAssignedTimestamp). - First pass of importSession(.) so sessions can be recreated on a new deployment with owner state SLA node lists router metadata etc. - Session Queue / Task module - Migration getters for tasks (getTaskCount getSessionTasksBatch etc.) plus extra getters for decorations /"
X Link 2026-02-11T07:56Z [----] followers, [---] engagements

"🛠 DevLog Session / Task Data Mobility Deployed (Testnet-0 First) Weve now deployed the Session Data and Session Queue / Task modules with their first-pass import/export functions. 🔹 Whats Live - Session module with admin read + importSession(.) support. - Session Queue / Task module with migration-friendly getters and import hooks. Because these imports will reset / rewrite state were treating Testnet-0 (#Arbitrum #Sepolia) as the sandbox for this: - Use Testnet-0 to exercise export serialize import flows end-to-end. - Start building small off-chain tooling to run full migrations (sessions"
X Link 2026-02-11T11:12Z [----] followers, [---] engagements

"🛠 DevLog Designing Migration Tools for Session / Task Data (Pre-Migration Stage) We havent started any live migrations yet - were focused on designing the tooling that will eventually power #L3 hardforks and module upgrades. 🔹 What Were Working On - Designing off-chain tools that will: - Read Session and Session Queue state via the new admin/paginated getters. - Serialize that state into a portable format for backups / snapshots. - Replay it into a new Session / Session Queue module using the on-chain import functions. - Intended use cases: - Planned hardforks of the #L3 orchestration"
X Link 2026-02-11T22:01Z [----] followers, [---] engagements

"From Cute Agents to a Real Agent Economy: /delegate + /validate 🔹 Two primitives decide whether agent economy is real or just demoware: - /delegate offload work into a scalable execution fabric (fast vs safe tiers) - /validate external checkpoint before actions/payments (VALID / INVALID / RETRY / NEEDS_SPEC) 🔹 On #Cortensor those live in two places: - #Corgent infra-native trust & execution oracle for agents & protocols (#ERC8004 etc.)./delegate + /validate here are minimal policy-driven services sitting closest to the Router + PoI/PoUW stack. - @BardielTech #Virtual-first service agent"
X Link 2026-02-12T02:20Z [----] followers, [---] engagements

"🛠 DevLog Session Data Mobility: First Export Pass We now have the first working export path for Session data on Testnet-0. 🔹 Whats Working - New off-chain Session export tool walks sessions in batches and writes: - one session_id.json per session plus - helper files (user_sessions node_mappings router info manifest etc.). - Counts and basic fields line up with on-chain state (no deep validation yet but structure looks correct). 🔹 Whats Next - Finish the matching import tool to replay these JSON sessions into a fresh Session module (future L3 hardfork / reset target). - If this pattern"
X Link 2026-02-12T04:17Z [----] followers, [---] engagements

"💡 Community Spotlight - Monthly Reward: Tools & Infrastructure Each month we reward community members who maintain and improve the critical tools and infrastructure that keep Cortensor's decentralized network running. This month's recipients: 🔹@01_choose Community RPC Node 🔹@ItsMeCryptality Node Monitoring Bot These contributions help node operators and developers onboard monitor and maintain reliable performance - making the network more resilient accessible and efficient. 📌 Access these tools or contribute your own: Thank you to all builders driving the decentralized AI movement"
X Link 2026-02-12T08:13Z [----] followers, [---] engagements

"🛠 DevLog Session Data Mobility Tooling (Export Import Verify) We now have a full export / import / validation loop working for the Session Data module on Arbitrum Sepolia. Target SessionData (new module dry run): 🔹 Whats Working - Export tool walks the current Session Data module in batches and writes local JSON. - Import tool reads that export bundle and recreates sessions + derived mappings in the new Session Data contract. - Validation tool runs twice: - Before import: compares exported JSON vs the original contract state. - After import: compares the new contract vs the original. -"
X Link 2026-02-12T10:38Z [----] followers, [---] engagements

"🛠 DevLog Session Queue Data Mobility & Testnet-0 Reset Weve finished the Session Queue data mobility changes but testing them properly requires a fresh deployment. 🔹 Whats Changing Today The old Session Queue contract on Testnet-0 (Arbitrum Sepolia) doesnt expose the new export/import getters we need. Well redeploy the Session + Session Queue data modules on Testnet-0 so both use the new migration-aware interfaces. As part of this Testnet-0 session / queue data will be reset today. 🔹 What Happens Next Re-run the same flow we used for Session data: Export Session Queue state from the old"
X Link 2026-02-12T20:12Z [----] followers, [---] engagements

"🛠 DevLog Session & Session Queue Migration Modules Live on Testnet-0 Weve deployed the latest Session Data and Session Queue contracts on Testnet-0 (Arbitrum Sepolia) the versions that include full admin import/export hooks so we can run real end-to-end migration tests. 🔹 Whats Now in Place - Both modules expose the new migration functions (export + import) needed to: - Move sessions and queue/task state into local JSON snapshots. - Replay that state into a fresh deployment for hardfork / L3 rotation experiments. - This required redeploying the Session/Queue pair on Testnet-0; earlier"
X Link 2026-02-13T01:48Z [----] followers, [---] engagements

"🛠 DevLog Session Queue Data Mobility: Export Import Validate We ran the same migration pattern we used for SessionData this time on SessionQueueData on Testnet-0. 🔹 What We Just Verified - Exported SessionQueueData (tasks + task results + per-session stats) from the current module into local JSON files. - Ran an export-side validation tool to compare on-chain data vs. the exported files [--] mismatches. - Imported the exported data into the new SessionQueueData module with the admin import functions. - Ran an import-side validation tool against the original source module again [--] mismatches"
X Link 2026-02-13T07:53Z [----] followers, [---] engagements

"🛠 DevLog Sunsetting RaaS #L3 (For Now) Were now comfortable running our self-managed #L3 so were sunsetting the RaaS #L3 by the end of today. 🔹 Why were turning it off - Focus ops and monitoring on a single self-managed #L3 instead of splitting attention. - Reduce extra moving parts while we iterate on fees data mobility and node tooling. 🔹 Not gone forever - Spinning up a new RaaS-based #L3 is now a well-understood path and only takes a short setup cycle. - If/when we need another L3 track (experiments staging or partner work) well bring it back with a fresh deployment. For now the main"
X Link 2026-02-13T09:13Z [----] followers, [---] engagements

"🛠 DevLog Session Payment Data Mobility (Export / Import / Validate) Weve now wired up and dry-run migration tooling for the SessionPaymentData module. 🔹 Whats Working - Built export tooling that pulls session-level payment state (per-node balances pending payments/credits totals globals) into local JSON. - Added import tooling that replays that snapshot into a new SessionPaymentData contract. - Implemented import-side validation: source vs target sessions + nodes now compare cleanly with mismatches = [--] in our test runs. 🔹 Why It Matters - This completes the first migration loop for the"
X Link 2026-02-13T11:08Z [----] followers, [----] engagements

"🛠 DevLog Full #L3 Data Mobility Rehearsal (Sessions / Queue / Payments) Weve moved from unit tests to full end-to-end migration / integration testing for the three primary data modules. 🔹 What Were Testing Now - Full export import validation loop on Testnet-0 for: - SessionData (sessions + user mappings) - SessionQueueData (tasks decorations request params task results) - SessionPaymentData (per-node balances pending payments/credits globals) - Flow under test: - Export state from the current contracts into local JSON snapshots. - Run source vs snapshot validation to ensure exports match"
X Link 2026-02-13T20:53Z [----] followers, [---] engagements

"🛠 DevLog Data Mobility E2E Integration Test (Sessions / Queue / Payments) We just ran a full export import relink rehearsal for the three core data modules on Arbitrum Sepolia (Testnet-0). 🔹 New Target Modules (Post-Migration) - SessionData: - SessionQueueData: - SessionPaymentData: 🔹 Source Modules (Pre-Migration Reference) - SessionData (old): - SessionQueueData (old): - SessionPaymentData (old): 🔹 What We Verified So Far - Exported all session queue/task and payment state from the old modules into local JSON snapshots. - Imported those snapshots into the new contracts above and"
X Link 2026-02-14T02:14Z [----] followers, [---] engagements

"🛠 DevLog Data Mobility: First Pass Complete Weve finished this round of data mobility work by adding the same export/import/validation pattern to NodePoolData and NetworkData on top of the earlier core modules. 🔹 Whats Covered Now - Session data - Session queue / task data - Session payment (pay-per-use) - Node pool data - Network data All five now support: export validate against source import to a new contract validate again with clean round-trips in dry runs. 🔹 What This Enables - Practical #L3 hardforks / rotations with preserved sessions queues payments node registry and network"
X Link 2026-02-14T09:14Z [----] followers, [---] engagements

"🛠 DevLog Lightweight Agent Framework Experiments on the Router Node Weve been quietly poking at a few open-source agent frameworks/orchestrators and using them as inspiration for something more native to Cortensor. 🔹 What Were Experimenting With - Tested several existing agent frameworks but its becoming clear it may be cleaner to borrow the patterns not the entire stack. - Goal is a lightweight agent framework inspired by OpenClaw ported and improved in Python that can run directly on the Router Node. - Design focus: tightly coupled with Cortensors infra (sessions PoI/PoUW node pool"
X Link 2026-02-15T12:34Z [----] followers, [---] engagements

"🛠 DevLog #Arbitrum #L3 Dry-Run: Batch Poster & Validator Live Following the first Arbitrum mainnet L3 dry-run weve now wired up the core L3 actors and will start watching real gas behavior. 🔹 Whats Live on Arbitrum Mainnet - Batch poster / sequencer: - Validator: - Setup feels effectively identical to Testnet-1A: same L3 stack just pointed at Arbitrum mainnet instead of Sepolia. - Well be monitoring these two addresses for batch posting + validation gas usage over time to get a real cost profile for L3 operations. 🔹 Whats Next (Still Experimental) - Bring up the remaining pieces"
X Link 2026-02-16T11:06Z [----] followers, [---] engagements

"🛠 DevLog Bridging Real $COR Into Pre-Mainnet L3 (Light E2E Test) 🔹 L2 L3 Bridge Dry-Run (Real $COR) - Sent [--] $COR from Arbitrum L2 mainnet Arbitrum Orbit L3 (Pre-Mainnet-1A) as a light end-to-end test. - L2 bridge tx: - L3 receive tx (Pre-Mainnet-1A): 🔹 What This Tells Us - Basic L2 L3 bridge wiring for $COR is working as expected on the pre-mainnet environments (1A/1B). - Confirms that the current pre-mainnet L3 setup behaves similarly to Testnet-1A from an ops / UX perspective just with real ETH + real $COR behind it. 🔹 Next Steps Mainnet RPC & Cost Awareness - Well likely need to"
X Link 2026-02-17T10:22Z [----] followers, [---] engagements

"🛠 DevLog /delegate & /validate v2: Core Primitives for Agent-Scale & Safety Were rolling out v2 versions of /delegate and /validate while keeping v1 fully supported. These two endpoints are shaping up as the core primitives for how agents safely scale on Cortensor. 🔹 What /delegate Does (Execution Primitive) - Think of /delegate as send this job to the network. - v1: simple prompt single completion. - v2: lets agents offload a small bounded workflow with tools max-step limits and guardrails so they dont have to manage infra retries or parallelism themselves. - It returns structured evidence"
X Link 2026-02-17T12:37Z [----] followers, [---] engagements

"🛠 DevLog Corgent MCP Endpoint & Light ERC-8004 Wiring for Phase #2 Weve set up the basics so Phase #2 can start exercising Corgent through #MCP + #ERC8004 again with deeper Corgent work planned for later phases. 🔹 Whats New Right Now (Light #MCP Integration) - MCP endpoint for Corgent / Router Node (for early /delegate + /validate experiments): - #ERC8004 testnet registry was reset so Corgent has been re-registered for testnets: - Eth Sepolia agent: - Base Sepolia agent: 🔹 How This Fits Into the Roadmap - Phase #2: Light #MCP integration only enough to exercise Corgent via #MCP and route a"
X Link 2026-01-16T07:07Z [----] followers, [----] engagements

"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"
X Link 2026-02-02T23:27Z [----] followers, [----] engagements

"Everyone wants the agent economy: Autonomous agents watching markets AI ops-goblins maintaining infra Personal copilots running in the background 24/7 But under all of that hype is a boring brutal http://x.com/i/article/2019376732147707911 http://x.com/i/article/2019376732147707911"
X Link 2026-02-06T22:05Z [----] followers, [----] engagements

"🛠 DevLog #L3 Base Fee Probe on Testnet-1A Weve kicked off a small economics experiment on the self-managed #L3 (Testnet-1A) to understand what realistic gas flows look like for miners. 🔹 What We Just Changed - Updated the L3 base fee to [----] Gwei on Testnet-1A (applied around Feb [--] 7:55 PM PST). - Fee collector were using as the main gauge: - - Starting snapshot for this experiment: - Collector balance: [----------] $COR at the time of the change. 🔹 What Well Measure Next - Let the network run under normal task load for about a week then: - Calculate balance / [--] days to get a rough daily"
X Link 2026-02-09T04:09Z [----] followers, [----] engagements

"🛠 DevLog /delegate & /validate as Core Agent Primitives Since we just shared the longer X article heres the compact builder view recap for Cortensor: 🔹 Two Primitives Were Standardizing - /delegate elastic execution fabric for agents (think AWS for agents): offload heavy work tools and sub-agents to the Cortensor network under clear SLAs. - /validate safety checkpoint before actions/payments: ask the network to judge results (VALID / INVALID / RETRY / NEEDS_SPEC) using PoI/PoUW + validators. 🔹 How This Fits Corgent & Bardiel - Corgent infra-native surface for ERC-8004 and agent frameworks"
X Link 2026-02-15T05:13Z [----] followers, [---] engagements

"🛠 DevLog First #Arbitrum #L3 Dry-Run on Mainnet We ran our first experimental #L3 deployment on Arbitrum mainnet as a dry-run to validate costs and flow. 🔹 Deployment Snapshot - Custom chain ID: [-----] - Tx: - Deploy time: 11.59s - L2 gas cost: $0.31 (for full L3 stack bring-up) 🔹 Whats Next (Still Experimental) - Run additional dry-runs this week including: - Validator Sequencer wiring for rollup txs into Arbitrum mainnet. - Comparing real gas usage vs. Arbitrum Sepolia (deploy validator reports sequencer batches). - Treat this strictly as an ops + cost probe not a mainnet ready signal."
X Link 2026-02-16T06:03Z [----] followers, [---] engagements

"🗓 Weekly Focus Phase #2 Hardening L3 Ops & Agent Surfaces 🔹 Testnet Phase #2 Stability & Support - Continued active monitoring across routing miners validators oracles indexers and dashboards. - Followed up on abnormal node states and kept Phase #2 environments stable. 🔹 Testnet-1a (Self-Managed L3) Ops + Replay/Break Testing - Continue replay/break-testing and recovery validation on Testnet-1a. - Run base fee adjustment exercises and fold learnings into the L3 ops playbook (including rough operational cost insights). 🔹 Hackathon #4 Support - Continued supporting builders with asks"
X Link 2026-02-16T08:20Z [----] followers, [---] engagements

"🛠 DevLog Arbitrum #L3 Pre-Mainnet-1A Dry-Run (Full Cortensor Stack) Weve started a pre-mainnet-1A #L3 dry-run on Arbitrum mainnet to rehearse what a real Cortensor #L3 bring-up will look like end-to-end and to avoid surprises later by applying our ops playbook against real mainnet conditions. 🔹 Whats Already Live - L3 deployment tx (rollup bring-up): - Batch poster / sequencer address: - Validator address: - Explorer: 🔹 What This Dry-Run Is For - Deploy and wire the full Cortensor module set (Sessions Queue Payments NodePool etc.) on this L3 to: - Measure real L3 deployment + module"
X Link 2026-02-16T23:30Z [----] followers, [---] engagements

"🛠 DevLog L3 Base Fee [--] Step-Up on Testnet-1A 🔹 Weve increased the L3 base fee on Testnet-1A by [--] as part of the ongoing fee + economics probing. - New base fee: [---] gwei [---------] wei [------------] $COR per gas unit. - Fee collector (for this experiment): - Current starting balance at the time of change: [----] $COR (approx). 🔹 What Well Observe This Week - How much $COR L3 gas accumulates under current network load (with [---] miners). - Rough daily fee generation vs. miner count and task volume. - Whether this base fee level has any visible impact on miner behavior or routing. 🔹 Next Step"
X Link 2026-02-17T02:35Z [----] followers, [---] engagements

"🛠 DevLog #A2A Agent Card Support on the Router Node Weve wired the Cortensor Router Node to speak #A2A (agent-to-agent) so other agents can discover how to use /delegate /validate and #MCP without guessing configs. 🔹 Agent Card Discovery - The router now serves a machine-readable agent card JSON (A2A schema) describing the router as an agent surface. - It advertises: - Available endpoints: /delegate v1+v2 /validate v1+v2 /completions - Where MCP lives (SSE + Streamable HTTP URLs) - Whether x402 is enabled and which x402 endpoint to call 🔹 What A2A Does (and Doesnt) - Its a discovery layer"
X Link 2026-02-17T13:34Z [----] followers, [---] engagements

"🛠 DevLog Router v2 Agentic Features: Local Shakedown Then Iteration All the new router-side agentic upgrades from the last [--] hours - /delegate v2 /validate v2 generalized #MCP and #A2A agent card support - are wired up behind the scenes but not yet exposed on public endpoints. 🔹 Current Plan - Well first run everything locally: #MCP + #x402 flows with completions delegate v1/v2 and validate v1/v2 to catch regressions. - Once that looks clean well roll the new router build onto Testnet-1A and point the #Corgent/#Bardiel endpoints there for live testing. - After a round of monitoring and"
X Link 2026-02-18T00:47Z [----] followers, [---] engagements

"🛠 DevLog Corgent & Bardiel Upgraded With #MCP + #A2A Skills Corgent and Bardiel have now been upgraded to the new MCP + A2A surface and 8004scan is reading both tools and skills correctly. 🔹 Where You Can See It - Corgent on 8004scan: - Bardiel on 8004scan: Both now show: - MCP tools: completions delegate v1/v2 (+ trial) validate v1/v2 (+ trial) info about etc. - A2A skills card: completions delegate_v1 delegate_v2 validate_v1 validate_v2 wired to the new router endpoints. 🔹 Session Mapping (Testnet1a Router Backends) Corgent router sessions - Default: - Completions: - Delegate: -"
X Link 2026-02-18T11:19Z [----] followers, [---] engagements

"🛠 DevLog Why Were Building Pyclaw for Open Models 🔹 The Problem: Agent Loops Are Quietly Expensive - Running a real agent today is way more expensive than most people admit. - A simple loop like: @8004xbt (This used for experiment and estimate the costs) - scout X / web for #ERC8004 trends - hand off to a drafting sub-agent - post like a human (timing cadence behavior) - report back with a summary - On full #Claude / top-tier APIs that kind of pipeline can easily land in the $2$5 per post range. - Now scale that to: prediction markets monitoring tasks research agents or anything 24/7 -"
X Link 2026-02-19T03:13Z [----] followers, [---] engagements

"🛠 DevLog Multi-RPC Rollout Looking Stable (Next: Cleanup & Merge) 🔹 Quick update on the new multi-RPC round-robin path in cortensord (PR #211): so far its behaving stably under testnet load - rotation works and were not seeing obvious regressions on task success or block lag. - If things stay stable over the next few hours well: - Clean up the remaining debug logs and temporary tracing. - Rebuild binaries with the finalized multi-RPC core. - Merge this work into the main branch so it becomes the default code path going forward (still opt-in via env flags). Once merged well ship updated docs"
X Link 2026-02-06T06:08Z [----] followers, [---] engagements

"🛠 DevLog Multi-RPC Support Now Merged into Main Quick follow-up on the multi-RPC work for cortensord: 🔹 Status Update - The new multi-RPC round-robin core is now merged into the main branch. - Behavior is still opt-in via env flags: - ENABLE_MULTIPLE_RPC_HOST - NUM_RPC_HOST - RPC_HOST_0 . RPC_HOST_N-1 🔹 What This Means for Node Ops - Default behavior is unchanged if multi-RPC is disabled. - If enabled cortensord will rotate across multiple RPC endpoints helping: - Spread load across public/free RPCs. - Reduce risk of rate limits or single-provider issues. Next steps: well keep watching"
X Link 2026-02-06T10:17Z [----] followers, [---] engagements

"https://testnet1a-explorer.cortensor.network/address/0xEa342E0A09FE3CB19245E49422bfea993b6864d1 https://testnet1a-explorer.cortensor.network/address/0xEa342E0A09FE3CB19245E49422bfea993b6864d1"
X Link 2026-02-09T04:06Z [----] followers, [--] engagements

"🛠 DevLog Secure LLM Worker Gateway: E2E (Default + DeepSeek Builds) We've expanded Gateway container testing by building images for both the default model and DeepSeek - first step toward rolling this out across all supported models. 🔹 Current Status - Gateway-enabled containers built for default model + DeepSeek. - Local e2e tests show Gateway + LLM worker working side by side. - Cortensord integration confirmed in dev mode. 🔹 Next Steps - Build remaining gateway-enabled images for all models. - Run full e2e trials on remote servers/miners with NodeOps. - Plan stability runs next week"
X Link 2025-09-19T23:20Z [----] followers, [----] engagements

"💡 Community Spotlight Claim Check Oracle One of the entries in Hackathon #3: Claim Check Oracle is a web app for verifying factual claims using decentralized AI on Cortensor. Instead of trusting a single model or a single source it combines web search + decentralized evaluation to deliver more transparent balanced fact-checking. How It Works 🔹 Submit a Claim Add optional context or reference links 🔹 Web Discovery The system searches the web for relevant information 🔹 Decentralized Evaluation Cortensor miners review and score the claim 🔹 Structured Result Returns: - Verdict (true / false"
X Link 2025-12-31T01:28Z [----] followers, [---] engagements

"🛠 DevLog Session Payment Module Refactor (In Progress) Todays focus is refactoring the pay-as-you-go path ahead of Phase #2. 🔹 What Were Doing - Separating business logic + funds from data storage for pay-as-you-go. - SessionPayment will remain the balance-holding / execution logic module. - A new SessionPaymentData module will own all tables/records (mirroring the staking side pattern). 🔹 Why It Matters - Keeps the $COR / token-holding contracts stable while allowing business logic and data schemas to evolve more safely. - Aligns pay-as-you-go with the existing SessionPaymentStaking"
X Link 2026-01-13T20:33Z [----] followers, [----] engagements

"🛠 DevLog SessionPayment Refactor (Phase [--] Complete) First pass of the SessionPayment / SessionPaymentData refactor is now in place logic and data are separated at the contract level but still pending full regression. Whats Done 🔹 SessionPayment now focuses on business logic + funds while SessionPaymentData holds the underlying records/state. 🔹 The same pattern is being mirrored toward SessionPaymentStaking so both paths can evolve more safely over time. 🔹 Dev versions of the contracts are deployed on #Arbitrum #Sepolia for local + E2E payment flow testing. Whats Next 🔹 Run full"
X Link 2026-01-14T06:39Z [----] followers, [----] engagements

"🗓 Weekly Recap Phase #2 Kickoff 4-Testnet Setup & Payments Refactor Progress This week we completed the Phase #2 prep work brought up all planned environments and officially kicked off Testnet Phase #2. 🔹 Testnet Phase #2 Final Prep + Hackathon #4 Setup - Final Phase #2 readiness work completed across infra docs and ops checklists. - Hackathon #4 prep is in place and queued to launch after Phase #2 stabilizes targeting Mon 1/19/2026. 🔹 Payments Module Refactor (Data Isolation) - Payment module refactoring and data isolation work largely completed. - Exception: SessionPaymentStaking hit the"
X Link 2026-01-17T22:01Z [----] followers, [---] engagements

"🗓 Weekly Focus Phase #2 Stabilization Self-Managed #L3 Load Hackathon #4 Kickoff Testnet Phase #2 is live. This week is about keeping all environments stable shifting stress testing toward the self-managed L3 and supporting Hackathon #4 as it kicks off in 24h. 🔹 Testnet Phase #2 Support & Stability - Monitor and stabilize all Phase #2 environments (routing miners validators oracles indexers dashboards). - Fast turnaround on abnormal node states and any environment-specific failures. 🔹 Testnet-1a Capacity + Automated Stress Tests - Move more nodes onto Testnet-1a (self-managed $COR #L3) to"
X Link 2026-01-19T07:30Z [----] followers, [----] engagements

"🚀 DevNet #3 Update: Node Reputation UI is Live Phase #1 wrapped up last week and we're now in the Phase #2 grace periodperfect timing to test the latest Node Reputation UI on DevNet #3 📊 You can now explore reputation data directly in the NodeStats subpage by clicking individual metrics. 🔗 Example Links: 👉 👉 👉 👉 👉 🛠 This is bleeding-edge so expect some bugs. Let us know if you find anything and explore the updates 💬 Join the discussion on Discord: #Cortensor #AI #DePIN #DevNet3 #NodeReputation #Dashboard #Phase2Testing http://discord.gg/cortensor"
X Link 2025-02-05T20:52Z [----] followers, [----] engagements

"🚀 Node Ping Metric - Uptime & Availability UI Coming Soon Were rolling out a new NodeStats Ping Metric UI to help node operators track their uptime and availability directly from the dashboard. 🔹 Whats New ✔ Visual uptime tracking via a heatmap-style dashboard. ✔ Real-time availability insights to monitor node stability. ✔ Easy access under Node Stats Ping Metric 🛠 Currently under dev branch but will be released soon 📊 Keep your nodes healthy & ready for Phase #2 testing. 🔗 Dashboard: 💬 Join the discussion: #Cortensor #AI #DePIN #NodeStats #DecentralizedAI http://discord.gg/cortensor"
X Link 2025-02-06T13:03Z [----] followers, [----] engagements

"🚀 Node Ping Metric - Uptime & Availability UI is Now Live The bleeding-edge version is here but you can already try it out 🔹 What You Can Do Now: ✅ Monitor your nodes uptime & availability in real-time. ✅ View historical ping data directly from the NodeStats section. ✅ Identify failures & optimize node performance. 📊 Check it out on the dashboard: 🔗 🔍 Example Node Stats: 👉 👉 👉 💬 Join the discussion on Discord: 🔗 This is just the beginningmore improvements are coming Stay tuned. #Cortensor #AI #DePIN #NodeStats #UptimeTracking http://discord.gg/cortensor"
X Link 2025-02-07T03:02Z [----] followers, [----] engagements

"🚀 Final Week of Grace Period Phase #2 Testing Begins Soon Were nearing the end of the grace period and Phase #2 testing is set to begin early to mid next week. Before launching we will reset the NodeStats and Reputation module datasets to ensure a clean slate for testing. 🔹 Whats Coming in Phase #2 - 📊 Node Reputation & Performance Refining task allocation based on reputation. - 📈 Node Uptime & Ping Metrics Improving real-time tracking for node stability. - ⚙ Node Operation Enhancements Optimizing system efficiency and reliability. - 🖥 Node Pool UI Integration Visualizing ephemeral node"
X Link 2025-02-10T09:22Z [----] followers, [----] engagements

"🚀 Final Weekend Before Phase #2 Last Chance to Get Ready Were entering the final weekend before Phase #2 testing officially begins next week 100+ nodes onboarded so farthis is your last chance to prepare before NodeStats & Reputation datasets are reset for a fresh testing cycle. 🔹 Phase #2 Key Highlights 📊 Node Reputation & Performance Task allocation based on reputation. 📈 Node Uptime & Ping Metrics Real-time tracking for stability & reliability. ⚙ Node Operation Enhancements Optimizing system efficiency. 🖥 Node Pool UI Revamp Improving transparency & usability. 🧪 Experimental"
X Link 2025-02-15T07:30Z [----] followers, [----] engagements

"Phase #2 Testing Begins NodeStats & Reputation Reset The NodeStats & Node Reputation modules have been reset officially kicking off Phase #2 testing 🔍 What Were Testing in Phase #2: ✅ Node Reputation & Performance Task allocation based on reputation scoring. ✅ Node Uptime & Ping Metrics Tracking stability & real-time node health. ✅ Node Operation Enhancements Optimizing overall system efficiency. ✅ Node Pool Selection & UI Integration Visualizing ephemeral nodes. ✅ Experimental Ephemeral Node Selection Testing Oracle Node-driven allocation. 💬 Join the Discussion: #Cortensor #AI #DePIN"
X Link 2025-02-17T10:24Z [----] followers, 10.6K engagements

"(1/17) Understanding #Cortensor's Core Modules & Node Initialization #Cortensors decentralized AI network is powered by key modulesACL IAM Cognitive SessionQueue Session NodeStats and NodeReputation. These ensure security efficiency and scalability in AI inference. Lets break it down #AI #DePIN #Cortensor #Blockchain https://twitter.com/i/web/status/1902533306698363284 https://twitter.com/i/web/status/1902533306698363284"
X Link 2025-03-20T01:31Z [----] followers, [----] engagements

"(11/17) Cognitive Module: AI Task Orchestration 🧠 The Cognitive Module executes Proof of Useful Work (PoUW) to organize inference tasks. It determines: 🔹 Task priority & complexity 🔹 Miner selection based on capability & uptime 🔹 Precommit & commit validation #AI #DePIN #Cortensor #AIInference"
X Link 2025-03-20T01:31Z [----] followers, [---] engagements

"(12/17) NodeStats: Performance Tracking 📈 NodeStats monitors: 🔹 Task completion rates & uptime 🔹 Node behavior metrics (ping failures SLA compliance) Reliable nodes gain priority while underperforming ones are flagged. #AI #DePIN #Cortensor #PerformanceMetrics https://twitter.com/i/web/status/1902533329523765541 https://twitter.com/i/web/status/1902533329523765541"
X Link 2025-03-20T01:31Z [----] followers, [---] engagements

"(15/17) Step 1: Configuration & Security Checks 🛠 When a node starts it: 🔸 Loads contract addresses & keys 🔸 Prepares IPFS storage for AI task processing 🔸 Sets security parameters for network interaction 🔸 Initializes AI model verification for inference accuracy #AI #DePIN #Cortensor #Configuration"
X Link 2025-03-20T01:31Z [----] followers, [---] engagements

"(16/17) Step 2: Heartbeat & Global Ping 🌐 After configuration nodes: ✅ Begin regular pings (heartbeats) to NodeStats ✅ Update the Global Ping Counter tracking uptime ✅ Pass SLA checks before task eligibility ✅ Confirm readiness for network participation Once verified the node officially enters Active Mode qualifying for mining and inference tasks. #AI #DePIN #Cortensor #Uptime https://twitter.com/i/web/status/1902533338579268060 https://twitter.com/i/web/status/1902533338579268060"
X Link 2025-03-20T01:31Z [----] followers, [---] engagements

"(17/17) Cortensors Modular Advantage 📚 Cortensors core modulesACL IAM Cognitive SessionQueue Session NodeStats and NodeReputationenable: ✅ Trustless AI execution ✅ Scalable decentralized inference ✅ Web2 & Web3 interoperability Cortensor is future-ready modular and scalable. Lets unleash the future of AI togetherits $COR or nothing Reference: #AI #DePIN #Cortensor #ModularArchitecture https://docs.cortensor.network/technical-architecture/modular-architecture-and-smart-contract-interactions https://twitter.com/i/web/status/1902533340202467551"
X Link 2025-03-20T01:31Z [----] followers, [---] engagements

"(5/8) Cognitive Module - The AI Coordination Hub 🧠 The Cognitive Module is the command center for AI task execution powered by Proof of Useful Work (PoUW). 🔹 Request & Create States Task initialization and preparation 🔹 Commit State Miners submit verified outputs for validation 🔹 Feedback Loops Enhances AI performance through continuous learning This modular coordination ensures AI tasks are executed securely efficiently and transparently. 🔗 Learn more: #Cortensor #AI #DePIN #AIInference"
X Link 2025-03-24T20:22Z [----] followers, [---] engagements

"(6/8) NodeStats & NodeReputation - Tracking Performance 📊 Cortensors NodeStats module monitors miner activity while NodeReputation dynamically ranks miner performance. 📊 NodeStats Tracks: 🔹 Task completion rates & uptime 🔹 Node behavior metrics (ping frequency efficiency) 📊 NodeReputation Tracks: 🔹 Time-series tracking Long-term miner performance analysis 🔹 Dynamic ranking updates Prioritizing the most reliable nodes 🔹 Ephemeral status assignment Ensuring high-priority task execution This trustless scoring system ensures only high-quality nodes receive priority AI tasks. 🔗 Learn"
X Link 2025-03-24T20:22Z [----] followers, [---] engagements

"🎯 Cortensor Quiz Contest Question #22 Q22: What is the role of Node Reputation in Cortensor 👀@aixbt_agent what do you think 🏆 Best answer wins [----] $COR How to participate: [--] Drop your answer in the comments [--] Follow Like & RT this post [--] Tag [--] friends to spread the word Rules & Eligibility: 🔹 Must be a member of our Telegram or Discord 🔹 Only original community members with history are eligibleour mods will verify 🔹 Must hold $COR for at least a weekwallets will be checked 🔹 One participation per person for the 10-question series 🔹 No spam or AI-generated answersoriginality counts 🕒"
X Link 2025-03-26T06:51Z [----] followers, [----] engagements

"🧪 Phase #3 Testing Has Officially Begun Were now live with Phase #3 focused on scaling stress testing and refining Cortensors decentralized AI infrastructure. 🔹 Whats New: 🔸 New contracts deployed: CognitiveV1 NodeReputation NodeStats 🔸 High-frequency node sampling for real-time reputation 🔸 Node Pool iteration for ephemeral session routing 🔸 Module migration testing for smoother upgrades 🔸 Desktop App auto-install flow (Win/macOS/Linux) 🔸 Expanded Session UI & task flow handling 🔹 Core Focus: ✅ Network-wide stress tests ✅ Session & SessionQueue refinements ✅ [----] $COR staking check"
X Link 2025-04-16T07:50Z [----] followers, [----] engagements

"🛠 DevLog: NodeStats Ping Time Series Now Public via API Weve exposed NodeStats Ping history through the Dashboard API giving node operators the ability to build more advanced operational and uptime monitoring tools. 🔹 Track historical ping timestamps per node 🔹 Get last_active and timestamp_count 🔹 Perfect for uptime graphs alerts or custom dashboards 🔹 Used internally for heatmaps and rank scoring now open to all Example endpoint: Expect more time series metrics to be exposed as we keep expanding #Cortensor #DevLog #NodeMonitoring #Web3Infra #DePIN #AI #DecentralizedAI #CortensorAPI"
X Link 2025-05-01T07:22Z [----] followers, [----] engagements

"🛠 DevLog: Session Task Metrics Rewards & Penalties Integration Weve extended the existing Node Stats and Node Reputation modules to also track Session-related metrics - for now both network and user tasks will share the same stat/reputation system to simplify development. Whats New 🔹 SessionQueue now tracks user task performance directly 🔹 Integrated rewards & penalties for three task states: ack precommit & commit 🔹 In the commit phase the data hash is now verified against actual output - similar to how the Cognitive (Network Task) module operates This system lays the foundation for"
X Link 2025-05-17T12:36Z [----] followers, [----] engagements

"🛠 DevLog: Observability - Differentiating SessionStats vs NodeStats/NodeReputation As we expand metrics visibility across both network tasks and user tasks its important to understand how SessionStats differs from NodeStats/NodeReputation even though they use similar mechanisms like counters and timestamps. Heres a breakdown of the distinctions: 🔹 [--]. Focus & Perspective NodeStats/NodeReputation: Focus on how nodes perform - tracking state transitions like prepare precommit and commit or ack precommit and commit. SessionStats: Focus on which nodes are assigned to which sessions - tracking"
X Link 2025-05-20T08:54Z [----] followers, [----] engagements

"🛠 DevLog: NodeStats & NodeReputation Verified for User Tasks - Next Up: SessionStats Weve successfully verified that NodeStats and NodeReputation now fully track user task (session) performance on DevNet5. These metrics - originally built for network tasks - are now functioning across both task layers. 🔹 NodeStats Tracks how often nodes enter key user task states like ack precommit and commit along with point-based scoring to indicate long-term functionality and performance. 🔹 NodeReputation Now logs timestamps for each of these user task states on a per-node basis - enabling detailed"
X Link 2025-05-22T04:42Z [----] followers, [----] engagements

"🛠 DevLog: Weekly Recap & Dynamic Node Pool in Final Implementation & Testing This week we made solid progress across the board: 🔹 User Task Metrics - NodeStats & NodeReputation fully integrated for session-based tracking 🔹 Dashboard Updates - Node Pool and node performance visualizations live on DevNet5 🔹 Idle Detection - Ephemeral and reserved state idle handling now working 🔹 SessionStats - Deployed and wired into the Session module for assignment tracking 🔄 Still in Progress: Finalizing the first version of dynamic Node Pool capacity planning - under implementation now and targeted"
X Link 2025-05-24T23:05Z [----] followers, [---] engagements

"🛠 DevLog: Oracle V3 - Enforcing User Task Signals for Penalties So far user tasks (ack precommit commit) have been tracked primarily for reward signals - helping build up NodeStats and Reputation for positive contributions. Next step: were developing Oracle V3 to introduce penalty tracking for user task failures. 🔹 What Oracle V3 Will Do Penalize missed or invalid ack precommit and commit states Extend scoring logic from network tasks to user tasks Feed directly into NodeStats & NodeReputation Enable stronger filtering and miner quality assessment 🔹 Architecture Built as a standalone"
X Link 2025-05-26T21:53Z [----] followers, [----] engagements

"🛠 DevLog Stat Separation Planned for Phase #5 As Phase #4 continues we're preparing a key upgrade for Phase #5: separating network-level and user-level stats for better accuracy and control. 🔹 Current Limitation: - NodeStats and NodeReputation are shared between network tasks and user sessions. - This prevents resetting session metrics without affecting overall network data. - Some early session stats are skewed - but can't be cleanly corrected. 🔹 Coming in Phase #5: - NodeStats / NodeReputation: for network-level tracking - SessionStats / SessionReputation: for user inference sessions 🔹"
X Link 2025-06-25T04:10Z [----] followers, [---] engagements

"🛠 DevLog Stat Separation Now Implemented We've implemented the planned stat separation - and testing begins on DevNet5. 🔹 What's Live: - Dual tracking via NodeStats + new SessionStats for session + queue activity - Once validated well fully switch to SessionStats and SessionReputation for user task metrics This allows us to isolate reset and analyze user-level stats without affecting network-level data - a key step toward fairer tracking and future reward scoring. #Cortensor #DevLog #SessionStats #NodeStats #Phase5 #AIInfra #DePIN 🛠 DevLog Stat Separation Planned for Phase #5 As Phase #4"
X Link 2025-06-26T03:58Z [----] followers, [---] engagements

"🛠 DevLog Dashboard Backend Refactor: 3-Part Architecture As the Dashboard backend grows to handle deeper Web3 activity and real-time monitoring we've refactored it into three focused components: 🔹 [--]. Event Listener - Listens to key onchain events (NodeStats NodeReputation SessionStats SessionReputation NodePool Session SessionQueue) in real time 🔹 [--]. Indexer - Structures and processes event data - Generates Redis-cached time-series datasets for efficient tracking 🔹 [--]. API Service Layer - Serves structured data via RESTful endpoints - Powers the dashboard UI and external tools This modular"
X Link 2025-06-27T05:18Z [----] followers, [----] engagements

"🛠 DevLog Rough Design: CognitiveLevel Module for Smarter Network Task Evaluation We've drafted the initial version of the CognitiveLevel contract - a new module that manages performance-based levels for nodes handling network tasks modeled after patterns used in NodeStats and NodeReputation. 🔹 What It Does - Tracks per-node task outcomes: success/failure counts streaks and average token size - Oracle nodes can upgrade/downgrade a nodes level based on historical performance 🔹 How It Fits - The Cognitive module (which manages network-level tasks) reports completion to CognitiveLevel - Oracle"
X Link 2025-07-09T11:30Z [----] followers, [---] engagements

"Cortensor's Path to an AI-Native L1 From the beginning Cortensor has been built as a layered architecture: 🔹 L2 (Arbitrum / Base / others soon) fast low-cost interoperable. Perfect for onboarding early testing and community apps. 🔹 L3 (COR Rollup) tuned for AI. COR as native gas AI-specific economics and throughput optimized for inference and agent workloads. Beside L1 this dual-layer approach gives us both scalability today and AI-native design tomorrow. 🔹 So where does an L1 fit An L1 for Cortensor is not about "yet another blockchain." It's about anchoring the full AI stack - inference"
X Link 2025-08-17T01:11Z [----] followers, [----] engagements

"🧭 [----] Sneak Peek Agentic Roadmap on Router Node (Priorities & Staging) We're outlining the agentic track for [----] centered on evolving the Router Node into an agent-ready surface then wiring it into #ERC8004 and Virtual. Early experiments are happening now; most of this solidifies across [----] testnet/mainnet phases. 🔹 Router Node v1.5 "Router Agent" (Node-Operated [----] Early) - #x402 on Router Node per-router pay-per-call endpoints (e.g. completions) so node ops can offer paid inference services directly to Web2 clients and Web3 agents. - #MCP on Router Node MCP server/proxy on top of"
X Link 2025-11-17T12:03Z [----] followers, 12.1K engagements

"🛠 DevLog #MCP Endpoint Now Streamable-HTTP Compatible (Router Node Experimental) This week's #MCP work is still exploratory but we now have a proper #MCP server on the Router Node that supports both the latest spec and legacy transport. 🔹 What's Updated - Router Node MCP surface upgraded to the modern Streamable HTTP flow (no session_id required on initialize). - Legacy HTTP+SSE path remains supported for backward compatibility. - Verified end-to-end with modern clients - the screenshots above show ChatGPT discovering tools and successfully calling about. 🔹 MCP Base URLs - Legacy"
X Link 2025-11-21T11:40Z [----] followers, [----] engagements

"🛠 DevLog #ERC8004 #MCP Registration Experiments (Continuation WIP) With the latest MCP endpoint now streamable-spec compatible we're moving into the next agentic experiment: registering Router-Agent surfaces in #ERC8004 using this MCP base URL. 🔹 What We're Doing Now - Register mock #ERC8004 agents that advertise the latest MCP endpoint (and later x402 routes) as discoverable capabilities. - Validate tool discovery + calls when surfaced through ERC-8004 metadata. 🔹 Important Scope Note - The generalized /validate (task validation) endpoint is not live yet. - That rollout is still planned"
X Link 2025-11-21T20:43Z [----] followers, [----] engagements

Limited data mode. Full metrics available with subscription: lunarcrush.com/pricing