Mailbox.process()
transactions. The Hyperlane Relayer agent currently supports configuration with AWS KMS keys that are accessed via API keys/secrets or raw hexadecimal private keys.customRpcUrls
.rpcConsensusType
):
Argument | Description |
---|---|
--relayChains | Comma separated names of the origin and destination chains to relay messages between. For example: ethereum,polygon,avalanche . |
--db | The path to where the Relayer should write persistent data to disk. Ensure this path to be persistent when using cloud setups. When using Docker, make sure to mount the persistent path/volume into the container. See config-reference for more info. |
--allowLocalCheckpointSyncers | If true , this will allow the Relayer to look for Validator signatures on the Relayer’s local filesystem. In a production environment, this should be false . If you’re running a Validator on the same machine by following the Validator local setup instructions, set this to true so that your Relayer can access the local Validator signatures. |
CONFIG_FILES
environment variable. If you choose to run in Docker, see the docker section of agent configuration for tips on mounting your config files into your Docker container.
Argument | Description |
---|---|
--defaultSigner.key | A hexadecimal private key used to sign transactions for all chains. For example: 1b3dead...beef . |
Environment variable | Description |
---|---|
AWS_ACCESS_KEY_ID | The access key ID of your Relayer’s AWS IAM user. |
AWS_SECRET_ACCESS_KEY | The secret access key of your Relayer’s AWS IAM user. |
/tmp/hyperlane-validator-signatures-ethereum
, you should mount a directory for the Docker container:db
in the config). This means running a Relayer for the first time may take some extra time to catch up with the current state.