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.
Configure Rate Limit ISM
Set, update, or remove the Rate Limit ISM on your HWR. The Rate Limit ISM
caps the daily token volume that can be delivered to your HWR on each
destination chain, bounding the worst-case loss from a bridge compromise.
Configure Pausable ISM
Pause and unpause your HWR in an incident. The Pausable ISM is an
emergency stop: while paused, all inbound deliveries on that destination
chain are rejected.