Mailbox
’s latest merkle root. Securing this key is important. If it is compromised, attackers can attempt to falsify messages, causing the Validator to be slashed.
customRpcUrls
.rpcConsensusType
):
Parameter | Description |
---|---|
--db | Path for writing persistent data to disk. |
--originChainName | Name of the chain being validated. For example: ethereum . |
--chains.[originChainName].customRpcUrls | Override the default RPC URLs used by the Validator for your origin chain. |
--chains.[originChainName].blocks.reorgPeriod | Number of block confirmations the Validator needs to wait for before signing the Mailbox merkle root. |
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 |
---|---|
--validator.key | Your Validator’s private key, which is used to sign merkle roots. |
--chains.${localChainName}.signer.key | Your Validator’s private key, which will be used to submit a transaction onchain that publicly announces your Validator’s checkpoint syncer. |
Argument | Description |
---|---|
--chains.${localChainName}.signer.key | Your Validator’s private key, which will be used to submit a transaction onchain that publicly announces your Validator’s checkpoint syncer. |
Argument | Description |
---|---|
--checkpointSyncer.type | Set to localStorage . |
--checkpointSyncer.path | The path to your local directory where Validator signatures will be written. This should be the value of $MY_VALIDATOR_SIGNATURES_DIRECTORY from the local setup. For example: --checkpointSyncer.path='/tmp/hyperlane-validator-signatures-ethereum' . |
--allowLocalCheckpointSyncers
to be able to read signatures from this
Validator.Environment variable | Description |
---|---|
AWS_ACCESS_KEY_ID | The access key ID of your Validator’s AWS IAM user. |
AWS_SECRET_ACCESS_KEY | The secret access key of your Validator’s AWS IAM user. |
ValidatorAnnounce
contract on the chain that you’re validating.
To do this, your Validator must have a small amount of tokens to pay for the gas for this transaction.
If your Validator has not yet announced itself, and does not have enough tokens to pay for gas, it will log a message specifying how many tokens are needed.
--checkpointSyncer.folder validator-1
, --checkpointSyncer.folder validator-2
).--db /hyperlane_db_validator1
).--metrics-port 9090
, --metrics-port 9091
).