Who really holds the power to stop a blockchain? ⚛️ The recent Neutron exploit and coordinated Cosmos Hub halt raise an important question: When an emergency strikes, who can stop the network, who decides, and what role do ATOM holders play? Let's explore the mechanics behind decentralization. 🧵👇 -- 1️⃣ 🧩 When security meets decentralization Following the Neutron exploit, Cosmos Hub validators coordinated a temporary halt to help limit the movement of stolen ATOM. The Hub itself was not exploited, yet an incident originating on another sovereign chain triggered a collective security response. This raises an important question: How can independent networks coordinate during an emergency without compromising their sovereignty? -- 2️⃣ ⚙️ How can validators stop a blockchain? Cosmos Hub uses CometBFT, a consensus engine where validators participate in proposing and validating blocks. To finalize a block, more than two-thirds of the total voting power must agree. Following the Neutron exploit, Cosmos Hub validators coordinated to temporarily stop participating in consensus. Once enough voting power went offline, the network could no longer finalize new blocks. No on-chain governance proposal was required for this coordinated halt. And here's the crucial detail: It's about voting power, not simply the number of validators. -- 3️⃣ 🔍 Why voting power matters Imagine two hypothetical networks: 🔹 Network A: 3 validators collectively control 35% of the voting power. 🔹 Network B: 50 validators each control 2%. In Network A, those 3 validators can collectively prevent block finalization. In Network B, at least 17 validators must coordinate to reach the same threshold. Both networks follow the same consensus rules. But the distribution of power changes who can interrupt block production. -- 4️⃣ 🪙 Delegators are part of the equation When ATOM holders delegate their tokens, they contribute to a validator's voting power. That power determines the validator's weight in consensus. Concentrating large amounts of ATOM among a few validators can therefore concentrate the ability to influence network availability. Distributing delegations across independent validators can reduce this concentration. But independence matters too. Twenty validators controlled by the same entity do not provide the same decentralization as twenty genuinely independent operators. Staking is also a question of how power is distributed. -- 5️⃣ 🚨 Emergency coordination: necessary or dangerous? A concentrated validator set may facilitate rapid coordination during an emergency. But the same concentration means fewer actors are needed to interrupt the network. The Neutron incident brings another dimension to this debate: Should validators on one sovereign chain halt their network to contain an exploit originating on another? Who determines when intervention is justified? And could repeated emergency interventions create an expectation that the Hub will act as a safety net for connected chains? These questions deserve open discussion. -- 6️⃣ 🛡️ Building safeguards without creating gatekeepers A decentralized ecosystem needs the ability to respond collectively to emergencies. But exceptional interventions should not become routine decisions made by a small group. Possible safeguards include: 🔹 Clearly defined emergency procedures 🔹 Transparent coordination between independent validators 🔹 Proportionate interventions with explicit recovery conditions 🔹 Public post-incident reviews and accountability Technical coordination and legitimate decision-making are two different challenges. Both matter when a blockchain's availability is at stake. -- 7️⃣ ⚛️ Who really holds the power? The ability to halt a blockchain is embedded in its consensus rules. But how that power is distributed depends on its validator set, the independence of its operators, and the decisions of its delegators. The Neutron incident reminds us that decentralization is not the absence of coordination. It is the challenge of coordinating without concentrating authority. A network should be able to weather a storm without handing its helm to a permanent captain. ⛵ 💛 YOU CAN HELP DECENTRALIZE COSMOS! Your staking decisions matter. Consider supporting smaller, independent validators and distributing voting power across the network. 🔍 Review your current validator: wallet.keplr.app/chains/cosm… Is your validator active? Are you paying high commission fees? How concentrated is its voting power? ⚛️ Support IBS Validator 🔹 5% commission 🔹 Daily automatic reward compounding via REStake 🔹 Active validator and IBC relayer supporting the ecosystem 👉 Delegate with IBS and enable automatic compounding: tinyurl.com/restake-atom Every delegation helps shape the network we want to build. 🔁💙 RT and Like to spread awareness about validator independence and decentralized staking. 💬 Let's build a new decentralized world together. #Cosmos #ATOM #NDW #validator cosmos:native

Interesting experiment at the intersection of AI agents, onchain governance and tokenized assets. 🤖🏛️ With @AfterHoursDAO, holders define strategies and risk limits while an autonomous agent executes within those mandates. A fascinating direction for exploring how human governance and agentic execution can work together onchain. Good luck to @helwan_mande and the team with their #Stocklana submission! 🚀 #Solana #AI #RWA

A native stablecoin may look like a small piece of infrastructure. Until you ask what the market settles in. 👀 With USTX, @txEcosystem is preparing a native liquidity layer for its upcoming RWA marketplace: • tokenized stocks • ETFs • other real-world assets • settlement directly on TX Instead of fragmenting liquidity across external stablecoin routes, the idea is to keep the asset and its settlement rail on the same chain. USTX, issued by @brale_xyz and announced as fully backed 1:1, could therefore become more than “another dollar token”. It could become the cash layer underneath TX’s tokenized markets. 💵⚙️ For an ecosystem positioning itself around RWAs, that is a rather important piece of plumbing. #TX #RWA #Stablecoins tx:native

An interesting signal for the next phase of the Interchain. ⚛️ @cosmos is joining @LFDecentralized alongside major names like @swiftcommunity and @WellsFargo This highlights a trend worth watching closely: Open-source blockchain infrastructure, interoperability players, and traditional financial institutions are increasingly coming together at the same table. And Cosmos brings with it a well-known challenge: how to move value between independent ledgers without forcing them to adopt a single, unified system. Different networks. Different rules. A shared, open infrastructure. This is precisely where interoperability moves beyond simple "cross-chain crypto transfers" and takes on a whole new dimension. 🌐 Open source could well become a meeting point between decentralized infrastructure and institutional finance. #Cosmos #Interoperability #NDW #Validator

