HYP_KEY
, funded on all relevant networks.ETH
.ETH
receipt token to ethereum to become your L2’s custom gas token.
ETH
receipt token is minted to the deployer or authorized address of choice. This must be a one-time mint event in order to avoid value dilution of the ethereum ↔ yourchain native HWR, below.
ETH
ERC20 receipt token.
ETH
receipt token from ethereum to yourchain.
ETH
EvmHypNative ↔ yourchain ETH
EvmHypNative HWR:
hyperlane warp init
and complete the following flow:
ethereum
and yourchain
using space, and hit enter.native
and accept the mailbox.native
and accept the mailbox.metadata.yaml
has a blockExplorers
field defined. This will be needed for contract verification in order to easily collateralize yourchain’s HWR.
hyperlane warp deploy
and confirm the warp deploy config is as expected.
yourchain-ethereum-config.yaml
deployment file will look similar to the following:
ETH
as collateral into yourchain’s native HWR via the receive()
function. If needed, you may use the verified contract to do this via your scanner’s UI, or a wallet such as Metamask
This collateralizes the native HWR, enabling users to bridge their native assets quickly to and from yourchain.
--relay
flag is optional and will relay the message to the destination chain.
You can also run a relayer that delivers only for your HWR in the background with:
$HOME/.hyperlane/deployments/warp_routes
to be used with the --warp
flag.