Description: (Env only) List of additional configuration file paths to load in order (such as those in hyperlane-monorepo/rust/main/config). They will be merged first to last, so if both the first one and the last one specify a specific config path, the value set in the last file listed will be used.These files must be accessible within the filesystem your agent has access to. If you’re running in Docker, see the agent configuration guide for tips on mounting your config files into your Docker container.Optional: YesAgents: AllType:string (Comma separated list of file paths)
Description: Configuration for each of the chains that must be used by an agent.Optional: NoAgents: AllType:Map<string, ChainSetup (Object)> (See chains.* for ChainSetup values)
Description: Name of the domain. Allows specifying a different name for the domain than the chain’s true name. This should almost always be the same as chain_name.Requires: Alignment with domain id if it is a known domain name.Optional: NoAgents: AllType:string
Description: Hyperplane domain id to uniquely identify the domain. See also: Domain Identifiers.Requires: Alignment with domain name if it is a known domain.Optional: NoAgents: AllType:Numeric (string | number)
Description: The type of signer that is defined. A HexKey signer uses a private key, an Aws signer uses an AWS based KMS, and Node assumes the local node will sign RPC calls.Optional: Yes; Defaults to node unless a key is specified in which case it defaults to hexKeyAgents: AllType:Enum ("hexKey" | "aws" | "cosmosKey" | "node")Accepted values for the different VMs are:
Description: A hex key. The hex string of a private key.Requires:chains.<chain_name>.signer.type = "hexKey" | undefinedOptional: No (iff requirements are met)Agents: AllType:string
Description: The UUID identifying the AWS KMS keyRequires:chains.<chain_name>.signer.type = "aws"Optional: No (iff requirements are met)Agents: AllType:string
The consensus type currently only applies to EVM chains.Connections to non-EVM chains only support a single RPC url. If more than one RPC url is specified in rpcUrls, only the first one will be used.
Description: How to communicate with the provider
"single" uses a basic http connection
"fallback" will try the first URL and then automatically “fall back” on a connection or other provider failure to the next provider; this should only retry calls which fail due to the provider and not the call itself such; an insufficient gas error for instance would not fall back.
"quorum" requires a majority of the URLs to agree with the exception of submitting transactions; it will automatically coordinate the “latest” block if not specified to reduce sync errors.
Connections to non-EVM chains only support a single RPC url. If more than one RPC url is specified, only the first one will be used.
Description: Comma-separated URLs to connect the provider to. The difference between customRpcUrls and rpcUrls is that customRpcUrls allows for more user friendly inputs from the CLI or environment variables (comma-separated vs array).Type:string (comma separated list of urls without spaces)
Connections to non-EVM chains only support a single RPC url. If more than one RPC url is specified, only the first one will be used.
Description: URLs to connect the provider to. The first one is initially used, and on failure the other ones are tried. See rpcConsensusType for more information.Requires:
(chains.<chain_name>.protocol = "ethereum" | undefined) AND (chains.<chain_name>.connection.type = "fallback" | "quorum") OR chains.<chain_name>.protocol = "cosmos" | "sealevel" | "fuel"
Optional: No (iff requirements are met)Agents: AllType:string
Connections to Cosmos chains require both RPC and gRPC URLs. There is no rpcConsensusType configuration for Cosmos chains, and gRPC URLs always operate in fallback mode—if the first URL fails, the next one is used.
Description: Comma-separated gRPC URLs used to connect to the provider. Similar to customRpcUrls.Type:string (comma-separated list of URLs without spaces)
Description: Number of blocks to query at once when indexing contracts. Note that the configured providers must support whatever value is set. The default should work with nearly all providers.Optional: Defaults to 1999Agents: Relayer & ScraperType:Numeric (string | number)
Because each VM supports a different signer type, the default signer can only support a single VM type. For instance, if the default signer is a ECDSA one, it will only be able to sign on EVM chains.
Description: The default signer that should be used for all chains which did not specify their own.Optional: YesAgents: AllType:SignerConf (Object)
Description: The type of signer that is defined. A HexKey signer uses a private key, an Aws signer uses an AWS-based KMS, and Node assumes the local node will sign RPC calls.Optional: Yes; Defaults to node unless a key is specified in which case it defaults to hexKeyAgents: AllType:Enum ("hexKey" | "aws" | "cosmosKey" | "node")
Description: A hex key. The hex string of a private key.Requires:defaultsigner.type = "hexKey" | undefinedOptional: No (iff requirements are met)Agents: AllType:string
Description: Configuration for the log module. This controls logging.Optional: Defaults to prettyAgents: AllType:Enum ("pretty" | "json" | "full" | "compact")
Description: Configuration for the log module. This controls logging. For full verbosity (including that of dependencies), use dependencyTrace.Optional: Defaults to infoAgents: AllType:Enum ("dependencyTrace" | "trace" | "debug" | "info" | "warn" | "error" | "off")
Description: Name of the chain a validator should validate for and name of the chain a relayer should relayer messages from. Deprecated for Relayer, use#relaychainsinstead.Optional: No - Validators; Yes - RelayerAgents: Validator & RelayerType:string
Description: The type of EVM signer that is defined. Note that regardless of the VM the validator is operating on, checkpoints are always signed using the EVM ECDSA curve. A HexKey signer uses a private key, an Aws signer uses an AWS based KMS, and Node assumes the local node will sign RPC calls.Optional: Yes; Defaults to node unless a key is specified in which case it defaults to hexKeyAgents: AllType:Enum ("hexKey" | "aws" | "node")
Description: A hex key. The hex string of a private key.Requires:validator.type = "hexKey" | undefinedOptional: No (iff requirements are met)Agents: AllType:string
Description: Path on the local disk of a local storage type checkpoint syncer configuration.Requires:checkpointsyncer.type = "localStorage"Optional: No (iff conditions are met)Agents: ValidatorType:string
Description: How frequently the validator should check for new checkpoints in seconds? See also latencies.Optional: NoAgents: ValidatorType:Numeric (string | number)
Description: This is a local filesystem path to where the agents store relevant data on disk. This must be unique per agent! Multiple agents must have different paths. The path is relative to the current working directory if it does not start with a system defined root path such as / on unix. When using docker images, ensure that this folder gets persisted across runs.For the scraper, this is the connection string to a postgresql database.Optional: For validators and relayer it is optional and defaults to a path in the current working directory which includes the originchainname. For the scraper it is required.Agents: AllType:string
# For the validator:{ "db": "/tmp/hyp/validator/ethereum-cache"}# For the relayer:{ "db": "/tmp/hyp/relayer/ethereum-cache"}# For the scraper:{ "db": "postgresql://postgres:password@localhost:5432/dbname"}
Description: JSON stringified array of gas payment enforcement configurations sorted by highest priority first. The last policy should be a catch-all and handle any messages that did not match a previous policy.Optional: Defaults to no enforcement ([{"type": "none"}])Agents: RelayerType:JSON (string)
type gaspaymentenforcement = Array<GasPaymentEnforcementPolicy>;type GasPaymentEnforcementPolicy =| // fields specific to each type...// No requirements - all messages are processed regardless of gas payment({type: "none";} & {// Messages that have paid a minimum amount will be processedtype: "minimum";payment: U256;} & { type: "onChainFeeQuoting"; gasfraction?: GasFraction }) // to on-chain fee quoting. `gasfraction` defaults to "1 / 2". // Required amount of gas on the foreign chain has been paid according| {// all types have the following fields...// If a message matches, this policy will be used.// If no matching list is specified, all messages will match.matchingList?: MatchingList;};// A list of matching rules. A message matches if any of the list// elements matches the message.type MatchingList = Array<MatchingListElement>;// Matches a message if any of the provided values matches.interface MatchingListElement {originDomain?: NumericFilter;senderAddress?: HashFilter;destinationDomain?: NumericFilter;recipientAddress?: HashFilter;}type NumericFilter = Wildcard | U32 | Array<U32>;type HashFilter = Wildcard | H256 | Array<H256>;// 32-bit unsigned integertype U32 = number | string;// 256-bit unsigned integer; Note: `number` type has limited precision.type U256 = string | number;// 256-bit hash (can also be less) encoded as hextype H256 = string;// Matches anythingtype Wildcard = "\*";// A numeric string in the form `{numerator} / {denominator}`, e.g. "1 / 2"type GasFraction = string;
Description: A matching list to define what messages should be allowed. Any messages which do not match this list will not be relayed. If no whitelist is supplied all messages will be allowed.See also message filteringOptional: YesAgents: RelayerType:JSON (string)
// A list of matching rules. A message matches if any of the list// elements matches the message.type MatchingList = Array<MatchingListElement>;// Matches a message if any of the provided values matches.interface MatchingListElement {originDomain?: NumericFiltersenderAddress?: HashFilterdestinationDomain?: NumericFilterrecipientAddress?: HashFilter}type NumericFilter = Wildcard | U32 | Array<U32>;type HashFilter = Wildcard | H256 | Array<H256>;// 32-bit unsigned integertype U32 = number | string;// 256-bit hash (can also be less) encoded as hextype H256 = string;// Matches anythingtype Wildcard = "\*";
Description: A matching list to define what messages should be ignored. Any messages which match this list will not be relayed. If no blacklist is supplied all messages will be allowed.See also message filteringOptional: YesAgents: RelayerType:JSON (string)
type blacklist = MatchingList | undefined;// A list of matching rules. A message matches if any of the list// elements matches the message.type MatchingList = Array<MatchingListElement>;// Matches a message if any of the provided values matches.interface MatchingListElement {originDomain?: NumericFilter;senderAddress?: HashFilter;destinationDomain?: NumericFilter;recipientAddress?: HashFilter;}type NumericFilter = Wildcard | U32 | Array<U32>;type HashFilter = Wildcard | H256 | Array<H256>;// 32-bit unsigned integertype U32 = number | string;// 256-bit hash (can also be less) encoded as hextype H256 = string;// Matches anythingtype Wildcard = "\*";
Description: List of domain ids to skip applying the transactiongaslimit for.Optional: Defaults to using the transactiongaslimit for all domainsAgents: RelayerType:string (comma separated list of domain ids)
Description: The maximum number of retries to attempt before dropping a message from the relayer queues. This prevents messages from being retried indefinitely.Optional: Defaults to a system default value of 66Agents: RelayerType:Numeric (string | number)
Description: (Env only) The access key ID of your validator’s AWS IAM user.Optional: Required if any signer configuration uses awsAgents: Relayer & ValidatorType:string
Description: (Env only) The secret access key of your validator’s AWS IAM user.Optional: Required if any signer configuration uses awsAgents: Relayer & ValidatorType:string