⟨GOD»CALL⟩

1.4K posts

⟨GOD»CALL⟩ banner
⟨GOD»CALL⟩

⟨GOD»CALL⟩

@ReallyReachUp

OG- #AI & #utility LOVER 👨🏻‍💻

Bergabung Mart 2024
76 Mengikuti30 Pengikut
⟨GOD»CALL⟩ me-retweet
Crypto Tony
Crypto Tony@CryptoTony__·
$ETH / $USD - Update $2083 is a long upon a reclaim. Again just seeing noise before hand.
Crypto Tony tweet media
English
130
9
79
8.8K
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
Market is brutally grinding between #Isreal and #Iran war 🟥Red in war 🟥Red in crypto All are reacting negatively
CryptoNinja tweet media
English
0
1
2
449
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
🚨 BREAKING: #Israel have launched a joint "preemptive strike" on #Iran, with multiple massive explosions currently reported across Tehran. Israeli Defense Minister Israel #Katz has declared a nationwide state of emergency as air raid sirens sound across Israel. The military operation follows weeks of stalled nuclear negotiations and heavily escalated tensions in the region.
CryptoNinja tweet media
English
0
4
12
3.3K
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
Partnering AI with defence networks makes us think: is this necessary for national security or is it a line we shouldn't cross? It seems like the idea is to use controlled deployment with strict safety measures, like no mass surveillance, human control over force and built-in technical guardrails. If these systems are going to use AI anyway, a regulated and open framework may be safer than not having any rules at all. But oversight will be key
CryptoNinja tweet media
Sam Altman@sama

Tonight, we reached an agreement with the Department of War to deploy our models in their classified network. In all of our interactions, the DoW displayed a deep respect for safety and a desire to partner to achieve the best possible outcome. AI safety and wide distribution of benefits are the core of our mission. Two of our most important safety principles are prohibitions on domestic mass surveillance and human responsibility for the use of force, including for autonomous weapon systems. The DoW agrees with these principles, reflects them in law and policy, and we put them into our agreement. We also will build technical safeguards to ensure our models behave as they should, which the DoW also wanted. We will deploy FDEs to help with our models and to ensure their safety, we will deploy on cloud networks only. We are asking the DoW to offer these same terms to all AI companies, which in our opinion we think everyone should be willing to accept. We have expressed our strong desire to see things de-escalate away from legal and governmental actions and towards reasonable agreements. We remain committed to serve all of humanity as best we can. The world is a complicated, messy, and sometimes dangerous place.

English
0
1
3
63
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
On X if you open the comment/reply section what will you see? Unnecessary tagging grok, for what? -> nothing Reply section is full of random grok tag stuff I know fact checking is fine, but why every time tag it? what's the point?
English
0
1
3
45
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
"Decentralized AI is just a marketing fluff?" #DePIN slashed cloud compute costs by 80%, you passed Render & Akash onboarded enterprise H100 GPUs, you yawned #Bittensor halved emissions with 100+ live machine learning subnets, you ignored it AI #agents started autonomously managing crypto treasuries...nah, not watching #Deepfake detection and open-weight models hit mainnet...no FOMO #Web2 cloud giants hit severe hardware shortages, still chilling And only now when Silicon Valley panics over a '$100B compute bottleneck' and begs for GPUs… yeah, that price action is justified...! Would u like to adjust any of the specific tokens mentioned or is this ready to go?
English
0
3
8
57
⟨GOD»CALL⟩ me-retweet
⟨GOD»CALL⟩ me-retweet
Cortensor
Cortensor@cortensor·
🛠️ DevLog – #MCP + #ERC8004 Interop Patch: Testing, Regression, Monitoring We’ve 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. 🔹 What’s 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 It’s Running •Corgent (mainnet agent): 8004scan.io/agents/ethereu… •Bardiel (mainnet agent): 8004scan.io/agents/ethereu… •Corgent MCP messages: router0-t1a.cortensor.app/mcp/messages •Bardiel MCP messages: router0-t1a.bardiel.app/mcp/messages 🔹 What We’re Watching •Regression against standard #MCP clients (#OpenAI tools, #Claude tools) to ensure /completions, /validate, /delegate, etc. still behave as before. •8004scan health status for both agents to confirm they pick up the static MCP advertisement and mark them healthy. •Endpoint logs + error rates; if everything holds up, we’ll mirror this MCP pattern to testnets and future agent surfaces. #Cortensor #DevLog #MCP #ERC8004 #Corgent #Bardiel #AgenticAI
Cortensor tweet mediaCortensor tweet media
Cortensor@cortensor

🛠️ DevLog – MCP + ERC-8004 Interop Patch Live on Corgent & Bardiel We’ve 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 It’s Live Corgent (mainnet): 8004scan.io/agents/ethereu… Bardiel (mainnet): 8004scan.io/agents/ethereu… 🔹 What We’re Testing Now - Verifying there’s no regression with standard MCP clients (OpenAI, Claude Tools, etc.) while 8004scan health checks read correctly. - Watching agent health + logs on these endpoints and, if stable, we’ll mirror the pattern across testnets and future MCP surfaces. #Cortensor #DevLog #MCP #ERC8004 #Corgent #Bardiel #AgenticAI

English
0
6
17
675
⟨GOD»CALL⟩ me-retweet
Cortensor
Cortensor@cortensor·
🛠️ DevLog – Corgent & Bardiel #MCP / #ERC8004 Interop Confirmed Healthy 🔹 What’s 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): 8004scan.io/agents/ethereu… •Bardiel (mainnet agent): 8004scan.io/agents/ethereu… •Corgent MCP: router0-t1a.cortensor.app/mcp/messages •Bardiel MCP: router0-t1a.bardiel.app/mcp/messages 🔹 What We Verified •Standard MCP clients (OpenAI-style, Claude tools) still discover and call completions / validation / sessions without regressions. •8004scan’s endpoint test view can list and ping all tools, confirming the new static advertisement contract. 🔹 What’s Next •We already expose /delegate as a REST endpoint, but it’s not fully mapped into the MCP tool set yet. •Next step is to surface /delegate as a first-class MCP tool so agents can use delegation, validation, and routing under one unified MCP contract. #Cortensor #DevLog #MCP #ERC8004 #Corgent #Bardiel #AgenticAI
Cortensor tweet mediaCortensor tweet mediaCortensor tweet mediaCortensor tweet media
Cortensor@cortensor

🛠️ DevLog – #MCP + #ERC8004 Interop Patch: Testing, Regression, Monitoring We’ve 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. 🔹 What’s 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 It’s Running •Corgent (mainnet agent): 8004scan.io/agents/ethereu… •Bardiel (mainnet agent): 8004scan.io/agents/ethereu… •Corgent MCP messages: router0-t1a.cortensor.app/mcp/messages •Bardiel MCP messages: router0-t1a.bardiel.app/mcp/messages 🔹 What We’re Watching •Regression against standard #MCP clients (#OpenAI tools, #Claude tools) to ensure /completions, /validate, /delegate, etc. still behave as before. •8004scan health status for both agents to confirm they pick up the static MCP advertisement and mark them healthy. •Endpoint logs + error rates; if everything holds up, we’ll mirror this MCP pattern to testnets and future agent surfaces. #Cortensor #DevLog #MCP #ERC8004 #Corgent #Bardiel #AgenticAI

English
4
8
22
903
⟨GOD»CALL⟩ me-retweet
Cortensor
Cortensor@cortensor·
🛠️ 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 we’re 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 reconstructable, so we may keep it out of the persistent migration path. •Goal: treat L3 state as portable, not permanent – so infra upgrades feel like planned maintenance, not emergencies. 🔹 /delegate – More Tooling + #MCP Exposure •Remaining cycles this week go into strengthening /delegate: - Add more internal tooling / guardrails around delegated execution flows. - Expose /delegate as an MCP tool alongside /completions, so agents can use delegate + validate + complete from the same Corgent/Bardiel surface. These two tracks - data mobility and a stronger /delegate surface - are the main engineering focus for the coming days. #Cortensor #DevLog #MCP #ERC8004 #DataMobility #Delegate #AgenticAI
Cortensor@cortensor

🗓️ 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 stress failure paths, replay incidents, and test recovery. - Run targeted base fee adjustment exercises to observe behavior under changing fee conditions and capture learnings in the L3 ops playbook. 🔹 Hackathon #4 Support - Ongoing builder support: answering asks, reviewing ideas, and guiding validation/delegation patterns. 🔹 /delegate & /validate Iteration (Follow-Up Week) - Resume deeper iteration on /delegate and /validate (templates, tooling, reliability). - Keep /delegate progressing as a thin agent SDK surface. 🔹 MCP + ERC-8004 Interop Patch (Corgent/Bardiel) - Includes small adjustments to deployed ERC-8004 agents so MCP metadata/health checks are more client-friendly. - Patch MCP stream behavior, redeploy router nodes, and re-check agent health. - Corgent: 8004scan.io/agents/ethereu… - Bardiel: 8004scan.io/agents/ethereu… 🔹 Data Mobility – Import/Export Rough Assessment - Start mapping import/export shapes for Session/Queue, payments, and NodePool metadata. - Run small migration drills (snapshot → export → re-import) to validate repeatability. #Cortensor #Testnet #AIInfra #DePIN #Corgent #Bardiel #AgenticAI #ERC8004 #MCP #PoI #PoUW #L3

English
2
6
22
342
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
@toady_hawk @arbitrum @base @zksync @toady_hawk check from @cortensor angle, strong L1s matter with progress comes from the layers built on top. Recent updates focus on multi RPC reliability and smarter routing logic, built to scale across L2/L3 environments.
English
0
1
6
51
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
#PiNetwork price is near ~90% drop from its ATH.. strong bearish pressure. Abt 82M #Pi tokens unlock this week, adding supply and likely increasing sell pressure if demand stays weak. More tokens (incl. validator rewards) are expected in coming months... which could keep supply high. Technically, PI is oversold (RSI <30) so bounce is possible. A potential upside catalyst is a listing on #Kraken, since its on their roadmap, which could IMPROVE LIQUIDITY and sentiment.
English
0
2
4
174
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
@0xSleuth_ But #Base is still activity growing According to @Cortensor infrastructure that can validate actual work.. rather than chatbots or launches.. is what endures, which is why routing, validation and execution logic are more important! x.com/cortensor/stat…
Cortensor@cortensor

🗓️ 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 the L3 operational playbook based on real-world incidents and exercises. 🔹 Hackathon #4 Support - Ongoing support for Hackathon #4 builders with reviews, guidance, and feedback loops. 🔹 SLA Filters – Ranking Logic Ported - Ported validation and ranking table logic into NodePoolUtil, preparing it as a first-class signal for routing. - This sets the stage for SLA-aware filters in the node selection pipeline. 🔹 RPC Resilience + Gas Optimization - Reduced RPC call volume and tightened gas usage for cortensord and miner operations. - Added support for configurable and rotating RPC endpoints, improving reliability under load. 🔹 /delegate & /validate Iteration (Follow-Up) - Deeper iteration on /delegate and /validate was lighter than planned and will continue next week. A strong execution week - Phase #2 stability improved, self-managed L3 ops matured, routing is closer to SLA-aware selection, and core infra reliability is tighter. #Cortensor #Testnet #AIInfra #DePIN #Validator #PoI #PoUW #Hackathon #Corgent #AgenticAI #L3

English
0
1
3
256
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
@GenuineDegen this article explains why AI agents need structure like AWS, but built for agents $COR positions itself as that layer with /delegate for execution and /validate for trust letting agents outsource heavy work safely
Cortensor@cortensor

x.com/i/article/2019…

English
0
2
6
78
⟨GOD»CALL⟩ me-retweet
Cortensor
Cortensor@cortensor·
🛠️ 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. 🔹 What’s Next (Early Next Week) - We’ll 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 can: - snapshot → export → re-import into a fresh module, and - keep payments and routing behavior intact. - Goal is to make hardforks + infra moves (for #L3/self-managed) a deliberate, repeatable tool rather than a last-minute emergency when storage or infra constraints show up. This stays on the design/experimentation track for now, but it’s the groundwork for future mainnet-grade data migrations when $COR #L3 needs to evolve under real load. #Cortensor #DevLog #L3 #DataMobility #ImportExport #AIInfra #DePIN
Cortensor@cortensor

🔹 DevLog – Data Mobility & Data Module Import/Export (Early Design Thoughts) As we see real data growth on the self-managed #L3, it’s becoming clearer that storage growth itself isn’t the real problem - data mobility is. 🔹 What We’re Thinking About - Instead of worrying only about raw disk size, we’re 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 - Session Queue Data – queued tasks and routing state - Session Payment Data – balances, credits, pending payouts - Node Pool Data – node specs, capacity, reputation metadata 🔹 Why This Matters - As long as these data modules can be exported/imported and we can safely transfer Session Payment balances to a new deployment, storage growth on any single #L3 instance is manageable, not fatal. - This would give us a controlled way to: - Perform hardforks when necessary in production/mainnet - Migrate to new infra (or new #L3 setups) while preserving critical network state - Treat $COR #L3 as an orchestration layer that can evolve operationally as load increases. 🔹 Next Step We’ll start deeper design + brainstorming on data module import/export flows so future #L3 hardforks and infra migrations are deliberate tools, not emergencies. #Cortensor #DevLog #L3 #DataMobility #AIInfra #DePIN

English
2
9
23
677
⟨GOD»CALL⟩ me-retweet
Cortensor
Cortensor@cortensor·
🛠️ DevLog – SaltStack Infra for cortensord Fleets We’ve 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: github.com/cortensor/salt 🔹 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 configs. - Built-in systemd service management, log rotation, and one-command upgrades to keep large fleets manageable without manual SSH gymnastics. 🔹 Why It Matters - Makes it much easier to run larger, more consistent cortensord fleets, especially as we lean harder into self-managed L3 + higher-load testnets. - Gives node operators and infra folks a clear path toward infra-as-code for Cortensor as we head toward mainnet-style operations. #Cortensor #DevLog #SaltStack #DevOps #NodeOps #AIInfra #DePIN
Cortensor tweet media
English
5
15
31
900
⟨GOD»CALL⟩ me-retweet
CryptoNinja
CryptoNinja@CryptoNinjaPro·
🟥 Red. Red. Red. 🟥 Huge crash in market
CryptoNinja tweet media
English
0
3
8
342