We’re excited to announce the launch of the $ASYNC drop Campaign, giving participants a fair chance to win from a massive pool of 8,000,000 $ASYNC tokens and Veera Points simply by swapping on the Router via Veera App. Whether you’re an active trader or new to Router, this campaign combines skill, luck, and fun for everyone.

This campaign is hosted in collaboration with Veera, a leading questing and platform for blockchain projects.

Download and Swap now: Veera App

How to get started

Here’s a step-by-step guide of how you can get started:

1. Install the Veera App on your android device from the Play Store (not available on iOS App Store)
2. On the homepage, tap on “Rewards” in the top-left corner.

3. Select “Web3 Wallet” and create your wallet.

4. Head back to the Points tab and click on “Exclusive Partner Quests.”

5. You’ll find the “Swap to win $ASYNC” quest — tap on it and complete your swap.

You have the chance to earn 4000 Veera Points per day and the more swaps you do, the more tickets you earn from the campaign. At the end of the campaign, winners are selected via:

• Top 3 ticket holders get guaranteed rewards
• 10 random participants are selected via raffle

We recommend swapping using Ethereum, BNB, or Base, as these are the supported chains on Veera.

Key Dates

• Campaign Period: Starting 24th October — no fixed end date
• Airdrop Date: Within 7–14 days after the campaign ends

Rewards

• Total Pool: 8M $ASYNC tokens
• Winners: 13 in total
• Top 3 ticket holders: Share 25% of rewards
• 10 random winners: Share 75% of rewards

Rewards will be distributed to the Veera wallet address used for the swaps.

Bonus: Participants will also earn Veera Points for their engagement, adding an extra layer of rewards for active users.

Participation & Ticketing

Tickets are earned based on swap volume. Each eligible transaction counts for tickets as follows:

Rules:

• Minimum transaction amount = $1
• Unlimited entries for raffle tickets

This campaign is designed to reward both active users and newcomers. The combination of guaranteed rewards for top ticket holders, a raffle system for random participants, and Veera Points incentives ensures fairness, transparency, and excitement.

Don’t miss out, start swapping today and see if luck is on your side!

Download and Swap now: https://play.google.com/store/apps/details?id=com.veera.browser

Router App: https://app.routerprotocol.com

Veera App: https://play.google.com/store/apps/details?id=com.veera.browser

Asynchrous: https://asynchronus.ai

Context

With the launch of the Open Graph Architecture (OGA), Router’s long-term direction has shifted from maintaining an independent L1 chain to powering onchain liquidity and rebalancing infrastructure!

Router Chain powered multiple products and experiments that shaped where we are today. But as we’ve grown, the landscape has changed. Running our own L1 introduced heavy infra costs, validator inflation, and security risks. And while Router Chain helped us prove our ideas, the broader aggregation ecosystem remained fragmented and controlled by a few centralised players, reinforcing why we needed to pivot toward a more open, permissionless, and scalable model.

That’s why we built the Open Graph Architecture (OGA), the natural next chapter. OGA lowers integration effort, removes centralization risks, and makes liquidity routing open and programmable, positioning Router as the infra layer for both institutions and retail users.

Hence, maintaining a separate chain today diverts resources away from OGA, the framework that now anchors our roadmap.

After extensive community discussions and feedback, it is time to decide whether to formally sunset the Router Chain.

What This Proposal Is About

This DAO proposal seeks community approval to:

• Sunset the Router Chain.
• Migrate all remaining Router Chain tokens back to Ethereum.
• Transition token utility and ecosystem functions to align with the OGA framework.

Proposal Options

• Yes → Approve the sunset of Router Chain as outlined below.
• No → Reject the sunset proposal; Router Chain continues to operate.
• Abstain → No opinion recorded.

What Happens If “Yes” Passes

Immediate Actions (within 1 week of proposal passing)

• Router Chain inflation will be set to 0 to stop further minting of tokens for validator rewards.
• The undelegation period will be reduced to 1 day.
• All foundation-delegated tokens will be redelegated to foundation validators to maintain stability during the transition.

Migration Period:

