ROUTE token migration

As part of our mainnet launch — we are migrating to the new ROUTE token, which will be the native token of Router Chain. Users holding old ROUTE tokens will have to migrate their tokens and will be able to stake their new ROUTE tokens.

In February 2024. Router Protocol concluded a community vote on the $ROUTE 2.0 tokenomics, marking a significant milestone as Router Protocol transitions from a bridge to a fully decentralized layer-1 blockchain.

The migration will be supported for at least 6 months from now, and if there are still many people pending after 6 months, we will support it for an additional 6 months.

The Migration, Bridging, and Staking Journey

The first part covers migration, in which users convert their old tokens to new tokens. The second part covers bridging, where users can bridge their new tokens to the Router Chain ( or Router Mainnet). The third part is about delegation, in which users can delegate their tokens to validators and earn rewards.

Migration

Users can swap their old ROUTE tokens on Polygon and Ethereum to new ones on Polygon and Ethereum. The flows supported in this are uni-directional flows (you can only move from old to new ROUTE. Once you swap into new ROUTE tokens, there is no going back). This supports two flows:

Once users finish their migration (between 2–5 minutes), they will get new ROUTE tokens. The new ROUTE tokens obtained after migration are omni-chain new ROUTE tokens. These tokens can be interchanged easily into new tokens on Polygon, Ethereum, and Router Chain as they are fungible 1:1 between Polygon, Ethereum, and Router Chain.

ROUTE new contract address：

• https://etherscan.io/token/0x60F67E1015b3f069DD4358a78c38f83fE3a667A9
• https://polygonscan.com/token/0x93890f346C5D02C3863a06657bc72555dC72c527
• https://routerscan.io

ROUTE old contract address：

• https://etherscan.io/token/0x16eccfdbb4ee1a85a33f3a9b21175cd7ae753db4
• https://polygonscan.com/token/0x16eccfdbb4ee1a85a33f3a9b21175cd7ae753db4

official announcement：

• https://x.com/routerprotocol/status/1816045510429413525