nodeset-org/hyperdrive v1.3.0-b1

v1.3.0 Beta 1

on GitHub

This is v1.3.0 Beta 1 of Hyperdrive.

This includes support for pruning Prysm and Lodestar, the new Post-Merge (History Expiry) data retention mode for Execution Clients, the official Prysm images, support for Commit-Boost's PBS client, and updated clients.

This is a ⚠️ high priority update for all users on the Hoodi testnet that haven't manually updated their clients to Fusaka-ready versions. Fusaka will be deployed to Hoodi on 2025-10-28 18:53:12 UTC.

PBS Client (formerly MEV-Boost) Changes and Commit-Boost

MEV-Boost's configuration has been renamed to the more general PBS Client (Proposer-Builder Separation) term, and it has some new features.

Hyperdrive now supports Commit-Boost's PBS client, a bridge sidecar that connects validator clients to the block-building marketplace - just like MEV-Boost. Users can now toggle between Commit-Boost and MEV-Boost in the Hyperdrive configuration using the PBS Client dropdown. Hyperdrive will now use Commit-Boost by default for the sake of diversity.

NOTE: this change will run Commit-Boost by default for all users, not just new ones. If you want to switch back to MEV-Boost after upgrading, you must do this in the configuration TUI before starting.

As a side-effect, the mev-boost Docker container has been replaced with the new pbs container. This will either be MEV-Boost or Commit-Boost depending on which you choose to run. To see the logs for the container, run hyperdrive s l pbs instead of hyperdrive s l mev-boost.

History Expiry and Pruning

Hyperdrive now supports opt-in history pruning on Prysm and Lodestar of old Beacon Chain data (older than 5 months), which is the same configuration that Nimbus has supported for years.

Additionally, Hyperdrive now supports three data retention options for Execution Clients:

• History Expiry (new): discards all old chain data (older than The Merge), as per EIP-4444. This uses the least disk space overall but is sufficient for running a validator. This is supported on all clients and networks, except for Geth on Hoodi.

• Full Node: retains all chain history, but discards any non-recent chain state. This was the standard mode before EIP-4444 was introduced, and most people that run locally managed mode are using this now.

• Archive: retains all of the chain history and state, so you can essentially replay any block. This takes the most disk space and generally should not be used unless you really need a local archive node.

Select the mode using the "History Mode" dropdown in the Execution Client settings. You will need to resync your Execution Client if you change modes.

⚠️ Anyone that had Archive Mode enabled before this update will need to change the History Mode back to "Archive" in order to continue using it.

Clients

• Updated Besu to v25.10.0.

• Updated Geth to v1.16.5.

• Updated Nethermind to v1.35.0.

• Updated Reth to v1.8.2.

• Updated Lighthouse to v8.0.0-rc.1 for test networks only.

• Updated Lodestar to v1.35.0.

• Updated Nimbus to v25.9.2.

• Updated Prysm to v6.1.2.

  • Hyperdrive now supports the official Prysm images published by Offchain Labs, rather than rolling our own custom image.

• Updated Teku to v25.9.3.

• Introduced Commit Boost PBS v0.8.0 for Mainnet, and v0.8.1-rc.4 for Hoodi.

Services

Config

• MEV-Boost has been renamed to PBS Client.

  • The mev-boost container has been replaced with pbs, so any commands that used the mev-boost container (such as hyperdrive service logs mev-boost should now be e.g. hyperdrive service logs pbs.

• Added support for Commit-Boost's PBS client. Support for MEV-Boost is still available, and users can now choose which one they want.

• Added opt-in pruning support for Prysm and Lodestar, with the "Enable Pruning" checkbox of the Beacon Node config page. This will delete all Beacon chain data older than 5 months, similar to the pruning mode that Nimbus has had for a while.

  • Note that when you first enable this, pruning will be started automatically and can take a long time; it may be faster to enable it and then checkpoint sync your Beacon Node from scratch.

• Added a "History Mode" dropdown in Execution Client settings. This supports Post-Merge (only retain data from after the merge), Full Node (retain all chain data except for non-recent state), and Archive (retain everything).

  • The "Archive Mode" dropdown has been removed from the Besu and Geth accordingly.
  • ⚠️ Anyone that had archive mode enabled before this update will need to change the History Mode back to "Archive" in order to continue using it.

StakeWise

• Updated the Stakewise Operator to v3.1.10.

  • This is the last client version that supports the current StakeWise v3 vault contracts used by the Nodeset private vault.

• Running hyperdrive stakewise validator status now sorts the output by Beacon index, in ascending order. Validators that don't have an index yet are at the bottom of the list.

• Added /info to the relay API in preparation for StakeWise Operator v4.

Misc

• Prysm's start scripts no longer rely on external utilities and work in a pure POSIX environment, meaning Hyperdrive now uses the official Prysm image.