diff --git a/build-with-hyperlane/troubleshooting.md b/build-with-hyperlane/troubleshooting.md index 5d03ed1..f00adf4 100644 --- a/build-with-hyperlane/troubleshooting.md +++ b/build-with-hyperlane/troubleshooting.md @@ -36,4 +36,4 @@ Once a message is enqueued on a Mailbox merkle tree, from the system perspective #### Missing name field error -An error about a missing `name` field most likely indicates that you have an environment variable that implies the existence of a chain, but said chain does not exist in the config files. You may have mispelled the ENV name (`HYP_BASE_CHAINS_GOERLI_CONNECTION_URL)`. Or you may have specified a new chain but forgot to load the corresponding config file. +An error about a missing `name` field most likely indicates that you have an environment variable that implies the existence of a chain, but said chain does not exist in the config files. You may have misspelled the ENV name (`HYP_BASE_CHAINS_GOERLI_CONNECTION_URL)`. Or you may have specified a new chain but forgot to load the corresponding config file. diff --git a/operators/relayers/setup.md b/operators/relayers/setup.md index 6b26995..37654ec 100644 --- a/operators/relayers/setup.md +++ b/operators/relayers/setup.md @@ -32,7 +32,7 @@ Your relayer takes as configuration the following: | Argument | Description | | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--relayChains` |
Comma separated names of the origin and destination chains to relay messages between.
Example: ethereum,polygon,avalanche
(See also the configuration-reference.md for how to specify origin and destination chains indipendently)
Comma separated names of the origin and destination chains to relay messages between.
Example: ethereum,polygon,avalanche
(See also the configuration-reference.md for how to specify origin and destination chains independently)
An RPC url for chain_name
.
Example: --chains.ethereum.connection.url='http://localhost:8545'
Relayers must set multiple connection URLs, one for each chain it interacts with.
An optional whitelist. The relayer will only relay messages that match this whitelist.
See message-filtering.mdfor more info.
An optional blacklist. The relayer will not relay messages that match this blacklist.
See message-filtering.mdfor more info.