Skip to content

Releases: nodeset-org/hyperdrive-daemon

v1.1.3

21 Feb 20:33
6ce6e5a
Compare
Choose a tag to compare

This is v1.1.3 of the Hyperdrive daemon. This is meant to be used by the Hyperdrive service.

This updates the Ethereum clients to add support for the upcoming Pectra network hardfork on Holesky. Pectra will be applied to the Holesky testnet on February 24, 21:55:12 UTC. This is a required update for Holesky node operators before that time (or you must manually update your clients to the below versions).


Clients

Holesky only:

v1.1.2

31 Jan 20:19
92b680e
Compare
Choose a tag to compare

This is v1.1.2 of the Hyperdrive daemon. This is meant to be used by the Hyperdrive service.


Clients

v1.1.1

30 Oct 21:24
fc0c595
Compare
Choose a tag to compare

This is v1.1.1 of the Hyperdrive daemon. This is meant to be used by the Hyperdrive service.


Known Issues

Clients

Bug Fixes

  • Changing the custom relays parameter in MEV-Boost will now properly mark the container as requiring a restart.

Service

  • When modules send transactions, if the priority fee is above the max fee, Hyperdrive will now reduce it to the max fee rather than reverting.

v1.1.0

16 Oct 00:25
11952ea
Compare
Choose a tag to compare

This is v1.1.0 of the Hyperdrive daemon. This is meant to be used by the Hyperdrive service.


Known Issues

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.

Bug Fixes

  • Validator status queries to the Beacon Node now work on machines with 1 CPU.

  • Error codes returned from NodeSet.io during Constellation requests have been standardized and are now handled in a more user-friendly.

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.

  • Added support for the nodeset.io encryption key. Messages like 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.
  • Added a config parameter to specify the timeout for HTTP requests. This is most relevant to requests for the Execution Client, Beacon Node, and nodeset.io APIs.

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

  • Updated to Go 1.22.

v1.1.0 Release Candidate 1

09 Oct 21:22
73dbca4
Compare
Choose a tag to compare
Pre-release

This is Release Candidate 1 for v1.1.0 of the Hyperdrive daemon. This is a public beta meant to be used by the Hyperdrive service.


Known Issues

Clients

Service

  • Added support for the nodeset.io encryption key. Messages like 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.

v1.1.0 Beta 2

03 Oct 06:22
25d2f8b
Compare
Choose a tag to compare
v1.1.0 Beta 2 Pre-release
Pre-release

This is release v1.1.0 Beta 2 of the Hyperdrive daemon. This is a public beta meant to be used by the Hyperdrive service.


Breaking Changes

  • Submitting requests to the daemon now requires JWT authorization. The secret key to use for authorization can be passed in with the -k flag. It should be at least 48 bytes long.
    • Thanks to @poupas for reporting this!

Known Issues

Clients

  • Updated Geth to v1.14.11.

    • Geth images are now published for both arm64 and amd64 once again, so all users can use this release.
  • Updated Reth to v1.0.7.

  • Updated Nimbus to v24.9.0.

Service

  • Added a config parameter to specify the timeout for HTTP requests. This is most relevant to requests for the Execution Client, Beacon Node, and nodeset.io APIs.

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

v1.1.0 Beta 1

23 Sep 17:41
45766bc
Compare
Choose a tag to compare
v1.1.0 Beta 1 Pre-release
Pre-release

This is release v1.1.0 Beta 1 of the Hyperdrive daemon. This is a public beta meant to be used by the Hyperdrive service.

⚠️ This is a BETA release and should only be used on the Holesky test network.


Clients

  • Updated Besu to v24.9.1.

  • Updated Geth to v1.14.8.

    • Note: while Geth v1.14.9 has been released, they haven't published a multiarch image to Docker Hub yet so we cannot include it in this release. Users are welcome to update manually once an image has been published.
  • Updated Nethermind to v1.28.0.

  • Updated Reth to v1.0.6.

  • Updated Lighthouse to v5.3.0.

  • Updated Lodestar to v1.22.0.

  • Updated Nimbus to v24.8.0.

  • Updated Prysm to v5.1.0.

  • Updated Teku to v24.8.0.

  • Updated Prometheus to v2.54.1.

  • Updated Node Exporter to v1.8.2.

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.

  • Updated to Go 1.22.

v1.0.1

02 Jul 15:54
3f61be3
Compare
Choose a tag to compare

This is release v1.0.1 of the Hyperdrive daemon. This is meant to be used by the Hyperdrive service.


Clients

  • Updated Nethermind to v1.27.0.

  • Updated Reth to v1.0.0.

  • Updated Lighthouse to v5.2.1.

    • ⚠️ NOTE: Reth v1.0.0 has a known bug that will cause the Lighthouse BN to fill its log with warnings. This will cause a slight performance decrease. See the patch notes for details.
  • Updated Nimbus to v24.6.0.

  • Updated Prysm to v5.0.4.

  • Updated Teku to v24.6.1.

  • Updated Grafana to v9.5.20.

  • Updated Prometheus to v2.53.0.

Service

  • Added support for IPv6 to the stack. It can be enabled with the new Enable IPv6 option in the Hyperdrive and TX Fees config section.
  • Community member @benv666 fixed a bug in the Beaconcha.in API key parser that would reject legal = characters.
  • Community member @dabdab-wrt fixed a bug in the Beaconcha.in machine name, which doesn't allow for spaces.

v1.0.0

20 Jun 19:21
e26fcd0
Compare
Choose a tag to compare

This is release v1.0.0 of the Hyperdrive daemon. This version adds support for running on Mainnet. This is meant to be used by the Hyperdrive service.


Clients

  • Updated Besu to v24.6.0.

  • Updated Geth to v1.14.5.

  • Updated Reth to v0.2.0 Beta 9.

  • Updated Lighthouse to v5.2.0.

    • Lighthouse no longer has different modern and portable images - there is only one image now, which dynamically determines your CPU features at runtime.
    • ⚠️ If you use Nethermind with Lighthouse, Nethermind v1.26.0 has a known bug that will cause the Lighthouse BN to fill its log with warnings. The Lighthouse team recommends reverting to Nethermind v1.25.0 until v1.27.0 is released, or ignorning the warnings. See the patch notes for details.
  • Updated Lodestar to v1.19.0.

  • Updated Teku to v24.6.0.

Service

  • Added support for Mainnet.
  • Fixed a bug that prevented Lighthouse's VC from working when MEV-Boost was enabled.
  • The MEV-Boost relay selection mode has been adjusted in preparation for Mainnet.
    • "Unregulated" relays have been removed from Hyperdrive's built-in list due to liability concerns.
    • The selection modes are now All and Manual; All automatically enables all of the built-in relays (similar to the old Profile mode), and Manual allows you to individually select the built-in relays you want to use (similar to the old Relay mode).
    • The new "Custom Relays" box allows you to add additional URLs for any other relays you'd like to use. Custom relays can be anything as long as they are on the same Ethereum network as your node. The ETHStaker relay list is a good resource to explore and compare all of the relay options.

v0.5.0 Beta 1

04 Jun 16:20
9349e00
Compare
Choose a tag to compare

This is v0.5.0 Beta 1 of the Hyperdrive daemon. This is meant to be used by the Hyperdrive service.


Clients

Service

  • Added MEV-Boost support to the daemon, with both Mainnet and Holesky configurations.