Hyperlane Warp Routes (HWR) are Hyperlane’s implementation of token bridging, allowing for permissionless transfer of native, ERC20, and synthetic (newly deployed ERC20) assets across any chain via Hyperlane. This document provides details on all 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.) |
Please note that this document does not include ERC721 HWRs.
Implemented in HypNative.sol
, native HWRs handle the transfer of native gas tokens (e.g. ETH on Ethereum or Arbitrum, MNT on Mantle) across different chains.
msg.value
for transfer amount.msg.value
as hook payment.receive()
function.See the implementation for more details.
Implemented in HypERC20Collateral.sol
, collateral HWR enable ERC20 tokens to be locked as collateral on the source chain and then used to mint a synthetic representation on the destination chain.
See the implementation for more details.
Implemented in HypERC20.sol
, synthetic HWRs mint new tokens on the destination chain that represent the original tokens from the source chain. The original tokens are not transferred but remain locked.
See the implementation for more details.
All HWRs extend the TokenRouter
contract, which provides the core functionality for HWR token transfers.
Message Structure: Uses TokenMessage library for encoding and decoding token transfer messages.
Transfer Initiation: transferRemote
function initiates cross-chain transfers.
Message Handling: _handle
function processes incoming transfer messages.
Abstract Methods:
_transferFromSender
: Implemented by all HWRs to handle token collection._transferTo
: Implemented by all HWRs to handle token distribution.This standardized format ensures consistent handling across different HWR implementations while allowing for extensibility through metadata.
See the implementation for more details.
Implemented in FastTokenRouter.sol
, this router extends TokenRouter and provides faster token transfers through a liquidity provider mechanism.
fastFee
to incentivize liquidity providers.fastTransferId
for unique transfer identification.See the implementation for more details.
For setup examples & use cases, check out Hyperlane Warp Routes: Example Usage.
Hyperlane Warp Routes (HWR) are Hyperlane’s implementation of token bridging, allowing for permissionless transfer of native, ERC20, and synthetic (newly deployed ERC20) assets across any chain via Hyperlane. This document provides details on all 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.) |
Please note that this document does not include ERC721 HWRs.
Implemented in HypNative.sol
, native HWRs handle the transfer of native gas tokens (e.g. ETH on Ethereum or Arbitrum, MNT on Mantle) across different chains.
msg.value
for transfer amount.msg.value
as hook payment.receive()
function.See the implementation for more details.
Implemented in HypERC20Collateral.sol
, collateral HWR enable ERC20 tokens to be locked as collateral on the source chain and then used to mint a synthetic representation on the destination chain.
See the implementation for more details.
Implemented in HypERC20.sol
, synthetic HWRs mint new tokens on the destination chain that represent the original tokens from the source chain. The original tokens are not transferred but remain locked.
See the implementation for more details.
All HWRs extend the TokenRouter
contract, which provides the core functionality for HWR token transfers.
Message Structure: Uses TokenMessage library for encoding and decoding token transfer messages.
Transfer Initiation: transferRemote
function initiates cross-chain transfers.
Message Handling: _handle
function processes incoming transfer messages.
Abstract Methods:
_transferFromSender
: Implemented by all HWRs to handle token collection._transferTo
: Implemented by all HWRs to handle token distribution.This standardized format ensures consistent handling across different HWR implementations while allowing for extensibility through metadata.
See the implementation for more details.
Implemented in FastTokenRouter.sol
, this router extends TokenRouter and provides faster token transfers through a liquidity provider mechanism.
fastFee
to incentivize liquidity providers.fastTransferId
for unique transfer identification.See the implementation for more details.
For setup examples & use cases, check out Hyperlane Warp Routes: Example Usage.