v1.1.0

This is v1.1.0 of the StakeWise daemon for Hyperdrive. This is 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 API authorization can be passed in with the -k flag. It should be at least 48 bytes long.
  • The secret key for authorizing requests to the Hyperdrive daemon can be passed in with the -hk flag.
  • Thanks to @poupas for reporting this!

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.

Clients

• Updated StakeWise v3 Operator to v2.1.3.

Service

• The daemon no longer interfaces directly with the nodeset.io API. It now uses the nodeset.io client provided by the Hyperdrive daemon.

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

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

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

• Updated to Go 1.22.