Cosmos Hub is back online! ⚛️ Following the Neutron exploit, a coordinated security response brought together validators, protocols and exchanges to limit further damage. What happened, how did the ecosystem respond, and what comes next? A quick update 🧵👇 --- 1️⃣ 🔍 How did the Neutron exploit happen? According to preliminary on-chain investigations, the attack appears to have involved a malicious proposal submitted through @neutron_org 's expedited governance process. The proposal reportedly enabled the attacker to gain admin control over several smart contracts, including those associated with @astroport_fi and @dropdotmoney . Subsequent contract migrations appear to have allowed the attacker to drain assets. The exact sequence of events and the full extent of the exploit remain under investigation. We will await the official technical post-mortem for a complete assessment. --- 2️⃣ 🛡️ Astroport's security response Following the exploit, @astroport_fi quickly alerted its community about the potential compromise of its smart contract admin privileges. As a precaution, the protocol advised users to withdraw liquidity from Astroport pools across all chains until further notice. This precautionary measure aimed to limit further exposure while the teams investigated the incident. --- 3️⃣ 🤝 An ecosystem-wide security response Multiple actors coordinated to contain the incident: 🔹 Neutron validators halted the affected network. 🔹 @cosmoshub validators coordinated a separate security halt to restrict the movement of stolen ATOM. 🔹 Exchanges were given time to respond and implement protective measures. Importantly, the Cosmos Hub itself was not exploited. The response illustrates how coordination between independent networks and infrastructure operators can help contain a cross-chain incident. --- 4️⃣ 🔄 Cosmos Hub resumes block production Following the coordinated security halt, block production has resumed on the Cosmos Hub. What comes next? The community continues working to address the consequences of the Neutron exploit. The upcoming technical post-mortem should provide a clearer understanding of the attack and the measures needed to prevent similar incidents. As a Cosmos validator and IBC relayer, IBS will continue monitoring developments and keeping our community informed of any significant updates. Security is a collective effort. ⚛️ Follow us to learn more, and let's build a new decentralized world together. #Cosmos #NDW #validator

A telecom operator. A digital asset prime broker. A technology investment fund. What do they have in common? 👀 Three different industries. One shared responsibility: securing @lumera . With NTT DOCOMO GLOBAL joining the network, a broader institutional trend is taking shape. But there's more to the story. Let's explore what's happening behind Lumera's AI infrastructure. 🧵👇 -- 1️⃣ 📡 NTT DOCOMO GLOBAL | Connectivity Part of Japan's NTT DOCOMO Group, @ndg_web3_en has joined Lumera as a mainnet validator. Its telecommunications background brings experience in connectivity and network operations. The company is also exploring Lumera's Intelligence Layer for the emerging AI and agent economy. A new perspective within the validator ecosystem, where network reliability and distributed infrastructure are essential. -- 2️⃣ 🏦 FalconX | Digital Asset Infrastructure @FalconXGlobal brings experience from a different world: institutional digital asset markets. Serving over 2,000 institutional clients, the prime broker now operates a validator on Lumera mainnet. Its participation connects institutional crypto market expertise with the network's Proof-of-Stake infrastructure. From digital asset markets to blockchain consensus, different environments with a shared need for reliable infrastructure. -- 3️⃣ 💼 Innovating Capital | Technology Investment @InnovatingCap represents a third institutional profile within Lumera's validator ecosystem. As a technology investment fund and existing backer of the project, it brings experience in financing and supporting emerging technologies. It also participates directly in securing Lumera mainnet as a validator. Three different sectors, three distinct backgrounds, and one common role in the network. -- 4️⃣ 🌐 Beyond institutions | 1XP joins the network Institutional participation is only part of the picture. On September 18, @lumera also welcomed @1XP_Inc, a professional validator from South Korea. 1XP operates infrastructure across multiple blockchain ecosystems, including Solana, Cosmos Hub, Axelar and Monad. Its arrival brings another experienced multi-chain operator into Lumera's validator ecosystem. Institutional participants and professional infrastructure providers now contribute to securing the same network. -- 5️⃣ 🧠 Beyond validators | Lagrange and verifiable AI But securing the blockchain is only one part of Lumera's broader infrastructure. On September 16, Lumera also announced a partnership with @lagrangedev. The idea is simple: 🔐 Lagrange's zkML technology generates cryptographic proofs that AI inference was performed correctly using the expected model. 💾 Lumera's Cascade provides permanent, verifiable storage for those proofs. An AI result could therefore be accompanied by evidence that remains accessible for future verification. A complementary approach to building trust in autonomous systems. -- 6️⃣ 🔗 What does this broader trend tell us? Lumera's ecosystem is developing across two complementary dimensions. 🛡️ NETWORK SECURITY Institutional participants and professional validators help secure the blockchain through consensus and transaction validation. ⚙️ INTELLIGENT SERVICES SuperNodes support services such as Cascade's decentralized storage, while collaborations with projects like Lagrange explore additional capabilities for verifiable AI. Different participants. Different responsibilities. Together, they illustrate Lumera's approach to building infrastructure for autonomous applications and AI agents. The next step is translating these developments into integrations, network usage and measurable adoption. Infrastructure first. Trust built through participation. -- 7️⃣ 🛡️ Supporting decentralization | IBS At Inter Blockchain Services, we're proud to contribute to securing Lumera alongside these institutional participants and professional validators. As the ecosystem grows, independent validators and community delegations remain essential components of its Proof-of-Stake infrastructure. Want to support our work on @lumera? You can delegate your LUME to IBS and enable automatic reward compounding through REStake. 🔄 Auto-compounding checks every 15 minutes. 🤝 Validator commission: 5%. 👉 Delegate to IBS: restake.app/lumera/lumeraval… Every delegation helps support the operators maintaining decentralized infrastructure. 🔁 💙 RT and Like to highlight the infrastructure behind decentralized AI. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Lumera #AI #Web3 #validator

ATOM is moving toward new financial rails. ⚛️🏦 The Cosmos Hub has voted on Proposal #1054, a $300,740 USDC initiative to integrate ATOM into Paxos' regulated brokerage infrastructure. What could this unlock for the ecosystem? 🧵👇 -- 1️⃣ 🧩 A New Gateway ATOM is already available on major crypto exchanges. The @Paxos integration targets a different market: traditional brokerage platforms and institutional custody. The goal is to make cosmos:native accessible through financial services beyond crypto-native exchanges. -- 2️⃣ 🏦 What Paxos Brings Paxos provides regulated digital asset infrastructure used by financial platforms including Interactive Brokers, Charles Schwab and PayPal. Integrating ATOM into its core platform would enable brokerage partners to offer ATOM trading and custody. But each partner decides independently whether to activate it. -- 3️⃣ 💰 What Governance Funded Proposal #1054 requested 300,740 USDC from the Cosmos Hub Community Pool. The one-time payment covers technical integration, regulatory work, liquidity onboarding and operational support. Paxos has agreed to waive recurring maintenance fees. -- 4️⃣ 🔐 What Comes Next? Infrastructure access does not automatically translate into adoption. The next indicators to monitor are: 🔹 Active brokerage listings 🔹 Trading volume 🔹 Assets held in custody Paxos has committed to quarterly updates during the first year. Institutional staking remains outside the initial integration's scope. -- 5️⃣ 🌐 Connecting Two Financial Worlds The objective is to create another gateway between traditional financial infrastructure and the Cosmos ecosystem. But the real milestone will be seeing financial platforms activate ATOM and users actually access it through these new channels. Infrastructure opens the door. Adoption begins when people walk through it. ⚛️ 🔁💙 RT and Like to spread the word about Cosmos! 💬 Let's discuss and move forward together toward a new decentralized world. #Cosmos #ATOM #NDW #validator #paxos

🚨 Security update on the SingularityNET exploit. Fetch.ai confirms its contracts remain unaffected and FET continues to operate normally. However, AGIX-to-FET conversions and its Ethereum-side bridge remain paused as a precaution while the investigation continues. 🔐 For users: • Avoid using the affected conversion and bridge services until officially restored. • Beware of fake migration or recovery links. • Follow official channels for verified updates. Security, transparency and clear communication remain essential for the entire ecosystem. #FetchAI #Security #validator ethereum:0xaea46a60368a7bd060eec7df8cba43b7ef41ad85

Tokenizing assets is becoming the easy part. The harder question starts after the token exists: How does it reach investors, move between financial systems, remain compliant, and eventually come home? 🤔 A recent Korean MMF case makes that question very real. 🧵👇 * 1️⃣ 🏝️ Tokenization created new islands For years, finance asked: “How do we put this asset onchain?” Funds. Bonds. Deposits. RWAs. We learned how to build the islands. Now we need to figure out how people, capital and instructions travel between them. * 2️⃣ 🇰🇷 A Korean MMF is a good example A recent Catalyze Research paper explores a structure where: Korean MMF ↓ Offshore fund ↓ Tokenized securities ↓ Global investors The interesting part isn't the token itself. It's everything required around it. * 3️⃣ 🚦 A financial product is more than an asset An investor doesn't simply receive a token. Someone may need to: • verify eligibility • receive the subscription • confirm settlement • issue the token • process redemption • burn it • return the capital Money moves. But instructions need to travel too. * 4️⃣ 🏙️ Institutions won't all move to one blockchain Banks, asset managers and custodians already have: their own systems, their own ledgers, their own compliance requirements, their own privacy constraints. The future of finance probably won't be one giant blockchain city. It will be many cities that need reliable roads. * 5️⃣ 🟠 This is where Axelar becomes interesting Axelar doesn't need every institution to abandon its infrastructure. Its role can be the connectivity layer between them. Assets can move. Messages can move. Instructions can move. Different systems can remain different while still communicating. That is a much bigger idea than “bridging a token.” * 6️⃣ 🏦 And this isn't purely theoretical Deutsche Bank’s DAMA 2 architecture includes Axelar for managed token issuance across multiple blockchains. J.P. Morgan and Apollo also used Axelar in a Project Guardian proof-of-concept to connect tokenized fund infrastructure across different ledgers. These are not just theoretical architectures: institutional pilots have already tested these interoperability rails. * 7️⃣ 🌐 From tokenization to connected finance First we asked: “Can we tokenize this asset?” Then: “Can we move this token?” The next question is bigger: “Can we connect the entire lifecycle of that financial product across institutions, jurisdictions and blockchains?” That's where interoperability becomes infrastructure. * 8️⃣ 🛰️ The roads may matter more than the islands Catalyze's Korean MMF scenario is still an analysis, not an announced Axelar deployment. But it illustrates something important: Tokenized finance doesn't only need more assets onchain. It needs a way for fragmented financial systems to work together. That is where “Gateway to Onchain Finance” starts to make much more sense. 🔁💙 RT and Like to support open, secure and decentralized interoperability. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Axelar #Tokenization #RWA #validator @axelar

We gave AI agents a brain. We gave them hands. We gave them memory. We even gave them wallets. But there is still something important missing: a private way to access the Internet. @SentinelP2P is trying to solve exactly that. 🧵👇 * 1️⃣ 🤖 Think of an AI agent like a digital worker • LLM → brain 🧠 • MCP / tools → hands 🦾 • Databases, files, .md notes → memory 🗂️ • Wallet / x402 → payments 💳 • Compute → energy ⚡ But even the smartest digital worker still needs one more thing: A road to the Internet, and sometimes, that road needs privacy. * 2️⃣ 🌐 Today, VPNs are mostly built for humans Think about the usual experience: • create an account • choose a plan • enter payment details • download an app • click “Connect” Perfectly normal for us. Pretty awkward for software trying to operate autonomously. * 3️⃣ 🛡️ Sentinel changes the interface Instead of asking an agent to behave like a human… Sentinel lets software access decentralized bandwidth programmatically. In simple terms: the agent asks for a private connection, pays for it, and connects. No dashboard gymnastics required. * 4️⃣ 🚧 Think of x402 as a digital toll booth An agent arrives and says: “I need private Internet access for one day.” The service answers: “That will cost $0.033.” The agent signs the payment. The gate opens. And the agent continues its journey through a Sentinel dVPN node. Request → payment → access. That is the important part. • 5️⃣ 💳 This is where HTTP 402 enters the story You probably know: •404 = page not found • 401 = unauthorized HTTP also has: • 402 = Payment Required x402 turns that old Internet code into something machines can actually use. The service can basically tell software: “Pay this amount and continue.” * 6️⃣ ⚙️ With Sentinel x402, the whole experience can happen automatically The agent: • requests VPN access • receives the price • signs a USDC payment • gets access to the Sentinel plan • connects to a dVPN node Then the VPN tunnel is established directly between the agent and the node. The operator does not sit inside the tunnel watching the traffic. * 7️⃣ 🚪 And there are actually two doors into the same network • The simple door: x402 Managed. The agent pays USDC and the infrastructure handles the boring blockchain plumbing behind the scenes. • The sovereign door: Autonomous. The agent holds its own Sentinel wallet, selects a node and pays that node directly. Same roads. Different levels of independence. * 8️⃣ 📡 This matters because AI agents increasingly need real Internet access An autonomous agent may need to: • retrieve data • access services in another region • protect its operator’s IP • connect to APIs • crawl public information • perform automated workflows Giving an agent intelligence is useful. Giving it somewhere safe to use that intelligence is another problem entirely. * 9️⃣ 🔐 Privacy cannot stop where automation begins Think about everything you or your company may need to do privately online: • research • access internal services • handle sensitive workflows • retrieve confidential information • operate without exposing unnecessary network metadata If an AI agent is going to perform those tasks on your behalf, it needs the ability to protect its connection too. We would never say: “Employees need secure Internet access, but autonomous software can use the open road.” The more responsibility we give agents, the more their connectivity becomes part of the security perimeter. * 🔟 📦 This also changes how bandwidth can be consumed Sentinel was already designed as infrastructure for decentralized VPN applications. Now bandwidth can increasingly behave like a programmable resource. Not only: “a human buys a VPN subscription.” But: “software needs connectivity, finds it, pays for it and uses it.” That is a very different Internet. * 1️⃣1️⃣ 🤝 And there is another side to the market • Someone has to provide those roads. • Sentinel node operators supply bandwidth. • Agents and applications create demand. • The network sits between them as an open marketplace for connectivity. Humans can use it. Apps can use it. Now machines can start using it too. * 1️⃣2️⃣ 🚀 This is why the interesting part is not simply: “AI can use a VPN.” The bigger shift is that connectivity itself is becoming programmable. Agents are slowly learning how to acquire their own: • compute • data • tools • payments • and now private Internet access. We gave machines a brain. Then hands. Then money. Now they are starting to build their own roads. 🌐🤖 • 🔁💙 RT if you think autonomous agents will need their own Internet infrastructure. Privacy should remain part of the AI stack. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Sentinel #AI #DePIN #validator

AI agents become much more interesting when we stop treating them like demos... and start treating them like infrastructure. Scaffold them. Run them. Inspect them. Register them. Connect them. Increasingly, this starts from a workflow developers already know well: the terminal. 👇 -- 1️⃣ 🛠️ Scaffold instead of starting from zero Fetch.ai's create-fetch-agent tooling can generate ready-to-run projects for: • single agents • chat agents • multi-agent systems • payment agents The plumbing is increasingly becoming part of the template. Less setup. More time building what the agent actually does. -- 2️⃣ 💻 Run the agent like software Once scaffolded, agents can run locally like independent services. Developers can watch logs, test interactions and iterate directly from their development environment. In multi-agent projects, each specialist can even run independently. The agent starts looking much less like a chatbot... and much more like software infrastructure. -- 3️⃣ 🔎 Inspect what autonomy is doing Autonomous does not have to mean invisible. Runtime logs provide visibility into what agents are doing, while tools such as Agent Inspector and Agentverse help developers inspect interactions and behavior. Because autonomy without observability is basically a black box with legs. Nobody needs that. 😅 -- 4️⃣ 🌐 From local process to agent network The bigger step comes when an agent leaves the local terminal. It can be registered through Agentverse, made discoverable, and exposed to a wider ecosystem where ASI:One can route requests toward relevant agents. Now you are not simply launching a bot. You are deploying a service that can become part of an agent network. That is where agentic AI starts looking less like a feature... and more like infrastructure. 🔁 Like & RT if you believe AI agents are becoming infrastructure. Follow us to learn more, and let's build a new decentralized world together. #FetchAI #AIagents #validator

A validator set is more than a list of names. It is the trust layer keeping a chain live and accountable. With @FalconXGlobal joining @lumera , Lumera adds an institutional operator with 2,000+ clients and $2.5T+ in executed volume. A signal for its infrastructure layer. 🛡️🦾

Cosmos is changing the rails beneath its USDC liquidity. For years, Noble was the main issuance hub for native USDC across the Interchain. Now, that architecture is changing. Injective is becoming the new shared issuance source. And underneath the migration sits something Cosmos knows very well: IBC infrastructure. ⚛️ 🧵👇 * 1️⃣ 💵 What is actually changing? Until now, much of the native USDC circulating across Cosmos originated from Noble. Across the Interchain, you may see it displayed as: USDC.n Circle is now discontinuing support for USDC and legacy CCTP V1 on Noble. So the ecosystem needs new rails. * 2️⃣ 💉 Enter Injective USDC Native USDC and Circle CCTP have been live on Injective since May. Unlike a wrapped asset, this USDC is issued natively by Circle. Across participating Cosmos chains, the new representation is displayed as: USDC.inj The goal is to progressively migrate liquidity from USDC.n toward this shared standard. * 3️⃣ 🔄 The migration is now live Since September 11, users on supported chains can migrate through Skip:Go. USDC.n ↓ USDC.inj Skip:Go coordinates the cross-chain steps underneath the interface, including the intermediate CCTP flow. 👉 go.skip.build/ The button looks simple. The infrastructure beneath it isn't. * 4️⃣ 🌐 USDC isn't simply "moving to Injective" Injective becomes the native issuance network. IBC then distributes USDC.inj across participating Cosmos chains. At launch, Skip:Go supports the migration on: Cosmos Hub Osmosis dYdX Neutron Terra 2.0 ZIGChain XPLA Initia More chains can be integrated over time. * 5️⃣ 📡 And this is where relayers matter IBC provides the communication protocol. Relayers carry the packets between chains. The Cosmos Hub team explicitly notes that chains wanting to become supported USDC.inj destinations need IBC relayer connectivity to Injective. No functioning route? The protocol may exist, but the road is still closed. * 6️⃣ 🛣️ Think of it as changing the main warehouse Simplified, the old architecture looked like: Circle ↓ Noble ↓ IBC ↓ Cosmos chains The new model becomes: Circle ↓ Injective ↓ IBC ↓ Cosmos chains The dollar is still USDC. But its logistics network is changing. * 7️⃣ ⚙️ This is not an overnight switch Circle has defined a transition period. 📅 Oct 13, 2026 New USDC minting to Noble through Circle Mint stops. 📅 Oct 31 Legacy CCTP burn limits begin decreasing. 📅 Jan 12, 2027 The Noble USDC contract and CCTP routes are paused. The migration is progressive, not instantaneous. * 8️⃣ ⚠️ Different parts of the ecosystem must adapt Wallets and frontends need to recognize USDC.inj. DEXs and protocols need liquidity and markets for the new denomination. Chains need the required IBC connectivity. dYdX will adopt USDC.inj as its sole eligible trading collateral, but will publish its own migration timing and instructions. A stablecoin migration is much more than changing a ticker. * 9️⃣ 🧩 There is also a fragmentation problem Cross-chain ecosystems can create multiple representations of the same underlying asset. USDC.n USDC.inj bridged variants different routes and denominations For users, they may all look like the same digital dollar. For infrastructure, they are not interchangeable by magic. The migration is also about converging liquidity around a shared standard. * 🔟 ⚛️ The bigger lesson Most users will simply see a different USDC label. Infrastructure operators see: new IBC routes, new liquidity paths, expanded relayer coverage, new integrations. The frontend shows a dollar. Underneath, an entire network of rails keeps that dollar moving. That invisible plumbing is what makes the Interchain work. 🔁 Like & RT if you believe interoperability infrastructure deserves more attention. Follow us to learn more, and let's build a new decentralized world together. #Injective #NDW #validator