• Users will be able to migrate their ROUTE tokens from Router Chain to Ethereum using the Nitro app.
• Only migration to Ethereum will be supported (not Polygon).
• Manual migration window: until October 15, 2025.

TENTATIVE Timeline:

• September 30, 2025: All users are advised to undelegate their tokens from the validators by this time.
• October 15, 2025: Bridging to and from Router Chain is paused. CEXs pause deposits/withdrawals on Router Chain.
• October 16, 2025: Snapshot of all Router Chain token balances is taken and shared with the community. Community has 3 days to review.
• October 20, 2025: Airdrop of migrated tokens on Ethereum to the equivalent Ethereum addresses of Router Chain holders. Metamask/Keplr users will see their updated balances automatically.
• October 31, 2025: CEXs fully migrate ROUTE deposits/withdrawals to Ethereum. Router Chain is formally closed.

Token Supply Transparency

As of 19th September 2025, Total Current Supply: 979,943,795 ROUTE

• Ethereum → 136,069,650
• Polygon → 52,986,002
• Router Chain → 790,888,143

When Router Chain launched, the community approved a comprehensive ROUTE 2.0 tokenomics upgrade. This included a token split (1 v1 ROUTE → 33.33 v2 ROUTE), a new total supply of 1B, and fresh allocations across the Foundation, Ecosystem, and Team. The design was meant to ensure sustainability, incentivize builders, and foster long-term ecosystem growth.

As part of that upgrade, 333M tokens were specifically minted for Router’s next growth chapter. These tokens were not random inflation, they were carefully allocated to bootstrap the chain’s lifecycle:

• Foundation, to support growth, fundraising, and listings,
• Ecosystem Building, to drive adoption, liquidity, and integrations,
• and the Team, to align long-term incentives.

With the proposed sunset of Router Chain, these allocations remain highly relevant. They will continue to fuel Router’s next phase under OGA, supporting liquidity operations, incentivizing partners, and ensuring the team and community stay aligned for the long haul.

Here’s the breakdown of the 333M tokens and how they’ve been used (or will be used) going forward:

Breakdown of 333M tokens minted for Router Chain:

The total supply of 333M tokens was allocated across three key buckets:

• Foundation — 30% (100M)
• Ecosystem Building — 60% (200M)
• Team — 10% (33M)

Let’s dive into each category and the current/future plans.

1. Foundation — 30% (100M)

• Already utilized: ~40M tokens were used during the strategic raise. Proceeds went towards team growth and marketing efforts, especially around the chain mainnet launch.
• Remaining: ~60M tokens.

Planned usage:

• Future fundraising with strategic partners to support long-term building.
• Potential use for future listings (not immediate, but as traction grows and more distribution is required).

We’ve been building for over 4.5 years, pivoting from a PoA-based bridge → a chain → the OGA framework. To sustain this journey, the remaining foundation tokens will be crucial for growth and long-term partnerships.

2. Ecosystem Building — 60% (200M)

Currently, these tokens remain unused and locked (vesting pushed by 6 months). They are essential for community and ecosystem growth, especially as OGA continues expanding.

Breakdown:

MM Operations on CEX/DEX — 67M

• For liquidity provisioning and supporting MM operations on exchanges where $ROUTE is listed.
• Also used for Uni v3 pools on Ethereum to ensure smooth trading.
• In future: to be extended to HL listings and liquidity.

Ecosystem / Community Building — 133M

Governance safeguard: Any campaign/grant requiring >5M ROUTE will go to community vote before execution.

Planned usage:

• Community traction: Campaigns on Router App to drive users, transactions, and volume. Includes direct campaigns + partner-led campaigns (where Router is integrated).
• Ecosystem integrations: Incentivizing B2B partners, devs, and projects integrating Router APIs/widgets for cross-chain solutions.
• Incentives may be milestone-based (transactions/volumes).
• Long-term revenue-sharing models where applicable.

These tokens are critical for growth, enabling Router to continue building strong community engagement and an active ecosystem around OGA.

3. Team — 10% (33M)

• Dedicated to team incentives and to keep builders motivated with long-term ownership.
• Vesting was pushed by 6 months earlier in July 2025, and now, as part of this proposal, we are pushing the vesting period by 6 more months. This means that the team tokens will start unlocking only in July 2026.

Voting Mechanics

• Snapshot Date & Time: September 19, 2025, 11:00 AM UTC
• Eligibility: 1 ROUTE = 1 vote (across Ethereum, Polygon, and Router Chain). ROUTE staked on Router Chain also counts 1:1.
• Weighted Voting: You can split your vote across options if desired.
• Voting Period: September 19, 2025, 2 PM UTC — September 24, 2025, 2 PM UTC
• Quorum: Option with the highest % of votes wins.

Where This Will Be Announced

The proposal and results will be communicated across all official Router Protocol channels:

• X (Twitter)
• Telegram (Chat + Announcement)
• Discord
• CoinMarketCap Community
• LinkedIn

Cast Your Vote here

Closing Note

This proposal is not about ending something, it’s about evolving. Router Chain gave us the foundation. OGA gives us the future.

By consolidating resources, removing unnecessary overhead, and aligning everything with OGA, we can position Router to scale as the most powerful onchain infrastructure layer.

Let’s make this transition together, in a way that is fair, transparent, and community-driven.

For migration support or proposal-related queries, please reach out to us on Discord or Telegram.

Cast Your Vote HERE

As you may know, Router Protocol recently experienced a security incident that affected a subset of assets on the Oasis Sapphire Chain. You can read the full incident report here.

As part of our recovery plan, we’re initiating a token migration process for users who hold USDC, USDT, or wETH on Oasis Sapphire Chain. If you hold any of these assets on Oasis Sapphire, please read the instructions below carefully and complete the process within the next 4 weeks.

What You Need to Do

To ensure a smooth and secure migration, follow these steps:

1. Burn your affected tokens
   Send your USDC, USDT, and wETH on Oasis Chain to the burn address below:
   0xB1b64005B11350a94c4D069eff4215592d98F2E2
2. Receive your tokens back on Ethereum
   Within 72 hours of the burn, the equivalent amount will be airdropped to your same wallet address on the Ethereum chain.

Important Notes

-Only the following assets are eligible for migration:

• USDC: 0x97eec1c29f745dC7c267F90292AA663d997a601D (6 decimals)
• USDT: 0x8C4aCd74Ff4385f3B7911432FA6787Aa14406f8B (6 decimals)
• wETH: 0xB6dc6C8b71e88642cEAD3be1025565A9eE74d1C6 (18 decimals)

-Do not send any other assets. Tokens outside of these three are not affected and will not be refunded.

-This migration process will be open for 4 weeks, so please ensure you complete the migration on time.

Need Help?

If you have any questions or face any issues during the process, please reach out to us for support on our official Discord: https://discord.gg/yjM2fUUHvN

We appreciate your cooperation and continued support as we work to completed this process responsibly and transparently.

Proposal Live: July 23, 2025 — July 27, 2025

Context:

As part of Router Chain’s mainnet launch, the community approved a major tokenomics upgrade via DAO vote concluded on February 11, 2024. This included a token migration from the original $ROUTE (v1) token to the new native $ROUTE token powering Router Chain.

Since then:

• We have actively promoted migration via a step-by-step guide released on July 23, 2024.
• The migration period was intended to last 6 months but has already been extended multiple times till date based on community needs and ongoing support.
• Now, after 12 months and repeated outreach, the community has voiced a need to bring closure to the process. To streamline all feedback and ensure everyone had a chance to weigh in, we also opened a dedicated community discussion thread on our official Discord server on July 21, 2025.

What This Proposal Is About:

As we reach the end of this extended support period, feedback from the community has been clear: it’s time to finalize the migration process.

This DAO proposal is a final call:

Proposal Options

Option 1: End Migration on August 25, 2025

• Migration ends on August 25, 2025
• All unmigrated ROUTE v1 tokens will be considered burned and equivalent new ROUTE tokens (i.e 1 ROUTE v1 = 33.33 new ROUTE) will be burnt and permanently removed from circulation

Option 2: Extend Migration by 6 Months

• Extend the migration deadline to February 25, 2026
• All users can still migrate 100% of their tokens during this period

Option 3: Partial Claim

