v1.3.0

This is v1.3.0 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 Mainnet that haven't manually updated their clients to Fusaka-ready versions. Fusaka will be deployed to Mainnet on 2025-12-03 21:49:11 UTC.

---

PBS Client (formerly MEV-Boost) Changes

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.11.0.

• Updated Geth to v1.16.7.

• Updated Nethermind to v1.35.2.

• Updated Reth to v1.9.1.

• Updated Lighthouse to v8.0.0.

• Updated Lodestar to v1.36.0.

• Updated Nimbus to v25.11.0.

• Updated Prysm to v7.0.0.

  • Hyperdrive now supports the official Prysm images published by Offchain Labs, rather than rolling our own custom image.
  • ⚠️ if you encounter a SIGSEGV with Prysm's Beacon Node after updating, just do a quick checkpoint sync with hyperdrive service resync-bn to regenerate its database.

• Updated Teku to v25.11.0.

• Updated MEV-Boost to v1.10.

• Introduced Commit Boost PBS v0.9.2.

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.

v1.3.0 Beta 1

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.

v1.2.2

This is v1.2.2 of Hyperdrive.

This includes some client updates, including the StakeWise Operator with its own optimizations that make Stakewise oracle approval happen faster.

This is a medium priority update for all users.

---

Clients

• Updated Geth to v1.15.11.

• Updated Nethermind to v1.31.11.

• Updated Reth to v1.4.3.

• Updated Lodestar to v1.30.0.

• Updated Nimbus to v25.5.0.

• Updated Prysm to v6.0.3.

Services

Config

• Changing the Auto TX Gas Threshold now restarts the StakeWise Operator container.
• Lowered the default auto TX gas threshold on new installs from 20 gwei to 8 gwei.

StakeWise

• Updated the Stakewise Operator to v3.1.6.
  • This update will no longer retry failed deposit approval requests to the StakeWise oracles, which significantly speeds up the deposit process for NodeSet node operators.

Misc

• Prysm's start scripts no longer rely on external utilities and work in a pure POSIX environment.

v1.2.1

This is v1.2.1 of Hyperdrive.

This includes some client updates, bug fixes, and optimizations to the StakeWise module. It also removes Holesky from the list of default networks.

⚠️ All Mainnet users must update to at least v1.2.0 before the Pectra upgrade on epoch 364032, May 7 2025 - 10:05:11 AM UTC.

If you are not on v1.2.0 yet, this is a required update.

If you are on v1.2.0 but use Nimbus, this is a high priority update unless you manually updated your client to v25.4.1 already.

For all other users on v1.2.0 already, this is a medium priority update. Update at your convenience.

---

Deprecations

• The Holesky network has been removed from the default networks. Users upgrading from a previous version will still see it presented as an option, because the network definitions on-disk are not automatically removed. That being said, if you're still using Holesky, please migrate to the new Hoodi testnet.

Clients

• Updated Geth to v1.15.10.

• Updated Lighthouse to v7.0.1.

• Updated Nimbus to v25.4.1.

Services

Core

• Fixed a bug with wallet init; you can now generate new wallets properly.

StakeWise

• When the StakeWise operator requests new deposit info, the daemon will now scan the latest deposit event first before querying nodeset.io's available validator limit. This keeps the available key scan up-to-date and reduces the amount of blocks to scan during each request.

• The daemon no longer scans the Beacon chain and pending deposit queue for a validator once it's already been scanned, as long as the deposit event scan is up to date.

• Scanning the deposit log no longer returns an error if the latest head block has already been scanned.

CLI

• stakewise wallet generate-keys will now restart the VC if an error occurs in the middle of the operation.

• When stakewise wallet recover-keys completes, or if it encounters an error, it will now ask if you've attested with the recovered keys in the last 15 minutes before restarting the VC, to prevent accidental slashing.

v1.2.0

This is v1.2.0 of Hyperdrive.

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

⚠️ This also updates all clients to versions that are ready for Pectra on Mainnet (epoch 364032, May 7 2025 - 10:05:11 AM UTC).
It is required for all Mainnet users before that time.

---

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.

---

Patch Notes (Including Beta Notes)

Deprecations

• The Holesky network is now deprecated and will be removed in a future release. If you're still using Holesky, please migrate to the new Hoodi testnet.

Clients

• Updated Besu to v25.4.1.

• Updated Geth to v1.15.9.

  • The supermajority warning has been removed from Geth, as it is now at 41% of the network.

• Updated Reth to v1.3.12.

  • Reth has been modified to preserve all event logs for all contracts (starting from the deposit contract deployment block).
  • If you previously used Reth without manually specifying this behavior, you will need to resync it to regenerate the events that StakeWise needs.

• Updated Nethermind to v1.13.9.

• Updated Lighthouse to v7.0.0.

• Updated Lodestar to v1.29.0.

• Updated Nimbus to v25.4.0.

• Updated Prysm to v6.0.0.

• Updated Teku to v25.4.1.

• Updated MEV-Boost to v1.9.

• Updated the Node Exporter to v1.9.1.

Services

Core

• MEV Boost is now supported on Hoodi.
• Manual installation via the install script now updates the service containers again (unless the --no-restart flag is specified).

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:
  • nodeset has been removed.
  • status has been removed.
  • 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 for Reth: State Prune Distance controls the number of blocks Reth keeps in its state cache (from the chain head). This is needed to query the chain using previous states.
• 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

• Updated to Go v1.24.
• The GPG key used to sign release artifacts has been updated to v2.

v1.2.0 Beta 1

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.

v1.1.4

This is v1.1.4 of Hyperdrive.

This updates the Ethereum clients to add support for the new Hoodi testnet. Hoodi is be the next-generation of public Ethereum testnet, superseding Holesky (which we now consider to be deprecated). Over time we expect many protocols to migrate from Holesky to Hoodi.

For mainnet users:
This is a recommended update if you use Besu, Lodestar, or Prysm because the latest client versions have some important fixes and optimizations. For everyone else, it's a low priority.

For testnet users:
This is recommended for everyone because it includes fixes that will help resync Holesky after the failed Pectra upgrade, and provides the ability to sync Hoodi clients for future usage as we transition away from Holesky.

Known Issues

• 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

• Added the Hoodi testnet, which will replace Holesky as the long-running Ethereum testnet.
  • Note that many protocols and contracts have not been deployed to Hoodi yet
  • MEV-Boost, StakeWise, and Constellation are currently disabled on Hoodi until the StakeWise and Rocket Pool contracts have been deployed to it respectively.
  • You are welcome to choose the network just to sync the chain so you're ready to use it later as module support is added.

Clients

• Updated Besu to v25.3.0.

• Updated Geth to v1.15.6.

• Updated Nethermind to v1.31.6.

• Updated Reth to v1.3.4.

• Updated Lodestar to v1.28.1.

• Updated Nimbus to v25.3.1.

• Updated Prysm to v5.3.2.

• Updated Teku to v25.3.0.

• Updated the Node Exporter to v1.9.0.

Holesky and Hoodi only:

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

v1.1.3

This is v1.1.3 of Hyperdrive.

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).

This is a low priority update for Mainnet users; as many of the clients have gone large revisions to support Pectra, you are welcome to wait before upgrading if you'd like to give them more time to ensure stability.

Known Issues

• 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 v25.2.0.

• Updated Geth to v1.15.2.

• Updated Nethermind to v1.31.0.

• Updated Reth to v1.2.0.

• Updated Lodestar to v1.27.0.

• Updated Nimbus to v25.2.0.

• Updated Prysm to v5.3.0.

• Updated Teku to v25.2.0.

Holesky only:

• Updated Lighthouse to v7.0.0-beta.0.
• Updated MEV-Boost to v1.9-rc2.

v1.1.2

This is v1.1.2 of Hyperdrive.

This is a high priority update for any users that haven't updated their Geth client to v1.14.13 manually yet.

Known Issues

• 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

• Clients have increased the block gas limit from 30M to 36M by default.

