CURRENT_DIR/configs/warp-route-deployment.yaml
.hyperlane warp read
if it exists in the Registry.$HOME/.hyperlane/deployments/warp_routes/<tokenSymbol>
.warp read
, you should see a similar config under interchainSecurityModule
containing a trustedRelayerIsm
:
trustedRelayerIsm
as part of the staticAggregationIsm
.
This means that the relayer
address will be allowed to call the HWR’s handle()
function. In other words, the relayer
can execute arbitrary messages on the HWR. This may be undesirable in cases outside of the self-relaying feature.
By default, warp read
will save the output to CURRENT_DIR/configs/warp-route-deployment.yaml
. Follow these steps using the CLI to transfer the existing ownership to another address.
warp-route-deployment.yaml
by removing the trustedRelayerIsm
block from modules
. Alternatively, you can configure the entire modules
block as desired.
warp read
, confirm that the trusted relayer ISM has been removed from your HWR (In this example, it should only contain the remaining defaultFallbackRoutingIsm
). You should see a similar config under interchainSecurityModule
: