Skip to main content

Warp Routes

Warp Routes are modular cross-chain asset bridges that enable the transfer of tokens between chains using Hyperlane. Developers can use Hyperlane to permissionlessly deploy Warp Routes to move assets between chains.

They support various asset types, including:

  • ERC20 & ERC721 tokens (for EVM-compatible chains)
  • SVM-based assets (for SVM-compatible chains)
  • Native tokens (such as ETH, or other gas tokens)

You can combine Warp Routes with a Hyperlane deployment to create economic routes between any chain and others already connected through Hyperlane.

Deploy a Warp Route​

Warp Routes can be deployed between any set of chains that have Hyperlane deployments.

To deploy a Warp Route head over to the following guides:

tip

If you would like to create a Warp Route that includes a chain that Hyperlane is not currently deployed on, feel free to deploy Hyperlane yourself!

Modular Security​

Like all applications built on top of Hyperlane, Warp Routes have customizable security via Interchain Security Modules. This allows Warp Route deployers to configure and enforce custom rules and constraints that the interchain token must follow.

Warp Route Architecture​

Warp Route contracts transfer value between chains by locking collateral tokens on the origin chain (aka the collateral chain) and then minting wrapped tokens on the destination chain (the synthetic chain).

The diagram below provides a simplified outline of the process for creating your Warp Route, and the resulting asset.

Warp Route diagram/doodle

  • Each Warp Route consists of one contract deployed on every chain that the token can move between. These contracts use the Mailbox to send interchain messages to one another.

  • When a user transfers from the canonical origin chain to a non-canonical destination chain, their tokens are locked in a HypERC20Collateral contract, which sends a message to the destination chain to mint wrapped tokens.

  • When a user transfers between non-canonical chains, their wrapped tokens are burned on the origin chain, which sends a message to the destination chain to mint wrapped tokens.

  • Finally, if a user transfers from a non-canonical origin chain back to the canonical destination chain, their wrapped tokens are burned on the origin chain, which sends a message to the destination chain to release the tokens locked in theHypERC20Collateral contract.