Here’s a structured overview of our progress:

Router Intents -

Detailed whitepaper on Cross-chain Intents Adapter framework in progress

Liquid Staking Integration and Testing:

• Ongoing integration of liquid staking on the same blockchain.

• Proof of Concept (PoC) testing is currently in an advanced stage.

Backend Integrations:

• Stader (Near), Metapool (Near), and Linear Protocol (Near) integrations have been successfully implemented.

• Stakewise (Ethereum) integration is also complete.

Lending and Borrowing:

• The Aave Proof of Concept for supply-only operations has been finalised.

• Completion of the Compound adapter for Ethereum, Arbitrum, Polygon, and Base and the Radiant adapter for BNB and Arbitrum.

Decentralised Exchange Liquidity Pools (Dex LP):

• Uni V3 Integration on PoC, including activating and testing two pools. Documentation related to this integration is now complete.

• TraderJoe adapter and backend integration are currently underway.

Cross-Chain Transaction Batching: Development of a system for batching cross-chain transactions to enable multiple adapters to function on the destination chain.

Chain Updates

• Implemented changes for SDK-Go Config Pagination.

• Orchestrator Keyring: Debugged to operate without passphrase prompts.

• Cosmos Chains Deposit Events Testing: Manually tested and verified on Router Chain Middleware contract.

• Refuel Mechanisms Analysis (getting a small amount of destination native token while doing your cross-chain swap/ transfer): Completed.

Audit

• Audit Report Fixes: Completed for the forwarder.

• Oak Router Integration Audit: Report completed.

Nitro dApp Updates

• EVM Upgradeable Contracts: Upgraded and ownership migration completed.

• Multi-Sig Wallet Operation POC: For Cosmwasm contracts key-management.

• Improvements in UI/UX on Router Nitro implemented.

• Nitro Explorer API: Included Cosmos Chain flow and Cosmos Chain fund deposit feature.

• Web2 APIs Stability Improvements: Enhanced request/response validation, timeouts, and logging.

• Nitro Forwarder: Integrated with Cosmos Chain.

• Access Control in Asset Forwarder and Bridge: Optimized and implemented.

• Gas Tank Support: Added in Middleware contracts.

• Nitro Contracts Improvements: Minor bug fixes and enhancements.

• Nitro Forwarder Logging: Successfully implemented.

Tools

Chain Explorer:

Added fund deposit information

Nitro Explorer:

• Near custom middleware API integration (testing pending).

• Fund-paid integration development completed.

• Addressed open issues set for testnet deployment.

Path-finder:

• The mainnet configuration was completed and tested for liquidity fetching and stability.

• Updated biasing logic for token compatibility.

• Removed v1 Pathfinder 1inch support.

Upcoming Focus

• IBC Connection and Code Polishing: Address packet failures in IBC connections and refine chain, forwarder, and contract codes.

• Multicaller for Forwarder: To enable batch transactions from the forwarder.

• Automation Test Suite for Nitro: Implementation in progress.

• Voyager Implementation for Cosmos Chains: Focusing on Cosmwasm Contracts.

• Nitro UI Stabilization and Explorer Fund Integration: Prioritized for implementation.

• Pathfinder API Update: Inclusion in Nitro SDK.

• Smart Wallet Development: For stateful contract interactions.

• Tron (Nile) Dexspan Integration: Finalization in process.

We invite you to stay connected with us for further updates and join our thriving community across our various social platforms. Keep an eye out for more exciting developments in the coming weeks!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

We also saw that the emergence of multiple smart contract chains across both Layer 1 and Layer 2 infrastructures brought forth a new challenge: seamless movement across these diverse platforms. This is where cross-chain comes into play, the possibility of a seamless multi-chain world!

Besides, as we continue to grow and adapt, a new term has emerged, capturing the essence of this landscape: ‘Intents’. We’ll delve into how cross-chain bridges facilitate value transfer and integrate these ‘Intents’ to streamline and enhance the interaction between diverse blockchain networks. Join us and see how ‘Intents’ fits into our broader picture, shaping the trajectory of Web3’s evolution and enriching the user experience.

So, what are Intents? Are they beyond a technical advancement?

Intents are something as simple as the Intent of users or goals users wish to accomplish within the blockchain ecosystem. Let’s consider a practical example. Imagine you have Ethereum (ETH) on the Ethereum blockchain, but you want to participate in a new DeFi protocol that operates on the Binance Smart Chain (BSC), which requires Binance Coin (BNB).

We can’t deny that users need to have a detailed understanding of the protocols and procedures to survive and thrive! Similarly, developers face considerable difficulties in creating applications that interact with multiple blockchains, primarily due to the intricate and often tangled nature of these cross-chain interactions, which is why we have an intent framework.

In the case of an intent framework, you go to a cross-chain platform and express your intent to swap ETH on Ethereum for BNB on Binance Smart Chain. The platform automatically finds the best path for this swap, considering factors like transaction fees, exchange rates, and network congestion. It might involve swapping ETH for a wrapped version of BNB on Ethereum and then bridging it to BSC, all in a single, streamlined transaction.

A single transaction can have multiple “intents” to achieve various goals simultaneously.

For example, you could exchange one token for another and invest it in a different dApp, all in a single step. This approach makes transactions faster and more cost-effective because it combines several actions into one, reducing the time and fees usually needed for multiple separate transactions.

The bottom line is that the ‘Intent Framework’ simplifies the process by allowing you to state your end goal (obtaining BNB on BSC) without worrying about the intermediary steps. The cross-chain platform takes care of the complexities, providing a more user-friendly and efficient experience.

Besides, ‘Intents’ is a shift beyond a technical leap; it transforms the blockchain into a user-centric environment where individuals can confidently express their requirements, trusting the system to find the most effective path to achieving them.

Intents and Interoperability

Intents serve as a bridge in the context of Interoperability, offering a flexible and strong framework that enables diverse blockchain protocols to understand and execute transactions in a harmonious manner.

By defining the purpose or goal of a transaction in a universally comprehensible format, intents bypass the barriers posed by varying protocols and standards. This universal language of intents streamlines cross-chain interactions and opens up new avenues for complex dApps that can operate across multiple blockchain ecosystems simultaneously.

Furthermore, the introduction of intents in interoperability scenarios brings a new layer of sophistication to blockchain applications as blockchains are not confined within the silos of individual networks but are part of a larger, integrated digital tapestry.

We’ll elaborate on this in our next section.

Intents, Steps, Paths, and Router

As mentioned above, to perform an operation effectively, users need to be well-versed in various blockchain networks, understand the dynamics of reactive gas assets, and understand the methodologies for obtaining these assets.

For example, the process of staking on Lido usually entails about 27 clicks, engagements with three different dApps, and six instances of wallet interaction, and can take up to 15 minutes of effort.

So, how do we solve this?

Before we answer this, let’s first understand that intent can be majorly categorised into two types: Vague and Precise. Vague intents are initial, often rudimentary, articulations of a user’s objectives. For example, a user stating, “I have 100 USDC and wish to stake,” presents a goal that lacks specificity.

Conversely, a Precise Intent encompasses more comprehensive details, such as, “I have 100 USDC on the Polygon network and wish to stake in Lido on Ethereum.” This type articulates a user’s goal with greater clarity and detail, essential for precise execution.

The transformation from a Vague Intent to a Precise Intent is enabled by interactions within our advanced user interface. This interface features a sophisticated model, known as “Prompter,” which engages users through a sequence of smart, adaptive prompts. These prompts are intricately crafted to elicit detailed information about the users’ specific intentions, ensuring a more tailored and effective user experience.

Once crystallised into a Precise Intent, we identify the necessary steps required to actualise it. For example, in this case, the necessary steps would be -

• Transfer funds

• Swap USDC to ETH

• Stake ETH

Considering various factors such as asset compatibility, blockchain-specific constraints to craft a viable execution path, etc, strategic assembly of these steps are created. This assembly or path ensures that the complex operations are streamlined, making the execution of user intents both practical and efficient. We find the best executable path for the user which is optimized on both speed and cost and gives the maximum output.

Here, the steps can be executed in the two ways -

• funds → DEX (Polygon) → Bridge 1 → Lido (Ethereum)

• funds → Bridge 1 → DEX (Ethereum) → Lido (Ethereum)

Our proprietary takes the different possible paths and simulates the execution from each of them. As part of the simulation it figures out the output which the user shall get for each of these paths. After choosing the best possible option and getting confirmation from the user, the steps are executed accordingly. This process not only enhances user experience but also underlines the sophistication and effectiveness of our cross-chain framework.

This is the high-level level understanding of how things would change for the end user with our upcoming intent framework.

Benefits of Router’s Intent Framework

The framework will play an important role in our wider strategy and will also influence the course of Web3’s journey; let’s take a look at some of the benefits -

1. Simplified user experience: As we mentioned above, understanding different blockchain ecosystems can be complex. However, with our new framework, this process becomes much more intuitive and straightforward, leading to increased user adoption.

2. Improved DeFi Accessibility: The framework’s capability to integrate services across various blockchains can unify the fragmented blockchain ecosystems, enhancing interoperability and functionality.

3. Simplified dApp development: The framework also simplifies the development of new blockchain applications, especially for new developers. It provides easy-to-use tools and clear pathways for building derived applications, lowering blockchain integration’s technical hurdles and complexities.

Conclusion

As we continue to refine and develop these concepts, we are streamlining processes and redefining how users and developers engage with blockchain technology. The future of blockchain lies in creating an intuitive, inclusive, and efficient environment, and ‘Intents’ are at the forefront.

The journey ahead is as exciting as it is promising!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Early Initiatives and Web3 Evolution

Tracing the origins of Router Protocol’s vision: to onboard the next billion users onto Web3. 2020 saw the advent of “Ethereum Killers” and an explosion of Layer 1 blockchains. Someone had to work on the movement of assets between these siloed ecosystems.

Router leapt forward with its bridging solution and became one of the earliest proponents of interoperability, launching our early version of an asset transfer bridge.

As the web3 space evolved further, NFTs grew in popularity, and so did dApps across ecosystems. The realisation that even NFTs needed to be bridged and dApps faced the problem of user-base and liquidity fragmentation dawned on. Router abstracted the capabilities of its bridge to be useful to dApps in the form of a widget/ API or an SDK and developed cross-talk for general message passing.

Amidst these technological advancements, our community has grown, currently boasting 70k+ followers on X and a vibrant 25k+ member community on Telegram and Discord.

Router’s Genetic Evolution

By 2022, we realised that the bridging technology needed a major overhaul. We then pursued the idea of using a blockchain as a bridge — an ambitious but robust approach in a pleasant contrast to the approach taken by incumbents.

We built our own Layer 1 blockchain utilising the Tendermint Consensus of Cosmos. This implied that we now had composable stateful middleware, which meant that bridging with intelligence was a real possibility. We coined the term IDapp, referring to dApps that were interoperable by default if deployed on the Router Chain.

Testnet Mandara of Router Chain went live, and several prominent Layer 1 and Layer 2 testnets were integrated. We started developing an ambitious gamified platform to simulate a truly interoperable ecosystem. More on this will be unveiled as we move closer to the mainnet in Q1 of 2024.

Besides, the journey has been about forming a wide range of partnerships. Router has closed more than 90 partnerships with notable projects in this industry from L1s & L2s like Near, Tron, Linea, and Scroll to Dapps like Rango, Frontier, etc., we covered a long journey.

Current State, the Interoperability Suite, & the path to user adoption

As things stand today, we have successfully developed an infrastructure that is arguably one of the best interoperability suites in web3.

A modular, intents-based, cross-chain solution built on Layer 1 blockchain, whose capabilities can be abstracted for web3 businesses, with an upcoming flagship dApp — Router Nitro that promises to be fast, secure and at least 60% cheaper than incumbent solutions. Great, but perhaps not enough to bring in the deluge of users from an adoption standpoint to web3.

Check out Router Nitro here — https://nitro.routerprotocol.com/swap

The realisation was loud and clear in the recently concluded X Spaces that saw participation from major DEXes in web3 like Sushiswap, Trader Joe, Levana, DODO, etc.,

Web3 needs a composable interoperability solution. Liquidity fragmentation and the cost of deploying on multiple blockchain ecosystems is a problem. In this context, Davide’s insights from Trader Joe are crucial, where he emphasises the importance of the deployment approach over mere execution during the Spaces.

Security is of utmost importance and priority. Router’s infrastructure is solving for all of this.

“Security should be, first and foremost, the base consideration of user experience when you’re building a product”
- Jared Grey, Head Chef, Sushiswap

An icing on the cake, as Jonathan, Levana Protocol highlighted how platforms need to relocate the resources to improve the experience– Over the last month, we at Router have solved the last mile of truly simplifying the user experience and onboarding.

The Complexity of Blockchain Interactions

Blockchain technology, with its promise of decentralisation, has heralded a new era of digital interactions. It has led to the birth of decentralised applications (dApps) that operate without a central authority. However, this decentralisation comes at the cost of complex interactions, especially when involving different blockchain networks. In blockchain vernacular, an intent represents a user’s aspiration to perform a specific operation. Yet, the voyage from a vague user intent to a programmable, executable intent often entails navigating a quagmire of protocols and procedures.

Picture this. A user says, ”I have 100 USDC and wish to stake it.” While this statement reveals the user’s desire to stake USDC, it lacks specifics like the blockchain network the USDC is on or the chosen staking platform. This lack of detail renders the intent too broad to be actionable in its current form.

The manual resolution would involve several distinct steps. First, the user must decide where to swap USDC for the required cryptocurrency (e.g., Ethereum), considering factors like exchange rates and fees. If the USDC is on Polygon and the staking is on Ethereum, they must use a bridge service to transfer assets. Finally, the user navigates to the staking platform (e.g., Lido on Ethereum) to complete the staking process. This entire procedure involves interacting with multiple dApps, executing various transactions, and dealing with different user interfaces and protocols.

It typically involves around 27 clicks, interactions with 3 different dApps, 6 wallet interactions, and up to 15 minutes of effort. Not to mention the need for the user to be familiar with multiple blockchain networks, their respective gas assets, and the processes for acquiring these assets. Additionally, knowledge about bridges for asset transfer and navigating through decentralised exchanges or aggregators is essential. This complexity and time investment add a significant inertia to user onboarding.

At Router, we have found a way to solve this! Stay tuned for more.

Happy Thanksgiving.

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Mint and Burn Flow

Essentially, as this mechanism sounds, it allows users to “burn” or destroy tokens on one blockchain and “mint” an equivalent number of tokens on another blockchain. This process not only maintains the integrity and value of the assets being transferred but also ensures the consistency of the total supply and guards against potential issues like double-spending.

For this approach, it is important to note that the bridge has permission to mint/burn the token on the source and destination chain.

In this blog, we aim to explore the nuances of how the Burn and Mint Flow operate, particularly in the context of the Router Nitro.

The high-level workflow of the flow -

If we have to break down this diagram and put it in a simpler way, we can say -

1. Starting the Transfer: A user decides to move funds from one blockchain (Chain A) to another (Chain B). They initiate this process by invoking a contract on the source chain (Nitro contract).

2. Validating and Burning Tokens: The Nitro contract checks if the user’s request is valid. If it is, the contract takes the tokens from the user’s account on Chain A and “burns” them.

3. Burning tokens means they are effectively destroyed or removed from circulation. At the same time, the contract (via the iSend() function) signals another contract (Router Gateway contract) about this action.

4. Communicating Across Chains: The Router Gateway contract on Chain A announces (emits an event) that tokens have been burned. This announcement is listened to by the Orchestrators on the Router chain. Upon receiving such an event, they confirm (attest) that the tokens on Chain A have indeed been burnt.

5. Processing the Transfer Request: After 2/3+1 validation, the Router chain forwards the burn event to the middleware Nitro contract. This middleware contract prepares a request to send new tokens to the user on Chain B and deducts fees from the funds being transferred to the user.

6. The Final Steps: The Nitro bridge contract, upon validation by the orchestrators, prompts a Nitro relayer to inform (forward) the Router Gateway contract on Chain B about the transfer. The Router Gateway contract on Chain B then tells the Nitro contract on Chain B about the incoming tokens.

Finally, the Nitro contract on Chain B creates (mints) new tokens and adds them to the user’s account on Chain B. This minting is like creating new tokens to replace the ones that were burned on Chain A.

As mentioned above, the following also ensures a high level of security by eliminating risks of double-spending, as tokens are irrevocably burned on the source chain before equivalent tokens are minted on the destination chain. It upholds asset integrity, as the total supply of the tokens remains constant across different networks, preventing inflation or devaluation of assets during transfers.

The flow also addresses the critical challenge of asset portability across various blockchains and aligns perfectly with blockchain technology’s core tenets of decentralisation and security.

Lastly, no forwarder fee is incurred via this flow as they are not fronting the liquidity, its just a message transfer from source to destination.

The USDC Flow

Cross-chain Bridges commonly offer the transfer of stablecoins between blockchains through “wrapping,” a method prone to security breaches.

Circle, the company behind USDC — the crypto market’s second-largest stablecoin — introduced a safer alternative for moving stablecoins across chains. The method involves a process where USDC is burned on the source chain and minted on the destination, bypassing the need for traditional wrapping-based bridges.

This is how it works with Router Nitro -

1. A user invokes the Nitro contract to transfer USDC from Chain A (source) to Chain B (destination). The nitro contract calls the USDC contract on the source chain, and the USDC contract burns the USDC.

2. Then, the USDC contract emits an event, and the forwarder listens to it and starts polling the circle API (in intervals until it gets the attestation).

3. Once the Circle API gives the attestation to the forwarder, the forwarder calls the USDC contract on the destination chain.

4. The USDC contract then proceeds to mint the USDC for the user (on the destination chain)

When USDC is burned on the source chain, the Nitro contract shares the user’s address details with the source chain’s USDC contract. Therefore, when the forwarder calls the destination chain’s USDC contract to mint new tokens, it doesn’t specify the recipient’s address. This ensures secure and accurate token minting.

We have completed all our flows; for a better understanding of the forwarder flow, you can explore our Medium article: https://medium.com/@routerprotocol/router-nitros-architecture-d5f354bbe43c

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Here are the key developments:

Chain Updates

• Nitro Module and Workflows for Cosmos chain: We have completed v1 development of the contracts. Development is ongoing on the Router chain side for integration, with testing scheduled upon completion of contracts.

• Starknet Integration: Orchestrator and Relayer changes have been successfully implemented.

• Logging for Nitro Modules: Logging functionalities for Chain and Orchestrator modules have been completed.

Router Nitro Updates

• New Feature in Asset Forwarder Flow: Added ‘Dest Token info in source’ feature for improved asset management.

• Swap UI Development: New designs for the Swap UI have been completed. This will be implemented soon and updated on testnet.

• UI Enhancements for Nitro Apps: Stability improvements and added a feature flag for maintenance notifications.

• Error Boundary for UI: Implemented to enhance user experience and handle failure scenarios.

Tools

• Explorer Enhancements: Deployment of revoke feepayer, cross-chain page, and CSV download feature.

Other Updates

• Forwarder UI Redesign: Enhanced filtering by chain and type.

• CoinFinance98 Wallet Integration: Integration has been completed, and the wallet has been added to the Nitro testnet.

• Optimisations for Nitro frontend: Stability improvements and deployments completed.

• Nitro’s Voyage Page UI: Development completed for the UI, data integration is pending, which will be picked in the upcoming weeks.

• Cosmostation Wallet Integration: Completed for ping-pong functionality.

Audit

• Asset Bridge Audit Fixes: Completed for both Informal and Oak audits.

• Dex Span Audit Report: Received from Oak.

Upcoming Week’s Focus

• Nitro Implementation for Cosmos Chains: continue development and testing on the integration of the cosmos chains with Nitro.

• Audit Follow-ups and Testnet Migrations: Continuing with validations and automated test suites. Completion of the audit fixes recommended by 0xCommit and Oak in the upcoming week.

• IRL Event: Showcasing Router’s Technology at RNSIT Bengaluru on 17th Nov.

• Roadshow in Indore: Continuation of Technological adoption of Router's cross-chain capabilities.

Stay tuned for more updates as we continue to build a more interconnected and efficient blockchain ecosystem. Join us on our journey towards a seamless cross-chain future.

Join us on our channels and be a part of the Router Protocol family

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

In our earlier blog, we went through the world of bridges, their technology, design, and innovation and also discussed the four important pillars — Capital Efficiency, Security, Latency, and Cost! We also discussed how the existing bridge solutions fail to achieve these critical benchmarks. However, on a promising note, we concluded by shedding light on the Router’s Asset Swapping Engine and its potential impact on the bridge landscape.

On that note, let’s begin-

Before we do that, we’re calling our bridge “Router Nitro”.

Router Nitro is a bridge built using our cross-chain primitive “Reverse Verification” flow, which enables high-speed and low-cost transfers.

The reverse verification flow is created using the application-specific bridging construct enabled by our chain. This primitive can be used by other applications to make them more efficient in the future.

Moreover, Router Nitro enables the flow of arbitrary instructions along with asset transfers, thus expanding the realm of composability within the DeFi ecosystem across diverse blockchain networks.

Picture a scenario where you need to transfer funds from Bank A to Bank B. In this process, Router Nitro acts as an intermediary, collecting the money from Bank A, and then its partners, referred to as forwarders, personally convey the funds to Bank B.

Following the transfer, Router Nitro undertakes a crucial verification step to ensure that the amount you originally deposited in Bank A matches the amount that arrives at Bank B. If the verification is successful, Router Nitro’s partners retrieve the funds they initially transferred to your Bank B, effectively completing the transaction.

Router Nitro has three flows with which it enables this swapping -

1. Forwarder Flow — It uses a trustless optimistic approach to handle cross-chain asset transfers and has an entity called the forwarder that provides the users with their desired assets on the destination chain.

2. Burn and Mint flow — For certain tokens, the bridge has mint/burn rights, which allows the bridge to burn the tokens on one chain and mint them on another.

3. USDC circle flow — This flow uses Circle’s CCTP infra to provide cross-chain transfers of USDC. The flow works for USDC transfers on chains where CCTP is live.

In this blog, we will be covering the Forwarder flow, and before we do that, here are some terms and their explanations for you to understand the flow in a better way

• Orchestrators: It ensures that all the validators and relayers are playing in sync and that the information being passed between them is accurate and legitimate.

• Middleware contract: It is a contract which is deployed on the Router chain, which enables custom business logic directly in the bridging layer.

• IBC: Inter-Blockchain Communication Protocol is an open-source protocol to handle authentication and transport of data between blockchains (within the Cosmos ecosystem.

• Gateway contracts: Gateway contracts serve as the interface for the application contracts on any chain to interact with contracts on other chains.

This is how the entire flow of bridging using forwarders looks-

In the forwarder flow, first of all, a user invokes the Nitro contract to transfer funds from Chain A (source) to Chain B (destination). The source chain Nitro contract will validate the request, deduct funds from the user’s account, increment event nonce and emit a FundsDeposited event.

Whenever a FundsDeposited event is emitted from a Nitro contract, Orchestrators listen to this event and submit the event to the Router chain along with their attestation. Parallely, the forwarders also listen to the FundsDeposited event.

After 2/3+1 validation, the Router chain will invoke the middleware Nitro contract with the event info, and after this, the middleware contract will persist with the request!

While the event was being processed on the Router chain (attestation, validator, submission on the middleware contract), in parallel, the forwarder also listens to the FundsDeposited event and invokes the Nitro contract on the destination chain.

Upon receiving the transaction, the Nitro contract on the destination chain will (a) transfer the defined amount from the forwarder address to the receiver address, (b) create a hash of the fields included in the request and persist it in the status map (to skip the replays), and © emit a FundsPaid event confirming the execution.

Orchestrators on the Router chain listen to the FundsPaid event from the destination chain Nitro contract and submit it to the Router chain with their attestation. Upon receiving the FundsPaid event, the middleware contract verifies that the message generated from the request data is the same as the message hash from the executed event, marks the request as Completed and persists the forwarder address and amount.

After the request is marked as completed, the forwarder can claim its funds by triggering an outbound request on the Router chain. This request undergoes processing through both the Router chain and the existing Gateway contracts. Subsequently, the Gateway contract will engage with the Nitro contract on the source chain, ensuring the settlement of funds for the forwarder.

So, just like that, Router Nitro bridges your assets from Chain A to Chain B efficiently, securely, and with minimal cost using the reverse verification flow!

Managing L1 and L2 Dynamics in Cross-Chain Transfers

When there are L1 chains on both ends, a similar process unfolds, with assets and instructions making their way across the bridge. However, when we shift our focus to transactions originating from an L2, a distinct challenge emerges. This challenge is the potential for a “rollback” during the fraud-proof window, a phenomenon that can disrupt the typical flow of things. Let’s understand how -

The Rollback Challenge

In an L2 ecosystem, a transaction is considered optimistically valid, and there’s typically a designated window of time within which verifiers can submit a fraudulent rollup transaction, often spanning several days. Now, consider a situation where a verifier, two days after the fact, reports an alleged invalid state transition (transaction), calling for a complete reversal, aka rollback of the entire batch of transactions.

Suppose this report is substantiated and a discrepancy between the state root on the L1 and the actual state of the rollup chain is identified. In that case, transactions executed during the past two days are deemed illicit.

Consequently, the rollup chain initiates a rollback, reverting to the last state root proposed by the sequencer, essentially nullifying all transactions within that time frame.

However, this creates a predicament for the bridge as users on the destination chain have already received assets based on the assumption that the transactions were valid. Due to the rollback, these transactions are invalidated, necessitating a return of assets by the source chain to the users.

This basically means that forwarders will not be able to claim the assets that they’ve already given on the destination chain as the source chain has returned the assets locked on the bridge contract back to users (because of the rollback).

This situation presents a significant challenge for the bridge that connects the source and destination chains, resulting in financial losses because assets have already moved on both sides and now reconciliation becomes imperative.

How do we address this challenge?

To address this challenge, forwarders can take a proactive approach. They can perform a quick status check of the chain (if the chain is in the correct state) before taking up a transaction event to handle.

The way to check the chain’s status is to get the transaction data, recreate the state root of the chain and then compare it with the existing root on the chain. After comparison, if both the roots align, then the forwarders can proceed with the transaction execution on the destination side.

This step is essential in maintaining the integrity and reliability of cross-chain transfers. In the coming future, Nitro will provide certain modules to enable this check.

Managing EVM and Cosmos Dynamics in Cross-Chain Transfers

Firstly, when we go from an EVM chain to a Cosmos chain, the flow pretty much remains the same; however, as there is Cosmos on the destination side, the orchestrators are replaced by IBC relayers!

The process begins with the user depositing funds into the EVM chain’s Nitro contract, which triggers a FundsDeposited event. Upon listening to this event, forwarders call the contract on the destination (Cosmos) chain to allow the transfer of tokens from his wallet to the user’s wallet. Simultaneously, orchestrators listen to this event and submit the event to the Router chain along with their attestation.

After 2/3+1 validation, the Router chain will invoke the middleware Nitro contract with

the event info, and after this, the middleware contract will persist with the request!

The contract on the Cosmos chain transfers the funds to the user from the forwarder’s account. Once the transfer is successful, the FundsPaid IBC message from the Cosmos chain is received by the Nitro middleware contract on the Router chain and the reverse verification is initiated. Post successful verification, the forwarder can initiate the withdrawal of the funds.

In another case, when we go from one Cosmos chain to another, a user deposits funds on the Nitro contract on Cosmos Chain A, and the Nitro contract on Cosmos Chain A triggers the FundsDeposited event. Here, we should remember orchestrators are not required as we have Cosmos chains on both ends!

Then, the Nitro contract on Cosmos chain A initiates a cross-chain request by sending a FundsDeposited IBC message to the Nitro middleware contract on the Router Chain.

A forwarder picks the deposit from the Nitro contract on Cosmos Chain A and transfers the funds to Cosmos Chain B from their account. After a successful transfer, Cosmos Chain B sends a FundsPaid IBC message to the Nitro Middleware Contract on the Router Chain.

The Nitro middleware contract on the Router Chain listens to both the FundsPaid IBC message from Cosmos Chain B and the FundsDeposited message from Cosmos Chain A. It then performs a reverse verification to ensure accuracy.

The forwarder can then initiate withdrawal from the Nitro middleware contract on the Router Chain. To enable this, the Nitro middleware contract on the Router chain triggers an IBC Crosschain Outbound Request to the Gateway contract on Cosmos Chain A.

That’s how Nitro will be pivotal in extending Cosmos chain connectivity to a broader spectrum of blockchain networks. This extension is a significant development, as it not only enhances interoperability but also expands the reach and utility of Cosmos-based chains within the larger blockchain ecosystem.

NOTE: The integration of Cosmos chains is a conceptual framework that is presently in the development phase.

As we’ve laid the foundation in this part, stay tuned for the upcoming blogs, where we’ll dive deeper into the other two flows and the individual pillars of Router Nitro’s architecture.

We’ll explore how it excels in capital efficiency, security, latency, and cost-effectiveness and how it is not just an ordinary bridge!!

To stay updated with our latest developments and to be part of our growing community, we invite you to follow us on our socials -

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

From integrating new chain support to advancing our analytics tools, each step forward is designed to bring you a robust and resilient platform. Here’s a closer look at the strides we’ve made and the innovative paths we’re paving in our blockchain ecosystem.

Chain Updates:

1. Enhanced Chain Queries:

• Significant upgrades to our query capabilities, including the introduction of ‘ReadyToExecute’ queries by workflow and relayer type, complemented by crucial bug fixes, have been implemented to ensure smoother operations.

• These enhancements aim to streamline the user experience in accessing and executing chain operations.

2. Analytics Tool Performance:

• Upgrades to our analytics tools have resulted in increased performance, providing users with faster and more accurate data analytics for better decision-making.

• The improved speed and efficiency mean that users can access the insights they need with minimal delay.

3. Contract Audit Rectifications:

• Following a detailed audit, all necessary rectifications have been made to the cosmwasm gateway contracts, underscoring our unwavering commitment to platform security.

• These rectifications are part of our ongoing efforts to adhere to the highest security standards and industry best practices.

Router Nitro Updates:

1. Cosmos chain integrations

• We have started efforts on cosmos chain integration for providing asset transfers between other chains and cosmos chains.

• This flow will utilize IBC for communication between the Router Chain and cosmos chains to complete the verification of the funds transfer

2. Introduction of partner IDs for partners

• The system for determining transaction fees has been revised to be more accurate or user-friendly.

• Partner IDs are identifiers for entities that partner with Router Nitro, and we’ve made the process of using these IDs smoother, possibly for tracking transactions or sharing fees.

3. Token Transfer Events and Explorer UI Enhancements:

• We’ve added more detailed tracking for when tokens are moved within the platform, which could be useful for users to monitor their transactions.

• Made more improvements in Nitro Explorer and User Interface.

4. Cross-chain swap improvements -

• Enabled instruction transfer along with swaps on the testnet. This can be crucial for dApps who want to enable 1-click cross-chain flows such as cross-chain liquid staking or cross-chain LPs.

5. Testing and Bug Fixes:

• Rigorous testing of all modules

• Continual refinements and addressing identified bugs across our systems.

• Addressing identified bugs across our systems

Other Updates:

• Google Cloud Platform (GCP) Migration: Our migration to GCP is complete, with Google Kubernetes Engine (GKE) hosting our web2 APIs and Kubernetes for our explorer API, ensuring robust scalability and reliability.

• Jenkins Secret Management: We’ve enhanced our environment and secret management within Jenkins, reinforcing our commitment to security and operational efficiency.

Upcoming Focus:

Nitro

• Cosmos chain integration will be a continued focus.

• Efforts would be put into testing and performance improvements, and UI optimizations.

• Showcasing POCs for different types of cross-chain dApps, which can enable developers to understand different capabilities using Router.

Chain

• Performance and functional testing of various flows.

• Preparation for mainnet.

Audit

• As the audit process continues and we will keep fixing issues raised by the auditors as they come.

Engagements and Audits:

• Unfold Hackathon and IRL Events: We’ve represented Router Protocol at the Unfold hackathon with Voyager V2.0, and engaged the community at Jamia Humdard College, Delhi.

• Audit Updates: The audit process is essential for our progress. We’ve cleared pending dependencies for Oak, and the Informal audit is on track with the current end date set for November 3.

In Conclusion, every update here is a step towards a more interconnected and efficient blockchain ecosystem. Stay connected with us for more insights and to be part of our journey toward a seamless cross-chain future.

Join us on our channels and be a part of the Router Protocol family.

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Bridges, in simple words, allow users to move assets/metadata from one blockchain to another and provide the solution of interoperability to the fragmented world of blockchains!

These bridges’ off-chain actors or verifiers act as intricate connectors to facilitate the flow across these decentralised galaxies.

In addition to facilitating the cross-chain transfer of assets and information, bridges provide a multitude of benefits for users, developers, and dApps alike.

Much like how each blockchain has its own universe with its unique rules, consensus mechanisms, and tokens, cross-chain bridges are also distinct in the way they operate and have various designs and intricacies.

This blog will delve into various design approaches and their implications, aiming to bridge the gap between bridge users and the bridges themselves! Phewf! So, let’s begin!

We’ve encountered the challenging scenario known as the “Interoperability Trilemma” in the world of bridges, which says Similar to the Scalability Trilemma, there exists an Interoperability Trilemma in the Ethereum ecosystem. Interop protocols can only have two of the following three properties:

• Trustlessness: having equivalent security to the underlying domains.

• Extensibility: able to be supported on any domain.

• Generalizeability: capable of handling arbitrary cross-domain data.

To simplify and elucidate this concept, let’s delve into what we call the “Four Pillars of Bridges”: Capital Efficiency, Security, Latency, and Cost. These pillars significantly impact both bridge operators and users, with users being particularly affected as their assets are at stake.

Capital Efficiency

In the decentralised finance (DeFi) world, the significance of Total Value Locked (TVL) as a measure of success has been overstated. Liquidity aggregation is essential, but what truly matters is how effectively that liquidity is utilised, and this is what we call Capital Efficiency!

However, most bridges, like Satellite, Stargate, etc, are still stuck in the “Liquidity Era of DeFi” and are accommodating extremely large TVL and do not acknowledge the paradox it presents.

The surge in liquidity has given rise to a pressing concern: the excessive emission of liquidity mining rewards. As projects strive to attract users and incentivise liquidity provision, they are obligated to distribute substantial sums, often reaching into the millions, in liquidity mining rewards. While these incentives are crucial for fostering participation and growth, the challenge lies in striking a balance between attracting users and maintaining these projects’ sustainability and long-term viability.

Brimming with assets, these bridges also act as honeypots for black-hat hackers on the prowl for high-value vulnerabilities!

The Ronin bridge attack is a testament to the fact that these bridges are not mature enough to accommodate such numbers; not only do they risk being compromised themselves, but they also run the risk of having their entire liquidity base compromised!

Before moving to the next section, let’s discuss how you, as a user, can select a more meaningful measure of a bridge’s success.

You can evaluate this measure through various metrics such as -

1. Utilisation Ratio = Daily Trading Volume / TVL

2. System Return on Investment (ROI) = Total Revenue Generated / Total Amount Spent in Sourcing the TVL

This measure focuses on assessing the efficiency of a protocol’s capital utilisation, thereby preventing unnecessary liquidity loss.

Security

Security is the foundation upon which trust and reliability are built. The importance of security cannot be overstated, especially considering the tumultuous events that have unfolded since 2021. With the rapid ascent of L1s and the growing significance of bridges, security breaches have become a recurrent concern and a pervasive theme.

Last year, Chainalysis estimated that around 70% of the loot, totalling around 2 billion, was from bridges, underlining the attractiveness of these platforms as profitable targets for malicious actors.

In this context, the linchpins of blockchain interoperability can be classified into two distinct categories: Trustless and Trusted Bridges.

Trusted Bridges are the ones that depend on third-party entities for ensuring the security of their operations, while trustless bridges maintain security via smart contracts and algorithms.

In a simpler way, Trusted Bridges are like a group of boat rowers that take you from one side to another. Celer’s cBridge and Axelar are some examples.

On the other hand, Trustless Bridges are like actual bridges, you can cross them on your own without placing your trust in a third-party entity. IBC is an example of such bridge.

Latency

Latency, in the context of cross-chain bridges, refers to the time delay between the initiation of a transaction on the source chain and its confirmation on the destination blockchain. It plays an important role in the user experience and efficiency of cross-chain transactions. There are two major ways here -

First is the Optimistic Model, which assumes submitted transactions are correct and transfers them without immediate verification. Imagine the Optimistic Model as a self-checkout lane at a grocery store. You scan your items and pay without immediate verification, assuming everything is correct. Beamer and Across are some examples of such models.

This fast model gives users quick access to their funds on the destination chain and also reduces transaction fees by minimising computational work, making it more attractive to users.

Second is the Pre-transaction verification model, which verifies the validity of a transaction before allowing it to proceed (so, be ready to be in the long queue). Verification processes, such as consensus among multiple validators, can introduce significant delays in transaction processing. Besides, pre-transaction verification’s computational and resource-intensive nature may result in higher transaction fees. Axelar and Stargate are examples of such models.

Cost

Most Cross-chain bridges entail various challenges, primarily stemming from their substantial Total Value Locked (TVL) and complex smart contract structures.

As we previously explored, the issue of high TVL carries its own complexities and paradoxes. However, another significant drawback arises from the necessity of effectively managing and upkeeping this liquidity, a task that inevitably imposes costs on end users.

Moreover, the very nature of the smart contracts that underpin most of the cross-chain bridges tends to be inherently intricate. These complex contracts demand substantial computational resources, increasing gas fees for users when they engage in transaction execution.

The explanation provided above is somewhat abstract in nature. It’s worth noting that numerous hybrid approaches and subsets of crypto-economic and technological mechanisms are today being employed to improve these aspects.

So, is there a bridge that can stand on these pillars in a way that balances everything for a user? The answer is YES!

It’s the Router’s new Asset Transfer Bridge. It’s trustless, it’s capital-efficient as there’s no TVL locked on it, and the cost to use it is considerably less than most of the bridges out there. And it uses a reverse verification security infra that ensures ultra-low latency.

We’ll delve into its architecture and touch upon every segment to explain what makes it one of the best bridges out there!

To stay updated with our latest developments and to be part of our growing community, we invite you to follow us on our socials!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Let’s run down the notable highlights.

The Upcoming Asset Transfer Bridge’s Updates:

As we continue to evolve and refine our platform, the Asset Transfer Bridge remains at the forefront of our development. This bridge, designed to streamline and fortify cross-chain operations, has seen a slew of updates and enhancements over the past fortnight. With an emphasis on user experience, security, and efficiency, we’re here to share the latest improvements we’ve achieved in this segment:

Chain Integrations

• EVM chains were added to the bridge, and testing was successfully completed

• For Tron and Near development was completed, testing is ongoing and is planned for completion in the coming week

Swap UI

• UI has been upgraded and made quite lean compared to the v1 Voyager

• UI allows you to connect your wallet via multiple sources and has also been updated to support Tron and Near wallets

Forwarder UI

• Users can set fees for their forwarders based on chains and tokens

• Forwarder can set the liquidity address as well as the withdrawal addresses from the UI

Chain Updates:

At the core of our platform lies the foundational technology that powers our services, and it has seen a series of upgrades and optimisations achieved in recent weeks. Here’s a comprehensive look at the advancements we’ve made in our chain’s infrastructure:

Performance Enhancement

• One of the most important focuses right now is to improve the performance of the chain. We have been continuously working to reduce the block time of the chain. Currently, we have been able to achieve a 1.64 sec block time with 22 validators. We will continue to optimise this as we move forward.

Testnet

• More than 100k transactions have been successfully completed on our Testnet Mandara.

• GT Mandara Phase 2: The development work for the second phase of GT Mandara is currently in progress.

Other Updates

• Workshop: Successfully conducted workshops IRL at SRM Chennai with over 300 attendees and at Galgotias College with over 100 attendees.

• Collaborations: Partnered with CoinDCX to attend Unfold as hackathon bounty sponsors.

• Tutorials: Working on an Asset Transfer Bridge video tutorial.

• First Month Completion: The inaugural month of Rabbit Rush has concluded, and rewards for participants have been sent. We witnessed an overwhelming number, with over 16k cross-chain NFTs being minted. Due to its success and positive reception, the lottery campaign will persist in the upcoming month.

Audit:

As we move closer to mainnet launch, one of the key things to focus on will be security. The chain and asset bridge audit is being done parallely by 2 auditors. Below you can find updates on where we are with our audits.

Informal Systems

• Informal Systems has already completed the audit for the chain. Now, they are focused on the audit for the asset bridge.

• The team has fixed all the issues raised by the auditors.

Oak:

• Oak has completed the audit of the chain as well.

• They have now initiated the next phase of the audit for Asset Transfer Bridge.

Upcoming Focus:

Asset Transfer Bridge

• Focus on completion of Tron and Near testing

• Begin efforts for EVM to Cosmos chain integrations to support token transfers

• Load testing for the asset transfer bridge to begin which could help in figuring out further optimizations on the chain and the process side

Chain

• Key managements for orchestrator to be tested

• Changes needed to support the cosmos chain integrations

• Further load testing on the chain to stress test to figure out the performance and the block time under very high load

Audit

• Support audit process and fix issues raised by the auditors as they come

With this, it’s time to wrap up this edition of Router’s Tech Fortnightly Updates! To stay updated with our latest developments and to be part of our growing community, we invite you to follow us on our socials!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

New Architecture, Optimisations, and more…

Our Chain, an interoperability hub built at a crucial intersection of decentralisation, scalability, and security, has been optimised from various aspects in the last couple of months.

The blockchain is focused primarily on enabling state transitions across networks, and it sits as a hub between various EVM and non-EVM ecosystems. In this light, we have added Tron and Near to our ecosystem! Along with connectivity, we have worked on a seamless experience for end users, like enhancing the block time by re-executing the logic for pending transactions. And introduced batching for the orchestrator, which has allowed for an increased TPS (transactions per second) for cross-chain requests.

You can read more about the architectural changes here — https://medium.com/@routerprotocol/router-chains-new-v-1-1-whitepaper-d1b6bcdd0221

New features like tracking refund mechanisms and acknowledgements can be accessed live via Explorer. Besides, new tools have been added like Router Explorer, Faucet, Station, and Hub -

• Router Explorer, much like other block explorers, helps you in tracking cross-chain transactions.

• Router Faucet helps you in optimizing testnet tokens for performing tasks on the tesnet.

• Router Station is a tool to manage contract lifecycle-related processes on the Chain.

• Router Hub allows users to delegate $ROUTE tokens to Validators.

• Router Sandbox provides a prototyping environment for compiling and deploying IDApps using Router.

New IDApps: Ping Pong, TExchange, and Rabbit Rush

As you already know, our tesnet Mandara is LIVE, and we’ve been releasing various IDApps or Interoperable Decentralised Applications to showcase the capabilities of our Chain! Let’s quickly take a look at the same -

Ping Pong is our inaugural IDApp on Mandara, it allows users to send an arbitrary message (Ping) from one chain to another and receive an acknowledgement in return (Pong) back to the source chain, all with the click of a button. This application serves as a proof-of-concept for Router-powered interoperable dApps and, in doing so, paves the way for a new era of seamless interoperability!

TExchange capitalises on the advanced middleware infrastructure facilitated by our chain and provides users with an efficient and seamless token swap functionality across various testnets. TExchange houses a decentralised exchange (DEX) in the background, which serves as the backbone for liquidity pairs involving all the testnet tokens and their respective wrapped USDC pairs.

Rabbit Rush enables you to mint your own cross-chain Rabbit NFTs and seamlessly hop them between blockchains. These NFTs, in turn, become your ticket to a daily Omnichain lottery system where users can participate from various chains and get a chance to win $ROUTE tokens!

Router’s Asset Transfer Bridge

Progress is underway for the upcoming version of Router’s asset transfer bridge, which focuses on enhancing decentralisation and improving transaction speed and cost-efficiency. To delve deeper into these advancements, we’ve introduced a novel approach: instead of the traditional lock/unlock mechanism for funds, we employ permissionless entities known as “Forwarders” to facilitate token transfers.

Here’s how it works at a high level:

• User Request: When a user initiates a cross-chain token transfer request through the Voyager contract on the source chain, the system generates an event associated with this request.

• Forwarder Action: A Forwarder, operating independently and without central control, detects and picks up the event corresponding to the user’s request. It then proceeds to provide the user with the requested token on the desired destination chain.

• Token Retrieval: At a later point in time, the Forwarder can claim the user-deposited token.

To know more, check out our docs here — https://docs.routerprotocol.com/develop/voyager/voyager-v2.0/high-level-workflow

We will soon reveal a gas cost comparison that will shed light on the cost-effectiveness of our new Asset Transfer Bridge compared to other bridges available in the market! Besides, the new Architecture of the bridge would also be revealed in our upcoming blogs.

As we prepare for the revival of our Fortnightly Tech Updates, think of this overview as your guiding light through the tech terrain of Router Protocol. Stay connected, stay informed, and brace yourself for the forthcoming era of decentralised innovation!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

So, what exactly is happening this time?

As you already know, we’ve partnered with Rootstock, and you just need to simply bridge $USDT from any supported networks to Rootstock via Voyager (https://app.thevoyager.io/swap)! It is going to be as seamless as it sounds, and through on-chain measurements, we will identify the wallets associated with the biggest bridging volumes and duly recognise and reward them.

And what are the rewards we’re looking at?

​​The top 150 addresses with the highest total volume bridged to Rootstock will be the lucky recipients of the rewards. Here’s a breakdown of the same:

• 1st Place: $1,000

• 2nd Place: $600

• 3rd Place: $400

• 4th to 10th Place: $35 each

• 11th to 30th Place: $15 each

• 31st to 150th Place: $10 each

• Raffle: Pool of $300, every participant will enter this Raffle

But how do you participate? Are there any eligibility criteria?

Yes, there is an eligibility criterion — bridge a minimum of 50 $USDT from any supported network to Rootstock using our Voyager cross-chain bridge from the 18th of September 2 PM UTC to the 29th of September 2 PM UTC.

Furthermore, to take part in Voyage 9.0, follow these steps:

1. Complete the transaction

2. Follow @routerprotocol and @rootstock_io on Twitter

3. Like and Retweet this announcement — https://twitter.com/routerprotocol/status/1703770590471991770?t=ujGa2S3c8BOM7RLmTU8i4g&s=19

4. Share the below-mentioned details for the verification of your participation here: https://forms.gle/i6zSaN3vm2AVEmccA

• Your wallet address used for bridging

• Your Twitter handle

Voyage 9.0 is your chance to embark on a rewarding journey, bridging the gap to a world of opportunities. Get ready to participate, earn rewards, and be part of something remarkable. We can’t wait to see you on this exciting voyage!

Website | Twitter | Telegram | Discord | Youtube | Instagram

Rabbit Rush lives up to its name, offering a user-friendly interface. Here, you have the opportunity to mint your very own Rabbit NFTs and seamlessly hop them between different blockchains while witnessing some cool transformations. These NFTs, in turn, become your ticket to a daily lottery, with the chance to win $ROUTE tokens!

Check it out! https://rabbit-rush.routerprotocol.com/

What makes Rabbit Rush so unique?

Let’s delve deeper into the remarkable features that Rabbit Rush brings to the table:

• Truly Interoperable DApp: Rabbit Rush stands out as a truly interoperable Decentralized Application (DApp). It can seamlessly communicate and operate across different blockchains and ecosystems, including Avalanche Fuji, Mumbai Matic, etc.

• Omnichain Lottery System: One of the standout features of Rabbit Rush is its Omnichain lottery system. Traditionally, lottery systems are confined to specific chains or platforms. However, it breaks free from this limitation. It enables users to participate in a daily lottery from any blockchain of their choice. This means that participants from various chains can participate in the same lottery, creating a more inclusive experience.

• Cross-Chain NFTs: With traditional NFTs, they are usually created and confined to a single blockchain, making them less versatile. However, Rabbit Rush’s cross-chain NFTs can seamlessly move across different blockchain networks. This means that your Rabbit NFTs aren’t limited to just one chain; they can hop and explore various blockchains and add a layer of uniqueness to each NFT as it interacts with different ecosystems.

• Seamless Cross-Chain Movement: The ability to move NFTs across chains seamlessly is a remarkable feat. Rabbit Rush makes this process effortless, providing users with a hassle-free experience when transferring their NFTs between different blockchains.

Besides, before we get into the step-by-step process, here are the faucet links where you get tesnet tokens for all three tesnet that Rabbit Rush is currently allowing -

• https://faucet.routerprotocol.com/

• https://faucets.chain.link/fuji

• https://faucet.polygon.technology/

Here’s how it works-

Our platform is designed to be exceptionally intuitive and informative, ensuring you won’t find yourself wondering what to do next. Nevertheless, if you ever encounter any confusion, you can always refer back to this guide for clarity.

1. First, connect your wallet and Switch to Router Tesnet

2. Now that the wallet is connected and switched to Router Testnet, you can simply click on “Mint my Rabbit NFT” and mint it!

3. After the NFT is minted, first share it on Twitter (this is super important) and then start the hopping game by clicking on Bridge to increase your chances to win the lottery.

4. Post Bridging, you’ll notice that your NFT has levelled up and changes its background. Now, to participate in the lottery, you need to select your Rabbit and stake it.

5. Click on “My Wallet” and you will be able to check your ticket’s status for the Lottery.

6. This is how the ticket section is going to look in three cases: when you have won, didn’t win, or the result is yet to be declared.

Conclusion

Router’s Tesnet Mandara continues to be a hub of innovation, and Rabbit Rush is the latest addition to our ever-expanding roster of Interoperable Decentralized Applications (IDApps). It offers a unique opportunity to mint NFTs, earn $ROUTE tokens daily, and experience the thrill of blockchain hopping. So, hop on board and start your Rabbit Rush adventure today!

Stay tuned and keep us close at hand by following us on your preferred social media platform!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

New Chain Integrations, Bridge Integrations, Bitcoin Interoperability

In the last few weeks, we have expanded Testnet Mandara to include various blockchain networks like Scroll, Near, and Linea. Along with Mantle, Ethereum’s Goerli, Avalanche Fuji, Polygon’s Mumbai Matic, and Arbitrum Testnet! Offering developers a comprehensive environment to test and experiment with different blockchain technologies, smart contracts, and interoperability solutions.

Router’s Asset Transfer Bridge also saw the integration of Circle’s CCTP on Arbitrum! This development enhanced our cross-chain dApp, enabling seamless interoperability for $USDC on the Arbitrum network. Along with this, we took our first step towards Bitcoin Interoperability by integrating the Rootstock chain on Router V1. Learn more about it here.

Phase 1 of Mandara GT with Updates on Horizon for Phase 2, Sandbox, and Ambassador Program Launch

As many of you may be aware, Phase 1 of our Gamified Testnet is now in full swing, with around 15,000 NFTs already being minted. If you haven’t had the chance to participate yet, you can access it through this link: https://testnet.routerprotocol.com/ and get yourselves ready for Phase 2, which will be an inclusive ecosystem that gives you a new gamified experience of participating in a testnet!

Additionally, the Router’s Sandbox is live. This intuitive prototyping environment streamlines the processes of compiling, deploying, and interacting with sample IDApps (interoperable Dapps) across various blockchain networks. Read more.

Our Ambassador’s Program, an opportunity for individuals to actively engage with and support the project while enjoying various benefits and rewards, is live. You can explore the provided link for more details on how to get involved. Check it out!

Router’s Networking Highlights and New Partnerships

Router made its presence felt at EthCC, and we also conducted various workshops in Bhopal and Bengaluru; we saw over 500 devs who explored Router’s cross-chain Infra and learnt the seamless way to build Interoperable dApps in these workshops!

Our Co-founder and CEO, Ramani Ramachandran, represented Router at Stanford Blockchain Week and was also a speaker at the 6th edition of Korea Blockchain Week, sharing our vision and expertise with a global audience. Further, Router’s team will be at Token2049 in Singapore from September 13–14, 2023. Stay tuned for more updates and opportunities to connect with us.

In our efforts to grow our ecosystem, we’ve formed strategic partnerships with a range of projects. These include collaborations with ForceFi, Firepot Finance, OPX Finance, Pontoon, Quick Intel, Planq Network, Kunji, Electron Labs, Rivera, Lamas Finance, Xade, and TrikOn.

Router Cross-Connect and IDAppathon

We hosted the inaugural Router Cross Connect event, a Twitter Spaces marathon featuring speakers from over 50+ prominent projects. Among the notable participants were Kyber, Shardeum, Push, Linea, Mantle, Circle, Near, Ankr, Sei, dYdX, LiFi, Rango, Biconomy, Rootstock, and many others. Manisha Khadanga and Justin Roberti hosted it, and you can listen to the event recording by following this link.

During our second Router Cross Connect, we underscored the vital role of wallet communication with speakers from 1inch, Halo wallet (Kucoin Wallet), Fox wallet, Krystal wallet, UKISS technology, XDefi & Timeless wallet. Our hosts, Chief Strategist and Marketing Officer Ashutosh Sahoo and Olesia Deineka from Business Development, expertly guided us through, and you can hear the recording of the spaces here.

Moreover, Router’s IDAppathon has concluded, dedicated to supporting projects and involving a diverse group of builders in experimenting with and launching blockchain solutions on Router Protocol’s Testnet. You can learn more about the winning projects by visiting the provided link.

Upcoming Major Events

After the successful launch of Ping Pong, TEXchange, and Sandbox, we’re coming up with another interesting Interoperable dApp, aka IDApp, on our Tesnet Mandara.

We’ve made significant architectural changes to our cross-chain bridge and making some refinements now, and it’ll be ready to ship in the second half of October. This bridge will be fully on-chain and technically the first flagship dApp of the blockchain we’ve built. With an eye on the commercial side of the business, the focus will be to get more transactions and volumes, thereby increasing the usage of $ROUTE.

Phase 2 of Mandara Gamified Testnet will be launched in the 1st half of October and will co-exist with our first flagship dApp.

Besides, our community’s biggest and favourite cross-chain campaign will be launched this September! Can you guess what we’re talking about?

Router Protocol continues to expand the ecosystem, fostering innovation and interoperability in the blockchain space. Stay connected and explore the latest developments by visiting our website and engaging on the social media channels.

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Performance Upgrades

The new update significantly reduces block time, shaving it down from the previous ~6 seconds to impressive ~1.4 seconds. This upgrade translates to quicker and smoother cross-chain operations, making your experience seamless.

To ensure you continue to harness the full potential of the Router’s enhanced capabilities, we kindly request your attention to a few important steps.

1. Update Your Contract Addresses: Our Gateway contracts have been refreshed to align perfectly with the latest improvements. For your cross-chain transactions to proceed without a hitch, make sure to update the addresses in your contracts.

2. No Changes to Tools and dApps Links: Good news — the links for tools and dApps remain unchanged! You can access them just as you always have, ensuring minimal disruption to your workflow.

New addresses -

You can also access these addresses at — https://docs.routerprotocol.com/networks/supported-chains

Stay connected and explore the smoother, more efficient world of cross-chain operations with Router’s Testnet Mandara!!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

The blockchain world is undergoing a development frenzy, and we at Router thought, what better way to nurture innovation than through a Hackathon? And today, we’re here to announce the winners of the first-ever Interoperability Hackathon — IDAppathon, hosted on Dorahacks.

The IDAppathon was dedicated to supporting projects and engaging a wide range of builders in experimenting and launching blockchain solutions on Router Protocol’s testnet. Over the course of the hackathon, participants worked tirelessly to develop their ideas into functional prototypes, leveraging the capabilities of Router Protocol’s Crosstalk and Omnichain Framework. After weeks of hard work, dedication, and creativity, let’s celebrate the achievements of our talented participants.

Meet the Winners

The solutions ranged from cross-chain DeFi platforms to data-sharing protocols and decentralized identity solutions — all contributing to the advancement of blockchain interoperability.

First Place:
DeployerX and RoutePlace NFT

• DeployerX simplifies smart contract deployment across multiple blockchain networks. With just a few clicks, users can deploy their smart contracts hassle-free. Powered by Router Protocol’s Crosstalk library, DeployerX makes multi-chain deployment a breeze.

• RoutePlace NFT serves as a marketplace for CrossChain NFTs. These special NFTs are designed to move across different blockchain systems and are created using Router Protocol’s CrossTalk Library. This platform allows users to explore and trade these unique NFTs within various blockchain networks.

Second Place:
Buildlt-Router and Horcross

• Buildlt-Router is a metaverse that redefines the concept of virtual ownership by inducing interoperability. Within this platform, users can mint and transfer virtual assets like lands, houses, and more across different blockchain networks by leveraging Router Protocol’s CrossTalk Library. Demo Link.

• Horcross is a project transforming ERC-6551 (TokenBound Accounts) by leveraging Router Protocol’s cross-chain capabilities. By enabling cross-chain functionality, Horcross empowers users to generate contract wallet addresses across different blockchain networks, breaking down barriers and expanding the potential of ERC-655. Demo Link.

Third Place:
Zixin and Avex

• Zixin introduces an innovative solution to validate social account ownership through CrossChain NFTs by leveraging Router Protocol’s CrossTalk Library. With Zixin, users can easily prove their ownership of social accounts like Google, GitHub, LinkedIn, and more by minting CrossChain NFTs. These NFTs can be seamlessly transferred from one blockchain to another, ensuring true ownership verification across diverse blockchain networks. Demo Link

• Avex serves as an innovative identity wallet, streamlining financial and data management into one platform in a chain-agnostic way. It facilitates the transfer of cross-chain tokens by using the Router Crosstalk library. Thus, in alignment with Router Protocol’s strengths, Avex truly exemplifies the potential of seamless cross-chain interactions, elevating the user experience and functionality within the decentralized world. Demo Link

The projects which have taken the top three places will be offered a prize of $5,000, $4,000, and $3,000, respectively. Besides, we’re also offering a pool prize of $3,000 to a few more projects that deserve recognition.

1. Chainflow: With Chainflow, users can effortlessly disperse CrossChain ERC-20 tokens built using Router Protocol’s CrossTalk Library from a specific address on the source chain to an unlimited number of recipients on the destination chain. Basically, it enables one-click fund transfer across multiple chains. This innovative platform leverages cutting-edge technology to simplify cross-chain transactions, making it seamless for users to transfer tokens across different blockchain networks

2. QuickRaven: QuickRaven is a platform that empowers users to make seamless CrossChain swaps. Leveraging the power of the CrossTalk Library, QuickRaven facilitates secure and efficient asset exchanges between different blockchain networks. Users can easily swap assets on existing chains and then transmit vital token details, such as token address and amount, to the destination chain in an encoded format using Router Protocol’s CrossTalk Library for transfer. Demo Link

3. ChainSwap: This innovative platform allows users to mint and seamlessly move CrossChain NFTs from one blockchain to another by leveraging Router Protocol’s CrossTalk Library. With ChainSwap, artists and collectors can explore new horizons, transcending the limitations of individual blockchain ecosystems. Demo Video.

4. Routation CrossChain NFT: Routation is a CrossChain NFT marketplace that facilitates the trading of CrossChain NFTs, created using Router Protocol’s CrossTalk Library. With Routation, users can explore and exchange NFTs across different blockchain networks, leveraging the power of interoperability. Demo Link.

Conclusion

A key stipulation of the IDAppathon was using Router Protocol’s Omni-Chain framework for stateful bridging or CrossTalk for message transfers. And the participants didn’t just impress us with their coding skills; they presented a vision for a blockchain future that addresses real-world problems and captures significant market potential.

We thank every participant, judge, and supporter for being part of this event, and we eagerly anticipate the future innovations that will spring from our blockchain community. Together, we are pioneering a new era of blockchain innovation. The IDAppathon was just the beginning.

Stay tuned for Phase 2, and keep us close at hand by following us on your preferred social media platform!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

We at Router Protocol have recently entered into a strategic partnership with Electron Labs, a renowned project for building and implementing various zk (Zero-Knowledge) solutions. As part of this collaboration, Electron’s ZK Light Client technology will be integrated into Router Protocol as an Additional Security Module (ASM) to help secure transactions on Router.

Electron uses zkSNARKs to generate valid proof of the state of a chain. These validity proofs are stored & verified by light client contracts on the destination chain. With the addition of Electron’s ZK Light Client technology-based ASM on the Router — the transactions will get verified by the Router chain and Electron ASM as well; the transactions will only go through when there is a consensus between both Router’s security and Electron’s security. This added security layer is valuable for high-value transactions like governance-based deployments.

The Router chain, operating as a PoS network and utilising Tendermint, boasts a solid security framework as its foundation. Nonetheless, at Router Protocol, we believe that applications making use of our infrastructure should have the freedom to enhance their existing security model according to their specific needs. The ASM will introduce an additional security layer to the already impressive Router transactions to enable this flexibility for the applications. On that note, let’s understand more about ASM and how it will benefit the dApps getting built on the Router chain.

ASM, a necessity for a secure cross-chain infrastructure -

In the growing realm of blockchain technology and the proliferation of interoperability protocols, ASM plays a crucial role in fortifying the integrity and protection of cross-chain transactions. While we provide several modules as a starting point, developers have the freedom to incorporate their own or externally sourced implementations. These can include security measures like a waiting period akin to optimistic roll-ups, rate-limiting, or other relevant features seamlessly integrated into the dApp to provide an extra layer of protection.

Hence, this development marks a milestone in enhancing the security and reliability of our platform. Now, let’s look at this partnership closely and explore the possibilities it holds for our platform’s future.

Understanding the Partnership’s Inner Workings

1. Facilitating Development and Integration: As part of this collaboration, we will be providing the necessary technical support and information to Electron with the aim is to facilitate the development and seamless integration of the ASM module.

2. Amplifying Awareness: Recognizing the importance of creating awareness for the new ASM module, we are actively engaged in marketing efforts alongside Electron. Through channels such as Twitter and other social media platforms, we are working together to generate interest and spread the word about the benefits of the ASM module to a broader audience.

3. A Way for the Future: Our long-term vision involves exploring to make the Electron ASM module the default ZK-security module within the Router Network.

We will also provide a dedicated testing environment for Electron to conduct rigorous testing. Besides, to give developers the opportunity to explore and experiment with the module, we will include the Electron ASM module in our developer programs, including events like hackathons.

Conclusion

In conclusion, the partnership between Router Protocol and Electron Labs brings together their expertise to enhance the security and privacy of transactions within the Router ecosystem. By providing technical support, a testing environment, and inclusion in developer programs, we are working to ensure the seamless integration and adoption of the Additional Security Module (ASM) developed by Electron Labs.

About Electron Labs

Electron Labs is an interoperability protocol that uses zero-knowledge and light clients to verify transactions across blockchains in a trustless and secure manner. They are currently live between Ethereum and Near mainnet, where users can send assets through their zkBridge.

zkBridge mainnet | Website | Twitter | Telegram | Discord

Stay engaged with us by following our official social media channels. Together, we’re working towards securing cross-chain transactions. Follow us now!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

1. Getting $ROUTE and adding Router Network

2. NFT minting via Wallet Connect using Chrome Browser

GETTING $ROUTE AND ADDING ROUTER NETWORK

To begin with, we recommend you first get Router Chain’s tesnet token from our faucet and add Router Network. Let’s see how it’s done —

STEP I. Visit https://faucet.routerprotocol.com/ and paste your Metamask wallet address —

STEP II. After pasting your address, click on ‘Router Network’ and click on ‘Connect’ —

STEP III. After its connected, click on Add Network —

STEP IV. Now, click on Get Test Tokens, and you’ll receive your tokens —

If you have completed the above steps, you’ll receive 0.5 $ROUTE in your wallet and your Metamask wallet also has Router’s Test Network added.

NOTE: If you’re trying it on your mobile screens, we request you to do the above-mentioned process within your Metamask Wallet.

MINTING THE NFT Via WALLET CONNECT WITH CHROME BROWSER

Now, let’s jump on the NFT minting part, but make sure you have $ROUTE tesnet tokens and Router’s Network in your Metamask Wallet before starting this process.

STEP I. Visit https://portal-testnet.routerprotocol.com/ and select your Character Class —

STEP II. After selecting the Character Class, Attributes, and answering your Skills and Goals, come to the Minting part —

STEP III. Now, click on ‘Connect Metamask’, and you’ll see this Wallet Connect Pop-up; choose Metamask here, and after that, connect your wallet —

STEP IV. After the completion of the connection, you’ll see your wallet connected, and now finally, you click on ‘Mint’

You’ll be taken to this game of collecting the coins while your NFT is being Minted —

STEP V. Within a few seconds, your NFT will be minted, and you’ll land here —

STEP VI. Collect your coins, see what’s in the future, and get connected on our Twitter, Telegram, and Discord —

Conclusion

In conclusion, with the recent launch of Phase 1 for Router Chain’s Gamified Testnet Mandara, you have the opportunity to seamlessly mint your unique character.

Whether you’re a seasoned crypto enthusiast or a newcomer, the Gamified and Incentivised Testnet Mandara offers an immersive experience for all.

Stay tuned for Phase 2, and keep us close at hand by following us on your preferred social media platform!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

The Recent Architectural Update

To understand the new update, let’s briefly recap the Router Chain’s flow; it has three major flows — Inbound, Outbound, and CrossTalk, each with a different function call and different modules for handling their execution.

The Inbound flow handles the transmission of requests from other chains to the Router chain, whereas the Outbound flow forwards requests from the Router chain to other chains.

Router empowers applications to exert greater control over their business logic through middleware contracts positioned between the Inbound and Outbound flow. The third flow, the CrossTalk workflow, is enabled by our CrossTalk module, an easy-to-integrate smart contract library that allows developers to build cross-chain applications without any custom bridging logic.

However, during our internal testnet, we made further improvements and standardized the function parameters. We merged the Inbound, Crosstalk, and Outbound into a unified flow on the implementation side. This resulted in reduced size of the Gateway contract and much lower gas costs while interacting with it. Now, developers can simply pass their request information using a single function. The Router Chain will decode it as metadata and data information, transforming the request for the destination chain. This enhanced compatibility allows us to add support for new types of chains much more easily.

Initially, the integration of Ethermint resulted in an increased block time (from 3 seconds to 30 seconds). As part of this update, we have made changes in the Ethermint implementation to bring back the block time to under 3 seconds. To further optimize our block time, we have also tweaked our re-execution logic for pending transactions. Earlier, we used to retry all the pending transactions in a block at the end of that block itself, which used to result in higher block times. Now, we maintain the pending transactions in a separate block queue, which is executed after every X blocks (where X is a configurable parameter currently set to 300).

In addition to the aforementioned changes, we have introduced batching for the orchestrator, which has allowed for an increased TPS (transactions per second) for cross-chain requests. Now, instead of forwarding every cross-chain request from a chain as it comes, we wait for either 100 requests from that chain or Y seconds (whichever happens first), batch all the requests and then forward the batched request to the Router chain. Note that Y is a chain-specific configurable parameter currently set to 20.

About Router Protocol

Router Protocol is a pioneering cross-chain solution that enables secure and efficient communication between blockchain networks. The L1 Router Chain uses Tendermint’s BFT consensus to address interoperability challenges while enhancing security and scalability through decentralization. The Chain enables cross-chain meta transactions, stateful bridging, transaction batching, and batch atomicity, providing a modular framework for building cross-chain dApps in web3. The use cases range from cross-chain NFTs, cross-chain governance, and cross-chain stablecoins to cross-chain oracles and cross-chain marketplaces and many more

Read our Whitepaper here — https://routerprotocol.com/router-chain-whitepaper.pdf

Stay tuned for more updates, and keep us close at hand by following us on your preferred social media platform!

Website | Twitter | Telegram | Telegram announcements | Discord

In the ever-expanding world of cryptocurrencies, Bitcoin stands as the undisputed pioneer, capturing the imagination of millions and shaping the digital financial landscape. However, despite its prominent status, Bitcoin’s lack of interoperability with other blockchain protocols has raised concerns within the crypto community.

Interoperability, the ability for different systems to seamlessly communicate and work together, is crucial for unlocking the full potential of decentralized finance and fostering innovation. This limitation poses challenges for developers, users, and the broader crypto ecosystem.

In this discussion, today we will delve into the concerns that protocols face due to the lack of Bitcoin interoperability and explore the efforts that we have been putting with Rootstock to bridge this divide, paving the way for a more interconnected and vibrant future for Web3 Space.

Addressing Bitcoin’s Interoperability Gap for Seamless Asset Transfer, DeFi Growth, and Cross-Protocol Innovation

The absence of interoperability between Bitcoin and other protocols has significant implications. It restricts the frictionless transfer of assets between different blockchain networks, necessitating reliance on centralized exchanges or third-party services for exchanging Bitcoin with other cryptocurrencies. This reliance introduces counterparty risk, potential security vulnerabilities, and higher transaction costs. Additionally, the lack of Bitcoin interoperability hampers the growth of decentralized finance (DeFi) applications.

Moreover, the lack of interoperability inhibits cross-chain collaborations and composability, which are crucial for fostering innovation and enhancing user experiences. Interoperability allows protocols to interact and leverage each other’s functionalities, leading to the creation of innovative applications. However, Bitcoin’s isolated nature prevents it from participating in these cross-protocol interactions, potentially impeding innovation and restricting the growth of the broader crypto ecosystem.

Our First Step Towards Bitcoin Interoperability with Rootstock Enabling Better Accessibility, Liquidity, and Innovation

In an effort to tackle the challenge of Bitcoin interoperability, Router Protocol has taken the first step by integrating with Rootstock on its V1 environment. Rootstock is a Bitcoin sidechain that brings EVM-compatible smart contract capabilities to Bitcoin, the world’s most decentralised and secure blockchain. Besides, Rootstock utilizes merge mining, a process that leverages the cryptographic connection and security provided by Bitcoin’s hashing power. This integration allows them to combine the security of Bitcoin with the programmability of Ethereum.

Bitcoins can be seamlessly transferred into the Rootstock blockchain, where they transform into “Smart Bitcoins” represented as $RBTC. These $RBTC tokens retain the same value as their Bitcoin counterparts and can be freely circulated within the Rootstock ecosystem. Importantly, $RBTC tokens can be converted back into Bitcoins, allowing users to maintain the intrinsic value and liquidity of their Bitcoin holdings.

Through the integration with Router Protocol, we provide $USDC and $USDT transfers. This means that users can effortlessly move their tokens between Rootstock and other supported blockchains, enabling interoperability and expanding the utility of their assets.

The integration with Router Protocol not only enhances the efficiency of Bitcoin interoperability but also opens up new possibilities for decentralized applications (dApps) and DeFi protocols. Developers can now leverage the Router Protocol’s ecosystem to build innovative applications and services that harness the power of both Bitcoin and Rootstock. This collaboration paves the way for a more interconnected and vibrant Web3 space, where the benefits of Bitcoin’s proven security and Rootstock’s scalability can be combined to fuel further growth and adoption.

To explore the array of capabilities offered by the Rootstock blockchain on Router Protocol, visit our cross-chain token swap dApp, Voyager: https://app.thevoyager.io/swap

Conclusion

As the crypto community faces concerns surrounding Bitcoin’s isolation, Router Protocol has already started its journey of finding a solution. However, this is just the beginning. Router Protocol recognizes that there is much more ground to cover to make Bitcoin interoperability a reality. By continuing to explore new partnerships, cutting-edge technologies, and creative solutions, we aim to offer the full potential of decentralized finance that will benefit developers, users, and the broader Blockchain ecosystem.

Stay tuned for more updates, and keep us close at hand by following us on your preferred social media platform!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram

Now that Router’s testnet is live, we have decided to give our users a sneak peek into the power and potential of Web 3.0 interoperability with the Router’s new infrastructure. To do so, we have developed an in-house IDApp (interoperable decentralised application) called Ping Pong.

This application allows users to send an arbitrary message (Ping) from one chain to another and receive an acknowledgment in return (Pong) back to the source chain, all with the click of a button. This application serves as a proof-of-concept for Router-powered interoperable dApps and, in doing so, paves the way for a new era of seamless interoperability. Try it out and claim your free participation NFT — https: /pingpong.routerprotocol.com/

In the following sections of this article, we will explore the features and benefits of Router’s cross-chain Ping Pong, along with a step-by-step guide on how to use it.

Features and Benefits

1) User-friendly Experience: One of the key strengths of our Ping Pong application is its user-friendly interface, making it accessible to Web 3.0 users of all levels of expertise. The intuitive design and straightforward functionality ensure that users can easily navigate and utilise the IDApp without extensive technical knowledge.

2) Proof-of-Concept for Router IDApps: As an open-source application, Router’s Ping Pong showcases the potential of Router to support robust and efficient applications that can communicate and interact across multiple blockchains.

Verified Contract Links

• Mumbai

• Fuji

• Goerli

• Router Testnet

How to use Router’s Ping Pong application and claim your free NFT?

Note that the guide given below is for those with little to no experience with decentralised applications. If you have sufficient experience in using dApps, you’ll be able to navigate our Ping Pong IDApp easily.

Step 1) Go to this link. You should see the following screen:

Figure 1. Ping Pong IDApp UI

Step 2) Connect your MetaMask wallet using the button on your screen’s top right.

Step 3) Select the source and the destination chain. Currently, we support four testnets — Avalanche Fuji, Polygon Mumbai, Router testnet, and Ethereum Goerli.

Figure 2. Chains supported by Ping Pong IDApp

Important notes:

1. By default, the source chain will be set to Mumbai, and the destination chain will be set to Fuji.

2. Upon changing the source chain, you will be asked to switch the network in your MetaMask wallet.

3. Make sure you have minimal NATIVE tokens on the source chain to perform a transaction. If not, you can use the following faucets:

• Mumbai:https: /mumbaifaucet.com/ or https: /faucet.polygon.technology/

• Fuji: https: /faucet.avax.network/

• Goerli: https: /goerlifaucet.com/

• Router testnet: https: /faucet.testnet.routerchain.dev/

Step 4) Enter the message you want to send to the destination chain and click the “Send Message” button.

