Using the Hyperlane CLI
After deploying your Hyperlane Warp Route (HWR), you may want to extend it to a new chain. Extending a HWR involves deploying a new token contract on the target chain and enrolling existing tokens with it. You can extend an existing HWR using the Hyperlane CLI.Gnosis Safe Users: The EOA that owns the HWR must either be a Safe signer or
delegate
to be able to propose update transactions.
hyperlane warp read
, the CLI will display a config similar to the following:
warp read
will save the output to CURRENT_DIR/configs/warp-route-deployment.yaml
. Follow these steps to add a chain to the existing HWR.
Step 1: Configuration
Update thewarp-route-deployment.yaml
by adding a config for the new chain.
warp-route-deployment.yaml
EOA Users: The extended config
owner
must match the EOA address from the
prerequisites step to avoid deployment failure.Step 2: Apply
Using the CLI, execute the command applicable to your HWR owner setup:Step 3: Confirm
To confirm that the HWR was successfully extended using the Hyperlane CLI, run the following command with your token symbol on the chain it is deployed on: After runningwarp read
, confirm that the HWR has been extended: