Imagine walking into a coffee shop. ☕️ You have ETH . The merchant prefers BTC. No problem. You scan a QR code, pay with your crypto, and the merchant receives the native asset they want. Simple enough to explain to your grandmother. 😄 But beneath that little QR code? ⚙️ @THORChain coordinates liquidity across independent blockchains, with THORNodes observing transactions and distributed vaults handling native settlement. No unnecessary wrapped tokens. No centralized exchange required by the protocol. No bank deciding whether to approve the payment. And that's what makes @mocadotapp interesting. Two people. Two different currencies. One payment. With decentralized infrastructure doing the complicated work in the background. A beautiful extension of Bitcoin's original peer-to-peer vision: open financial rails, fewer gatekeepers, and more freedom to choose how we exchange value. ⚡️ #THORChain #CrossChain #validator thorchain:native

A marketplace needs more than assets on the shelves. It needs money moving between them. @txEcosystem has announced the launch of USTX, its native dollar stablecoin issued by @brale_xyz . Here’s how it fits into TX’s RWA plans—and what the launch bonus requires. 🧵👇 ___ 1️⃣ 💵 What is USTX? USTX is the native stablecoin of the tx ecosystem. According to TX, each token is backed 1:1 by dollar-denominated reserve assets overseen by Brale. USTX is distinct from TX, the network token. ___ 2️⃣ 🌉 How does funding work? TX announced USDC deposits from Ethereum, Base, Polygon and Solana at launch, with USTX delivered to a tx wallet. Redemption back into USDC is also supported, according to the announcement. Four additional deposit networks are planned. ___ 3️⃣ 🏗️ Why introduce a native dollar? TX wants USTX to provide a common balance across its upcoming marketplace, SoloTex and supported RWA offerings. The aim: fewer conversions and transfers as users move between products. Those integrations remain a rollout to watch. ___ 4️⃣ 🎁 What does the launch bonus require? According to TX’s latest announcement: • Convert 100+ USDC in one transaction • Receive USTX in the tx Super App wallet • Hold it for 7 days • Complete verification Bonus: 1,500 TX, or 3,000 TX for Elite Club members. ___ 5️⃣ 🛂 Eligibility matters TX states that the bonus is available once per verified user in supported regions. Mints to third-party wallets do not qualify. The promotion is time-limited and subject to jurisdiction restrictions and program limits. Check the current terms before participating. ___ 6️⃣ 🔎 A launch incentive is only the beginning The bonus rewards an eligible first mint. What follows will matter more for the ecosystem: Will balances remain after incentives? Which products will use USTX? Will meaningful trading liquidity develop? A funded wallet is the starting point. ___ 7️⃣ ⚙️ From funding wallets to functioning markets USTX gives TX a native dollar instrument around which to build. The next milestones are usable products, accessible markets and reliable redemption. That is where the infrastructure meets everyday use. #TX #USTX #RWA --- 🔁💙 RT and Like if you enjoy exploring the infrastructure behind tokenized markets. 💬 What will convince users to keep using USTX once the launch incentives end? Follow @IBSvalidator to learn more, and let’s build a new decentralized world together. 🌐 #TX #USTX #RWA #NDW tx:native

AI can analyze the market in a second. But feed it the wrong price, and it can get things wrong faster than lightning. 🤖📉 Before listening to a trading bot, let’s look at what feeds its instruments. The @BandProtocol × @BellaProtocol announcement offers a useful case study. 🧵👇 -- 1️⃣ 📲 What exactly is Bella? Bella Protocol develops tools for trading and DeFi. Its Bella Alpha assistant, available on Telegram, combines AI-powered research, market analysis, and long/short signals for selected perpetual trading pairs. The announced collaboration aims to feed its models with Band’s price data. -- 2️⃣ 🛰️ Why bring in an oracle? Imagine a pilot whose altimeter displays an outdated reading. Even with an excellent flight computer, the flight path can become dangerous. For a trading AI, a stale or manipulated price can distort the analysis before a signal is even generated. The oracle works upstream: it supplies the data the model will use. -- 3️⃣ 🔎 How does Band build this information? Its approach combines multiple price sources with a network of validators on BandChain, its blockchain built with the Cosmos SDK. Prices are collected, reported, and aggregated to produce a value applications can use. The goal: reduce dependence on a single source and limit the influence of an outlier. Multiple sources observe the market. Multiple validators contribute to the result. Reliability also depends on their quality and independence. -- 4️⃣ 🧭 Reliable instruments are still just instruments. A verified price does not predict the market’s next move. Data quality matters; model quality and risk management remain essential. Before following a bot, take the time to understand its sources, strategy, and limitations. An automated signal can still lead to a loss. This thread explains infrastructure. It is not financial advice. -- 💬 Before asking “How much does your AI earn?”, let’s also ask “Where do its prices come from?” 🔁 ❤️ RT and like to help more users understand what happens behind the scenes of trading bots. Let’s build a more decentralized digital world together. #NDW #Band #AI #validator ethereum:0xba11d00c5f74255f56a5e366f4f77f5a186d7f55