• Updated Geth to v1.14.13.

  • This is an urgent security update; all users must update to at least this version ASAP.

• Updated Besu to v25.1.0.

• Updated Nethermind to v1.30.3.

• Updated Reth to v1.1.5.

• Updated Lighthouse to v6.0.1.

• Updated Lodestar to v1.25.0.

• Updated Nimbus to v25.1.0.

• Updated Prysm to v5.2.0.

  • Prysm now comes with QUIC support. Hyperdrive assigns 8001 by default, so if you want to take advantage of it, ensure that you forward that port in your router's configuration.

• Updated Teku to v25.1.0.

• Updated Prometheus to v2.55.1.

Configuration

• Removed the Holesky Staging network option from the default list.

CLI

• The CLI now supports bash autocompletion (contributed by @benv666). To use it, enter part of a command (such as hyperdrive constellation) and then press tab twice to autocomplete the available subcommands.
  • Note that this will not work if you're using a Bash alias for hyperdrive; check some of these options for such a setup.

Bug Fixes

• Fixed the URL used by Prysm for downloading the initial Holesky genesis state when setting it up for the first time.

v1.1.1

This is v1.1.1 of Hyperdrive. This fixes some issues reported by the community, and adds a few important features related to upgrading.

This is a high priority update for anyone that switched from Holesky to Mainnet on the same machine; in general, all users should plan to update when they are able to do so.

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.10.0.

• Updated Nethermind to v1.29.1.

• Updated Reth to v1.1.0.

• Updated Nimbus to v24.10.0.

• Updated Prysm to v5.1.2.

• Updated Teku to v24.10.3.

• Updated Prometheus to v2.55.0.

Service

• Installing Hyperdrive updates via apt update now prompts you to automatically restart the service so the daemons will be up to date.

• Automatic TXs will now ignore the gas threshold setting if a manual max fee is specified, as the threshold setting is only useful for dynamic network-based fees.

• Automatic TXs will now lower the max priority fee down to the max fee if the priority fee is greater than the max fee.

Config

• Switching networks in the service config network dropdown now properly loads the new network settings before starting the containers again.

  • Thanks to @jshufro for reporting this issue!

• The default max fee has been reduced to 20, and the default max priority fee has been reduced to 0.1. Note this only affects new users that are configuring Hyperdrive for the first time.

• The config validation routine will now work properly if you don't have any of the default MEV-Boost relays enabled but do have your own custom relays.

• Changing the contents of the MEV-Boost custom relay option will now properly flag the mev_boost container as needing to be restarted.

CLI

• Updating manually via hyperdrive service install will now automatically restart the service unless the --no-restart flag is provided.

• New global flags:

  • --itsf can be used to ignore TX simulation failues and sign / submit TXs anyway, even if they will revert.
  • --fgl can force a specific gas limit on all transactions created by whatever command is being run.
  • Do NOT use these unless you know what you're doing and have a good reason.

• The max fee selection prompt now properly shows the low and high transaction cost range, instead of just showing the high cost twice.

• Running Constellation or StakeWise commands without the respective module enabled will now print a proper warning message instead of a connection error.

• Manual TXs will now lower the max priority fee down to the max fee if the priority fee is greater than the max fee, and prompt the user with a notice before confirming the fee choices.

---

Modules

Constellation

• Fixed a bug that broke Constellation's automatic signed-exit upload task if an exit message was manually uploaded first via cs minipool upload-signed-exit.

• Fixed a bug that caused Rocket Pool contract queries to hang on single-CPU systems.

• New flags on cs minipool create:

  • --sbc skips checking if the node balance is sufficient to cover the temporary staking lockup.
  • --slc skips checking if Constellation has enough ETH and RPL in its vaults to fund a new minipool.
  • Only use these if you intend to sign (but not submit) a TX for manual bundling, or submit at a later date when the on-chain conditions become correct. Otherwise the transaction may revert when submitted and cost you gas fees!

• Removed delegate info from cs minipool status since it is not relevant for Constellation node operators.