./rust/sealevel/environments/${environment}
, create a directory called warp-routes
warp-routes
, create a new directory for your HWR deployment, e.g., e.g. environments/mainnet3/warp-routes/pzeth
hyperlane-registry
with metadata to associate with the synthetic token in the HWR. Example here.
image
field try to pick a source that is unlikely to break the URLtoken-config.json
for the SVM configuration, e.g.
remoteDecimals: 18
.hyperlane warp init
The command provides a walkthrough, prompting you for configuration choices directly in the terminal.
Use the following steps for your HWR configuration. You can input during the walkthrough or directly in the generated YAML config file.
foreignDeployment: <SVM address>
for the SVM chain, as shown in the config example below.interchainSecurityModule: "0x0000000000000000000000000000000000000000"
to use the default ISM set in the destination chain Mailboxgas
to a ceiling of the compute units you expect the SVM message delivery transaction to take. For instance, HWRs have gas set to 300
. It’s important for this to be an upper limit - the relayer will not deliver HWR transfer messages otherwise, because senders would pay an insufficient amount to have them delivered.hyperlane warp deploy
token-config.json
with the foreign deployment:
ethereum
should be set to values from the HWR contract artifact.token
should be set to collateralAddressOrDenom
(the address of the token being bridge)foreignDeployment
should be set to addressOrDenom
(the address of the HWR contract, like HypERC20Collateral
).