ONE dollar. 💵 THREE versions of USDC. 💵💵💵 And somehow, YOU have to figure out which one your app actually accepts. 🤯 Welcome to the stablecoin maze. What if moving digital dollars across blockchains didn't require a detective license? @axelar just opened a new route. 🧵👇 -- 1️⃣ 🧩 The USDC identity crisis You want to send USDC. But your wallet shows different versions of the same digital dollar. Native USDC? Bridged USDC? USDbC? On @base , for example, circle -issued USDC and bridged USDbC are different tokens. Same dollar reference. Different contracts. And users are expected to know the difference. 🕵️ -- 2️⃣ 🧱 Fragmentation has a cost The problem goes beyond a confusing wallet. Multiple token versions can mean: 🔹 Liquidity split across different pools 🔹 More integrations for developers to manage 🔹 Extra friction for payments and DeFi 🔹 More confusion for users One digital dollar, multiple isolated markets. Not exactly the seamless Web3 experience we were promised. -- 3️⃣ 🔌 Axelar opens another route @axelar has announced native USDC swaps across supported chains. Its interface now shows routes such as: 💵 USDC on Ethereum ↓ 🌐 Axelar ↓ 💵 USDC on Base The idea is simple: Make cross-chain USDC transfers easier to navigate, with native USDC on supported routes. Fewer detours through the stablecoin maze. -- 4️⃣ 💳 Why native USDC matters Native USDC is issued directly by @circle . Bridged versions are created through separate mechanisms and carry different dependencies. For users, having a clearer route to native USDC means less confusion over which version to use. For protocols, reducing fragmentation can make liquidity and integrations easier to manage. Less detective work. More useful infrastructure. 🛠️ -- 5️⃣ 🌐 One USDC should feel like one USDC This launch doesn't magically remove every wrapped token or every cross-chain risk. But it's a step toward something Web3 badly needs: A world where users can focus on sending, receiving and using digital dollars. Not decoding token names and bridge contracts. The best interoperability makes complexity less visible, without ignoring security. That's a future worth building. 🌐 -- 🔁❤️ RT and Like to support simpler, more accessible cross-chain payments and decentralized interoperability. 💬 Have you ever struggled with multiple versions of USDC in your wallet? Do you think native USDC routes could make the multichain experience easier? Share your experience! 👇 Let's move forward together toward a new decentralized world. 🌐 #NDW #Axelar #USDC #Interoperability #validator base:0x23ee2343b892b1bb63503a4fabc840e0e2c6810f

RWA markets need assets to trade. They also need a way in. 💵🏦 With USTX set to launch and fiat purchases planned via @BanxaOfficial in the tx Super App, @txEcosystem is working to simplify how users fund their activity onchain. Infrastructure matters. So does accessibility. tx🌉 #tx tx:native #ustx #RWA

A TOKEN is not a MARKET. Tokenizing an asset is getting easier. Making it actually trade? That's another story. @PanteraCapital 's September 2026 report reveals a striking gap: 41% of tracked tokenized asset value generated 99.8% of observed spot trading. What does this tell us about the future of RWAs, and why is @txEcosystem building around this challenge? Let's unpack it. 🧵👇 -- 1️⃣ 🏗️ A token is not a market Imagine building an entire city. Beautiful buildings. Modern infrastructure. Everything connected. But there's a problem. The roads are empty. That's what can happen with tokenized real-world assets. Putting stocks, bonds or funds onchain creates digital representations. But functioning markets also need: • Eligible buyers and sellers • Trading venues • Market makers • Reliable settlement • Sufficient liquidity A token can exist without a meaningful secondary market around it. -- 2️⃣ 📊 The 99.8% paradox Pantera studied 110 non-stablecoin tokenized products, each worth at least $10M. In June 2026: 🟢 Open-access products: • 41% of tracked value • 99.8% of observed spot trading 🔒 Permissioned products: • 59% of tracked value • Just 0.2% of observed spot trading And 46 of 48 whitelist-only products recorded less than 1% monthly spot turnover. An enormous difference. But there's an important nuance. 👇 -- 3️⃣ 🚧 Why do permissioned markets struggle? Imagine a financial highway where every vehicle needs special authorization. The buyer is approved. But what about the seller? The trading venue? The liquidity pool? Its settlement address? For whitelist-only assets, these restrictions can prevent ordinary public trading pools from operating. Yet permissioned doesn't automatically mean illiquid. Many Treasury funds are designed to earn yield and offer redemptions, rather than trade constantly. Different assets need different market infrastructure. -- 4️⃣ 💧 Liquidity needs more than an open road Only 29 of the 110 products passed Pantera's trading-activity and holder-distribution tests. All 29 were open-access. But unrestricted transfers don't guarantee liquidity. Someone still needs to provide capital, quote prices and absorb orders. And for assets that rarely trade, traditional AMM incentives may not be enough. The familiar chicken-and-egg problem: Low volume → fewer fees → less liquidity → even less trading. Solutions may include dedicated market makers, request-for-quote execution or reliable issuer redemptions. -- 5️⃣ ⚙️ This is where TX enters the picture @txEcosystem approaches this challenge from the infrastructure side. Born from the convergence of Coreum and Sologenic, TX aims to bring together: 🔐 Identity and compliance 🏦 Institutional custody 🤝 Market making 📈 Regulated trading infrastructure ⚡ Blockchain settlement TX identifies BitGo for custody, Keyrock for market making, and SoloTex under development with SEC-registered broker-dealer Texture Capital. The ambition? Connect the pieces needed to turn tokenized assets into usable financial markets. Not just create more tokens. -- 6️⃣ 🛂 Compliance at the entrance Imagine entering an airport. Your identity and eligibility are checked before you enter the secure area. Once inside, you don't repeat the entire process at every shop. TX proposes a similar principle: Verify eligibility at the access layer, then allow supported assets to circulate within an appropriately controlled ecosystem. Its Cosmos-based Layer 1 also inherits Smart Token capabilities, including programmable transfer restrictions and issuer controls. Financial rules don't magically disappear, of course. Every asset and venue must still satisfy applicable requirements. The goal is to make compliance compatible with efficient market activity. -- 7️⃣ 💵 Why USTX matters Stablecoins represented $295.5B, or 89.1% of tracked tokenized market value at the end of June, according to Pantera. Why? Because the dollar remains the common language of onchain finance. Assets are priced in dollars. Liquidity is quoted in dollars. Collateral and settlement frequently rely on dollar-denominated instruments. This helps explain TX's introduction of USTX as a native dollar settlement asset. A marketplace needs assets to trade. It also needs reliable money to trade them against. -- 8️⃣ 📈 Demand exists. But where is it going? Pantera uncovered another fascinating contrast. In June: • $67.8B in equity perpetual trading on Hyperliquid and Lighter • $4.2B in observed tokenized-equity spot trading That's approximately 16× more activity in synthetic exposure. Perpetual traders can speculate on equity prices without owning tokenized shares. Leverage and repeated trading amplify these figures, so they don't represent equivalent invested capital. But the contrast is revealing: Demand for onchain financial exposure is growing, while liquid markets for direct tokenized ownership remain a challenge. -- 9️⃣ 🌉 From tokenized assets to functioning markets The next phase of RWA adoption will be measured by more than issuance announcements. The questions become practical: • Can investors access the asset? • Can they trade it at a reasonable price? • Can they redeem it? • Can they use it as collateral? • Can the infrastructure support these activities reliably? This is the challenge @txEcosystem is positioning itself to address. Its architecture and partnerships provide a roadmap. Actual liquidity, adoption and market activity will determine how successfully that vision translates into reality. For validators and infrastructure operators, the lesson is clear: A financial market needs more than tokens. It needs dependable rails, participants and liquidity. The next chapter of tokenization won't be written by issuance numbers alone. It will be written by what those assets can actually do. 🌐 #TX #RWA #Tokenization tx:native

40 fewer validators. More rewards for stakers. Two governance proposals. One fundamental trade-off. ⚖️ @osmosis is reshaping its economic model through two major governance decisions. On paper, greater efficiency and stronger staking incentives sound promising. But what happens to decentralization? And how can a network remain economically sustainable without concentrating too much power? Let's explore the economics of decentralization. 🧵👇 — 1️⃣ 🗳️ Two proposals, two different mechanisms. Osmosis has approved two significant governance changes: 🔹 #1051: Reducing the active validator cap from 70 to 30. 🔹 #1052: Increasing the share of non-OSMO taker fees allocated to stakers. These decisions affect two different aspects of the network: • Who participates directly in consensus. • How trading-generated revenue is distributed. Importantly, governance approval and technical implementation are separate steps. The real impact will depend on how these changes play out. — 2️⃣ ⚙️ Why do validator economics matter? Validators do much more than simply run servers. They participate in consensus, maintain infrastructure, secure signing keys, monitor uptime and coordinate network upgrades. All of this comes at a cost. A larger validator set creates more opportunities for participation. But without sustainable revenue, maintaining reliable infrastructure can become increasingly difficult. — 3️⃣ 🏗️ Proposal #1051: From 70 to 30 validators. That's 40 fewer active slots, representing a 57.1% reduction in the maximum validator set size. The proposal argues that a smaller set could: • Reduce consensus overhead. • Improve coordination during upgrades. • Make validator operations more economically sustainable. However, a smaller validator set also means fewer independent operators participating directly in consensus. — 4️⃣ ⚖️ Does fewer validators mean less decentralization? Not necessarily in the same proportion. Decentralization also depends on how voting power is distributed across the network. According to the proposal's snapshot, validators outside the top 30 represented approximately 11.9% of bonded OSMO. Still, fewer available slots can raise barriers to entry and make it harder for smaller or emerging validators to participate. Affected delegators may also need to redelegate to an active validator to continue earning staking rewards. Validator count alone doesn't tell the whole story of decentralization. — 5️⃣ 💰 Proposal #1052: Redistributing trading revenue. Previously, non-OSMO taker fees were allocated as follows: • 22.5% → Stakers • 25% → Community Pool • 52.5% → Burn The newly approved allocation: • 47.5% → Stakers • 0% → Community Pool • 52.5% → Burn The distribution of taker fees collected in OSMO remains unchanged. And the Community Pool continues to receive revenue from other sources. — 6️⃣ 🧩 Two changes, one broader economic debate. Reducing the validator set changes who can participate directly in consensus. Redistributing taker fees changes how protocol-generated revenue is shared with stakers. These decisions deserve to be examined together, without assuming that one was designed to compensate for the other. What matters now is how their combined effects influence network security, operator diversity and long-term economic incentives. — 7️⃣ 🌐 Decentralization comes at an economic cost. A blockchain needs sufficient revenue to sustain the infrastructure securing it. But it also needs room for independent operators, broad participation and a healthy distribution of power. Finding the right balance is an ongoing challenge. And the consequences of these decisions should remain transparent, measurable and open to community scrutiny. Because decentralization isn't simply about how many validators a network has. It's also about how power, responsibility and economic opportunities are distributed. — 8️⃣ 💭 So, where should the balance lie? Can a smaller validator set improve economic sustainability without creating excessive concentration? And can stronger staking incentives help secure a network while preserving opportunities for independent operators? These are questions worth discussing well beyond Osmosis. Follow us to learn more, and let's build a new decentralized world together. #Osmosis #NDW #validator

Really clear walkthrough by @AsankaKasum. 👏 No reason to reinvent the tutorial when someone has already explained the Gno.world onboarding, Gnoname, Gnomail and $BUBBLE referral flow this well. If you want to explore it yourself, you can start here 👇 🔗 gno.world/go/mmwjo2fg Good community documentation deserves to be shared. 🛠️ #Gnoland #Gno #validator

A blockchain can make every transaction public. But what about the work happening behind the scenes? 🔍 @THORChain is opening the engine room: 🔹 Development progress and code reviews 🔹 Stagenet tests, including failures 🔹 Blockers, fixes and upcoming releases 🔹 Node upgrades and adoption For validators, operators and users, this kind of visibility matters. Transparency also means showing what is still broken, blocked or unfinished. A valuable initiative for a more accountable blockchain ecosystem. ⚛️ #THORChain #NDW #validator thorchain:native

🌐 The Internet was supposed to be global. But increasingly, where you live determines what you can see, access, say… or even connect to. Meanwhile, @SentinelP2P is approaching 2 million cumulative users and preparing its next chapter on Solana. Those two stories are more connected than they seem. 🧵👇 — 1️⃣ 🔐 Internet freedom is becoming infrastructure For years, privacy tools were often treated as optional products: “Need more privacy? Download a VPN.” But the Internet is becoming more fragmented. Websites get blocked. Platforms get restricted. Networks get shut down. Access changes across borders. In that world, alternative routes matter. — 2️⃣ 🌍 And this is no longer a marginal geopolitical issue According to Access Now, at least 313 internet shutdowns were documented across 52 countries in 2025. The highest number they have ever recorded. Freedom House also reported a 15th consecutive year of decline in global Internet freedom. The open Internet cannot simply be taken for granted anymore. — 3️⃣ 🗳️ Nor is the debate limited to authoritarian states Democratic societies are also wrestling with increasingly difficult questions around: • platform blocking • age verification • online surveillance • content regulation • encryption • digital identity • access to information Some measures pursue legitimate goals such as child protection, crime prevention or national security. But every new gate raises the same infrastructure question: Who ultimately controls the road? — 4️⃣ 🛡️ This is where Sentinel becomes interesting Sentinel is not simply a VPN application. It provides infrastructure that independent applications can use to connect users with independently operated bandwidth nodes. Different apps. Different interfaces. Different communities. One shared network underneath. Think less “one VPN company.” Think more “public railway for private connectivity.” — 5️⃣ 📈 And people are already boarding the trains Sentinel has been reporting adoption approaching the 2 million cumulative-user milestone across its dVPN ecosystem. The exact methodology behind these cumulative figures still deserves more transparency. But the broader trajectory is interesting: Sentinel is no longer an experiment looking for its first users. Its infrastructure is already carrying meaningful traffic. — 6️⃣ ☀️ Now comes Solana Sentinel has announced preparations to rewrite parts of the protocol in Rust and move toward Solana. The migration is not completed yet. But the strategic direction is important. Why Solana? A much larger ecosystem of: • users • wallets • applications • liquidity • payments • developers For privacy infrastructure, distribution matters. The best tunnel in the world is useless if nobody can find the entrance. — 7️⃣ 🧩 But moving to Solana does NOT mean the physical network disappears This distinction matters. Solana can become part of the coordination and economic layer. But the actual bandwidth still comes from independent dVPN nodes. Servers still move packets. Apps still create the user experience. Operators still provide connectivity. Blockchain is the coordination layer. The road still needs asphalt. — 8️⃣ 🤖 And humans may not be the only passengers Sentinel is also exploring a world where bandwidth becomes programmable. Through initiatives such as x402, software and AI agents can request connectivity, pay for it and establish access programmatically. That changes the model again. Not only: “I subscribe to a VPN.” But eventually: “My software needs connectivity, finds it, pays for it and uses it.” Internet access becomes a machine-consumable resource. — 9️⃣ 🌐 Which brings us back to Internet freedom A free Internet cannot depend only on political promises. It also needs technical alternatives. Alternative nodes. Alternative routes. Open protocols. Independent applications. Infrastructure that remains usable across borders. Because censorship does not always arrive as a giant red OFF switch. Sometimes it arrives one small gate at a time. — 🔟 🛤️ Sentinel's next chapter is therefore bigger than a chain migration. Solana could give the protocol access to a much larger distribution layer. More builders can create applications. More users can discover them. Machines may eventually consume bandwidth directly. But the underlying mission remains remarkably physical: Keep routes to the Internet open. In a world slowly building more digital borders, decentralized bandwidth may become less of a crypto experiment… and more of a piece of public digital infrastructure. 🛡️🌐 🔁 💙 RT and Like if open access should remain part of the Internet's foundations. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Sentinel #Solana #dVPN #validator #VPN

Lava has voted to move house. The new address is still undecided. 🏠 Proposal #69 approved the direction: move from Lava’s own Cosmos chain to an EVM-based protocol. But choosing to move and completing the move are very different steps. What changes for the infrastructure behind your apps? Let’s unpack it. 🌋 @lavanetxyz 🧵👇 -- 1️⃣ 🗳️ What the community approved Proposal #69 passed on October 2. Lava reports that around 290M LAVA voted YES. The decision supports moving away from operating its own blockchain toward a protocol hosted on an EVM-compatible network. The host chain, technical plan and tokenomics remain separate community decisions. The green light is for the direction. The migration is not complete. -- 2️⃣ 🔌 Two jobs under one roof Today, Lava has two distinct infrastructure roles: Validators keep Lava’s own blockchain running. Providers serve the blockchain requests used by wallets and apps. Under the intended architecture, the host network would provide consensus. Providers would still be needed to serve RPC requests. Changing where Lava runs does not, by itself, determine which blockchains it can serve. Cosmos access and a Cosmos-based home are different things. -- 3️⃣ 🛠️ Why consider moving? Running your own blockchain comes with a maintenance bill. Chain software. Coordinated upgrades. Validator operations. Wallet and explorer compatibility. The Foundation’s argument is that a hosted protocol could reduce that burden and let Lava focus more on its core service: helping applications reach reliable blockchain data. Owning the whole building also means maintaining the whole building. -- 4️⃣ 📦 This is a rebuild The CTO describes a reimplementation, informed by years of running Lava. Some features may change. Some little-used features may not be migrated. The team wants to use that experience to simplify the protocol. Expected improvements in efficiency, performance and security remain goals. They are not measured results of a completed migration. -- 5️⃣ 🏠 The new address matters EVM is a family of compatible networks. It does not mean Ethereum has been selected. The future host will bring its own: • fees • capacity • security • availability Lava could shed some maintenance work while taking on new dependencies. Reliable RPC Providers and a reliable host network are both important. Choosing the address deserves as much attention as choosing to move. -- 6️⃣ 📱 What does this mean for users? For someone opening a wallet, the useful outcome would be dependable access without extra complexity. For LAVA holders and stakers, the transition details matter directly. How will balances and existing staking be handled? What changes for current validators? How will apps maintain access during the switch? Those details are not settled by #69. A vote on direction is not a wallet migration guide. -- 7️⃣ 👀 What to watch next In its September Ecosystem Call, the team outlined a target of around late January 2027 for full migration. It aims to finalize discussions around economics and the host chain by late November 2026. These are planning targets, not guaranteed deadlines. Next, watch for: • the proposed host network • the technical migration plan and security checks • instructions for holders, stakers and operators • separate tokenomics decisions The community has agreed to move house. Now comes the part that matters to everyone using it: making sure the lights stay on during the move. 🌋 #LavaNetwork #EVM #Infrastructure #Web3

We’ve been quietly building something for the Gno.land ecosystem. 👀 Meet GnoDelve, our explorer for @_gnoland : 🔎 Explore blocks, transactions & validators 🧩 Browse and interact with realms 👛 Connect with Adena 🌐 Follow network & IBC activity 📊 Access key network and economic data The goal is simple: make Gno.land easier to explore and progressively more useful to interact with. It’s still evolving, and we’re regularly adding features, fixes and improvements. Take a look 👇 delve.ibs.team/ #Gnoland #Gno #validator

A blockchain upgrades its locks… and its neighbors can no longer recognize its keys. 🔐🛂 That’s the challenge of the post-quantum transition in @cosmos : stronger signatures while keeping IBC crossings open. What this means for your transactions, delegations, and networks 👇 -- 1️⃣ 🧩 Preparing tomorrow’s locks Cosmos Labs introduces “Post-Quantum Ledger Security 2026.1”. On the agenda: 🛡️ Quantum-resistant signatures. 🔄 Validator key rotation. 🗝️ Remote signing. Three tools to help the infrastructure evolve. -- 2️⃣ 🔑 Signatures: your digital authorization When you send tokens, your key signs the transaction. Think of it as your account’s “approved” stamp: the network can verify it. Validators also sign their consensus votes. These signatures secure both accounts and consensus. -- 3️⃣ 🛡️ Why change signatures? A sufficiently powerful quantum computer could break the protection provided by conventional signatures. The Cosmos Stack adds ML-DSA-65, a NIST-standardized algorithm designed to resist this threat. Preparing new locks before they’re needed. This does not make transactions private. -- 4️⃣ 🔄 A new key, the same delegations On a compatible chain, a validator can replace its consensus key while keeping its identity and delegations. Like changing a house’s lock without asking everyone to move out. 🏠 With proper preparation, the transition can happen without downtime. -- 5️⃣ 🗝️ The key can stay in the vault With cosmos/kms, a validator node can request a signature from a separate service. Imagine a desk sending a document to a secure vault: the signature comes back, while the key stays inside. Compatible key management services or hardware can safeguard it. -- 6️⃣ 🛂 IBC: neighbors need compatible readers Imagine more secure passports… presented to an outdated border scanner. IBC faces a similar challenge: partner chains must be able to verify the new signatures. Otherwise, connections can be disrupted and transfers between those networks blocked. Relayers carry the proofs; chains verify them. -- 7️⃣ 🚦 Your wallet doesn’t migrate itself Available tools do not mean every Cosmos network already uses them. Each chain must prepare its software and enable the new consensus key types. User accounts require their own migration. And larger signatures mean more data to carry. -- 8️⃣ ⚛️ Stronger keys, open crossings For users, the goal is tangible: secure transaction authorizations and preserve exchanges between networks. For technical teams, that takes preparation and coordination. The locks evolve. The borders must keep up. 🔁💙 RT and Like to spread the explanation. 💬 Let’s discuss and move forward together toward a new decentralized world. #Cosmos #IBC #NDW #validator cosmos:native

Your wallet doesn’t run on magic. 🪄 Someone runs the servers. Someone pays the bill. @lavanetxyz is proposing a new way to connect paid usage to the infrastructure behind your apps. And it starts with a surprising number: 98% of its recorded Provider Drop quota was burned. Here’s what that actually means. 🌋 🧵👇 -- 1️⃣ 🔌 Who keeps the lights on? When you check a balance or use a blockchain app, it needs to communicate with the network. That connection usually happens through RPC. Think of it as the road between your app and the blockchain. Lava coordinates independent Providers that serve these requests. Those roads need working servers. And working servers have real costs. -- 2️⃣ 💧 A fuel allowance with plenty left over Provider Drops helped bootstrap Lava’s infrastructure. Each month, up to 1.375M LAVA becomes available from reserves. Providers receive rewards under the mechanism’s rules. The unused balance is burned before the next refill. Between Nov 2024 and Sep 2026, around 98% of the recorded quota was burned. That measures unused funding capacity. It does not mean Providers did only 2% of the work. -- 3️⃣ 🔄 Let usage help pay the bill The proposed flow is simple: Customers pay for RPC access. Gateway revenue purchases LAVA. The purchased LAVA is then split: → 70% to Providers → 30% to an Assistance Fund Revenue already purchases or converts into LAVA today. The redesign changes how that value is distributed and would replace reserve-funded Drops. The proposed direction: let paid usage fuel the infrastructure serving it. -- 4️⃣ 🗳️ The 30% is not a burn button The Assistance Fund would hold LAVA onchain, with separate accounting and governance-defined limits. What happens to those tokens? The community would decide. Burning, redistribution or another approved treatment remain options. It would not be a general Foundation spending account. Think of a separate compartment with rules still to be agreed. -- 5️⃣ 💳 Busy roads don’t always collect tolls A billion requests sounds impressive. But free requests and paying customers tell different economic stories. This proposal focuses on paid Gateway usage. For September, Lava reported $29,233 in subscription-funded rewards, its third consecutive month without a Foundation contribution to that pool. A concrete example of customers funding infrastructure. That figure covers those rewards, not total Gateway revenue. -- 6️⃣ 📱 Why should users care? Because reliable access needs more than a token reward schedule. Providers need an economy that can sustain their servers. Multiple independent Providers give applications alternative routes when one operator struggles. Sustainable compensation helps support those routes. For users, the goal is straightforward: open the app, get the data, carry on. The machinery behind that simplicity still needs funding. -- 7️⃣ 👀 What to watch next This is a proposal, not an adopted model. The current system remains active until governance approves a replacement. The next questions matter: • Will the 70/30 split be adopted? • What limits will the Fund have? • How will existing reserves transition? • How will Provider rewards reflect paid usage and service quality? Lava is putting the infrastructure bill back on the table. Because the loading spinner may be free. The servers behind it aren’t. 🌋 #LavaNetwork #RPC #Infrastructure #Web3 base:0x11e969e9b3f89cb16d686a03cd8508c9fc0361af

Native ZEC is now live on @THORChain . ⚡ That means another native, permissionless route is now open between Zcash and the wider cross-chain economy. No account. No wrapped zcash:native . No KYC at the protocol level. For anyone who likes open financial rails… this is the fun part. 😄 But how does one simple “Swap” button actually make that possible? Let’s follow the transaction under the hood. 👇 -- 1️⃣ 🌐 From the user side, it feels simple You choose ZEC. You choose another native asset. You hit Swap. That’s exactly how good infrastructure should feel: simple on the surface, complicated underneath. Because behind that button, several independent blockchains have to coordinate without sharing the same rules. -- 2️⃣ ⚡ Permissionless by design One of the most interesting parts is what you don’t need. No centralized exchange account is required by the protocol. No wrapped version of ZEC has to be created first. No single company sits in the middle approving the route. THORChain provides the infrastructure for native assets to move between native chains. That’s a pretty cypherpunk idea hiding inside a very normal-looking button. -- 3️⃣ 👀 So what happens underneath? Before THORChain can process a ZEC swap, its nodes need to understand what is happening on @Zcash . They observe the chain. They watch incoming transactions. They track the vaults. And they report what they see back to THORChain. For the user: one new route. For THORNodes: one more blockchain to speak. -- 4️⃣ 🧩 Zcash is not just “Bitcoin with another logo” Zcash uses the UTXO model, so some concepts look familiar. But every chain has its own dialect. Different fee logic. Different transaction rules. Different network upgrades. That’s why adding a blockchain is very different from listing another token on a frontend. The network itself has to learn the chain. -- 5️⃣ 🔐 Then the network coordinates the swap Once the inbound ZEC is observed, THORChain coordinates the swap through its liquidity and vault infrastructure. The outbound asset is then sent natively on its own blockchain. No wrapped ZEC detour. No “bridge token” that the user has to hold first. Zcash on one side. Another native chain on the other. THORChain coordinating the route between them. -- 6️⃣ 🕶️ One important privacy nuance ZEC may be famous for privacy. But native ZEC on THORChain does NOT mean shielded cross-chain swaps. The current integration uses Zcash’s transparent UTXO infrastructure. So: Native? Yes. Permissionless? Yes. Censorship resistant at the protocol level? Yes. Automatically private? No. Permissionless infrastructure and privacy are powerful ideas. They are not the same thing. -- 7️⃣ ⚙️ The best infrastructure disappears For users, this new route can eventually feel almost boring: choose an asset, choose another, swap. And that’s the interesting part. Because underneath that simple UX, a distributed network is observing another blockchain, coordinating vaults and keeping a native cross-chain route open. More native assets. More open routes. Fewer unnecessary gates. That’s the machine hiding behind the Swap button. Educational thread, not financial advice. 🔁❤️ RT and like to support decentralized cross-chain infrastructure 💬 Let’s discuss and move forward together toward a new decentralized world. #NDW #THORChain #Zcash #validator #ZEC

A token can survive on-chain for years. But what gives that token meaning also needs to survive. If the image, metadata or provenance behind it disappears… you suddenly own a beautiful certificate pointing into the interstellar void. 🌌😅 That’s why the @ProtocolTalis × @lumera partnership is more interesting than a simple storage integration. Let’s unpack it 👇 1️⃣ 🧾 The token is not the whole story NFTs can live on-chain while much of what gives them context lives elsewhere: • media • metadata • authenticity records • provenance • RWA documentation If that external data disappears, the token may still exist… but part of its memory disappears with it. And sometimes, part of its utility too. -- 2️⃣ 💾 Enter Cascade Talis is an NFT marketplace built on @injective , with tools for creators, launches and digital assets. Talis plans to use Lumera’s Cascade as a permanent, verifiable storage layer for this kind of data. Cascade doesn’t simply throw a file onto one server and hope someone remembers to renew the bill. 😅 Data is encoded with redundancy and distributed across Lumera SuperNodes. The goal: keep it available, retrievable and verifiable over time. -- 3️⃣ 🧩 The network checks its homework SuperNodes don’t simply say: “Trust me bro, the file is still here.” 👀 Cascade includes mechanisms designed to verify that data is actually being retained. Operators can earn rewards for providing the service, while failures can trigger penalties and recovery mechanisms. Storage becomes infrastructure backed by economic accountability. -- 4️⃣ ⚙️ But Talis goes one step further Talis doesn’t only plan to use Cascade. It also plans to operate: 🗄️ a Lumera SuperNode 🛡️ a Lumera validator Two different jobs. The SuperNode helps provide services such as Cascade storage. The validator helps secure Lumera’s blockchain through consensus. One helps keep the memory alive. The other helps secure the ledger coordinating it. -- 5️⃣ 🔧 From customer to operator And this may be the most interesting part. The traditional model looks like: application → infrastructure provider Here, the relationship starts looking more like: application ↓ uses the infrastructure ↓ helps operate the infrastructure ↓ helps secure the network behind it Talis moves from simply using the machinery… to becoming part of the machinery underneath. -- 6️⃣ 🏗️ Secure the infrastructure you depend on That idea captures something important about decentralized systems. If your application depends on infrastructure for long-term storage, participating in that infrastructure can help align incentives. You are no longer simply renting someone else’s machine. You have a reason to help keep the machine running. Users become operators. Dependency becomes participation. -- 7️⃣ 🧠 From minted to remembered A token can persist on-chain. But the data giving it context also needs somewhere durable to live. And decentralized infrastructure becomes especially interesting when the applications depending on it also help operate and secure it. Not just using the rails. Helping maintain them. 🛤️ Durable tokens need durable data. 🔁 ❤️ RT & Like if you believe Web3 infrastructure becomes stronger when the applications that rely on it also participate in operating it. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Lumera #Web3 #DecentralizedStorage #validator

The best bridge UX may be no bridge at all. No route hunting. No infrastructure puzzle. No need to understand what happens underneath. Just tell the system where you want to go. That’s the direction @axelar is now exploring with Axelar Intents. 👇 -- 1️⃣ 🧭 Bridges ask you to choose the road. Intents start with a different question: Where do you want to arrive? @axelar is now developing its own intents protocol — alongside a new RFQ API designed to make cross-chain execution easier for wallets, exchanges and apps. Here’s what we actually know. 👇 -- 2️⃣ 🧩 Intents are not completely new to Axelar Back in 2023, Axelar was already exploring intent-based execution through Squid Boost + GMP Express. A third party could advance liquidity on the destination chain, then recover it once the canonical Axelar transaction settled. The concept existed. What changes now is who builds the execution layer. -- 3️⃣ 🛠️ Axelar is building its own protocol In September 2026, Axelar confirmed it was developing: “our own intents protocol” for instant cross-chain transfers and swaps. Important distinction: This new Axelar Intents protocol is still being built. It is not a publicly documented mainnet product yet. -- 4️⃣ 🛰️ The RFQ API may be the most important piece Common Prefix revealed an RFQ API being built alongside Axelar Intents. It brings together four ways to move assets through Axelar: → Intents → ITS → Gateway transfers → Express delivery One integration layer. Several possible execution paths underneath. -- 5️⃣ ⚡ Express ≠ Intents Express already solves one specific problem: waiting. An executor can deliver value earlier and be reimbursed once the canonical Axelar transaction settles. Intents aim at a broader abstraction: the user specifies the desired transfer or swap. More of the execution complexity can move behind the interface. Different problems. Different primitives. -- 6️⃣ 🧠 This changes the UX model The old cross-chain experience often looks like: User → choose chain → choose bridge → choose asset → understand the route → wait The direction Axelar is moving toward looks more like: User → request an outcome → infrastructure handles more of the journey → destination The cables start disappearing behind the interface. -- 7️⃣ 🌐 From roads to routing Axelar already built infrastructure for assets and messages to move between chains. Intents + RFQ suggest the next step: making the user care less about which road is taken. The user says where they want to go. The infrastructure handles more of the journey. That may be the real evolution of interoperability: not more bridges on the screen… but fewer reasons to think about bridges at all. 🔁💙 RT and Like to support open, secure and decentralized interoperability. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Axelar #Interoperability #Intents #validator @Axl_Ecosystem @CommonPrefix base:0x23ee2343b892b1bb63503a4fabc840e0e2c6810f

Quiet timeline. Busy ledger. 👀 @provenancefdn has been unusually quiet on X. But on-chain? Provenance governance just approved the creation of NUVA’s HOME vault. And underneath that small governance proposal sits a much bigger story: how real financial activity may feed the economics of the network itself. Let’s open the hood 👇 -- 1️⃣ 🏠 First, meet HOME Proposal #112 created the upcoming NUVA HOME vault directly on Provenance Blockchain. Very simplified: real-world housing credit ↓ structured into a vault ↓ shares represented on-chain ↓ YLDS used underneath the vault No need for a TradFi headache yet. 😅 Think of a vault as a financial container with rules written into the infrastructure. -- 2️⃣ 🧱 The interesting part is underneath HOME is not just “a token representing some loans.” Provenance has a native Vault Module designed to manage things like: assets vault shares NAV redemptions fees settlement In other words: less “put a shiny wrapper on the asset.” More “build the machinery around it.” -- 3️⃣ 🚰 Now follow the plumbing If financial applications actually use these rails, they generate activity. Transactions. Asset exchanges. Settlement. Network fees. And this is where Provenance becomes interesting from a validator perspective. Because the new HASH economy tries to connect that activity to the network securing it. -- 4️⃣ ⚙️ Where do the fees go? For standard network fees, the model described by Provenance is: 60% → validators / network security 40% → HASH Market Settlement fees go even further: 100% → HASH Market So the plumbing starts looking like: financial activity ↓ fees ↓ security + HASH Market Pretty simple so far. 😄 -- 5️⃣ 🛒 Wait… what is the HASH Market? Imagine a small on-chain auction house. Assets collected through the fee system can be auctioned. Participants bid for them. And when HASH is used as the winning bid... 🔥 that HASH is burned. Important nuance: activity does NOT automatically burn HASH. The activity feeds the mechanism. The auction determines what happens next. -- 6️⃣ 🛡️ Then comes staking Provenance also redesigned HASH inflation around network security. The target is roughly 60% of HASH staked. If staking falls too low, inflation can increase. Around the target, inflation can fall toward 1%. So staking becomes less of a fixed faucet... and more of a thermostat. 🌡️ The goal: keep enough HASH helping secure the network. -- 7️⃣ 🔄 Now connect the whole machine HOME makes the story easier to visualize. Real financial activity ↓ Provenance infrastructure ↓ transactions + settlement ↓ fees ↓ validators + HASH Market ↓ staking + auctions ↓ potential HASH burn Not just: “Look, we tokenized an asset.” 🖼️ But: “What economic activity does that asset create for the network carrying it?” -- 8️⃣ 🧠 The bigger picture Provenance has spent years talking about making financial assets digitally native. Origination. Ownership. Trading. Financing. Settlement. The quieter evolution is happening underneath: HASH is increasingly being designed as the bridge between network usage, validator security and the economics of the chain. The fascinating part will not be the diagram. It will be watching how much of this loop becomes measurable on-chain as products like HOME go live. Less timeline. More ledger. 🔎 Educational thread, not financial advice. 🔁❤️ RT and like to support more educational content about verifiable on-chain finance. 💬 Let’s discuss and move forward together toward a new decentralized world. #NDW #Provenance #RWA #HASH #validator hash-2:native

Launching a blockchain is easy to celebrate. Shutting one down properly is much harder. @stride_zone is now proposing an orderly wind-down of the Stride chain. And it reveals something Web3 rarely talks about: Sovereignty has an operating cost. 🧵👇 — 1️⃣ 🏗️ What does blockchain sovereignty actually cost? An appchain is more than code. It requires sustained attention around: • security • validators • upgrades • infrastructure • monitoring • governance The chain may be autonomous. The maintenance bill is very real. — 2️⃣ 💰 Stride reached an economic wall. Stride Labs and the Stride Association say they are low on runway. At the current burn rate, they expect to run out of funds around February 2027. Meanwhile, Stride currently secures roughly $6M in TVL. Their conclusion: Keeping the chain running indefinitely without adequate resources would not be responsible. — 3️⃣ ⚙️ And Stride had already reduced the cost of securing its chain. In 2025, Cosmos Hub governance approved Stride's move from Top-N 95% PSS to an opt-in model with 7 validators. At the time, Stride explained that validator commissions were not enough to cover operating costs. That change significantly reduced the chain's security budget. But the broader business sustainability problem remained. — 4️⃣ 🧯 So Stride is choosing to wind down while it still has the resources to do it properly. The timeline: 📅 Until Oct 12 Normal stToken redemptions. ⏸️ From Oct 12 New redemptions pause while the backing assets unbond. 🌊 Around Nov 20 Redemptions resume on Osmosis. Exact timing depends on unbonding periods. — 5️⃣ 🔄 What happens to stTokens? They don't disappear. All stTokens and their backing assets are planned to move into Transmuter pools on Osmosis. stATOM → ATOM stOSMO → OSMO and so on. Redemption effectively becomes a swap at a fixed redemption rate. Every stToken remains fully backed. — 6️⃣ ⏳ And holders aren't being forced into an immediate exit. Once migration is complete: • stTokens do not expire • redemption pools remain available • staking rewards stop accruing • redemption rates become fixed Even stTokens already on other chains won't need to be bridged back to Stride first. The Osmosis pools are designed to accept them directly. — 7️⃣ 🧩 And this is where the economic dependencies become visible. One day after Stride's announcement, two new Osmosis governance discussions appeared around Community Pool liquidity. They aren't on-chain decisions yet. But they show how one chain winding down can force surrounding infrastructure to be reconsidered. — 8️⃣ 🧹 The first discussion is broader than Stride. Margined is discontinuing its managed liquidity service on Osmosis. The Community Pool still owns vault positions involving: • stOSMO/OSMO • bOSMO/OSMO • ampOSMO/OSMO • ETH/BTC Governance is discussing unwinding them. — 9️⃣ 🔥 If that proposal reaches governance and passes as currently written: Around 8.1M OSMO would be recovered directly. Another ~1.27M OSMO could come from redeeming bOSMO. The plan would burn roughly 9.4M OSMO in total. BTC and ETH would return to the Community Pool. This isn't caused solely by Stride. But Stride's wind-down is part of the changing LST landscape around it. — 🔟 🛟 The second Osmosis discussion connects much more directly to Stride. Osmosis currently maintains an 8M OSMO position below the stOSMO market. Think of it as a standing emergency bid. If stOSMO depegged, this liquidity could absorb selling pressure and help lending liquidations clear. But the environment has changed. — 1️⃣1️⃣ 📉 Those lending markets are now largely inactive. And during Stride's redemption pause, that 8M OSMO backstop could end up buying stOSMO whose redemption depends on the wind-down completing. So Osmosis governance is discussing removing it. Not because stOSMO suddenly became unbacked. It remains backed. The economic purpose of the safety mechanism simply changed. — 1️⃣2️⃣ 🧱 This is why shutting down a blockchain isn't an ON/OFF button. Stride can eventually stop producing blocks. But first: • backing assets must unbond • stTokens need redemption paths • liquidity positions must be reconsidered • support mechanisms must be unwound • users need a safe exit Economic dependencies don't disappear when the validator set stops. — 1️⃣3️⃣ ⚖️ This is the hidden cost of sovereignty. A dedicated blockchain gives a protocol control over its: • execution • governance • architecture • economic design But specialization only makes sense while the activity above can justify the infrastructure below. Sovereignty is powerful. It isn't free. — 1️⃣4️⃣ ⚛️ And this isn't an argument against Cosmos appchains. Quite the opposite. A modular ecosystem shouldn't only make it possible to launch specialized chains. It should also make it possible to retire them responsibly when their economics no longer work. Stride is becoming a rare real-world case study of exactly that. — 1️⃣5️⃣ 🚪 Stride's story isn't simply: "Another blockchain is shutting down." It's a demonstration of what responsible wind-down can look like. Act before the treasury reaches zero. Keep every asset backed. Give users time. Build the exits before turning off the lights. #Stride #Cosmos #Osmosis Follow us to learn more, and let's build a new decentralized world together. #NDW #validator

Banks don’t need to become crypto companies. They need better rails. 🏦🚄 Swift is building infrastructure to move tokenized bank money 24/7. Cosmos wants to help connect existing banking systems to those new rails. Here’s what that actually means 👇 -- 1️⃣ 🚄 What Swift is building @swiftcommunity has added a blockchain-based ledger to its infrastructure. Its first use case: enabling banks to move tokenized deposits across borders 24/7. 17 banks are participating, including BNP Paribas, Citi, HSBC, UBS and Wells Fargo. But there is an important detail... -- 2️⃣ 🏦 The money stays with the banks A tokenized deposit is still commercial bank money. The issuing bank keeps the deposit on its own ledger and balance sheet. Swift provides a shared orchestration layer so institutions can coordinate movements between them. Final settlement can still happen through existing financial systems. 🏦 → 🚦 → 🏦 -- 3️⃣ 🔧 The old plumbing problem Banks already run enormous core banking infrastructures. Fiserv. FIS. Jack Henry. Temenos. Hogan. Replacing these systems just to enter tokenized finance would be... slightly inconvenient. 😅 So the challenge becomes: How do you connect decades-old banking infrastructure to new digital rails? -- 4️⃣ 🔌 This is where Cosmos enters The Cosmos Tokenization Suite is designed to let financial institutions: • deploy their own tokenized deposit ledger • synchronize it with existing core banking systems • connect it to external networks Including Swift’s ledger, Canton, Partior, Ethereum and Solana. Think connectors, not replacement. -- 5️⃣ 🗺️ The architecture A simplified version looks like this: 🏦 Core banking system ↓ 🪙 Bank’s tokenized deposit ledger ↓ 🔌 Cosmos Tokenization Suite ↓ 🌐 Swift + other networks Cosmos isn’t claiming to own Swift’s railway. It is building the switches and connections that can help banks reach it. -- 6️⃣ 🌐 The next problem is interoperability Creating a token is relatively easy. Making value move between different banks, ledgers, networks and counterparties while preserving settlement, compliance and reconciliation is much harder. Otherwise, finance simply replaces old database silos... with shiny new blockchain silos. -- 7️⃣ ⚠️ One important distinction This announcement is about @cosmoslabs_io , @cosmos technology and the Cosmos Tokenization Suite. It does NOT currently demonstrate that: ❌ Swift runs on Cosmos Hub ❌ Swift uses ATOM ❌ ATOM captures value from these transactions What it does show is increasingly clear: Cosmos technology is being positioned as connective infrastructure for institutional tokenized finance. Not just another blockchain. Infrastructure between infrastructures. ⚛️ Sources: Cosmos Labs: prnewswire.com/news-releases… Swift: swift.com/news-events/press-… 🔁💙 RT and Like to help make institutional blockchain infrastructure easier to understand. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Cosmos #Swift #Tokenization #validator cosmos:native