Warp Routes are permissionless Hyperlane-powered contracts that enable secure and seamless asset transfers—such as ERC20 tokens, ERC721 NFTs, and native tokens—across blockchains by locking tokens on the origin chain and minting wrapped equivalents on the destination chain. They integrate with Hyperlane’s Interchain Security Modules (ISMs) for customizable security configurations, allowing developers to enforce specific rules. Warp Routes create economic “trade routes” between chains, handling the processes of locking, burning, minting, and releasing tokens, making them vital for cross-chain interoperability and liquidity in decentralized ecosystems.

Wrap Routes Framework

The structure of Warp Routes is composed of a distributed system of smart contracts deployed on each participating blockchain, which leverage Hyperlane’s Mailbox interchain messaging protocol to facilitate asset transfers. On the origin chain, the HypERC20Collateral contract locks tokens as collateral and dispatches interchain messages to destination chains, where the corresponding HypERC20Synthetic contracts mint wrapped tokens representing the locked assets. Transfers between non-canonical chains involve burning wrapped tokens on the source chain and minting equivalent tokens on the target chain, while transfers back to the canonical chain trigger the release of the locked collateral. This architecture is highly modular, enabling deployers to integrate Interchain Security Modules (ISMs) to enforce security policies such as message validation thresholds or trusted relayer configurations, ensuring secure and efficient cross-chain interoperability.

This guide will walk you through deploying a DEGEN token contract on the Base Mainnet as a HypERC20 Collateral and minting a HypERC20 Synthetic on Zora. In practice, synthetics can be created on any number of Hyperlane-connected chains. Lets dive into it:

Setting up the server:

sudo apt update

sudo apt install -y curl iptables build-essential git wget jq make gcc nano tmux htop nvme-cli pkg-config libssl-dev libleveldb-dev libgmp3-dev tar clang bsdmainutils ncdu unzip llvm libudev-dev protobuf-compiler

Installing Hyperlane CLI:

npm install -g @hyperlane-xyz/cli

Create Warp Configuration:

hyperlane warp init

Then we enter wallet address and Choose “Mainnet” or “Testnet” to configure

There are several Mainnet and Testnet networks available in Hyperlane CLI; for this setup, we will choose Base and Zora. To select the chains, press the TAB or space bar button and press Enter.

Then we answer the following options as follow:

Is this chain selection correct: Press “y”

Use an existing Proxy Admin contract for the warp route deployment on chain "base"? : Press “n”

Do you want to use a trusted ISM for warp route?: Press “y”

Select base's token type: Select “Collateral”

Enter the existing token address on chain base: Enter “0x4ed4e862860bed51a9570b96d89af5e1b0efefed”

Use an existing Proxy Admin contract for the warp route deployment on chain "zoramainnet"?: “n”

Do you want to use a trusted ISM for warp route?: “y“

Select zoramainnet's token type: “Synthetic“

You should see a confirmation of success. The Warp configuration was a success!

Deploying the Wrap Route:

hyperlane warp deploy

when prompted to Please enter private key or use the HYP_KEY environment variable: Enter your EVM Private key “0x……………“

Do you want to use an API key to verify on this (base) chain's block explorer: “n'“

Do you want to use an API key to verify on this (zoramainnet) chain's block explorer: “n“Is this deployment plan correct? If you followed everything correctly above, Press “y'“

Upon successful deployment, you should see the following:

Now that the contract is deployed, we can use it to test the bridges.

Go to Superbridge Interface:

https://hyperlane.superbridge.app/

Click on the gear icon, then select “Customize.

Let’s paste our warp deployment configuration from the CLI into the custom route field.

Each Warp configuration generates a unique link, so a new link is created every time, and multiple configs cannot be stored under a single link. Be sure to bookmark and label your links if you intend to share them.

Now, let’s use the UI to transfer DEGEN tokens from Base to Zora!

I purchased some DEGEN tokens from a dex on Base Network

Click on “Review Bridge” and Bridge Away. Expansion

we can also bridge via the HyperlaneCLI

To avoid having to repeatedly enter the “Owner Address” and “Private Key,” let’s run the following command:

export HYP_KEY=0xPrivateKey

Next, let’s enter the following:

hyperlane warp send --relay --warp $HOME/.hyperlane/deployments/warp_routes/DEGEN/base-zoramainnet-config.yaml --amount 1000/DEGEN - Wrap token

/base-zoramainnet - Origin bridge and destination respectively

-amount - Token amount (18 decimal for DEGEN)

The bridge transaction was successful

You can find and track your bridge transaction on the Hyperlane Explorer -  https://explorer.hyperlane.xyz/

Check out these link for more information on warp routes:

https://medium.com/hyperlane/how-to-launch-a-token-bridge-with-hyperlane-warp-routes-befaf91217b5

Also checkout Hyperlane Official Twitter and Discord to stay upto date with the latest updates

Twitter:

https://x.com/hyperlane

Discord:

https://discord.gg/hyperlane