Logging
LOG_LEVEL
: The log level to filter to. Defaults to info
. Choices: debug | info | warn | error | off
LOG_FORMAT
: The format of the log output. Defaults to pretty
. Choices: pretty | json
--log
and --verbosity
flags.Chain Configuration
chains/
yaml files organized by chain name. These metadata.yaml
files describe the information needed to use the chain in Hyperlane deployments and apps.You can define a full configuration for any new chain in this file. The metadata that can be configured is defined in this example configuration. You can also find the chain metadata schema at chainMetadataTypes.ts.Here’s an example configuration for two local anvil chains:Override RPC URLs
Override transaction settings
gasPrice
: number | stringmaxFeePerGas
: number | stringmaxPriorityFeePerGas
: number | stringnonce
: number | stringtype
: numberccipReadEnabled
: booleanLong Message Delivery Times or Timeouts
Deprioritizing an inner provider in FallbackProvider
To address these delays:Validator has not announced any storage locations Warning
Validator has announced signature storage location, locations: ["file:///tmp/hyperlane-validator-signatures-local"]
--checkpointSyncer.path
) to prevent overwriting.No ISM Found for Origin Error
Checking Pending Messages in the Queue
list_operations
endpoint to inspect the relayer’s queue:Debugging with Logs
HYP_LOG_LEVEL=debug
. Once logs are captured, you can use them to locate issues with specific message IDs.Retrying Messages
message_retry
endpoint:Relayer Selecting Incorrect ISM
eth_getStorageAt() Compatibility
eth_getStorageAt()
API. If you’re deploying on one of these chains and encounter issues, review the changes made to the Hyperlane codebase in this commit.To deploy Hyperlane on these chains follow the steps: