This is the much-anticipated v1.1.0 of Hyperdrive. This adds support for the Constellation module on mainnet, many updates to support for nodeset.io requests, updates the Ethereum clients, and more!

⚠️ NOTE: As usual, after upgrading, it's important to run hyperdrive service config and/or hyperdrive service start before running any other commands so the latest daemon services are pulled first.

Known Issues

• Lodestar v1.22.0 does not currently support x64 systems without the avx instruction set. This will be fixed in a later client release.

• Reth still has a configuration issue that prevents it from working with the StakeWise v3 Operator service. If you're a StakeWise operator, be advised that you will have to use a different client for now.

  • We believe we have a fix in place for this and will release it in a future version.

Hyperdrive Core

Clients

• Updated Besu to v24.9.1.

• Updated Geth to v1.14.11.

• Updated Nethermind to v1.29.0.

• Updated Reth to v1.0.7.

• Updated Lighthouse to v5.3.0.

• Updated Lodestar to v1.22.0.

• Updated Nimbus to v24.9.0.

• Updated Prysm to v5.1.0.

• Updated Teku to v24.10.1.

• Updated Prometheus to v2.54.1.

• Updated Node Exporter to v1.8.2.

• Updated MEV-Boost to v1.8.1.

  • The release notes are for v1.8, but the Docker image being used is for v1.8.1.

Service

• The daemon has been updated to use v2 of the nodeset.io API. It now manages a connection to the server that can be used by multiple modules, rather than the modules managing their own independent connections.

• The configuration system has been overhauled. The options in the Network dropdown are now loaded dynamically from disk rather than being built directly into Hyperdrive. As such, advanced users can now create their own configurations and use Hyperdrive on custom Ethereum chains for things such as development and testing.

• The Eden MEV-Boost relay has been removed from the list of standard relay options because it has been merged with Titan.

• Signed exits are now encrypted locally before sending them to nodeset.io, in addition to regular TLS encryption.

  • Thanks to @poupas for suggesting this enhancement.

• The Hyperdrive daemon and module daemons now require JWT authorization for API access. The Hyperdrive CLI takes care of this automatically, but you can no longer run custom HTTP requests against the daemons without providing a JWT.

  • Thanks to @poupas for reporting this!

Config

• When running the service config TUI, if you have externally managed clients and have MEV-Boost enabled in Hyperdrive, you will now see a modal before the review screen warning you to ensure you have MEV-Boost turned on in your external Beacon Node configuration. If you don't have it enabled in your Beacon Node configuration, your Hyperdrive validators may not be able to propose blocks.

• New parameter: Hyperdrive and TX Fees > Client Timeout

  • This lets you control the timeout for HTTP requests to the Execution Client, Beacon Node, and nodeset.io.

CLI

• New command: hyperdrive nodeset can be used to manage your node's status with the NodeSet service.

  • hyperdrive stakewise nodeset registration-status has been moved to hyperdrive nodeset registration-status.
  • hyperdrive stakewise nodeset register-node has been moved to hyperdrive nodeset register-node.

• New command: hyperdrive constellation (hyperdrive cs) can be used to manage the new Constellation module.

  • See the section below for more information on this module.

• The service stats command has been deprecated. We recommend you just run docker stats -a as a replacement.

• Running service daemon-logs without any other arguments no longer hangs; instead, it will now print the list of daemon logs you can pass in as arguments.

• Fixed an issue that caused the CLI to hang when querying validator status from the Beacon Node if you only have 1 CPU.

Modules

Constellation

• Added support for the Constellation module. It can be accessed from the hyperdrive constellation (hyperdrive cs) command. Please consult the Constellation documentation for information about how Constellation works and how to use the module.

Changes since RC1

• cs minipool create now saves the validator pubkey before submitting the transaction. Note that if you perform a nonce override due to an initial low gas amount, a new pubkey will be created and the original pubkey will remain even though it will be useless.

• cs minipool create now prints a warning about the expense of the transaction, and forces the user to confirm that they understand submitting with a high gas fee may have an excessively long breakeven time.

• Fixed the text on cs minipool exit.

• Added the cs network stats command to view info about the Constellation settings and deposit pool status.

StakeWise

• Updated StakeWise v3 Operator to v2.1.3.

• Submitting voluntary exits now requires the Beacon node to be synced first.

• Signed exits now use the latest finalized epoch, rather than the head epoch.

• Signed exits are now encrypted locally before sending them to nodeset.io, in addition to regular TLS encryption.

  • Thanks to @poupas for suggesting this enhancement.

• nodeset.io deployment names are no longer tied directly to the Hyperdrive network selection. They are now handled by individual modules.

• Increased the delay in the tasks loop during a failed ready-check from 10s to 15s.

Miscellaneous

• Generating validator deposit data now prints the BLS signature (and other intermediate artifacts) to the debug log for easy reference.

• hyperdrive service version now prints the versions of the enabled modules.

• Added better error handling to the nodeset.io request manager for a better explanation about what went wrong during an error.

• Updated to Go 1.22.