This is v1.2.0 Beta 1 of Hyperdrive.

This is meant to be used on the Hoodi Testnet only. Do NOT use this on mainnet.

This introduces support for the new StakeWise v3 vaults, which dramatically improve the operator experience for NodeSet node operators.

For all node operators, please read our documentation on what's new with the new StakeWise module and how to use it. Essentially, it comes down to a few simple commands:

• Make sure your wallet has enough funds to cover depositing gas costs.
• Run hyperdrive stakewise wallet generate-keys to generate new validator keys that can be used for new deposits. This is the only step that needs to be done manually.
• The rest of the process (depositing when assets are available) is all done automatically on a first-come-first-served basis. There's no more queue and no more blacklisting!
• To view which keys have been used for deposits and which are still available, take a look at the guide.

Hyperdrive Core

• The StakeWise module has been disabled on Mainnet, as the old module has been deprecated. It will be replaced with the new module once new Mainnet vaults have been created.

• The StakeWise module has been enabled on Hoodi.

Clients

• Updated Besu to v25.4.1.

• Updated Geth to v1.15.8.

• Updated Reth to v1.3.11.

  • NOTE: the --full flag has been added to Reth, so it keeps the entire history of deposit logs. This is required for StakeWise support.
  • If you had previously used Reth without manually specifying this flag, you will need to resync it in order to regenerate the deposit log history.

• Updated Teku to v25.4.1.

• Updated the Node Exporter to v1.9.1.

Holesky and Hoodi only:

• Updated Lighthouse to v7.0.0-beta.7.

Services

StakeWise

Please read our documentation on what's new with the new StakeWise module and how to use it.

• Support for StakeWise v1 vaults has been removed.
• The daemon no longer generates deposit data in advance and uploads it to nodeset.io.
• The StakeWise operator no longer requires a complete deposit data file for all node operators in a vault, so this is no longer retrieved from nodeset.io.
• The daemon now provides a relay service for the StakeWise operator to interact with. This coordinates between your generated keys, nodeset.io, and the operator to provide deposit data to the operator when it wants to make new validators for StakeWise v3 vaults.
• Prepared the backend for multiple vault support.

CLI

• The stakewise command has had some changes:
  • stakewise nodeset has been removed.
  • stakewise status has been removed.
  • stakewise wallet claim-rewards has been removed, since rewards claiming is done via nodeset.io and not via Hyperdrive.
  • New command: network status can be used to retrieve the status of all StakeWise vaults, including how much ETH they have available to deposit, how many validators each user is able to run, and how many you currently have.
  • New command: validator status will show the status of all of your registered validators, including which vault they belong to and their Beacon chain information (state, balance, etc.).
  • New command: wallet get-available-keys shows which keys you have generated that haven't been used for deposits yet.
  • New command: wallet recover-keys can be used to regenerate your validator keys during disaster recovery. It retrieves the list of registered validator keys from nodeset.io in order to determine what to recover.

Config

• New parameter: StakeWise / Relay Port is used to control the internal port used by the StakeWise daemon container for the StakeWise HTTP relay service. Since this is internal to the Docker network, this isn't exposed on your host system or to outside traffic.

Misc

Note: the GPG key used to sign release artifacts has been updated to v2.