HYP_KEY
env var funded on your origin and destination networks.hyperlane warp init
This command provides a walkthrough, prompting you for configuration choices directly in the terminal.
Here’s how your setup should look like:
collateral
for the two source networks, and synthetic
for the destination network../configs/warp-route-deployment.yaml
.
hyperlane warp deploy
During deployment, the CLI requires access to your private key to sign transactions. You can enter it when prompted or set your private key as HYP_KEY
. Make sure that your wallet has sufficient funds on all relevant chains to cover the gas costs for the deployment.
hyperlane warp send --symbol TOKEN
The CLI will prompt you to:
collateral
chains, make sure there’s sufficient
collateral available on the destination chain to complete the transfer.
Synthetic tokens are minted on the destination. In collateral routes, tokens
must already exist on the destination chain in order to be released.