Hyperlane Warp Routes (HWR) are modular cross-chain asset bridges that enable the transfer of tokens between chains using Hyperlane. Developers can use Hyperlane to permissionlessly deploy HWRs to move assets between chains.
They support various asset types, including:
You can combine HWR with a Hyperlane deployment to create economic routes between any chain and others already connected through Hyperlane.
Like all applications built on top of Hyperlane, HWRs have customizable security via Interchain Security Modules.
The deployer of a HWR can specify the ISMs that are used to verify interchain transfer messages. This means that each HWR may have a unique security configuration. Users transferring interchain tokens should understand the trust assumptions of a Route before using it.
Similarly, Warp frontends should manually curate their HWRs to avoid supporting insecure ones. See the Warp UI deployment docs details.
HWRs let deployers choose how tokens are transferred between chains. Depending on the type of HWR, contracts will lock tokens, mint wrapped tokens, burn wrapped tokens, or release original tokens.
For example:
Each HWR requires a contract deployed on every chain its on that acts as an entry/exists point. These contracts use the Mailbox to send interchain messages to one another.
This table gives a high-level overview of HWR types. For detailed explanations, see: Hyperlane Warp Route Types.
Hyperlane Warp Route Type | Description |
---|---|
Native Token HWR | Enables direct transfers of native gas tokens (e.g., ETH) across chains without wrapping. |
Collateral-Backed ERC20 | Locks ERC20 tokens as collateral on the source chain for cross-chain transfers. |
Synthetic ERC20 | Mints new ERC20 tokens on the destination chain to represent the original tokens. |
Hyperlane Warp Routes 2.0 | Allows liquidity to be sourced from multiple collateral tokens. |
Specialized HWR | Adds advanced features or integrates with specific use cases (e.g., vaults, fiat-backed tokens.) |
Let’s walk through a Collateral to Synthetic HWR using the lock-and-mint model to transfer ERC20 tokens between two chains:
In the diagram below, the ISM is a Multisig ISM, which uses a set of validators to approve messages. (Note: Not all ISMs require validators, this depends on the chosen security model.)
Here’s a simplified view of the flow:
HWRs can be deployed between any set of chains that have Hyperlane deployments.
To deploy a HWR, head over to the following guides:
If you would like to create a HWR that includes a chain that Hyperlane is not currently deployed on, feel free to deploy Hyperlane yourself!
Hyperlane Warp Routes (HWR) are modular cross-chain asset bridges that enable the transfer of tokens between chains using Hyperlane. Developers can use Hyperlane to permissionlessly deploy HWRs to move assets between chains.
They support various asset types, including:
You can combine HWR with a Hyperlane deployment to create economic routes between any chain and others already connected through Hyperlane.
Like all applications built on top of Hyperlane, HWRs have customizable security via Interchain Security Modules.
The deployer of a HWR can specify the ISMs that are used to verify interchain transfer messages. This means that each HWR may have a unique security configuration. Users transferring interchain tokens should understand the trust assumptions of a Route before using it.
Similarly, Warp frontends should manually curate their HWRs to avoid supporting insecure ones. See the Warp UI deployment docs details.
HWRs let deployers choose how tokens are transferred between chains. Depending on the type of HWR, contracts will lock tokens, mint wrapped tokens, burn wrapped tokens, or release original tokens.
For example:
Each HWR requires a contract deployed on every chain its on that acts as an entry/exists point. These contracts use the Mailbox to send interchain messages to one another.
This table gives a high-level overview of HWR types. For detailed explanations, see: Hyperlane Warp Route Types.
Hyperlane Warp Route Type | Description |
---|---|
Native Token HWR | Enables direct transfers of native gas tokens (e.g., ETH) across chains without wrapping. |
Collateral-Backed ERC20 | Locks ERC20 tokens as collateral on the source chain for cross-chain transfers. |
Synthetic ERC20 | Mints new ERC20 tokens on the destination chain to represent the original tokens. |
Hyperlane Warp Routes 2.0 | Allows liquidity to be sourced from multiple collateral tokens. |
Specialized HWR | Adds advanced features or integrates with specific use cases (e.g., vaults, fiat-backed tokens.) |
Let’s walk through a Collateral to Synthetic HWR using the lock-and-mint model to transfer ERC20 tokens between two chains:
In the diagram below, the ISM is a Multisig ISM, which uses a set of validators to approve messages. (Note: Not all ISMs require validators, this depends on the chosen security model.)
Here’s a simplified view of the flow:
HWRs can be deployed between any set of chains that have Hyperlane deployments.
To deploy a HWR, head over to the following guides:
If you would like to create a HWR that includes a chain that Hyperlane is not currently deployed on, feel free to deploy Hyperlane yourself!