Releases: attestantio/vouch
Release 1.9.0-alpha.5
This is an alpha feature release for Vouch.
This release is not suitable for running on mainnet. Please only run this release on testnets.
Major changes in this release include:
- additional metrics for sync committee validation
Major changes in prior alpha releases include:
- additional logging for sync committee participation
- upgrade go to version 1.22
- remove note about additional options required for Lodestar clients
- improvements to memory and CPU usage, especially with high numbers of validators
- add beaconblockproposer.builder-boost-factor
- allow Vouch to act as an MEV-boost client for non-Vouch validators
- increase proposal performance with new validator REST APIs
- allow Vouch to start with some consensus nodes unavailable
- reduce time and memory spent obtaining and verifying accounts
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Below no longer needed for Lodestar v1.20 onwards.
## Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.8.2
This is a maintenance release for Vouch 1.8.x. Changes include:
- update go-eth2-client dependency (compatibility with lodestar 1.20.0)
- use proposer V3 APIs
- do not error if proposal graffiti has been altered
This update is recommended only if you run lodestar 1.20.0, or if you are seeing errors with attempting to generate proposals to to the consensus client rewriting graffiti. Outside of these situations upgrading is optional.
Release 1.9.0-alpha.4
This is an alpha feature release for Vouch.
This release is not suitable for running on mainnet. Please only run this release on testnets.
Major changes in this release include:
- additional logging for sync committee participation
- upgrade go to version 1.22
- remove note about additional options required for Lodestar clients
Major changes in prior alpha releases include:
- improvements to memory and CPU usage, especially with high numbers of validators
- add beaconblockproposer.builder-boost-factor
- allow Vouch to act as an MEV-boost client for non-Vouch validators
- increase proposal performance with new validator REST APIs
- allow Vouch to start with some consensus nodes unavailable
- reduce time and memory spent obtaining and verifying accounts
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Below no longer needed for Lodestar v1.20 onwards.
## Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.9.0-alpha.3
This is an alpha feature release for Vouch.
This release is not suitable for running on mainnet. Please only run this release on testnets.
Major changes in this release include:
- improvements to memory and CPU usage, especially with high numbers of validators
- add beaconblockproposer.builder-boost-factor
Major changes in prior alpha releases include:
- allow Vouch to act as an MEV-boost client for non-Vouch validators
- increase proposal performance with new validator REST APIs
- allow Vouch to start with some consensus nodes unavailable
- reduce time and memory spent obtaining and verifying accounts
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.9.0-alpha.2
This is an alpha feature release for Vouch.
This release is not suitable for running on mainnet. Please only run this release on testnets.
Major changes in this release include:
- allow Vouch to act as an MEV-boost client for non-Vouch validators
- increase proposal performance with new validator REST APIs
Major changes in prior alpha releases include:
- allow Vouch to start with some consensus nodes unavailable
- reduce time and memory spent obtaining and verifying accounts
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.9.0-alpha.1
This is an alpha feature release for Vouch.
This release is not suitable for running on mainnet. Please only run this release on testnets.
Major changes in this release include:
- allow Vouch to start with some consensus nodes unavailable
- reduce time and memory spent obtaining and verifying accounts
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.8.1
This is a maintenance release for Vouch 1.8.x. Changes include:
- ensure proposer-config-check command operates correctly
- avoid crash by suitably locking a controller read/write map
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.8.0
This is a feature release for Vouch. Highlights include:
- support Deneb
- fetch blinded and unblinded proposals in parallel to speed up block production
- compose multiclients from clients, reducing connections to beacon nodes
- add option to attempt unblinding of payloads from all contacted relays
- add "majority" attestation data strategy
- start validator registrations randomly in middle 80% of each epoch, to avoid overloading relays
- reduce CPU and memory requirements for refreshing validator information
- implement exclusion list for builders
Plus the usual round of performance, stability and security updates. The full list of changes can be found in CHANGELOG.md.
This release is required to enable Vouch to work with chains that have undergone the Deneb upgrade. Upgrades must take place prior to 13th March 2024 to continue validating.
Notes for Prysm and Lodestar
Prysm
Prysm must be started with the --enable-debug-rpc-endpoints option for Vouch to operate correctly.
Lodestar
Lodestar must be started with the --rest.namespace=beacon,config,events,node,validator,lightclient,debug option for Vouch to operate correctly.
Release 1.8.0-beta.3
This is a beta release. Please do not use this for production systems.
This is a beta feature release for Vouch. Changes from beta 1 include:
- do not use compression between Vouch and Dirk, as some Dirk instances do not support it
Usage with Prysm
To use Vouch with prysm we require the additional command-line flag --enable-debug-rpc-endpoints on the beacon node.
Changes include:
- support Deneb beta
- fetch blinded and unblinded proposals in parallel to speed up block production
- compose multiclients from clients, reducing connections to beacon nodes
- start validator registrations randomly in middle 80% of each epoch, to avoid overloading relays
- reduce CPU and memory requirements for refreshing validator information
- implement exclusion list for builders
- add option to attempt unblinding of payloads from all contacted relays
- add "majority" attestation data strategy
Release 1.8.0-beta.1
This is a beta release. Please do not use this for production systems.
This is a beta feature release for Vouch. Changes include:
- support Deneb beta
- fetch blinded and unblinded proposals in parallel to speed up block production
- compose multiclients from clients, reducing connections to beacon nodes
- start validator registrations randomly in middle 80% of each epoch, to avoid overloading relays
- reduce CPU and memory requirements for refreshing validator information
- implement exclusion list for builders
- add option to attempt unblinding of payloads from all contacted relays
- add "majority" attestation data strategy