Notes
- This is a messaging protocol, not a direct token bridge. Token bridging uses Warp Routes built on top of Hyperlane
- Uses domain IDs (uint32), NOT EVM chain IDs. Common domains: Ethereum=1, Arbitrum=42161, Optimism=10 (may differ from EVM chain IDs)
- Permissionless: anyone can deploy Hyperlane to a new chain without governance approval
- Modular security via ISMs (Interchain Security Modules) — apps choose their own security model
- Use
quoteDispatch()to estimate fees before sending delivered()to check if a message has already been processed on the destination- Finality: depends on ISM configuration, typically 1-5 minutes
- On Arc (5042) interchain gas is paid in native USDC at 18 decimals, from the same balance as the USDC ERC-20
0x3600…0000. A transfer of the whole USDC balance cannot also pay its gas. Hyperlane’s CCTP-backed USDC warp route on Arc is0x16BF93e259ee7f7074453a2948379C35C6851b71(itsquoteGasPayment(8453)was about 0.054 USDC on 2026-09-28)
Its names in a program
On Ethereum,Hyperlane is a namespace: its contracts need no import.
Deployments
ABI
HyperlaneMailboxABI
import HyperlaneMailboxABI from "./protocols/hyperlane/HyperlaneMailboxABI.json"; Speaks for: mailbox.
dispatch(uint32 _destinationDomain, bytes32 _recipientAddress, bytes _messageBody) payable returns (bytes32)quoteDispatch(uint32 _destinationDomain, bytes32 _recipientAddress, bytes _messageBody) view returns (uint256)process(bytes _metadata, bytes _message) payabledelivered(bytes32 _id) view returns (bool)
Next steps
- Protocols: the other protocols, by what they do.
- Protocols and tokens: calling a contract by its namespace, or through its ABI.
- Glossary: the words these pages use, in plain terms.
