Learn how to update your mailbox default ISM using the Hyperlane CLI for production deployments
hyperlane core init
.
CURRENT_DIR/configs/core-config.yaml
.--chain
set to the name of your chain that the mailbox is deployed on:
core read
, you should see a similar config with owner
set to private key’s address:
CURRENT_DIR/configs/core-config.yaml
.
This particular config has a trustedRelayerIsm
. This means contracts (e.g., Hyperlane Warp Route) that fallback to the mailbox’s defaultIsm
will give permission to relayer
address to execute arbitrary messages. This may be undesirable in cases outside of the self-relaying feature.
Follow these steps using the CLI to update the existing default Ism to a different configuration.
relayer
address to something else (e.g., “burn” it by setting it to an inaccessible address).
defaultIsm
config to a different ISM config. As shown, it is updated to a messageIdMultisigIsm
.
core read
, you should see a similar config with the now updated default ISM: