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

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. 🛡️🦾

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

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

Same dollar. Too many wrappers. Too much friction. @osmosis has already chosen its canonical USDC. Now it may start moving its own capital to match. That is where a governance choice starts becoming real infrastructure. 🧪💵 Let’s break it down 👇 - 1️⃣ 💵 What is Alloyed USDC? Osmosis currently has multiple USDC routes: • USDC.noble • USDC.inj • USDC.eth.axl Alloyed USDC (allUSDC) brings them under one common representation instead of leaving liquidity fragmented across separate versions. - 2️⃣ ⚙️ How does it work? Through Osmosis’ Transmuter infrastructure, a constituent like USDC.noble can be converted 1:1 into allUSDC: • no swap fee • no slippage • no price impact So allUSDC is not a new dollar. It is a unified representation of several existing USDC routes. - 3️⃣ 🗳️ Step one is already done Proposal 1039 has PASSED. It made Alloyed USDC the canonical USDC on Osmosis and updated protocol parameters accordingly. In short: the standard has already changed. - 4️⃣ 🏦 Now comes step two A new governance discussion published on Sept. 3 proposes migrating DAO-controlled USDC positions into allUSDC. That includes: • Community Pool USDC • Margined vaults • static liquidity positions • the BTC/USDC position tied to Prop 1029 - 5️⃣ 💰 This affects real protocol-owned capital Roughly: • ~$692k Community Pool USDC • ~$196k Margined vaults • ~$669k static positions • ~$297k former Magma-related position Around $1.85M in protocol-controlled positions could be restructured. - 6️⃣ 🔧 This is more than a simple rename If approved, BTC/USDC and USDT/USDC liquidity would be rebuilt using allUSDC, while DOGE and XRP bootstrapping positions would be unwound and redirected. So the change is operational, not cosmetic. - 7️⃣ 🧩 Why this matters This is a good example of how DeFi infrastructure evolves in stages: governance decision → parameter changes → real asset migration Osmosis is not only saying allUSDC is canonical. It is preparing to align its own treasury and liquidity with that architecture. - 8️⃣ ⏳ Important: this is not final yet The Sept. 3 post is still a governance discussion. Target on-chain date: 📅 September 9, 2026 So for now, we are watching the blueprint before the final on-chain decision. -- 🔁💙 RT and Like if you enjoy seeing how protocol architecture becomes economic reality. Should canonical assets abstract multiple routes for a better UX, or should users continue to interact with each route separately? 💬 Join us to learn more, discuss, and ask questions as we move together toward a new decentralized world. #NDW #Osmosis #Cosmos #DeFi #IBSvalidator

