hyperlane

Implement Hyperlane cross-chain messaging, Warp Routes, and custom Interchain Security Modules.

1|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/naruto11eth/cryptoskills --skill hyperlane-naruto11eth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyperlane
Source: https://github.com/naruto11eth/cryptoskills/tree/main/skills/hyperlane
Command: npx skills add https://github.com/naruto11eth/cryptoskills --skill hyperlane-naruto11eth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents frequently produce incorrect Hyperlane integrations — confusing Warp Routes with generic bridges, mishandling bytes32 address padding, skipping interchain gas payment, or misunderstanding ISM security models. This Skill provides verified contract addresses, correct V3 SDK patterns, and security configuration guidance so cross-chain messaging code works on the first attempt. ## Core Features & Use Cases - Cross-Chain Messaging: Dispatch and receive messages via the Mailbox contract with correct quoteDispatch() fee estimation, bytes32 address conversion, and IMessageRecipient.handle() implementation. - Warp Route Token Bridging: Deploy collateral/synthetic Warp Routes and execute transferRemote() bridging between chains like Ethereum and Arbitrum. - Custom Security Modules: Configure MultisigISM, RoutingISM, and AggregationISM via factory contracts for sovereign control over message verification. - Interchain Accounts: Execute batched remote transactions on destination chains through deterministic ICA addresses. - Use Case: You need to send a governance instruction from Ethereum to a contract on Arbitrum. The Skill guides you to quote the interchain gas fee, dispatch the message with proper encoding, and verify delivery via the Hyperlane Explorer. ## Quick Start Ask the agent to send a Hyperlane message from Ethereum to Arbitrum using the Mailbox contract, including gas fee quoting and recipient address padding.

Frequently Asked Questions about hyperlane

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send a cross-chain message with Hyperlane?

Call `quoteDispatch()` on the origin chain Mailbox to get the interchain gas fee, then call `dispatch()` with the destination domain ID, bytes32-padded recipient address, and message body, sending the quoted fee as msg.value. The recipient contract must implement `IMessageRecipient.handle()`.

How do I bridge tokens using Hyperlane Warp Routes?

Approve the collateral Warp Route contract to spend your ERC-20, quote gas with `quoteGasPayment()`, then call `transferRemote()` with the destination domain, bytes32 recipient, and amount. Synthetic tokens are minted on the destination chain after relayer delivery.

What is an Interchain Security Module in Hyperlane?

An ISM is a modular contract that verifies inbound message authenticity before the Mailbox delivers it. Types include MultisigISM (M-of-N validator signatures), RoutingISM (per-origin security), and AggregationISM (multiple ISMs must pass), and recipients can set custom ISMs via `interchainSecurityModule()`.

Why is my Hyperlane message not delivered on the destination chain?

The most common cause is missing interchain gas payment — you must send the `quoteDispatch()` fee as msg.value. Other causes include no relayer running for the destination chain, ISM verification failure, or the recipient contract reverting in `handle()`.

How do I convert addresses between address and bytes32 for Hyperlane?

EVM addresses are left-padded with 12 zero bytes to form bytes32: use `bytes32(uint256(uint160(addr)))` in Solidity or `pad(addr, { size: 32 })` in viem. Convert back with `address(uint160(uint256(buf)))` — incorrect conversion silently breaks sender validation.

Can I deploy Hyperlane to a chain that is not officially supported?

Yes, Hyperlane is permissionless — you deploy the Mailbox, ISM, and ValidatorAnnounce contracts yourself using the Hyperlane CLI, then run your own validators and relayer. No governance vote or approval is required, unlike LayerZero or Wormhole.