Osmosis wanted to solve a very simple problem: Bitcoin liquidity in DeFi is fragmented. WBTC here. cbBTC there. nBTC somewhere else. So instead of forcing users to choose between multiple versions of Bitcoin, Osmosis created Alloyed BTC: one asset, allBTC, backed by several BTC representations. Cleaner UX. Deeper liquidity. Less fragmentation. At least, that was the idea. Because in September, Osmosis discovered that part of the Bitcoin supposedly backing allBTC… did not actually exist. And suddenly, the question was no longer only: “How did this happen?” It became: “Who pays when a DeFi asset discovers a hole in its backing?” 🧵👇 * 1️⃣ 🧺 First, what is allBTC? Think of allBTC as a basket. Instead of holding only one bridged version of Bitcoin, the basket can contain several approved BTC assets. The goal is simple: reduce fragmentation and give users one unified BTC asset across Osmosis. The user sees one token. Behind it, several forms of Bitcoin provide the backing. * 2️⃣ 🧩 That diversification has an advantage If one BTC route fails, it does not necessarily destroy the entire basket. That is one of the ideas behind Alloyed Assets. Different routes. Different collateral. One unified asset. But diversification reduces risk. It does not remove it. And that distinction became painfully important. * 3️⃣ 👻 On June 25, something abnormal happened on Nomic According to the restoration proposal, Nomic created 40.650602 nBTC without corresponding BTC backing. Those tokens were generated through 25 identical IBC transfers inside a single transaction. Most of them eventually reached Osmosis. The problem? They looked like Bitcoin inside the system. But there was no corresponding BTC behind them. Ghost collateral. * 4️⃣ ⏳ And the problem remained hidden for 74 days The discrepancy was not detected immediately. It stayed inside the system until Nomic halted on September 7. By then, around 39.84 unbacked nBTC were sitting inside the allBTC Transmuter. So the basket still looked full from the outside. But part of what was inside was hollow. * 5️⃣ 📉 That changed the real backing of allBTC Around 110.57 allBTC were outstanding. But only about 70.73 BTC were actually backed by real WBTC and cbBTC collateral. The remaining ~39.84 nBTC had no corresponding BTC behind them. Real backing dropped to roughly: 63.97%. At that point, this was no longer just a technical incident. It was a solvency problem. * 6️⃣ 🛑 Osmosis then moved into emergency mode On September 7, validators coordinated the v31.1.0 emergency upgrade. Its goal was to stop the situation from getting worse. Around 22.65 allBTC linked to the attacker were frozen. That was a major step. But there is an important distinction: Frozen funds are not yet recovered funds. Moving them still requires governance and another software upgrade. * 7️⃣ ⚖️ And this is where the story becomes much more interesting Stopping an exploit is a security problem. Repairing the economic damage is a governance problem. Because after freezing the attacker’s funds, approximately 17.19 BTC worth of deficit still had to be addressed. Someone, somewhere, has to absorb that loss. And blockchains do not have a customer service desk hiding behind the protocol. * 8️⃣ 💰 So who actually pays? The current restoration proposal combines several sources. First: recover the ~22.65 allBTC frozen on the attacker’s address. Then: use around 12.48 allBTC already held by the Osmosis Community Pool. Finally: cover the remaining ~4.71 BTC using BTC liquidity controlled by Osmosis governance. So this is not one giant bailout. It is a layered recovery plan. * 9️⃣ 🔄 And here comes an interesting twist Part of that BTC liquidity was originally intended for another operation: the migration from USDC.noble toward Alloyed USDC. So two governance stories that looked completely separate suddenly collide. allUSDC migration 🤝 allBTC recovery Treasury management becomes crisis management. The Community Pool stops being an abstract governance wallet. It becomes a strategic reserve. * 🔟 🏛️ This is what on-chain governance looks like when things get real Most governance discussions sound harmless: change a parameter, adjust an incentive, approve a budget. This one is different. Governance may have to decide: • whether exploited assets can be reassigned • whether Community Pool funds should cover user losses • how much collective capital should absorb a protocol failure • under which conditions minting and redemption can safely reopen These are no longer theoretical votes. They are economic decisions with real consequences. * 1️⃣1️⃣ 🧠 There is also a bigger lesson about Alloyed Assets The diversified structure helped. nBTC did not represent 100% of allBTC backing. Without diversification, the damage could have been much worse. But around 36% exposure to one compromised component was still enough to create a major crisis. Diversification reduces the blast radius. It does not make the system invincible. * 1️⃣2️⃣ 🔐 And that may be the most useful takeaway DeFi risk is rarely isolated to one smart contract. It can travel through: bridges, IBC routes, collateral, liquidity pools, governance, and treasury decisions. The technical architecture determines how far the shock can travel. Governance determines what happens once it stops. * 1️⃣3️⃣ 🚨 The incident is not fully resolved yet The current restoration plan still needs to move through governance. Several things remain important to watch: • transition from forum discussion to on-chain proposal • details of the required software upgrade • validator participation • potential response from Nomic • conditions for reopening allBTC minting and redemption The emergency phase may be over. The governance phase is only beginning. * 1️⃣4️⃣ 🌊 The interesting part of this story is no longer the exploit itself. It is what happens after. An attacker creates unbacked assets. Validators freeze what they can. A DAO discovers a hole. Then the community has to decide how to repair it. That is DeFi governance stripped of theory. Not just voting on parameters. But deciding how a decentralized financial system absorbs a real loss. 🔁💙 RT and Like if you think governance matters most when difficult decisions have to be made. 💬 Should a DAO treasury act as a backstop when infrastructure approved by governance fails? Follow us to learn more, and let's build a new decentralized world together. #Osmosis #DeFi #NDW #validator

Tokenizing an asset is getting easier. Getting a bank to actually use it in production is still painfully complicated. Custody. Compliance. Security. Integration. Operations. @cosmoslabs_io just brought 17 companies together to attack that bottleneck. And that may matter more than launching another blockchain. 🧵👇 * 1️⃣ 🏦The pilot → production gap A financial institution can experiment with tokenized deposits relatively quickly. But going live means coordinating multiple layers: • KYC / KYB • custody • transaction monitoring • wallet infrastructure • security • enterprise integration That coordination is often where things slow down. * 2️⃣ ⚙️ Tokenization itself is only one piece of the puzzle A bank may be able to issue a tokenized deposit. But putting it into production also requires: • KYC / KYB • custody • transaction monitoring • wallet infrastructure • security • enterprise integration That coordination quickly becomes complex. * 3️⃣ 🌐 Enter the Cosmos Partner Network Cosmos has launched an initial network of 17 service providers around its Tokenization Suite and digital ledger solutions. The idea is simple: Cosmos provides the ledger and tokenization infrastructure. Partners provide the surrounding institutional stack. * 4️⃣ 🧩 And the partner list covers almost every layer The initial network includes companies working across: 🔐 Custody 🛡️ Security ⚖️ Compliance 🏗️ Blockchain infrastructure 👛 Wallets 📊 Trading & settlement 🔧 Enterprise integration Including @BitGo , @galaxyhq , @BlockdaemonHQ , @OpenZeppelin , @HypernativeLabs , @0xZeeve, @Peersyst @CoinbaxHQ and others. * 5️⃣ 💵 Why does this matter for tokenized deposits? Because financial institutions aren't just experimenting with digital assets anymore. Cosmos is targeting practical use cases such as: • 24/7 settlement • improved treasury liquidity • programmable escrow • programmable trade finance • tokenized deposits And eventually, even agentic commerce. * 6️⃣ 🧠 The real bottleneck may no longer be blockchain technology A pilot can be built relatively quickly. Production is harder. Institutions need multiple providers to work together while meeting security, compliance and operational requirements. Cosmos is trying to package that complexity into a more coordinated path. * 7️⃣ 🏗️ This also shows how Cosmos' positioning is evolving For years, Cosmos was mostly discussed as: SDK + sovereign chains + IBC. Now another layer is becoming increasingly visible: institutional financial infrastructure. Not simply helping organizations launch blockchains... but helping them operate real financial products on top of them. * 8️⃣ 🌉 And that distinction matters Tokenization becomes much more useful when institutions don't have to rebuild the surrounding infrastructure every time. The ledger is one rail. Custody, compliance, security and operations are the stations around it. Without them, the train doesn't carry many passengers. * 9️⃣ ⚛️ The bigger picture The Cosmos Partner Network doesn't guarantee institutional adoption. But it removes one very practical obstacle: the need for every bank to assemble its own digital-asset infrastructure from scratch. That could make the journey from pilot → production considerably shorter. 💬 What matters more for institutional adoption now: better blockchain technology... or better integration around it? Follow us to learn more, and let's build a new decentralized world together. #Cosmos #NDW #validator cosmos:native