Figure didn’t just buy another lender. It just connected a much bigger pipe of real-world credit to its blockchain-native marketplace. 🏠⛓️ And for Provenance Blockchain, that is where the Kiavi acquisition gets interesting: more assets, more financial workflows, more reason for the rails to exist. Let’s break it down 👇 -- 1️⃣ 🏠 Meet Kiavi @kiavifunding is a major U.S. non-bank lender focused on residential real estate investors. Its specialties include: • Residential Transition Loans (RTL) • DSCR rental-property loans • data-driven and AI-powered underwriting Figure officially completed the acquisition on September 1. But buying the lender is only half the story. -- 2️⃣ 🚰 Figure bought a new asset faucet @Figure Connect connects loan originators with capital markets buyers. Kiavi now gives Figure another large source of private-credit assets that can flow into that marketplace. When the transaction was announced, Figure said it expected Kiavi to contribute over $7B in annual first-lien volume to Figure Connect. That is a rather large faucet. 😅 -- 3️⃣ ⛓️ Now add the blockchain This is where the plumbing changes. Figure Connect runs on blockchain rails and uses Provenance Blockchain for its loan infrastructure. Figure has described the goal very clearly: bring Kiavi assets onto its tokenized marketplace rails. So instead of blockchain being added as a decorative sticker at the end... it becomes part of the asset lifecycle. -- 4️⃣ 📚 From loan to verifiable asset A loan moving through this architecture can carry blockchain-based records that help create a shared source of truth. That matters for things like: • ownership and asset registration • data provenance • collateral verification • transaction history • reducing double-pledging risk Less: “Trust the spreadsheet someone emailed Tuesday.” More: “Verify the record.” A small cultural revolution for finance. 😄 -- 5️⃣ 🤖 AI meets the ledger There is another interesting layer: Adaptor. Figure plans to use its AI system to normalize data coming from different originators before assets enter its marketplaces. Kiavi is the first planned use case for this agent-to-agent onboarding model. Think of it as: AI helping check and standardize the luggage... before blockchain rails move it through the financial airport. 🧳 -- 6️⃣ 🔄 And the assets do not have to stop there Figure’s stack connects Figure Connect with other infrastructure including DART and Democratized Prime. At announcement, Figure said Kiavi was expected to bring more than $100M in monthly flow to Democratized Prime. This is important. The goal is not simply: tokenize a loan → admire tokenized loan. 🖼️ It is to make financial assets easier to fund, transfer, verify and potentially use across programmable markets. -- 7️⃣ 🧭 Why this matters for Provenance Here is the @provenancefdn angle. Figure Connect uses Provenance Blockchain. So if Figure successfully integrates more Kiavi-originated assets into this architecture, Provenance is not merely hosting another “RWA project.” It can become the underlying registry and infrastructure through which more real credit activity is recorded and coordinated. More assets can mean more: registration, verification, transactions, settlement, financial activity. That is a much healthier metric than counting logos on an ecosystem page. -- 8️⃣ 🏗️ The bigger picture Figure + Kiavi illustrates what RWA adoption may increasingly look like. Not: TradFi disappears and everyone wakes up farming JPEGs. 🌾 But existing financial businesses gradually connect their assets to shared, programmable infrastructure. Kiavi brings origination. Figure brings the marketplace, financing and technology stack. Provenance provides the public blockchain rails underneath part of that machinery. Not just assets on-chain. Financial infrastructure becoming more verifiable and usable. Educational thread, not financial advice. 🔁💙 RT and like to help explain why real blockchain adoption is hidden inside the financial plumbing. 💬 Let’s discuss and move forward together toward a new decentralized world. #NDW #Figure #Provenance #RWA #validator

Sentinel’s latest network figures show something important for decentralized infrastructure: real usage is already happening at scale. In August, the Sentinel ecosystem recorded: 🔒 6 million encrypted dVPN sessions in one month. 👩‍💻 77,263 new users. 📈More than 9.6 million on-chain transactions. @SentinelP2P is entering its next phase with something many infrastructure projects spend years searching for: real usage. Let’s look at what August tells us. 🧵👇 -- 1️⃣ 📊 August set another milestone for Sentinel Over the month, the ecosystem recorded: • 77,263 new users • 6M+ encrypted dVPN sessions • 9,622,134 blockchain transactions • 695,069 blocks processed • 13.84 transactions per block on average These are not testnet numbers. They represent activity generated by a live network. -- 2️⃣ 🛡️ But Sentinel should not be viewed as one VPN application This distinction matters. Sentinel provides decentralized bandwidth infrastructure on which multiple independent dVPN applications can operate. Different applications. Different interfaces. Different communities. One underlying network. -- 3️⃣ 🌐 Think infrastructure, not application Traditional VPN services usually control most of the stack: servers applications subscriptions users infrastructure Sentinel separates these layers. Independent node operators provide bandwidth. Builders create applications. Users connect through the products they choose. The network becomes the shared foundation beneath them. -- 4️⃣ 📱 This is also how Web3 starts becoming invisible Most mainstream users do not want to understand: validators blockchains nodes wallet architecture network economics They simply want a VPN that works. Sentinel-powered applications can abstract the blockchain layer while still using decentralized infrastructure underneath. That abstraction is important for adoption. -- 5️⃣ 🚪 Web2-scale adoption may enter through a Web2-shaped door Sentinel is already supporting VPN partners and consumer-facing applications capable of onboarding users who may never realize they are interacting with decentralized infrastructure. And that may be exactly the point. The technology succeeds when users no longer need a blockchain manual before pressing “Connect”. -- 6️⃣ 📡 Six million sessions tell another story Transactions measure blockchain activity. But encrypted sessions measure something closer to actual network utility. Every session represents demand for: • bandwidth • connectivity • privacy infrastructure • access to the open internet For a DePIN network, physical resource consumption matters. Bandwidth is being used. -- 7️⃣ ⚙️ This creates an interesting infrastructure loop More applications can attract more users. More users create demand for bandwidth. More demand creates opportunities for node operators. A larger node network can improve geographic coverage and infrastructure diversity. And better infrastructure gives builders more room to create new products. That is how a network effect can begin forming around bandwidth itself. -- 8️⃣ 🔄 Now comes the Solana migration Sentinel is preparing to move into a new technical phase. But it is not migrating an empty protocol. The network is carrying forward: • millions of encrypted sessions • millions of transactions • multiple applications • independent infrastructure providers • existing user demand That distinction is worth watching closely. -- 9️⃣ 🚀 Migration should therefore be judged on continuity The important question will not simply be: “Did Sentinel move to Solana?” It will be: Can the next architecture preserve and expand the ecosystem already operating today? • Users. • Applications. • Node operators. • Bandwidth demand. Infrastructure becomes valuable when activity survives architectural change. -- 🔟 🧭 Sentinel started with decentralized VPN technology. The broader picture emerging today is decentralized bandwidth infrastructure capable of supporting many applications while remaining largely invisible to their users. August provided another useful signal: • 77,263 new users. • 6M+ encrypted sessions. • 9.6M+ transactions. The rails are already carrying traffic. The next chapter is about seeing how far those rails can scale. 🔁 RT to help more people understand why real usage matters for decentralized infrastructure. Privacy and open internet access need infrastructure, not promises. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Sentinel #dVPN #DePIN #validator

A Personal AI becomes far more useful when it stops feeling like a stranger every time you open the door. The real shift starts when AI remembers who you are, understands your preferences, and can coordinate other agents around that context. Here’s why that matters 👇 -- 1️⃣ 🧠 Intelligence needs context An AI can know almost everything about the world... while knowing almost nothing about YOU. • your preferences • your habits • your priorities • your relationships Personal AI adds that missing layer. -- 2️⃣ 🧩 More than another chatbot @asi1_official describes a Personal AI that can: • develop its own personality • learn from your preferences • remember context over time • connect with other AIs and agents • act on your behalf The important word here is continuity. -- 3️⃣ 🧭 Context becomes infrastructure Imagine asking: “Help me organize this trip.” Your Personal AI already knows what matters to you. Then it can connect with specialized agents from Agentverse to handle specific parts of the task. You provide the intent. Your AI provides the context. Agents provide the capabilities. -- 4️⃣ 🌐 A network around you This becomes even more interesting when Personal AIs can interact with: • your friends’ AIs • specialized AI Agents • services across Agentverse Instead of one giant AI trying to do everything... you get personalized intelligence coordinating specialists around you. -- 5️⃣ 🔐 Personal also means responsibility The more your AI learns about you, the more important one question becomes: Who controls the memory, identity and permissions? Personalization is powerful. But without user control, it can also become another form of dependency. Privacy and sovereignty need to grow alongside intelligence. -- 6️⃣ 🚀 The bigger picture The future of AI may not be one assistant for everyone. It could be millions of Personal AIs, each carrying human context and coordinating with millions of specialized agents. Less: “One brain knows everything.” More: “The right intelligence, working around the right person.” -- 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #ASIOne #FetchAI #validator @ASI_Alliance @ASI_LatAm ethereum:0xaea46a60368a7bd060eec7df8cba43b7ef41ad85