• Extend the migration by 6 months until February 25, 2026
• Users can still migrate, but will receive only 50% of the token if migration occurs after August 25, 2025. The remaining 50% non-redeemable ROUTE v1 tokens will be considered burned and equivalent new ROUTE tokens (1 ROUTE v1 = 33.33 new ROUTE) will be burnt and permanently removed from circulation

Voting Mechanics:

• Snapshot has been taken on 23rd July.
• 1 new $ROUTE held on Ethereum or Polygon or Router Chain = 1 Vote
• ROUTE tokens staked on Router Chain are also eligible for 1:1 voting power
• Weighted voting: You can split your vote across both options if desired
• Voting Period: July 23 — July 27, 2025
• Quorum: Option with the highest % of votes wins

What Happens If Option 1 Passes?

If Option 1 is selected, all unclaimed ROUTE v1 tokens after August 25, 2025, will be considered as burnt — these tokens will be permanently excluded from circulation and will no longer be eligible for migration.

Where This Will Be Announced

This proposal and its outcome will be shared across all official Router Protocol channels:

• X (Twitter)
• Telegram (Chat + Announcement)
• Discord
• WhatsApp Community
• CoinMarketCap Community
• LinkedIn

Cast Your Vote here: https://vote.routerprotocol.com/#/proposal/0xa687fd5c1eac7669dc7dfd7dd260be44f1ef26665aa4daeeeff5118b83970460

For any doubts regarding the proposal or assistance with the migration process, please reach out to us on Discord or Telegram.

On July 2, 2025, between 07:37–07:46 UTC, Router Protocol experienced a targeted exploit on its asset bridge module, resulting in the unauthorized transfer of multiple tokens amounting to over $1.1 million USD. The attacker exploited a vulnerability in our cross-chain request logic specific to Router Chain’s custom IBC implementation.

Root Cause:
The vulnerability stemmed from a missing validation check in outbound requests. Specifically, the system failed to ensure that RequestSender == TxSender, allowing an attacker to spoof the sender and craft malicious outbound token requests.

Exploit Flow:

• A forged cross-chain request was submitted to Router Chain.
• Orchestrators unknowingly signed this request.
• The Ethereum Gateway contract, trusting the RequestSender, processed the malicious request and released funds to the hacker.

This exploit was unique to Router’s custom implementation and not found in standard Cosmos SDK chains. Importantly, the affected codebase had been audited by multiple top-tier firms, including Oak Security and Informal Systems, and had been live for over two years.

You can access our previous audit reports here:
🔎 Audit Reports — Oak Security & Informal Systems

2. What We Did

Upon identifying the attack, our team took immediate steps to contain the damage, investigate the root cause, and coordinate response efforts with security experts, exchanges, and law enforcement.

Immediate Actions:

• Paused impacted asset bridge flows while unaffected services, such as Router Nitro, continued to function independently.
• Engaged security firms and audit partners to conduct detailed post-mortems.
• Published a full technical report in the Telegram community, outlining the vulnerability, timeline, and key transactions involved:
  → Full Internal Incident Report
• Read the official Oak Security post-incident analysis:
  → Oak Team Incident Report (July 7, 2025)

Key Findings:

• The bug resided in a custom cross-chain module in Router Chain, unrelated to Nitro or standard Cosmos chains.
• Audit firms had flagged the general issue class, but the exact exploit vector was missed during earlier reviews and incorrectly marked resolved.

Chain Status:

To mitigate any risk and conduct a thorough analysis, we have temporarily paused bridging operations on the following chains:

Arthera, DogeChain, JFIN, Matchain, Oasis, Nero, Redbelly, Saakuru, Tangle, and Vanar.

All other supported chains on Router Nitro remain fully operational.

3. What We’re Doing Next

This incident has reinforced our belief in rigorous, multi-layered security and the need for constant vigilance, even in long-standing audited systems.

Patches and Protocol Changes:

• Validation Fix Implemented: We added a strict msg.sender == RequestSender check in outbound logic.
• Reviewed and approved by three Oak Security auditors.
• Enhanced off-chain tooling for orchestrators to detect and flag forged requests.

Broader Ecosystem Coordination:

