CLI Commands
Please store back up your BLS and ECDSA key pairs. Do not discard keys under any circumstance. Your keys are located at ~/.lagrange/keystore/<key_type>_<public_key_prefix>.key
.
We recommend using performant providers such Alchemy, Quicknode, Infura, in the case that you do not run your own Ethereum node. For the Beacon RPC endpoint, you should check if the given RPC provider supports the Beacon RPC API like /eth/v1/beacon/genesis
. Quicknode supports this API.
You can check client config files in at~/.lagrange/config/client_<network_name>_<chain_name>_<bls_pub_key_prefix>.toml
and docker-compose files in the ~/.lagrange/docker-compose_<network_name>_<chain_name>_<bls_pub_key_prefix>.yml
.
Generating Keystore: generates a new key pair for the given key type and password, and saves it in the keystore file. The key type can be either
ecdsa
orbls
.Importing Keystore: imports a key pair from the given private key and saves it in the keystore file. The key type can be either
ecdsa
orbls
.Exporting Keystore: exports a private key from the keystore file for the given key type and password.
Registering Operator: registers an operator to the Lagrange State Committee. The network name can be either
mainnet
orholesky
. The BLS key and Signer address are referenced from the config file.Deregistering Operator: deregisters an operator from the Lagrange State Committee. The network name can be either
mainnet
orholesky
.Updating BLS Public Key: updates the BLS public key for the operator at the given index. The network name can be either
mainnet
orholesky
. New BLS key is referenced from the config file.Updating Signer Address: updates the signer address for the operator. The network name can be either
mainnet
orholesky
. New signer address is referenced from the config file.Adding BLS Public Key: adds a new BLS public key for the operator. The network name can be either
mainnet
orholesky
. New BLS key is referenced from the config file.Removing BLS Public Key: removes the BLS public key for the operator at the given index. The network name can be either
mainnet
orholesky
.Subscribing to Chain: subscribes the operator to the given chain. The network name can be either
mainnet
orholesky
. The chain name can be eitheroptimism
orbase
.Unsubscribing from Chain: unsubscribes the operator from the given chain. The network name can be either
mainnet
orholesky
. The chain name can be eitheroptimism
orbase
.Generating Config: generates an attestation node config file. The network name can be either
mainnet
orholesky
. The chain name can be eitheroptimism
orbase
. The L1 RPC endpoint is the Ethereum mainnet RPC endpoint for both mainnet and Holesky testnet. The L2 (Optimism
orBase
) RPC endpoint is the rollup chain's mainnet RPC endpoint for both mainnet and Holesky testnet. The Beacon RPC endpoint is the Beacon mainnet RPC endpoint for both mainnet and Holesky testnet.Deploying Node: creates a docker-compose file and deploys the docker container for the attestation node. The network name can be either
mainnet
orholesky
.
Last updated