Operator Registration
To operate the network, participants must register as EigenLayer Operators and sign up on the AVS
Last updated
To operate the network, participants must register as EigenLayer Operators and sign up on the AVS
Last updated
The Othentic CLI allows you to register as an Operator to an AVS. This guide covers the commands and key configurations needed to get started.
To register as an Operator, use the following command:
This command initiates the registration process on both EigenLayer (if required) and the AVS. You will be prompted to provide the following details:
Private Key and Signing key
For testnet, you can use the same key for both.
For mainnet, two different keys are required. Detailed information on using separate keys is provided in the section below.
AVS Governance Contract Address
You will be prompted to pass in AVS Governance contract address
Rewards Receiver Address
It is recommended to set the rewards receiver address to a smart contract that distributes rewards to stakers. If left empty, the Operator address will be used as the default.
To register an operator on mainnet add:
--l1-chain mainnet
To unregister as an Operator, use the following command:
If you are unfamiliar with these terms, please refer to the Key Management section for more detailed information. To run an AVS Operator, two keys are required:
Controller key:
Used to sign up with the shared security protocolComment
Represents the account to which restakers delegate their staked assets.
Consensus key:
Used by the node to sign the consensus messages.
For the following examples, we will use:
0x1 as the Controller Key
0x2 as the Consensus Key
0xA as the public address for the Controller Key
To use separate keys during registration, provide both keys when running the registration command:
When running the node, configure the environment variables as follows:
PRIVATE_KEY: Set this to the Consensus Key.
OPERATOR_ADDRESS: Set this to the public address of the Controller Key.
OPERATOR_ADDRESS is the public address of the account that has signed up with the shared security protocol—the address to which stakers delegate their staked assets.
Example .env file:
Othentic CLI allows you to update the consensus key for an operator. It internally calls updateBlsKey method on the Attestation Center contract. To update the key, run the following command:
Follow these steps when prompted:
Provide the Controller key of the operator.
Enter the Attestation Center contract address.
Enter the new Consensus key.
At the end, the CLI will display the transaction hash. Alternatively, you can pass a keystore file and its password to update the same.
