nodeset-org/hyperdrive v1.0.1 on GitHub

This is release v1.0.1 of Hyperdrive. This is a point release with client updates and fixes for some bugs reported by our users from v1.0.0.

Clients

Updated Nethermind to v1.27.0.
Updated Reth to v1.0.0.
- ⚠️ While this release means Reth is no longer considered in beta, we have not been able to verify if it fixes the compatibility issues with the StakeWise Operator. If you have the StakeWise module enabled, you will likely still need to use a different Execution client for now.
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.

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.
- Note that if you already have Hyperdrive installed and running, you'll need to do the following after checking the box:
- hyperdrive service down to remove the containers and Docker network while preserving chain data and personal information like your config, wallet, and validator keys
- Follow the instructions at https://docs.docker.com/config/daemon/ipv6/#dynamic-ipv6-subnet-allocation to enable IPv6 in Docker itself
- hyperdrive service start to regenerate the containers and Docker network which should all now have IPv6 support
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.
service start will now deploy the ~/.hyperdrive/metrics/modules folder prior to instantiating the Docker compose templates. This should resolve a rare permissions problem that occurred when migrating from v0.5.0 to v1.0.0.

New command: hyperdrive service down runs a docker compose down operation, removing Hyperdrive's Docker containers and networks while leaving its volumes (i.e. chain data, Grafana and Prometheus databases, and StakeWise Operator database) intact as well along with the Hyperdrive configuration and your user data (such as your wallet and validator keys).
- This is useful for anyone needing to adjust the Docker service, such as by enabling IPv6, without wanting to delete any data that's important or expensive to regenerate.
The External IP address retriever used in some of the hyperdrive service commands has had its timeout reduced from 30 seconds to 3 seconds, which will make those commands much more responsive.
Removed the dialog in the service config wizard that prompted for the externally-managed MEV-Boost URL if you selected externally-managed clients. That dialog only now properly only applies for locally managed clients.
Fixed the text printed in wallet init and wallet recover to correctly refer to the hyperdrive sw ns register-node command.

Moved the StakeWise v3 Operator's database from the user data folder into its own Docker volume.
- ⚠️ NOTE: the first time you upgrade to Hyperdrive v1.0.1, the StakeWise Operator will regenerate its database which will cause high CPU load for a few hours. This is expected.
- We will add a function to clean up the old database from your user data folder in a later release. If you'd like to do it manually, you can remove the folder at ~/.hyperdrive/data/modules/stakewise/0x646f5285d195e08e309cf9a5adfdf68d6fcc51c4 on Holesky or ~/.hyperdrive/data/modules/stakewise/0xe2aeecc76839692aea35a8d119181b14ebf411c9 on Mainnet.
The CLI will no longer print an error about the clients not being synced if an error occured during a sync check, and will instead report the actual error.