Figure 3. Sending a message to the destination chain

Step 5) Sign the transaction on your MetaMask wallet. Once the transaction is sent from your wallet, you should see a loader under the “Destination Chain” section.

Step 6) [Optional] You can monitor the status of your transaction by copying the transaction hash from your MetaMask wallet and pasting it into Router’s testnet explorer.

Figure 4. Searching for your transaction on Router’s explorer

By clicking on the row corresponding to your transaction hash, you can see the detailed view of your transaction, including its end-to-end lifecycle, acknowledgment timeline, voting details, and gas refund status:

Figure 5. Detailed view of your transaction

Step 7) [Optional] In the “Contract Calls” subsection of your transaction’s explorer page, you can also decode the data to verify that the cross-chain request was sent with the correct payload.

Figure 6. Contract calls in your cross-chain request

• Step 7.1) To decode the data, click on “Decode” under the “Request Payload” and enter “uint8, string” in the field that pops up.

Figure 7. Decoding the message

• Step 7.2) Click on the “Decode” button. You should now see the decoded message under the “Request Payload”:

Figure 8. Decoded message

Step 8) Once the request is marked as completed under the “Destination Timeline” subsection in the explorer, you should be able to see your message in the Ping Pong IDApp.

Figure 9. Message received on the destination chain (Fuji)

Step 9) As mentioned above, with Ping Pong, we also showcase Router’s ability to send acknowledgments back to the source chain. Therefore, you will also be able to see an acknowledgement on the Ping Pong UI once the ack request is marked as completed under the “Ack Timeline” subsection in the explorer.

Figure 10. Acknowledgement received on the source chain (Mumbai)

Step 10) A few minutes after the acknowledgment is received on the source chain, a Ping Pong NFT will be credited to your wallet on the Router chain. To check it out, click the “View on explorer” button or go to the Router testnet explorer and paste your address there.

Note: You might not see your NFT in the Explorer instantly. It will reflect in a few minutes.

Figure 11. NFT received on the Router chain

As the concept of Web 3.0 interoperability continues to gain traction, we can look forward to a future where blockchain networks seamlessly communicate and collaborate, unlocking endless possibilities for decentralised applications. With Router Protocol at the forefront of innovation in this space, we can expect to see a wide range of innovative applications leveraging its capabilities. Ping Pong is just the beginning of this exciting journey.

Keep us close at hand by following us on your preferred social media platform!

Website | Twitter | Telegram | Discord | Reddit | Youtube | Instagram