Due to the foundational nature of the vulnerability, our disclosure was initially delayed on advice from audit partners to allow time for similar patterns to be evaluated across other Cosmos-based ecosystems.

We’ve since:

• Notified similar Cosmos chains to audit and fix potential vulnerabilities.
• Fully briefed our investors and partners, maintaining transparency throughout.

While we work on a long-term fix, we are temporarily collaborating with another bridge provider to support bridging capabilities for a few impacted chains for provision of immediate alternative routes. We’re also in active discussions with the affected chain teams to explore this routing option and ensure users have continued access wherever possible.

Final Thoughts

This exploit serves as a hard reminder: security is never one-and-done. Even well-audited systems can have edge cases that go undetected. While the vulnerability affected a specific Router Chain module, we’re taking ecosystem-wide lessons from it.

We remain committed to full transparency, strengthening our infrastructure, and earning the trust of our community.

We’ll continue to share updates as the investigation and recovery efforts progress.

Thank you for your continued support.

— The Router Protocol Team

Update: Fund Recovery Progress — July 14, 2025

Over the weekend, we made substantial progress in tracking and securing the exploited funds. Our efforts have led to approximately 12.5% (~$150K) being successfully frozen across multiple sources.

We are actively working with centralized exchanges to ensure any incoming funds are promptly frozen and are coordinating with law enforcement authorities to initiate legal action against the attacker.

The world of blockchain is growing increasingly modular, multi-chain, and data-hungry. In this rapidly evolving ecosystem, protocols can no longer operate in silos. Whether you’re building DeFi, deploying AI-powered strategies, or bringing Real-World Assets (RWAs) on-chain, one thing is clear:

Your application is only as powerful as the data it can access — across chains, in real time, and without compromise.

That’s why we’re thrilled to share our progress on a collaboration that’s been months in the making: Router Protocol x Band Protocol, a partnership that delivers free, secure, and cross-chain accessible price feeds to every developer building on Router-connected chains.

While the Band team recently published a deep dive on our successful end-to-end oracle relay from Band Oracle v3 → Router Chain → Ethereum Holesky, we wanted to offer a perspective from the Router side of the tunnel.

Let’s dive in.

Why This Matters: Data is the New Liquidity

At Router, we’ve always viewed interoperability as more than just moving assets — it’s about moving knowledge. Price feeds, identity states, governance decisions, intents — these are the new atomic units of DeFi and beyond.

Without reliable, real-time data transfer across chains, the vision of seamless DeFi, intelligent agents (DeFAI), and tokenized asset markets breaks down. With Band Oracle v3 + Router Protocol, we’re making trustless, open, real-time oracle data a baseline offering — not a luxury.

What We’ve Built: The Cross-chain Oracle Tunnel

Together with Band Protocol, we’ve completed a full-stack testnet relay from BandChain to Holesky (Ethereum testnet), using the Router bridge infrastructure.

Highlights from the Integration:

• Data Source: Band Oracle v3 testnet
• Bridge Infrastructure: Router Protocol
• Destination: Ethereum Holesky Testnet
• Delivery Mechanism: IBC Hooks → Router Chain → iReceive-compatible consumer contract
• Example Transaction: https://holesky.etherscan.io/tx/0xa4b70b2d9d8d0a69a0d816b3f2de46ac134f19c88ce61d750ced6b37fa4fac36/advanced#eventlog

The delivered data includes mock price feeds for BTC and ETH, showcasing how any smart contract can access the Band Standard Dataset via Router’s generalized iReceive interface.

This lays the foundation for custom oracle logic, real-time financial triggers, and AI automation — all deployed trustlessly across chains.

Router Protocol’s Role: Data Infrastructure for the Multi-chain World

While Band provides the data, Router ensures that data can move securely and instantly across blockchains. Here’s how:

1. Cross-chain Abstraction Layer

Router provides a unified interface for contracts to receive and verify messages across heterogeneous blockchains (EVM & non-EVM). Whether it’s Solana, BSC, Ethereum, or Cosmos-based networks — if you can write a smart contract, you can now subscribe to oracle feeds via Router Protocol.

2. Developer Simplicity