Cosmos may have found a new door into traditional finance. The awkward part? @cosmoslabs_io says it cannot legally pay for the key. So the decision could fall directly to ATOM governance. And that makes the Paxos proposal much more interesting than a simple listing. 🧵👇 * 1️⃣ 🏦 First, what is Paxos proposing? This isn't another exchange listing. Paxos provides regulated crypto infrastructure behind financial platforms and brokerages. Integrate ATOM once into its infrastructure, and current and future Paxos clients can potentially activate it for their users. One connection. Multiple possible doors. * 2️⃣ 🌉 But access is not adoption Once integrated, each brokerage remains free to decide: • whether to support ATOM • when to activate it • how to offer trading or custody So Cosmos would be paying for infrastructure and potential distribution. Not guaranteed volume. Not guaranteed users. * 3️⃣ 💰 And here comes the governance puzzle The integration requires a one-time payment of 300,740 USDC from the Cosmos Hub Community Pool. Naturally, part of the community asked: Why should ATOM holders fund it? Why not Cosmos Labs or the ICF? * 4️⃣ ⚖️ The answer is surprisingly important According to Cosmos Labs' RoboMcGobo, they can't directly fund token listings because of legal and regulatory restrictions. The ICF historically hasn't funded ATOM exchange listings for the same reason. And according to him: without community approval, the Paxos integration cannot move forward in its current form. * 5️⃣ 🗳️ Governance becomes part of the financing layer This creates an unusual situation. The organization helping develop the institutional strategy can negotiate and coordinate the opportunity... but the decentralized treasury must decide whether to finance it. The Community Pool isn't just funding development here. It would be funding market access. * 6️⃣ 🤔 And that's where the debate gets interesting Supporters see the spend as a strategic investment: one integration could make ATOM available to many current and future brokerage platforms. Critics see a different equation: 300k upfront, with no contractual guarantee that those platforms will actually activate ATOM. Both questions are legitimate. * 7️⃣ 🥩 And staking could open a second debate Institutional staking is NOT part of the current proposal. But Paxos says it is being explored for later. If large institutional ATOM balances eventually enter staking, another question appears: Where will that voting power be delegated? More stake strengthens economic security. Poor validator distribution could also concentrate governance power. * 8️⃣ ⚛️ So this proposal is about more than Paxos It raises three broader questions for the Cosmos Hub: 🏦 Should the Community Pool finance institutional distribution? 📊 What accountability should exist when adoption cannot be guaranteed? 🗳️ And if institutional staking follows, how should validator decentralization be protected? The proposal is still under discussion and has not yet moved on-chain. * 9️⃣ 💬 Cosmonauts, where would you draw the line? Would you use community funds to open a potentially important institutional gateway even without guaranteed adoption? And if yes: what safeguards would you expect in return? Milestones? Reporting? Performance indicators? Validator diversification if staking eventually follows? what safeguards or reporting would you expect in return? Let's discuss and move forward together toward a new decentralized world. ⚛️ #Cosmos #ATOM #validator #NDW $ATOM

A DeFi protocol can be: ✅ audited ✅ approved by governance ✅ ready to launch …and still be forced to stop because one piece of infrastructure stopped telling the time. That is exactly what just happened to BlueChip on Osmosis. Let’s talk about oracles. 🧵👇 * 1️⃣ 🕰️ First: what does an oracle actually do? A blockchain is a room with no windows. It knows what happens on-chain. But it doesn’t naturally know: • the price of OSMO • the price of BTC • interest rates • market data Oracles are the windows. They bring outside information on-chain. * 2️⃣ 💰 And DeFi depends heavily on those windows Imagine a lending protocol. Before accepting collateral, it needs to know: “How much is this asset worth right now?” The same applies to: • lending • perpetuals • vaults • stablecoins • liquidations A wrong price can become a very expensive mistake. * 3️⃣ 🔧 BlueChip depended on Pyth for OSMO/USD Its contracts were already approved through three Osmosis StoreCode proposals. But before deployment, the team discovered a problem. The Pyth CosmWasm contract they relied on could no longer accept fresh price updates. The contracts were ready. Their clock wasn’t. * 4️⃣ 🔐 What changed? Pyth recently upgraded its Core infrastructure. Previously, cross-chain price updates relied on Wormhole guardians. The new architecture uses: 5 independent routers → 3 signatures required → one validated price update A new mechanism for delivering the same essential information. * 5️⃣ 🧩 But the old CosmWasm contract speaks the old language The contract on Osmosis still expects signatures from the previous Wormhole guardian system. Its trusted guardian set expired. So fresh updates arrive… …and the contract replies: `GuardianSetExpired` The oracle contract still exists on-chain. But its hands have stopped moving. 🕰️ * 6️⃣ 🛑 This is where BlueChip made the important decision They did NOT say: “Well… yesterday’s price is probably close enough.” 😅 Their contracts reject stale prices by design. No reliable price → no deployment. That is called failing closed. And in financial infrastructure, sometimes refusing to operate is the safest feature available. * 7️⃣ 🌐 The lesson goes beyond BlueChip Pyth now explicitly states: Pyth Core no longer supports CosmWasm as of August 26, 2026. So any CosmWasm application still depending on a legacy Pyth Core integration should verify its oracle architecture. Not panic. Verify. Because dependencies age too. * 8️⃣ 🏗️ And this raises a bigger architectural question Should a DeFi protocol depend on only ONE oracle integration? Even if the oracle itself is decentralized, the protocol can still have one external dependency: Oracle A fails → application stops. That is still a form of infrastructure concentration. * 9️⃣ 🔀 A multi-oracle architecture can reduce that risk Think of it as giving the protocol several clocks. For example: Primary oracle ↓ freshness + deviation checks ↓ independent fallback source ↓ circuit breaker if neither can be trusted The goal is NOT to blindly average random prices. The goal is graceful degradation. * 🔟 ⚠️ More oracles do not automatically mean more security Three clocks built from the same broken mechanism are still one dependency wearing three watches. Sources need to be sufficiently independent. Fallback rules need to be carefully designed. And if every source disagrees? The safest answer may still be: STOP. * 1️⃣1️⃣ 🧠 That may be the most important lesson here Decentralization does not stop at consensus. A dApp can run on a decentralized blockchain while depending on: one RPC provider one bridge one oracle one API one data pipeline Resilience has to travel through the entire stack. * 1️⃣2️⃣ ⚛️ BlueChip’s launch delay is frustrating. But it also demonstrates something healthy: the system detected stale data and refused to pretend everything was fine. Because in DeFi, an oracle that cannot reliably tell the time should never be allowed to decide how much your money is worth. Follow us to learn more, and let's build a new decentralized world together. #Osmosis #Oracle #NDW #validator

