How to Go to Production with your Hyperlane Deployment
To launch your Hyperlane deployment into a production environment, follow these steps to set up your chain’s core deployment and configure warp route deployments.
1. Core Deployment
To being 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. Warp Route 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 Warp Route Ownership: Transfer ownership of the Warp Route to the designated production owner. This step ensures that only trusted parties have control over critical Warp Route settings, such as ISM configurations, Validator options, and relayer settings.