Hyperlane Docs home page
Search...
⌘K
Ask AI
Search...
Navigation
Go to Production
Overview
Home
Learn
Agent Operators
Overview
Introduction
Intro to Hyperlane
Deployments
Quickstart
Get Started Building with Hyperlane
Bridge a Token
Local Setup: Sending Messages between Anvil Nodes
Applications
Hyperlane Warp Routes
Interchain Accounts
Guides
Setup Hyperlane on your Chain
Hyperlane Warp Routes (HWR)
Go to Production
Overview
Core Deployment
HWR Deployment
Create your own Hook & ISM
Troubleshooting Guide
Developer Tools
Hyperlane CLI
Libraries
Typescript SDK
Developer Tips
Resources
Hyperlane Explorer
On this page
1. Core Deployment
2. HWR Deployment
Go to Production
Overview
Copy page
To launch your Hyperlane deployment into a production environment, follow these steps to set up your chain’s core deployment and configure Hyperlane Warp Route (HWR) deployments.
1. Core Deployment
To begin you’ll need to set up and productionize the core components of your Hyperlane deployment.
Update Mailbox Default ISM
Update the Interchain Security Module (ISM) associated with the Mailbox contract. The ISM acts as a critical security layer, verifying messages between chains. Ensure that the default ISM settings align with your security requirements.
Transfer Mailbox Ownership
Transfer ownership of the Mailbox contract to a production-ready owner account. This step secures the Mailbox by ensuring only trusted parties have control over its configuration.
2. HWR Deployment
Remove Trusted Relayer
Remove any test or development relayers that may have been configured initially. In production, ensure that only trusted, secure relayers are used to prevent unauthorized message relaying.
Transfer HWR Ownership
Transfer ownership of the HWR to the designated production owner. This step ensures that only trusted parties have control over critical HWR settings, such as ISM configurations, Validator options, and relayer settings.
Was this page helpful?
Yes
No
Deploying a Bridge UI for your HWR
Update Mailbox Default ISM
Assistant
Responses are generated using AI and may contain mistakes.