With our iReceive interface, developers don’t need to worry about packet formatting, relayers, or finality across chains. You simply write a function to receive price data — and Router handles the rest.

3. Composable Data Infrastructure

Price feeds are just the beginning. Router is positioning itself as the execution and data movement layer of the modular crypto stack. Want to build AI agents that arbitrage across chains? Use Band Oracle + Router automation. Building RWAs that require off-chain price attestation on multiple chains? Router tunnels are the proof.

What’s Next: From Testnet to Mainnet and Beyond

As we move toward a planned mainnet release by the end of Q3, here’s what’s coming:

1. Co-branded Oracle Feeds

Band x Router will launch an open data oracle that any dApp can use — no signup, no fees. Just plug in and build.

2. Developer-ready Infrastructure

Documentation, SDKs, and boilerplate contracts will be released to empower devs to integrate Band Price Feed via Router with just a few lines of code.

3. Ecosystem Partnerships

We’re already exploring integrations with leading DeFi, RWA, and DeFAI projects to showcase real-world use cases. Want to be part of the launch cohort? Get in touch.

Why This Collaboration Sets a New Standard

The synergy between Band Protocol and Router Protocol reflects a larger shift in the crypto ecosystem:

• From bridges to execution layers
• From fragmented dApps to networked agents
• From expensive oracles to free, open, public data utilities

And this is just the beginning. Router is evolving into the intelligence layer of crypto — Band feeds give it vision. Together, we’re not just relaying data. We’re laying the foundation for a modular, multi-chain, data-rich internet of value.

Ready to Build? You can already start exploring the testnet integration. Here’s the guide to get started. Follow us and Band Protocol on X for more updates as we prepare to launch the Ultimate Data Bridge for DeFi, DeFAI, and RWAs.

A few weeks ago, we broke down how Router Pay simplifies CEX withdrawals — eliminating manual bridging and token swaps. Now, we’re taking it to the next level: introducing the CEX Withdrawals Page on Router Nitro!

Get Started: https://routernitro.com/withdrawals

The Problem: Fragmented Withdrawals

As we highlighted in our previous article, Router Pay is designed to simplify crypto transactions, and CEX withdrawals are no exception. Traditionally, users trying to move funds from centralized exchanges (CEXes) to DeFi platforms have faced numerous challenges. Since most CEXes support only a limited number of withdrawal networks, users had to:

1. Withdraw funds to an established blockchain (such as Ethereum, BNB Chain, or Polygon), which is supported by their CEX.
2. Use a bridging service to move funds from that chain to their desired destination chain.

This two-step process not only introduced extra costs in the form of withdrawal and bridge fees but also created unnecessary friction for users who wanted to access assets on newer chains quickly. Moreover, some assets may not be withdrawable on the same chain, further complicating the process and requiring additional swaps.

The Solution: One-step Withdrawals via Router Nitro

With the launch of our CEX withdrawal page, this problem is now a thing of the past. Users can now withdraw funds in a single step by specifying the exchange from which to withdraw the funds and the final chain where they want to receive their funds. Nitro will automatically handle the intermediary steps, routing the withdrawal efficiently to the destination chain of user’s choice.

For instance, instead of withdrawing USDC from Binance to an intermediate chain like Arbitrum or Polygon before bridging to a newer chain, users can now withdraw directly to the desired chain without extra steps or fees. Router Pay’s instruction-specific address (ISA) system ensures that funds are automatically processed and routed to the correct chain, eliminating the need for manual bridging or token swaps.

Why This Matters

Better UX

No more manual bridging or multiple transactions — just select your destination chain and receive funds directly.

Cost Efficiency

By eliminating the need for intermediate transactions, users save on fees and avoid potential slippage.

Expanded Chain Support

Nitro’s extensive support for over 50 chains ensures users can withdraw to networks that were previously inaccessible via CEXes.

How to Withdraw Funds Using the Router Nitro CEX Withdrawal Page

Our newly launched withdrawal page features an intuitive UI that guides users through the process seamlessly. Follow these steps to withdraw funds from a CEX directly to your desired chain:

Step 1: Select Your CEX

• Begin by selecting your centralized exchange from the available options, such as Binance, Bybit, OKX, and others.

Step 2: Choose the Token and Amount

• Select the token you wish to withdraw (e.g., USDC, ETH, or USDT).
• Enter the amount you want to withdraw.

Step 3: Select the Destination Chain

• Choose the chain where you want to receive your funds. With support for 50+ chains, Nitro ensures you can withdraw to even the latest networks that are typically unsupported by CEXes.

Step 4: Provide the Recipient and Refund Addresses

• Recipient Address: Specify the wallet address where you want to receive the funds.
• Refund Address: In case the transaction is reverted, this is the fallback address where the funds will be returned.

Step 5: Confirm and Execute the Withdrawal

• Review your selections carefully and send the funds to the deposit address shared with you or Scan the QR code.
• Once confirmed, Router Nitro will handle the rest, ensuring seamless and cost-efficient routing of your funds.

Ready to experience effortless CEX withdrawals? Head to the CEX Withdrawals Page on Router Nitro and start withdrawing the easy way!

As February comes to a close, Router Protocol has continued to make significant strides in expanding our ecosystem. This month, we’ve introduced new swap functionalities, integrated more chains, brought to light innovative use-cases for Router Pay, and observed notable growth in user engagement on Nitro. Let’s delve into the highlights!

Product Highlights

Solana swaps

By enabling cross-chain swaps to and from the Solana network, and enhancing our liquidity on Solana, Nitro made it possible for its users to trade memecoins on Solana from over 40 EVM and non-EVM chains.

Tron Swaps via OKX Integration

Through our collaboration with OKX, we enabled cross-chain swaps involving the Tron network, providing users with more flexibility and options for their transactions.

Router Pay: Expanding Use-Cases

Building upon its January launch, this month we highlighted how Router Pay can be used for various purposes including merchant payments and CEX withdrawals.

Router Nitro Plugin on Eliza AI

Router Nitro was made available as a plugin on Eliza AI, allowing users to execute cross-chain swaps and actions directly via their AI agents.

Partnerships, Ecosystem Growth & New Chain Integrations

1. New Chains Integrated into Router Nitro

February saw the addition of 6 new mainnet chains and 1 testnet chain to Router Nitro, expanding the platform’s network of networks (see what we did there ;)).

• Mainnet Integrations: Unichain, World Chain, Story, Morph, Zero Network, HyperEVM
• Testnet Integrations: Monad

2. SPACE ID Web3 Domain Service Integration Nitro

• We’ve integrated SPACE ID into Router Nitro, allowing users to receive funds across chains using SPACE ID .bnb and .arb domains.
• This integration was undertaken to enhance Nitro’s cross-chain UX by removing the effort for users to copy-paste their recipient addresses.

Router Nitro Analytics

• Monthly Volume: $33.1 million
• Total Transactions: 41,600 transactions
• Unique Users: Over 35,000 unique users

Following our strong start of the year in January, February marked another important month for Router Protocol. With the introduction of the highly anticipated Solana and Tron swaps, Router Nitro’s Eliza plugin for easier integration into AI agents, and expanded chain support, we not only fulfilled our commitments but went beyond. March promises even more advancements! Stay tuned — exciting updates are on the way!

Website | Router Nitro | Twitter | Telegram | Discord

In our previous article, we explored how Router Pay can revolutionize crypto payments by enabling merchants to accept payments seamlessly across chains. But Router Pay isn’t just about payments — it’s about simplifying complex crypto transactions for users everywhere.

In this edition of Router Pay in Action, we’re tackling another major challenge: moving funds from Centralized Exchanges (CEX) to Decentralized Finance (DeFi) without the usual friction of bridging and swapping. Our Scan to Pay feature makes this transition effortless, allowing users to withdraw from CEXs directly to the chain of their choice — without extra steps, extra fees, or extra headaches.

The Problem Statement

Despite the rise of decentralized finance, a large percentage of users still trade crypto on centralized exchanges (CEX) for various reasons, such as ease of use, liquidity, or specific asset availability. However, traders are constantly moving funds from CEX to DEX for several reasons:

• To trade tokens that are not listed on CEXs (as listings on CEXs take more time compared to the near-instant token availability on DEXs)
• To use other protocols beyond trading, such as staking, providing liquidity, or lending and borrowing protocols.

The problem arises when users try to withdraw their assets from CEXs. Asset withdrawals are often limited to specific chains depending on the exchange. Moreover, not all assets are available for withdrawal on the same chain, and many users want to withdraw their assets to new chains that the CEX may not yet support.

For example, users may face difficulties when withdrawing assets to newer or unsupported chains. To resolve this, they typically need to perform additional steps like bridging or swapping — sometimes both — to continue their actions on-chain.

Current CEXs Withdrawal Flow

Consider the case where a user wants to transfer USDC from a CEX (such as MEXC, Binance, or KuCoin) to use a new chain, say Abstract chain. MEXC, KuCoin, or Binance may support USDC withdrawals but not directly to Abstract; therefore, users need to:

1. Withdraw USDC from their CEX account on a popular chain like Arbitrum, BNB Chain, Polygon, among others. In this step, the user will incur withdrawal fees.
2. Bridge USDC to the Abstract chain and incur the bridging fees.

This process involves multiple manual steps and is often time-consuming and costly, which can deter users from participating in DEX activities.

Router Pay’s Solution

Router Pay offers a streamlined solution to this problem. For the scenario mentioned above, the user can easily transfer assets from CEX to DEX without the need for manual bridging or token swaps. Here’s how it works:

1. Generate a Router Pay instruction-specific address (ISA) on Router Nitro with the following details:

• Source Token: USDC
• Source Chain: Arbitrum/Polygon (or any other chain supported for withdrawal by the CEX)
• Destination Chain: Abstract
• Recipient Address: User’s wallet address

2. Withdraw to the ISA on the selected source chain.

Once the user withdraws to the ISA address on the selected source chain, the transaction is completed and bridged automatically by Router Pay. The user no longer needs to manually swap or bridge assets themselves, which simplifies the process and reduces cost & friction when moving between chains.

What’s next? Soon, we’ll have a dedicated CEX withdrawals page on Nitro that will make it even more intuitive to withdraw funds from CEX. Stay tuned for more updates!

Website | Twitter | Telegram | Discord

Crypto payments are evolving, and Router Pay is at the forefront of this transformation. Designed to combine the ease of Web 2.0 with the security and trustlessness of Web 3.0, Router Pay enables merchants to seamlessly accept cryptocurrency payments — whether in Bitcoin, Ethereum, stablecoins, or other digital assets.

Why Router Pay by Router Protocol is a Game-changer for Merchants

The world of commerce is rapidly shifting, and more customers want to pay with crypto. However, most traditional crypto payment solutions come with high fees, slow transactions, and security risks that make them impractical for small businesses.

Challenges of Traditional Crypto Payment Solutions

• High Fees — Many crypto payment providers charge high transaction fees, making them unsustainable for small merchants.
• Limited Support — Existing crypto payment solutions restrict the end users to pay only using a few tokens.
• Slow Transaction Speeds — Long confirmation times result in delayed payments, frustrating both merchants and customers.

How Router Pay Solves these Problems

• Lower Transaction Costs — Router Pay ensures merchants save on fees, making crypto payments more cost-effective.
• Flexible-payment Options — With Router Pay + Nitro, merchants can allow their customers to pay their way, while still receiving payments in the token of their choice on the blockchain of their choice.
• Near-instant Settlements — In conjunction with Router Nitro, Router pay ensures that all customer payments are settled on the merchant’s preferred blockchain in a few minutes.

Seamless Integration for Businesses

Whether you’re a merchant selling products online, offering services, or running a subscription model, integrating Router Pay is effortless:

• Robust APIs — Developers can customize payment flows to fit their business needs.
• Custom Solutions — Router Pay has partnered with a payment gateway platform to provide tailored crypto payment experiences for enterprises. Stay tuned for more updates on this front.

Merchants shouldn’t have to choose between simplicity and security when accepting crypto payments. Router Pay delivers both — giving businesses the ability to tap into the growing crypto economy without the usual headaches. Start accepting crypto payments today and transform how you do business.

Learn more & integrate Router Pay: https://docs.routerprotocol.com/router-pay/integrate-router-pay/