Get to know what Ethereum Staking configurations Blockdaemon offers. Staking configurations are both requested and created manually.
Selecting the appropriate staking configuration is crucial for meeting your staking goals. When setting up your account and requesting an Ethereum validator inventory from Blockdaemon, you will have to define the quantity of validator nodes needed from Blockdaemon and agree on your staking configuration options. These staking configurations are both requested and created manually. Your validator inventory, generated as a result of how you setup your staking configuration, is either static or dynamic.
The below table gives you an overview of what both configuration types offer; choosing the right one will depend on your staking requirements.
| Static Configuration | Dynamic Configuration | |
|---|---|---|
| Description | This is a fixed set of validators with specific configurations. | This is an on-demand, self-maintaining inventory of validators, optimized to ensure validators are available when required. |
| Cost Management | Validator funding can happen in batches. You never pay for the # of Unfunded or Exited Validators. | Validator funding can happen in batches. You never pay for the # of Unfunded or Exited Validators. |
| Expansion | Need to have a new plan set up by Blockdaemon. Maximum of 1000 validators per plan. | Dynamically scaling, when you don’t know how your $ETH staking will grow. |
| Use Case | E.g., for own known treasury, B2B | E.g., for customer fund staking, B2B2C |
| Main Benefit | Possible to diversify across geographical locations, cloud vs. bare metal, etc. (additional costs may apply) | Seamless scaling without interacting with Blockdaemon staff. |
By understanding the differences between static and dynamic configurations and considering your staking requirements, you can choose the configuration type that best suits your needs.