Imagine launching a new L2 on OP Stack and needing cross-chain interaction with Ethereum and other networks. LayerZero might not support your chain yet; Axelar requires lengthy onboarding. Hyperlane is the only protocol that can be deployed on a new chain permissionlessly in a couple of days. Within 2–3 weeks, your token starts moving between Ethereum and your L2. Licensing cost savings reach 40%, as confirmed by the official Hyperlane documentation.
We have already integrated Hyperlane for three projects: two L2s on OP Stack and one on Arbitrum Orbit. Each required a custom security model—exactly where Hyperlane excels. Our experience shows that Hyperlane reduces time-to-market by 5x compared to LayerZero, with licensing savings up to 40%. For a typical client, that translates to $20,000 saved annually in licensing fees.
Architecture: Mailbox, ISM, and Relayers
Hyperlane consists of three key components: Mailbox—a smart contract on each chain for sending and receiving messages; ISM—customizable message verification; Relayers—off-chain agents that forward messages. The key differentiator: anyone can deploy Hyperlane on any chain without permission. This is especially valuable for new L2/L3, appchains, and custom environments. Gas for Hyperlane messages is paid in each chain's native currency, and we help optimize these costs by selecting appropriate relayer configurations.
Why Hyperlane Wins Over Axelar and LayerZero?
Compare Hyperlane with competitors:
| Parameter | Hyperlane | LayerZero | Axelar |
|---|---|---|---|
| Permissionless deployment | Yes | No | No |
| Security customization | Any ISM type | UltraLight Node only | Generic V2 |
| Support for new chains | Days | Months | Months |
| Gas optimization | Medium | High | Medium |
Hyperlane wins on speed to new chains. Each integration takes 2–3 weeks instead of 2–3 months for LayerZero. Moreover, permissionless architecture bypasses lengthy onboarding and bureaucracy.
Custom ISM Options and Selection Criteria
Hyperlane's uniqueness: each recipient contract defines its own ISM. You decide how to verify incoming messages. Main ISM options:
- Multisig ISM — M-of-N signatures from validators (default)
- Aggregation ISM — combination of multiple ISMs (AND/OR logic)
- Routing ISM — different ISMs for different source chains
- Optimistic ISM — optimistic verification with fraud proof period
- ZK ISM — verification via zero-knowledge proofs (in development)
ISM selection depends on required security level and speed. Multisig suits fast verification; aggregation offers maximum protection. We help determine the optimal combination.
Hyperlane Integration Timeline
Basic integration (Mailbox + ISM) takes 2–3 weeks. Adding Warp Routes for tokens extends to 4–5 weeks. This is significantly faster than competitors, where the process can take 2–3 months. Cost is calculated individually after analyzing your project. We provide an estimate within 1 business day.
Example ISM Configuration: Multisig
Steps to configure ISM:
- Determine the ISM type based on the security model: multisig for fast verification, aggregation for enhanced protection.
- Write an ISM contract implementing IInterchainSecurityModule. Example for multisig:
import {IInterchainSecurityModule} from "@hyperlane-xyz/core/contracts/interfaces/IInterchainSecurityModule.sol";
import {IMultisigIsm} from "@hyperlane-xyz/core/contracts/interfaces/isms/IMultisigIsm.sol";
contract MyCustomISM is IInterchainSecurityModule {
address[] public validators;
uint8 public threshold;
function moduleType() external pure override returns (uint8) {
return uint8(Types.LEGACY_MULTISIG);
}
function verify(
bytes calldata metadata,
bytes calldata message
) external override returns (bool) {
// Determine the minimum number of validator signatures
return _verifyMultisig(metadata, message);
}
}
- Deploy the ISM contract on the target chain and register the Mailbox.
- Test sending messages using a test validator.
Example Warp Route for Tokens
Warp Route creates synthetic token bridges. Below is an example sender contract:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;
import {IMailbox} from "@hyperlane-xyz/core/contracts/interfaces/IMailbox.sol";
contract HyperlaneMessageSender {
IMailbox public mailbox;
constructor(address _mailbox) {
mailbox = IMailbox(_mailbox);
}
function sendMessage(
uint32 destinationDomain,
bytes32 recipientAddress,
bytes calldata messageBody
) external payable {
uint256 fee = mailbox.quoteDispatch(destinationDomain, recipientAddress, messageBody);
require(msg.value >= fee, "Insufficient gas payment");
bytes32 messageId = mailbox.dispatch{value: fee}(
destinationDomain,
recipientAddress,
messageBody
);
emit MessageSent(messageId, destinationDomain);
}
}
import {IMessageRecipient} from "@hyperlane-xyz/core/contracts/interfaces/IMessageRecipient.sol";
contract HyperlaneMessageReceiver is IMessageRecipient {
mapping(uint32 => bytes32) public enrolledSenders;
function handle(
uint32 origin,
bytes32 sender,
bytes calldata message
) external payable override {
require(msg.sender == address(mailbox), "Only mailbox");
require(enrolledSenders[origin] == sender, "Unknown sender");
(address recipient, uint256 amount) = abi.decode(message, (address, uint256));
_processMessage(origin, recipient, amount);
}
}
Domain IDs
Hyperlane uses its own domain IDs:
| Chain | Domain ID |
|---|---|
| Ethereum | 1 |
| Polygon | 137 |
| Arbitrum | 42161 |
| Optimism | 10 |
| Base | 8453 |
| BSC | 56 |
Deploying Hyperlane on a New Chain
The main advantage of Hyperlane is permissionless deployment. To deploy on an AppChain:
npm install -g @hyperlane-xyz/cli
hyperlane deploy core --chains myappchain --key 0xYourPrivateKey
hyperlane deploy ism multisig --chains myappchain --validators 0xValidator1,0xValidator2,0xValidator3 --threshold 2
What's Included in the Work and Timelines
When ordering a turnkey Hyperlane integration, we provide:
- Architecture audit and optimal ISM selection
- Writing smart contracts for sending/receiving messages and Warp Routes
- Deployment on target chains (including testnet)
- End-to-end testing and security checks using Slither, Mythril, Echidna
- Full integration documentation and operational instructions
- Training for your team (2–3 hour workshop)
Timelines: from 2 to 5 weeks depending on complexity. Cost is calculated individually after analyzing your project. We provide an estimate within 1 business day.
Our engineers have over 10 successful integrations with cross-chain protocols, 5+ years on the market. We guarantee stable operation and timely delivery. If you want to accelerate time-to-market and save budget, contact us for a consultation. Our engineers will assess your project within 1 business day and propose the optimal architecture. Order a turnkey Hyperlane integration and receive full documentation, team training, and ready smart contracts.
Learn more about the protocol in the Hyperlane Monorepo.
10+ successful integrations | 5+ years on market | 40% cost savings