π₯ Operator Roles
CSM has two roles to interact with your Node Operator: Manager and Rewards. When you first create your operator, both roles are assigned to the wallet you used at creation (unless you are explicitly specifying custom addresses), but both can be changed later. Let's see what each role can do and how to change the wallet:
You won't be able to change permissions or use certain claim methods if you can't sign transactions, make sure you're using an EOA or Smart Account that can sign arbitrary transactions as the Reward address.
You can work around this by using the Extended mode explained here. Note: you can only do this when creating the Node Operator.
Rolesβ
Manager addressβ
The Manager can perform the following actions:
- Add new validator keys
- Compensate the reported MEV stealing penalty
- Delete validator keys that were not deposited yet
- Claim rewards (rewards will be transferred to the Reward address)
- Put depositable keys back into the deposit queue if they were skipped during the queue iteration
- Propose a new
managerAddress
As it has limited access, you can set the Manager as a hot wallet for more convenient management of your Node Operator within CSM.
Reward addressβ
The Reward can do the following:
- Claim rewards
- Propose a new Reward address
- Reset the Manager to make it equal to the current Reward address
Given the Reward address is the recipient of funds, it is recommended to be set to a cold wallet.
Permissionless operationsβ
On top of the permissions above, there's several methods that can be called by any Ethereum address:
- Top-up bond
- Distribute allocated rewards to the Node Operator's bond
- Report validator withdrawal to release bond tokens (usually done by the CSM Bot)
- Report validator slashing (usually done by the CSM Bot)
Change rolesβ
To change the roles for either the Manager or Reward address, navigate to the Roles tab.
Select the role you want to changeβremember the Manager can only change itself, and the Reward can change itself and reset the Manager.
Put the new address in the textbox, and confirm the changes.
The other wallet will then have to sign a transaction accepting the request.
Extended modeβ
The extended mode can only be set upon the creation of the Node Operator and can't be changed later.
If you need to use a wallet that can't sign arbitrary transactions as the Reward address (e.g., Obol clusters using Splitter contracts), you can select Extended mode which gives the manager the ability to change the Reward address as well.
Find it at the bottom of the Lido CSM Widget during operator creation.
Examplesβ
Defaultβ
By default, the Node Operator creator's address is set as the Manager and Rewards.
Following the creation of the operator (i.e. once at least one key has been registered), it is recommended that addresses be re-assigned according to one of the optimal configurations below.
Optimal for solo operatorβ
It's optimal to set the Manager to a hot address and the Rewards to a secure cold wallet or multisig.
Optimal for DVT clustersβ
There's multiple ways to set up a DVT cluster using CSM.
- Set the Manager address to a hot wallet controled by the cluster coordinator and the Rewards to a cluster mulgisig. This option is only recommended in cases where cluster participants trust the coordinator completely (or have other types of guarantees/agreements in place) or if the DVT setup is an intra-operator setup rather than an inter-operator setup.
- Set both Manager and Rewards address to a cluster multisig.
- Set Manager address to a cluster multisig and Rewards to a splitter contract (e.g. to benefit from automated rewards splitting between cluster participants). For this to work you need to set up Extended Mode at the creation of the operator.