Lava’s latest updates may look like separate RPC announcements. They aren’t. Gateway migration. New production users. Multi-provider routing. A possible EVM rebuild. New tokenomics. They all point in the same direction. @lavanetxyz is simplifying the front end while decentralizing what happens underneath. 🧵👇 -- 1️⃣ 🚪 One door, many chains Lava has moved its endpoints to Lava Gateway. @ethereum . @solana . @base . @arbitrum . @0xPolygon . @NEARProtocol . And more. For builders, the idea becomes simple: one gateway to access multiple chains. But simplicity at the front does not mean one provider behind it. -- 2️⃣ 🌐 One endpoint ≠ one dependency This distinction matters. A single URL can still route requests across multiple independent infrastructure providers. Lava evaluates provider performance in real time and can redirect traffic when one degrades or fails. The front door becomes simpler. The infrastructure behind it becomes redundant. -- 3️⃣ 🛡️ Reliability is becoming the product Hypernative shows why this matters. Its security infrastructure monitors multiple networks for threats and anomalies in real time. If blockchain data arrives late, inconsistently, or not at all… a threat may be detected late too. For systems like this, RPC reliability is no longer a developer convenience. It becomes part of the security model. -- 4️⃣ 🏢 The same applies to RWAs Sabai is now running on Lava RPC. And tokenization infrastructure raises the stakes again. Issuance. Payments. Investor management. Compliance. Asset transfers. All of them depend on accurate and continuously available blockchain data. A stale RPC response in a hobby project is annoying. In financial infrastructure, it can become an operational problem. -- 5️⃣ ⚙️ Decentralization is disappearing behind the UX This may be one of the most important shifts. Lava is packaging decentralized infrastructure like a normal developer product: one Gateway, multiple chains, usage-based plans, automatic failover. Builders should not need to manually stitch together five RPC providers just to achieve redundancy. The complexity moves into the infrastructure layer. Exactly where it belongs. -- 6️⃣ 🌋 Then comes the bigger architecture question Lava Foundation is also debating whether Lava still needs its own appchain. Its current position favors rebuilding Lava as an EVM smart-contract protocol hosted by another network. Why? Because experience suggests Lava’s core value increasingly sits in: routing, metering, quality, and Provider coordination. Not in maintaining consensus itself. Important: this direction is still conditional and would require governance approval. -- 7️⃣ 💰 And that could reshape LAVA itself Under the proposed model: Customers pay for RPC. ↓ Revenue purchases LAVA from the market. ↓ LAVA compensates the Providers serving the traffic. ↓ A share goes to the Assistance Fund. Instead of token economics primarily funding consensus, usage could become directly connected to Provider compensation and LAVA demand. Again, this model is proposed, not approved. But the direction is becoming increasingly coherent. One Gateway. Many independent Providers. Real usage. Infrastructure that becomes almost invisible to the user. Because decentralization works best when users do not have to think about the machinery keeping the data flowing. 🌋 #LavaNetwork #RPC #Infrastructure #Web3‌‌ base:0x11e969e9b3f89cb16d686a03cd8508c9fc0361af

A genuinely great initiative for the Cosmos community. ⚛️ A big thank you to @TCC_ATOM, who have built much more than a simple showcase for their own validator services. The Cosmonauts’ Corner brings together validator information, direct delegation options, ecosystem tools, and a growing range of community resources designed to make Cosmos easier to explore and understand. Today, they added @IBSvalidator to their featured validators section. 💙 We truly appreciate the recognition, but also the visibility they are giving to validators contributing across the ecosystem, each in their own way, with different strengths, approaches, and areas of expertise. Cosmos grows through protocols and infrastructure... but also through independent initiatives that help the community discover the people working behind the scenes to keep the network alive, accessible, and decentralized. Glad to join the Corner alongside so many committed contributors across the Cosmos ecosystem. 🛰️⚛️ #Cosmos #ATOM #Validator cosmos:native