5 core principles that define decentralized interoperability: - Non-custodial architecture - Permissionless participation - Open-source code - Immutable recordkeeping - Distributed governance

Tokenomics are usually presented as if they were carved in stone. Fixed allocations. Fixed emissions. Fixed schedules. But @txEcosystem just demonstrated something more interesting: onchain governance can directly reshape the rhythm of a network's economy. Let’s look at TX, its Proof of Support Emission, and Proposal #46. ⚙️ 🧵👇 - 1️⃣ 🧩 First, what is TX? TX is a finance-first Layer 1. born from the merger of Coreum and Sologenic. Its ecosystem is being built around: • tokenized real-world assets • financial infrastructure • compliant markets • cross-chain finance And its token economy includes an unusual mechanism: Proof of Support Emission, or PSE. - 2️⃣ ⚙️ What is Proof of Support Emission? At TGE, 100B $TX were allocated to a dedicated PSE pool, locked onchain and governed by protocol rules. The original model planned 84 monthly distributions. But PSE isn't simply another unlock schedule. Part of those emissions is designed to reward participants supporting the network. - 3️⃣ 🔐 Where does each PSE distribution go? 40% → Stakers 30% → Treasury & Operations 20% → Founding Partners 5% → Investors 3% → Partnerships & Growth 2% → Team When PSE is active, roughly 1.19B TX is distributed per cycle. Around 476M TX goes to stakers. - 4️⃣ ⏱️ And TX adds another ingredient: time PSE rewards are based on: Score = Stake × Time Stake more → higher score. Remain delegated longer → higher score. So the mechanism attempts to reward not only capital... but continued support for the network. - 5️⃣ 🔄 Rewards also reinforce staking The community share isn't simply dropped into wallets as liquid tokens. PSE rewards are automatically added to existing delegations. So part of the emission flows directly back into the network's security layer. A distribution mechanism feeding the machine that secures it. 🔐 - 6️⃣ ⏸️ But governance just changed the tempo Proposal #46 has passed. After the final PSE distribution before the pause on **November 6, 2026**, the remaining PSE schedule will be postponed for 12 months. During that period: • no new TX enters circulation through PSE • native staking continues • validator & delegator rewards continue • inflation parameters target **24% staking APY** PSE is set to automatically resume on **December 6, 2027**, unless governance decides otherwise. - 7️⃣ 🧠 PSE isn't being cancelled The original **100B TX PSE framework remains intact.** The allocation percentages remain unchanged. The remaining distributions are simply shifted forward. This is essentially a monetary-policy adjustment: reduce near-term PSE-driven supply growth while maintaining incentives to secure the network. - 8️⃣ 🗳️ And this is where blockchain gets fascinating A network defines its economic rules in code. Then its participants can collectively decide to adjust those rules as economic conditions evolve. Here, governance is directly influencing: • emission timing • circulating supply growth • inflation parameters • staking incentives And the decision is made through a public, verifiable onchain governance process. Governance isn't sitting beside the economic model. It's becoming part of the economic engine itself. ⚙️ - 9️⃣ 🏗️ From a validator perspective, this matters Validators don't only secure transactions. They operate inside economic systems whose incentives, emissions and security incentives can evolve through governance. @IBSvalidator is already an active validator on TX. So we'll be watching closely as this experiment develops from the infrastructure layer itself. 🔧 - 🔟 ⚖️ The interesting question now isn't simply whether PSE is “good” or “bad”. It's whether TX can successfully balance: • network security • staking incentives • supply discipline • ecosystem growth • long-term demand Proposal #46 turns that balancing act into a live economic experiment. And that's one of the fascinating things about programmable economies: the rules can evolve with the network they govern. ⚙️ - 🔁💙 RT and Like if you enjoy looking beneath the surface of blockchain tokenomics. 💬 Should onchain governance be able to intervene this directly in a network's economic model? Follow us to learn more, and let's build a new decentralized world together. #TX #NDW #validator