Hello, everyone! Our team at Router Protocol recently submitted a rapid grant proposal to the grant committee, and we are thrilled to announce that after much deliberation they have approved our grant request. Before moving forward, we feel it is necessary to introduce our project to the Terra community. We would like to engage with the Terra community members and get their valuable feedback.
Router’s cross-chain bridge on Terra
We, at Router, are committed to building a bridging infrastructure that facilitates interoperability between blockchains. Such an infrastructure will a) allow for a range of use cases that leverage and extend the composability of DeFi across various blockchains, b) promote liquidity migration and developer efforts towards various emerging chains and solutions and c) eventually lead to a thriving multi-chain ecosystem that will onboard the next wave of crypto users.
The crypto industry was built on a fundamental premise; the fragmentation and limitations endemic to traditional finance needed to be replaced with a better, more robust system with user needs at the heart of it. Unfortunately, even the crypto market is littered with fragmented liquidity pools and creating the infrastructure that bridges the gap between them is becoming increasingly important. With over 5,000 different cryptocurrencies on the market encapsulating trillions of dollars in value, there has never been a more pressing need for porting liquidity across them. As more institutional investors join the crypto space, the need for better efficiency and flexibility increases almost exponentially. At Router, we believe that the crypto industry does not have to suffer from the fragmentation seen in traditional finance.
What is your team’s proposed solution to the problem listed above, and how does Terra come into the picture?
To combat the problem of liquidity fragmentation, Router is building a host of cross-chain infra primitives that will allow seamless flow of liquidity across chains. Aside from connecting blockchains and enabling a free flow of information, Router will also enable token mapping in a decentralized environment.
With over $3B in liquidity and a large user base, Terra is one of the most popular blockchains in DeFi. To realize our goal of becoming a liquidity super-mesh, we need to deploy Router bridges on all the major chains, Terra being one of them.
Router’s XCLP testnet is live here. It currently supports cross-chain transfers and cross-chain swaps between Kovan (Ethereum testnet) and Polygon testnet, and other chains will follow soon. For tokens with liquidity reserves on both sides of the bridge, transfers/swaps are almost instantaneous and require very low fees. For some tokens that do not have sufficient native ‘on-bridge’ liquidity on one or both chains, transfers/swaps might take a bit longer and cost a little more. Here the costs are primarily driven by the operations of the underlying AMM.
We also have a internal mainnet which is undergoing a security audit from Halborn. We have already completed a security audit from Certik, details of which can be found here. Since the security of cross-chain projects has been under scrutiny as a result of recent hacks, we thought it was prudent to get a second audit to cover all our bases.
- Bridge Contracts (ParaRouters): Every chain supported by Router Protocol will have a bridge contract known as ParaRouter deployed on it. The ParaRouter is able to lock a stablecoin and broadcast an event that can be picked up by the event listener associated with the ParaRouter.
- Event Handlers: ParaRouter uses event handlers to handle different operations based on the calldata passed by the UI (ERC20 token transfer, ERC721 token transfer, arbitrary message transfers, etc.).
- Router Nodes: XCLP maintains a set of router nodes that listen for events on the source chain, generate proposals for those events, and submit signed proposals on the destination chain as a vote. For a transfer to be accepted and sent across the bridge, it must receive enough votes to exceed a predetermined threshold.
When users submit their asset on the source chain, they are converted to stablecoins and locked in the source chain’s ParaRouter. The conversion to stablecoins takes place using an aggregator contract that fulfills the swap using the DEX that offers the best price. If the user-submitted asset is a stablecoin itself, the asset is directly locked in the bridge contract. Following this, the ParaRouter reserve on the source chain emits an event to be received by the listener interface attached to the router nodes. Upon receiving the event, listener parses the event into a general bridge message and relays it to the router interface. The router interface forwards this message to the writer interface, which converts the message to a valid proposal and submits it on the target blockchain. Once a proposal is created on the destination chain, other router nodes sign the proposal. Once the voting threshold is achieved, an executeProposal call is initiated, which releases the funds from the destination chain’s ParaRouter reserve and credits it to the user’s wallet. In case the user-requested asset is not available on the destination chain’s ParaRouter, the ParaRouter uses aggregator contracts to convert the stablecoins to the user-requested asset on the target chain.
- Liquidity Mining
To ensure high throughput while maintaining protocol security, Router Protocol will initially operate under a trusted federation model, i.e. the validation mechanism will only be partially decentralized. However, in the spirit of DeFi, Router will eventually achieve full decentralization and trustlessness in a phased manner:
Phase 1 (Current version) - The validators are selected via a Proof-of-Authority mechanism wherein they are required to stake $ROUTE tokens (Router Protocol’s native currency). To curb any kind of malicious behaviour, validators are required to stake $ROUTE in value equal to the protocol’s AUM. Any validator having excessive downtime or engaging in any kind of malicious activity will be penalized by having a portion of their staked $ROUTE slashed.
Phase 2 (4 - 6 months) - Validator selection will move to a Delegated Proof-of-Stake (DPoS) mechanism. More validators will be added to the network and a Multi Party Computation (MPC) system will be set up to validate transactions.
Phase 3 (8 - 12 months) - Router will build and host a dedicated chain (tendermint consensus) to host the aggregator infrastructure. Consensus for all cross-chain transactions will be achieved on this chain.
First, a custom bridge contract will be coded for the Terra chain. Since Terra is not EVM compatible, we will not be refactoring our code from the Ethereum bridge contract. We will have to custom-code the contract from the ground up. After rigorous testing and audits, we will launch a Router bridge between Ethereum, Polygon and Terra. Router bridges on Solana, Avalanche and Arbitrum are also in the pipeline. After the launch of the bridge, we will be able to allow for seamless communication between Terra and other blockchains.
- Router’s dedicated liquidity reservoir, Dfyn AMM has a large community of users on Polygon. Even without a direct bridge between Polygon and Terra, we had an ATH of $80 million in UST liquidity. With a direct bridge between Polygon and Terra, much more liquidity can flow between these two chains.
- One immediate application of Router Protocol is its ability to enable cross-chain swaps in addition to cross-chain transfers. Basically, users will be able to swap any token on chain A to any other token on chain B.
- Router will enable token mapping across all chains that are a part of its network. This will enable more and more projects to map their tokens on Terra and start their operations there.
- Router will eventually launch its SDK to allow other DApps to plug into its infrastructure:
- DEXes will be able to build on top of Router to allow cross-chain swaps for users.
- Asset management applications will be able to use Router Protocol to power the bridge on their UI.
- Wallet applications will be able to use Router to enable the direct transfer of funds to other blockchains from the wallet itself.
MIT, Deloitte, Moody’s, Schlumberger; In Crypto since 2014, built and ran Asia’s earliest crypto fund, returned 4x; Built Fordex - the world’s first stablecoin DEX; Qume, an institutional grade crypto exchange; Launched Asia’s first crypto-index token
Full-stack Developer and Technical Architect building in crypto and blockchain since 2016; Built a crypto-index (108token) as well as Fordex - the world’s first stablecoin DEX
Researcher and Architect building in crypto since 2014. Theorized the concept of DEX in FC2014. Proposed and developed a blockchain scaling solution based on capacity.
Email: [email protected]
Google Scholar: Harsh Patel
Head of Strategy at Bitpolo, leading Indian crypto exchange; Veteran trader and advisor across asset classes spanning over 15 years. Energy trader at Futures first; Managed crypto fund, generating 4x returns; Head of Ops & Market Research at Tradelab
Full-stack Developer and Technical Architect building in crypto /blockchain since 2016; Built 108token (Asia’s first crypto index token) and Fordex, the world’s first stablecoin DEX with 0x grant; Worked on matching engine for crypto derivatives platform
Engineer/Growth hacker/Product Manager; Technical Advisor @ Umbrella Network; Software Engineer @ Ola; Journalist @ Cryptoslate & @ 8BTC
Surojit Chatterjee is a former Head of Product for the Indian e-commerce giant Flipkart and served as VP of Product at Google until the beginning of 2020. Last year, Chatterjee joined Coinbase, where he serves as the Chief Product Officer. While his investment in Router is in a personal capacity, it clearly resonates with his professed goal of using Coinbase as an enabler to deliver economic freedom to everyone.
Gokul Rajaram is often referred to as the Godfather of Google AdSense, and has headed product development at companies such as Facebook and Square subsequently. In addition to his role on the board of Coinbase, Rajaram is also on the board of consumer-focused unicorn Pinterest.
In bold → Milestones
T0 → the start of the development
|Task||Deliverable||Team member(s) involved||Estimated Completion Time|
|1. Planning the architecture of our bride contract to suit the Terra ecosystem. The goal of this step is to simplify the development process.||A clear architecture depicting the business logic of the smart contract and product specs for mapping out a path for developers to follow during the coding process.||Shubham Singh and Harsh Patel||T0 + 5|
|2. The bridge contract will be coded from the ground up since Terra is non-EVM compatible. The contracts will need to be coded in Rust instead of Solidity.||Well compiled bridge contract compatible with Terra testnet.||Shubham Singh and Harsh Patel||T0 + 21|
|3. Adding test cases to the ParaRouter contract, performing rigorous manual testing and deploying the ParaRouter contract on Terra testnet.||Working smart contract free from major bugs and issues deployed on Terra testnet.||Shubham Singh and Harsh Patel||T0 + 28|
|4. Router node (the bridge that enables the communication between different ParaRouters) config will be updated to enable transfers between Terra and other blockchains.||Support for cross-chain transfers between Terra testnet and other testnets.||Harsh Patel, Siva Ganesh (Senior Blockchain Engineer at Router Protocol)||T0 + 35|
|5. Integrating the bridge contract with the testnet UI.||Updated UI for the community to test cross-chain transfers between Kovan, Polygon testnet, OKExChain testnet and Terra testnet.||Mayank Rawat (Front-end Engineer at Router Protocol)||T0 + 42|
|6. Integrating the bridge contract with TerraSwap to add the swap functionality to the contract.||Updated testnet bridge contracts supporting swaps between Kovan, Polygon testnet, OKExChain testnet and Terra testnet.||Shubham Singh and Harsh Patel||T0 + 49|
|7. Building Router analytics.||An analytics engine to monitor on-chain stats.||Siva Ganesh||T0 + 49|
|8. Recording all the transactions while testing on test-net, analyzing results of all transactions with actual business logic of smart contracts.||Stats detailing the reception of the testnet by the community, points to address, etc.||Siva Ganesh||T0 + 56|
|9. Unit testing and smart contract audit by a third party followed by bug fixes and code optimizations.||Optimized smart contracts supporting cross-chain transfers and swaps, ready for deployment on Terra mainnet.||Harsh Patel and Siva Ganesh||T0 + 63|
|10. Deployment of bridge contract on mainnet.||Router bridge contract deployed on Terra mainnet, supporting cross-chain swaps and transfers between Terra and other blockchains.||Harsh Patel and Siva Ganesh||T0 + 63|
Specification of the software or deliverable (will be used to confirm milestones have been reached), and the cost involved in each milestone
Deliverable from Milestone 1: Terra-compatible ParaRouter contract
The first phase of the project will involve coding Router’s ParaRouter contract in Rust. This contract will be responsible for interacting with the bridge (Central Router) that connects multiple blockchains.
ETA: 3 week from the start of development
Full Time Equivalent (FTE): 0.8
Deliverable from Milestone 2: Router’s bridge supporting Terra testnet
The second phase of the project will involve deploying our ParaRouter contract on Terra testnet that will allow transfers between Kovan, Polygon testnet, OKExChain testnet and Terra testnet.
ETA: 3 week from the attainment of the first milestone
Full Time Equivalent (FTE): 0.6
Deliverable from Milestone 3: Swap functionality in the Router testnet
This phase will involve the integration of TerraSwap on Terra with Router’s bridge contract. At the end of this phase, users will be able to swap assets on Polygon testnet and Kovan directly from Terra’s testnet.
ETA: 1 week from the attainment of the second milestone
Full Time Equivalent (FTE): 0.2
Deliverable from Milestone 4: Router’s cross-chain bridge on Terra mainnet
The fourth phase of the project will involve testing the ParaRouter contract, getting it audited and then finally deploying it on Terra mainnet. The deployment of the Router bridge on Terra mainnet will enable the movement of liquidity from Ethereum and Polygon to Terra.
ETA: 2 weeks from the attainment of the third milestone
Full Time Equivalent (FTE): 0.5
Estimated Cost: $42,000 + Audit Costs
Estimated Duration: 8-10 weeks
To facilitate transparency, our team will provide brief progress reports for the work done at the completion of each milestone. To ensure a smooth collaborative experience, a telegram/discord channel will be set up for integrations and project discussion.
- Router Website: https://routerprotocol.com/
- Router Testnet: https://testnet.routerprotocol.com/
- Router Protocol Litepaper: https://routerprotocol.com/assets/docs/Router-Litepaper.pdf
- Router GitHub: https://github.com/router-protocol (Currently not open source, but will be made so within a few months of the launc)
- Certik Audit Report: https://www.certik.org/projects/router
- Router Protocol Medium: https://routerprotocol.medium.com/
- Router Protocol Twitter: https://twitter.com/routerprotocol
- Router Protocol Telegram Channel: https://t.me/routerprotocol