Advanced guide for deploying Hyperlane with local validators and relayers
CONFIG_FILES
environment variable to the path of the agent config generated in the deploy contracts step. For example:
/tmp
when running the agent via Docker on Mac. To counter this, create a local tmp
directory to mount instead.Parameter | Description |
---|---|
--db | Path for writing persistent data to disk. |
--originChainName | Name of the chain being validated (e.g. ethereum ). |
--checkpointSyncer.type | Set to localStorage for this guide. |
--checkpointSyncer.path | Path to local directory where validator signatures will be written. Same path as $VALIDATOR_SIGNATURES_DIR . |
--validator.key | Your validator’s hexadecimal private key. |
host
network mode on Mac, Windows or Windows Server.To do this, navigate to the agent-configuration at $CONFIG_FILES
and replace all instances of “localhost” or “127.0.0.1” in to host.docker.internal
. For example:$CONFIG_FILES
environment variable to a fixed path within the container.hyperlane_db_validator_<your_chain_name>
if it does not exist yet.CONFIG_FILES
environment variable to the path of the agent config generated in the agent configs step. If not, do so now.
Parameter | Description |
---|---|
--db | Path for writing persistent data to disk. |
--relayChains | Comma separated names of the chains to relay between. E.g. ethereum,polygon,avalanche . |
--allowLocalCheckpointSyncers | Allows the relayer to look for validator signatures on the local filesystem. |
--defaultSigner.key | A hexadecimal private key used to sign transactions for all chains. |
--metrics-port | Optional. The port to expose prometheus metrics on, defaults to 9090 . |
$CONFIG_FILES
environment variable to a fixed path within the container.hyperlane_db_relayer
if it does not exist yet.