Open source gives you freedom. But when a vulnerability appears at 3 AM… who carries the pager? The recent Cosmos EVM exploit raises a bigger question than the ~$5.7M involved: How should security responsibility work in an open-source blockchain ecosystem? 👇 -- 1️⃣ 🧩 Freedom has a cost Cosmos is permissionless infrastructure. Anyone can take the code, modify it, deploy a blockchain and operate independently. That sovereignty is one of its greatest strengths. But sovereignty also means responsibility. If you own the house, you also need to check the electrical panel. -- 2️⃣ 🔍 The coordination problem During the response to the Cosmos EVM exploit, Cosmos Labs coordinated with around 40 chains. They also discovered 11 Cosmos EVM deployments that were not previously registered in their security communication channels. That illustrates the paradox perfectly: Open source lets anyone build. But maintainers may not even know who is running their software. :contentReference[oaicite:0]{index=0} -- 3️⃣ 🛡️ Security cannot stop at the maintainer Cosmos Labs made an important mistake here. The vulnerability had previously been reported through the bug bounty program, but its potential impact on production networks was underestimated. The post-mortem openly acknowledges this and proposes changes to vulnerability triage, disclosure and security coordination. :contentReference[oaicite:1]{index=1} But there is another side. Chains running critical financial infrastructure must also maintain their stack. Updates, advisories, dependencies and emergency procedures cannot become optional housekeeping. -- 4️⃣ 🧭 Sovereignty ≠ isolation A sovereign blockchain should control its infrastructure. That does not mean operating alone in the dark. The ecosystem needs stronger security coordination: • verified security contacts • coordinated vulnerability disclosure • faster risk classification • upgrade procedures • dependency monitoring • emergency response channels Decentralization does not remove coordination. It makes good coordination infrastructure essential. -- 5️⃣ 🏗️ Maybe there is a business model here Perhaps the future of blockchain open source looks something like this: The protocol remains open. The expertise around operating it becomes a professional service. Chains could pay Cosmos Labs, specialized infrastructure providers or security teams for: security monitoring, upgrade assistance, configuration reviews, incident response and SLAs. Not paying for access to the patch. Paying for someone to make sure you understand when the engine needs one. -- 6️⃣ 🔌 The same logic applies to interoperability This direction already exists elsewhere in the Cosmos stack. Cosmos Labs is increasingly developing enterprise infrastructure around interoperability, operations and institutional deployments. Open protocols can remain public goods while professional services around them create sustainable businesses. The value may increasingly sit in: open software + interoperability + security + support. -- 7️⃣ ⚛️ A more mature open-source economy This incident should not become an argument against open source. It should become an argument for making open source operationally stronger. Because “Don’t trust. Verify.” sounds great… until your infrastructure contains dozens of dependencies and somebody needs to tell you which one is burning. 🔥 The next step is not more centralization. It is better responsibility. -- 8️⃣ 🌐 Responsibility must be designed Open source distributes power. But responsibility cannot simply dissolve into the network. Maintainers must improve vulnerability assessment. Projects must keep their infrastructure updated. Operators must monitor what they run. And professional security services can connect those layers together. Not one guardian holding every key. A network where everyone knows which door they are responsible for. 🔁💙 RT and Like to support stronger open-source security across the Interchain. 💬 Let's discuss and move forward together toward a new decentralized world. #NDW #Cosmos #OpenSource #Security #validator

Nolus started by building its own financial rails inside #Cosmos. Now those rails are reaching one of crypto’s busiest cities. @NolusProtocol is LIVE on @solana. 🔅🟣 Solana has speed. It has liquidity. It has traders. What it did not have was Nolus-style asset-backed leverage. Now it does. 🦾 🧵👇 -- 1️⃣ Nolus just opened a much bigger door. 🔅🟣 @NolusProtocol is now LIVE on @solana. And this is bigger than adding another chain to a dropdown menu. It means bringing Nolus' asset-backed leverage model closer to one of crypto's most active ecosystems. Let's unpack why this matters 👇 -- 2️⃣ Solana already has the users, liquidity and trading culture. Nolus brings a different way to use leverage there: 🔅 Up to 5x on SOL 🔅 Fixed rates for the life of the position 🔅 No traditional margin calls 🔅 Liquidations designed to reduce positions rather than immediately wipe them out Less casino lever. More seatbelt. 🎢 -- 3️⃣ The interesting part is the direction. ↗ Until now, traders wanting margin exposure often had to choose between: → staying onchain with the available DeFi tools → or moving funds to a centralized exchange Nolus is trying to make that choice less necessary. Keep the experience onchain. Bring the financial tool to the liquidity instead. -- 4️⃣ And Solana may only be the first stop. 🌐 Nolus has been building its architecture around remote execution, allowing its core protocol to reach liquidity across connected ecosystems without rebuilding the entire product from scratch on every chain. @solana turns that idea into something users can actually touch. As a validator supporting @NolusProtocol, we're proud to see the protocol expanding beyond its Cosmos roots while keeping interoperability at the center of its journey. 🔅 Join us to discover more, discuss, and ask your questions, as we move together towards a New Decentralized World. #NDW #Nolus #Solana #DeFi #IBSvalidator

AI agents become much more interesting when we stop asking one AI to be good at everything. @Fetch_ai ’s approach points toward something closer to a digital city: specialists everywhere, with ASI:One acting as the dispatcher. Here’s why that matters 👇 -- 1️⃣ 🧩 One AI ≠ every job A great researcher is not automatically a great accountant, travel planner, nutrition assistant or video director. Yet most AI products still try to squeeze everything through one giant brain. Fetch.ai explores another model: find the right specialist for the job. -- 2️⃣ 🧭 ASI:One as the dispatcher A user expresses an intent in natural language. ASI:One can search Agentverse, identify agents whose capabilities match that intent, and route work to them. So instead of manually hunting for 5 different tools... the system can start assembling the right workers around the task. -- 3️⃣ 🧠 Context makes specialists smarter This is where the examples shared by @Fetch_ai become interesting. A Blog Creator Agent does not need your whole life story. It needs your documents, tone and context. A Meal Finder needs dietary preferences. A Finance Agent needs objectives and constraints. ASI:One’s memory layer is designed to retain preferences and context across interactions. Less: “Let me explain everything again.” More: “You already know how I work.” -- 4️⃣ 🛠️ Now chain the specialists This is where things get fun. Imagine asking: “Turn this research into a campaign.” 🔎 Research agent gathers information ✍️ Blog agent creates the article 🎬 Prompt agent prepares the video concept 📊 Another agent extracts key data 🖼️ Another prepares visual assets You gave one objective. Several specialists handled the workflow. That is much closer to an AI team than a chatbot. -- 5️⃣ 🌍 The same pattern works everywhere Travel: ✈️ flights 🏨 hotels 🍽️ restaurants 📅 scheduling Business: 📦 inventory 💬 support 💰 pricing 📈 analytics Personal productivity: 📰 research 📚 learning 🥗 meal planning 🗓️ organization Different agents can expose different capabilities while ASI:One becomes the common doorway. Fetch.ai is explicitly building around this idea of multiple agents collaborating around one request. -- 6️⃣ 💸 And eventually, agents can transact The architecture gets even more interesting once agents can do more than exchange information. Fetch.ai already documents agent payment flows where agents can request, commit, reject, verify and complete payments. That opens the door to agents paying for: APIs compute data services other agents The “AI team” can gradually become an economy. -- 7️⃣ 🚀 The bigger picture Agentverse is not interesting because it contains “lots of agents.” A toolbox with 2 million tools is still useless if you must search through every drawer yourself. The interesting part is discovery + context + orchestration + execution. Your job becomes: “I want this outcome.” The network figures out who should help. That is a very different vision of AI. Less super-app. More coordinated intelligence. 🌐🤖 🔁💙 RT and Like to support open, useful and decentralized AI 💬 Let's discuss and move forward together toward a new decentralized world. #FetchAI #ASIOne #validator @ASI_LatAm ethereum:0xaea46a60368a7bd060eec7df8cba43b7ef41ad85 @ASI_Alliance