Ethereum consensus client in Rust
This hotfix release includes several bug fixes related to the handling of blobs. Upgrading to this release should result in less cache misses, lower peak memory usage, reduced bandwidth and greater stability.
This is a medium priority release.
We recommend that all users upgrade at their convenience. We particularly recommend upgrading if you are seeing either of these logs:
Mar 13 10:26:50.229 WARN Peer sent invalid response to parent request., reason: ExtraBlocksReturned, peer_id: ..., service: sync
Mar 24 23:20:56.001 WARN Did not advance head state reason: Err(HeadMissingFromSnapshotCache(...)), service: state_advance
Since the release of v5.1.2 we have found a few more cases where Lighthouse could issue an excessive number of lookup requests for the same block. This would manifest as a warning log, followed by a loss of peers due to downscoring:
Mar 13 10:26:50.229 WARN Peer sent invalid response to parent request., reason: ExtraBlocksReturned, peer_id: ..., service: sync
The additional cases were related to concurrent lookups, and have been addressed in pull request #5488.
We found that when Lighthouse imported a block after a blob RPC request, it was failing to run fork choice. This had several knock-on effects: the head state would be absent from the snapshot cache, which would lead to cache misses and further errors. In some instances, the cache misses would lead to a spike in memory usage while snapshots were reloaded from disk.
Fork choice now runs after all block imports (implemented in #5475). Some snapshot cache misses may still occur. We are planning to further improve snapshot handling in a future release.
The size of the seen-cache for attestation gossip has been updated in pull request #5493 to accomodate the wider validity window for attestations post-Deneb. This should result in reduced load by preventing old duplicate attestations from being reprocessed.
The experimental light client server has been updated with Capella and Deneb support in pull request #4946. We do not yet recommend enabling it on mainnet. We will provide an update on the light client server in a future release.
None.
There is an outstanding bug in Lighthouse's UPnP implementation:
It can be worked around by running with --disable-upnp
and manual port forwarding. We are planning another release containing a fix soon.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium | Medium |
Non-Staking Users | Medium | --- |
See Update Priorities for more information about this table.
Lighthouse BNs and VCs from v5.0.0 and v5.1.0/v5.1.1/v5.1.2/v5.1.3 are intercompatible. However, we recommend that users update both the VC and BN to v5.1.3 if upgrading.
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.1.3-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.3-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.3-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.3-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.3-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.3-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.3-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.3-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.1.3 | sigp/lighthouse |
This hotfix release includes a block lookup efficiency fix, a fix to stop propagation of slashings for attesters who have already been slashed, a fix to the --disable-upnp
flag, and a couple of metric fixes.
This is a medium priority release.
We recommend you upgrade if you are seeing this log:
Mar 13 10:26:50.229 WARN Peer sent invalid response to parent request., reason: ExtraBlocksReturned, peer_id: ..., service: sync
We've had a couple reports of users seeing this log:
Mar 13 10:26:50.229 WARN Peer sent invalid response to parent request., reason: ExtraBlocksReturned, peer_id: ..., service: sync
This is a result of Lighthouse making duplicate requests to peers for the same block. This has been fixed in (#5432). If you are seeing this log, we recommend you upgrade.
Other client teams have notified us that Lighthouse propagates slashing messages for validators that have already been slashed. These messages are useless from the network's perspective so should be ignored (thanks @nisdas from Prysm). This has been resolved in (#5385).
The --disable-upnp
was inneffective previously, but this has been fixed in (#5449).
Additionally this hotfix includes fixes to some metrics (#5404 and #5427).
None.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium | Medium |
Non-Staking Users | Medium | --- |
See Update Priorities for more information about this table.
Lighthouse BNs and VCs from v5.0.0 and v5.1.0/v5.1.1/v5.1.2 are intercompatible. However, we recommend that users update both the VC and BN to v5.1.2 if upgrading.
Changes relative to v5.1.1
:
nat_open
metrics report (#5427)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.1.2-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.2-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.2-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.2-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.2-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.2-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.2-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.2-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.1.2 | sigp/lighthouse |
This hotfix release is identical to v5.1.0, with the exception of some build system fixes for macOS.
If you have already updated to v5.1.0 then you can ignore this release.
The rest of the release notes describe the changes relative to v5.0.0.
This high-priority release includes a fix to ensure validator's messages are published on the network (#5357). Additionally, out-of-memory crashes are prevented by reducing peak memory usage (#5270).
This release (v5.1.1) and the previous v5 releases (v5.1.0 and v5.0.0) support the Deneb upgrade on March 13, 2024 at 13:55 UTC. Users who are already running v5.0.0 are not required to upgrade to v5.1.0/v5.1.1 before Deneb, but it is recommended.
Notable changes in this release:
--state-cache-size
(#5270)PATCH /lighthouse/validators/{validator_pubkey}
VC HTTP API endpoint has been optimised (#5064)WARN Not enough time for a discovery search
has been fixed (#5305)Lighthouse no longer supports the Milagro BLS library (#5298). This library was not recommended for production use and had to be manually enabled at compile time. We do not expect this change to impact users.
The minimum supported Rust version (MSRV) was updated to 1.75.0 in a previous release (v5.0.0). Users who compile from source (i.e., not Docker or pre-built binary users) will receive the following error if they are using an earlier version of Rust:
lighthouse v5.1.0 (/home/sigp/lighthouse/lighthouse) cannot be built because it requires rustc 1.75 or newer
Users can typically obtain the latest version of Rust by running rustup update
.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | High | High |
Non-Staking Users | High | --- |
See Update Priorities for more information about this table.
Lighthouse BNs and VCs from v5.0.0 and v5.1.0/v5.1.1 are intercompatible. However, we recommend that users update both the VC and BN to v5.1.0/v5.1.1.
Changes relative to v5.0.0
:
cc
(#5393)AddrInUse
error in cli tests (#5266)whoami
(#5351)apt update
before install. (#5295)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.1.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.1.1 | sigp/lighthouse |
:warning: You should not run this alpha release supporting mainnet validators :warning:
If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.
This is an alpha release of upcoming changes to Lighthouse which improve disk usage and state management.
We are making this alpha release so that expert users may help us test these improvements. It is not backwards-compatible and not recommended for mainnet validators. Our current plan is to stabilise these changes shortly after the Deneb hard fork on mainnet.
For the adventurous, the main benefits are:
--reconstruct-historic-states
.We hope that this is useful for running block explorers and supporting other beacon chain analytics. We are using it internally at SigP to run some of our analytics.
This release includes all the latest changes from v5.1.0 including Deneb on mainnet and the fixes for attestation performance. Check out the release notes for v5.1.0 for more information. Note that we do not recommend running mainnet validators using tree-states
.
There are no substantial tree-states
specific changes in this release, as we have been focussed on cleaning up the branch and preparing it for review & merge.
This release is backwards compatible with v5.0.111-exp, v4.6.222-exp, v4.6.111-exp, v4.5.444-exp, v4.5.222-exp and v4.4.111-exp.
This release is not backwards compatible with stable Lighthouse or tree-states
releases prior to v4.4.111-exp. It uses a different database schema (v24) for which no automatic upgrade or downgrade is implemented. We intend to implement an automatic upgrade process once the new schema is finalized. A re-sync might be required to run future versions of tree-states
. This release's schema might be the final iteration.
Please only run this release if you are willing to re-sync now, and again in several weeks/months.
There are several breaking changes to CLI flags:
--unsafe-and-dangerous-mode
must be supplied. This is to prevent accidental upgrades to the release by users who don't know what they're getting themselves into. Unfortunately we found that far too many people accidentally ran previous tree-states
releases on mainnet.--slots-per-restore-point
and --historic-state-cache-size
are deprecated and no longer necessary due to the freezer database using hierarchical diffs.--db-migration-period
from tree-states
v4.2.0-999-exp release is gone and has been replaced by --epochs-per-migration
(same name as stable
).Expect a few sharp edges. Some things you may run into:
WARN Parent state is not advanced
is logged excessively during sync. This is harmless, albeit annoying.If you observe any panics, crashes or major performance regressions, please open an issue!
Build the v5.1.222-exp
tag.
cc
(#5392)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.1.222-exp-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.222-exp-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.222-exp-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.222-exp-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.222-exp-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.222-exp-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.222-exp-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.222-exp-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.1.222-exp | sigp/lighthouse |
This high-priority release includes a fix to ensure validator's messages are published on the network (#5357). Additionally, out-of-memory crashes are prevented by reducing peak memory usage (#5270).
This release (v5.1.0) and the previous release (v5.0.0) both support the Deneb upgrade on March 13, 2024 at 13:55 UTC. Users who are already running v5.0.0 are not required to upgrade to v5.1.0 before Deneb, but it is recommended.
Notable changes in this release:
--state-cache-size
(#5270)PATCH /lighthouse/validators/{validator_pubkey}
VC HTTP API endpoint has been optimised (#5064)WARN Not enough time for a discovery search
has been fixed (#5305)Lighthouse no longer supports the Milagro BLS library (#5298). This library was not recommended for production use and had to be manually enabled at compile time. We do not expect this change to impact users.
The minimum supported Rust version (MSRV) was updated to 1.75.0 in a previous release (v5.0.0). Users who compile from source (i.e., not Docker or pre-built binary users) will receive the following error if they are using an earlier version of Rust:
lighthouse v5.1.0 (/home/sigp/lighthouse/lighthouse) cannot be built because it requires rustc 1.75 or newer
Users can typically obtain the latest version of Rust by running rustup update
.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | High | High |
Non-Staking Users | High | --- |
See Update Priorities for more information about this table.
Lighthouse BNs and VCs from v5.0.0 and v5.1.0 are intercompatible. However, we recommend that users update both the VC and BN to v5.1.0.
AddrInUse
error in cli tests (#5266)whoami
(#5351)apt update
before install. (#5295)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.1.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.1.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.1.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.1.0 | sigp/lighthouse |
:warning: You should not run this alpha release supporting mainnet validators :warning:
If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.
This is an alpha release of upcoming changes to Lighthouse which improve disk usage and state management.
We are making this alpha release so that expert users may help us test these improvements. It is not backwards-compatible and not recommended for mainnet validators. Our current plan is to stabilise these changes shortly after the Deneb hard fork on mainnet.
For the adventurous, the main benefits are:
--reconstruct-historic-states
.We hope that this is useful for running block explorers and supporting other beacon chain analytics. We are using it internally at SigP to run some of our analytics.
This release includes all the latest changes from v5.0.0 including Deneb on mainnet. Check out the release notes for v5.0.0 for more information. Note that we do not recommend running mainnet validators using tree-states
.
There are no substantial tree-states
specific changes in this release, as we have been focussed on cleaning up the branch and preparing it for review & merge.
This release is backwards compatible with v4.6.222-exp, v4.6.111-exp, v4.5.444-exp, v4.5.222-exp and v4.4.111-exp.
This release is not backwards compatible with stable Lighthouse or tree-states
releases prior to v4.4.111-exp. It uses a different database schema (v24) for which no automatic upgrade or downgrade is implemented. We intend to implement an automatic upgrade process once the new schema is finalized. A re-sync might be required to run future versions of tree-states
. This release's schema might be the final iteration.
Please only run this release if you are willing to re-sync now, and again in several weeks/months.
There are several breaking changes to CLI flags:
--unsafe-and-dangerous-mode
must be supplied. This is to prevent accidental upgrades to the release by users who don't know what they're getting themselves into. Unfortunately we found that far too many people accidentally ran previous tree-states
releases on mainnet.--slots-per-restore-point
and --historic-state-cache-size
are deprecated and no longer necessary due to the freezer database using hierarchical diffs.--db-migration-period
from tree-states
v4.2.0-999-exp release is gone and has been replaced by --epochs-per-migration
(same name as stable
).Expect a few sharp edges. Some things you may run into:
WARN Parent state is not advanced
is logged excessively during sync. This is harmless, albeit annoying.If you observe any panics, crashes or major performance regressions, please open an issue!
Build the v5.0.111-exp
tag.
lighthouse db diff
(#5171)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.0.111-exp-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.111-exp-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.111-exp-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.111-exp-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.0.111-exp-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.0.111-exp-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.111-exp-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.111-exp-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.0.111-exp | sigp/lighthouse |
This release is mandatory for all Mainnet and Gnosis users. It enables the Deneb/Cancun ("Dencun") upgrade on:
Any node which is not updated to a Lighthouse v5.x.x release by this time will stop following the chain and will need to be resynced. For stakers, this would result in missed rewards and penalties.
All Mainnet Lighthouse users must update their BNs and VCs to v5.0.0 by March 13, 2024, 01:55:35pm UTC.
This release also contains various bug-fixes, optimisations and new features:
--builder-proposals
(#5151)distributed
flag to VC to enable support for DVT (#4867)There are a few breaking changes. Please see the section on Breaking Changes below.
The Deneb/Cancun ("Dencun") upgrade will occur on mainnet at:
All Lighthouse Beacon Nodes and Validator Clients must be upgraded to a v5.x.x release to ensure they follow the correct chain. The following table demonstrates which releases are reliable, Dencun-ready releases:
Release | Is Reliable, Dencun-Ready v5.x.x Release |
---|---|
v4.6.0 | ❌ No |
v5.0.0 | ✅ Yes |
Any release after v5.0.0 | ✅ Yes |
To be Dencun ready, user will need to:
There are no new flags to be added or removed for the Dencun upgrade, simply upgrade and wait.
Lighthouse will start periodically emitting the following logs two weeks before the Dencun upgrade (28th of February):
Not ready for Deneb
if Lighthouse has detected that the execution engine is too outdated to support Cancun.Ready for Deneb
if Lighthouse has detected a modern execution engine release.Just because Lighthouse is logging Ready for Deneb
does not indicate that your execution engine is on the correct version. There is no way for Lighthouse to determine this exactly and users are responsible for ensuring that their execution engine is using the latest release.
Note that with blobs (EIP-4844) being added in Dencun, each node is expected to consume additional disk space, with an expected average of 50 GiB, up to a maximum of 103GiB for blobs.
--builder-proposals
(#5151)There was a bug in the logic for the --builder-proposals
VC flag introduced in Lighthouse v4.6.0. Rather than setting the boost to 0 when builder-propsals
was false, it was setting it to 0 when builder-proposals
was true. Users have been using --builder-boost-factor 100
as a workaround until now.
This issue has been resolved and the preference can now be enabled with the --builder-proposals
.
See https://github.com/sigp/lighthouse/pull/5151.
This release contains breaking changes, all of which are detailed below.
The standard liveness endpoint (/eth/v1/validator/liveness
) was introduced in the previous version of Lighthouse but did not accept string-encoded validator indices, which is part of the specification. This has been fixed and will require updating both BN and VC to the latest version.
See https://github.com/sigp/lighthouse/pull/5184.
The minimum supported Rust version (MSRV) has been updated to 1.75.0. Users who compile from source (i.e., not Docker or pre-built binary users) will receive the following error if they are using an earlier version of Rust:
lighthouse v5.0.0 (/home/sigp/lighthouse/lighthouse) cannot be built because it requires rustc 1.75 or newer
Users can typically obtain the latest version of Rust by running rustup update
.
lighthouse/beacon/states/{state_id}/ssz
This endpoint is redundant and no longer required, because equivalent endpoints now exist in the standard beacon API.
See https://github.com/sigp/lighthouse/pull/5065.
--checkpoint-blobs
flag for manual checkpoint syncingFor users checkpoint syncing manually (previously using --checkpoint-block
and --checkpoint-state
), there is now an additional mandatory --checkpoint-blobs
flag for users to supply the checkpoint blobs. Users using the --checkpoint-sync
flag are not affected.
See https://github.com/sigp/lighthouse/pull/5252.
--disable-duplicate-warn-logs
This BN flag was introduced in Lighthouse v4.6.0. It has now become the default behaviour in this version, where gossipsub duplicate logs are debug
level instead of warn
, thus deprecating this flag.
See https://github.com/sigp/lighthouse/pull/5163.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | High | High |
Non-Staking Users | High | --- |
See Update Priorities more information about this table.
distributed
flag to VC to enable support for DVT (#4867)curve25519-dalek
patch (#5214)prune-states
(#5142)blobs_by_root_request
rpc limit. (#5181)--builder-proposals
(#5151)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v5.0.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.0.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v5.0.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v5.0.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v5.0.0 | sigp/lighthouse |
:warning: You should not run this alpha release supporting mainnet validators :warning:
If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.
This is an alpha release of upcoming changes to Lighthouse which improve disk usage and state management.
We are making this alpha release so that expert users may help us test these improvements. It is not backwards-compatible and not recommended for mainnet validators. Our current plan is to stabilise these changes shortly after the Deneb hard fork on mainnet.
For the adventurous, the main benefits are:
--reconstruct-historic-states
.We hope that this is useful for running block explorers and supporting other beacon chain analytics. We are using it internally at SigP to run some of our analytics.
This release includes all the latest changes from v4.6.0 including Deneb on Sepolia, Holesky and Chiado. Check out the release notes for v4.6.0 for more information.
In terms of tree-states specific changes, we have:
lighthouse db prune-states
(https://github.com/sigp/lighthouse/pull/5097).hierarchy-exponents
after pruning states.hierarchy-exponents
that do diffs within a single epoch (e.g. --hierarchy-exponents "0,2,4,6,8"
).This release is backwards compatible with v4.6.111-exp, v4.5.444-exp, v4.5.222-exp and v4.4.111-exp.
This release is not backwards compatible with stable Lighthouse or tree-states
releases prior to v4.4.111-exp. It uses a different database schema (v24) for which no automatic upgrade or downgrade is implemented. We intend to implement an automatic upgrade process once the new schema is finalized. A re-sync might be required to run future versions of tree-states
. This release's schema might be the final iteration.
Please only run this release if you are willing to re-sync now, and again in several weeks/months.
There are several breaking changes to CLI flags:
--unsafe-and-dangerous-mode
must be supplied. This is to prevent accidental upgrades to the release by users who don't know what they're getting themselves into. Unfortunately we found that far too many people accidentally ran previous tree-states
releases on mainnet.--slots-per-restore-point
and --historic-state-cache-size
are deprecated and no longer necessary due to the freezer database using hierarchical diffs.--db-migration-period
from tree-states
v4.2.0-999-exp release is gone and has been replaced by --epochs-per-migration
(same name as stable
).Expect a few sharp edges. Some things you may run into:
WARN Parent state is not advanced
is logged excessively during sync. This is harmless, albeit annoying.If you observe any panics, crashes or major performance regressions, please open an issue!
Build the v4.6.222-exp
tag.
fsync
during backfill to prevent DB corruption (#5144)purge-db
(#5081)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v4.6.222-exp-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.222-exp-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.222-exp-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.222-exp-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.6.222-exp-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.6.222-exp-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.222-exp-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.222-exp-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v4.6.222-exp | sigp/lighthouse |
This medium-priority release provides valuable features, performance improvements and bug fixes for mainnet users. It also enables the Deneb upgrade on the Sepolia, Holesky and Chiado testnets.
The Deneb upgrades are scheduled for:
All Sepolia, Holesky and Chiado users must upgrade both their testnet VCs and BNs before the respective upgrade time. Failing to upgrade will require the user to manually resync their nodes.
This release also includes a variety of new features and a few breaking changes. Please see the section on Breaking Changes below.
Users who rely exclusively on builder blocks (e.g., RocketPool) should be sure to read the "Standard block V3 endpoint" section.
The new produce block V3 API has been standardized across clients (https://github.com/ethereum/beacon-APIs/pull/339). This endpoint allows us to give validators more control over whether to prefer a local or builder payload during proposals. The validator client will not use this new endpoint by default; it must be enabled by adding --produce-block-v3
to the validator client. This mode will be enabled by default in the future. With the advent of V3, the following BN flags will no longer be supported:
--builder-profit-threshold
--always-prefer-builder-payload
Please refer to the Breaking Changes section below for detailed information and necessary actions.
Per-validator configuration of whether to use an external builder is still possible via the builder_proposals
field. This has been extended to allow each validator to specify one of the following:
builder_boost_factor
: a percentage multiplier to apply to the builder's payload value when choosing between a builder proposal and a local proposal.prefer_builder_proposals
: a boolean flag to indicate preference for blocks constructed by builders, regardless of payload value.The block V3 endpoint also allows validators working with multiple beacon nodes (e.g. via Vouch) to compare rewards between beacon nodes before selecting payloads. This is done by exposing the consensus rewards of the block, as well as the execution rewards of the payload directly to the validator.
On the block V2 endpoints, if a validator is using the blinded block flow and gets exceptionally unlucky, falling back to another beacon node at an inopportune time, it could miss its proposal. This is no longer possible with the V3 endpoint.
NOTE: If you are using --builder-proposals
you must also set --builder-boost-factor 100
to work around a bug, see below.
There is a bug in the validator client flag --builder-proposals
which causes the VC not to use builder proposals when the following conditions are met:
--builder-proposals
is set, and--produce-block-v3
flag is set, and--builder-boost-factor
, --prefer-builder-proposals
, or per-validator builder_boost_factor
.The bug has been identified and fixed in this PR which will part of our next release: https://github.com/sigp/lighthouse/pull/5151.
Until then, the workaround is to add --builder-boost-factor 100
to the validator client flags. The 100% setting is the intended default, and will cause Lighthouse to use the builder payload only when it is more profitable than a local payload. You may also set a different value (see Breaking Changes for more information on this flag).
Recent changes in the execution APIs have also provided a new should_override_builder
field along with each local payload. Lighthouse will check if this is set to true
and return a local payload if it is. This field allows the execution layer to monitor the mempool and look for signs of ongoing censorship from block builders. It can signal its suggestion to use a local payload to combat censorship to the consensus layer to select a local payload in these scenarios.
Validator clients can now be configured to publish messages to all connected beacon nodes using the --broadcast
flag. This allows users to improve redundancy when publishing messages related to validator duties. The flag can be configured with specific message types (attestations
,sync-committee
,blocks
, subscriptions
). It can also be configured to make sure subscriptions are not sent to all beacon nodes (--broadcast none
). This replaces the now deprecated --disable-run-on-all
flag. Thanks @uvizhe for the contribution!
More information is available in the Redundancy section of the Lighthouse book.
(see https://github.com/sigp/lighthouse/pull/4920)
Some extensive changes have been made to the networking components in this release. We have focused on a number of performance and structural changes to the gossipsub protocol and discovery mechanism. Some of the main gossipsub changes are listed in issue (https://github.com/sigp/lighthouse/issues/4918). An overview of the primary changes are:
The validator client now uses the standard liveness endpoint for doppelganger protection (see https://github.com/sigp/lighthouse/pull/4853). This makes the Lighthouse VC's doppelganger protection compatible with any beacon node that implements the standard liveness endpoint.
The Lighthouse BN supports the following new HTTP APIs:
POST
APIs for fetching validators & balances in bulk: https://github.com/sigp/lighthouse/pull/4872
GET /eth/v1/beacon/blob_sidecars
for Deneb (https://ethereum.github.io/beacon-APIs/#/Beacon/getBlobSidecars)The Lighthouse VC now uses the liveness endpoint from the standard API, rather than a custom Lightouse endpoint (#4853). This only affects the --enable-doppelganger-protection
feature.
When Doppelganger protection is enabled, Lighthouse VCs from this version will not work with Lighthouse BNs prior to v4.4.1 (released Sept. 2023).
To support Deneb, this release includes an automatic upgrade from v17 to v19.
Some Goerli users might notice a delay of one or two minutes when starting up for the first time after the upgrade. Lighthouse is correcting a issue with blob storage after checkpoint sync, no user intervention is required (see: https://github.com/sigp/lighthouse/pull/5119).
To downgrade, follow the instructions in the book for Database Migrations.
Genesis sync will no longer work without the use of --allow-insecure-genesis-sync
. Checkpoint sync should always be preferred to protect yourself from long-range attacks. Additionally, genesis sync is not compatible with data availability checks that are added in Deneb. On chains that have been running for less than ~2 weeks, genesis sync will still work without --allow-insecure-genesis-sync
, so this change won't impact local testnets or short-lived testnets.
The following flags have been deprecated in prior releases and are being removed. Lighthouse will not start up if any are included in the startup command.
--spec
for lighthouse bn
--eth1-endpoint
for lighthouse bn
--eth1-endpoints
for lighthouse bn
--beacon-node
for lighthouse vc
--server
for lighthouse vc
--delete-lockfiles
for lighthouse vc
--allow-unsynced
for lighthouse vc
--strict-fee-recipient
for lighthouse vc
--merge
for lighthouse bn
--count-unrealized
for lighthouse bn
--count-unrealized-full
for lighthouse bn
--http-disable-legacy-spec
for lighthouse bn
--minify
for lighthouse account validator slashing-protection import/export
(see https://github.com/sigp/lighthouse/pull/4906)
The following flags should be removed from setups. If they are not removed, they will have no effect.
--builder-profit-threshold
BN flagPrefer using the -min-bid
flag in mev-boost
. Alternatively, the new --builder-boost-factor
VC flag can be used to achieve a similar effect using a percentage multiplier (see https://github.com/sigp/lighthouse/pull/5086). For example, using --builder-boost-factor 120
increases a builder proposal's value by 20% for comparison, effectively making it 120% of its actual value and thereby favoring it over a local payload by this margin. Alternatively, to prefer local payloads, set a value lower than 100. For example --builder-boost-factor 50
will only use the builder payload if it is 2x more profitable than the local payload. To use builder boost flag, --produce-block-v3
must also be enabled.
--always-prefer-builder-payload
BN flagUse the new and equivalent --prefer-builder-proposals
VC flag to restore this functionality (see https://github.com/sigp/lighthouse/pull/5086). You must also use the --produce-block-v3
flag.
--disable-run-on-all
VC flagThis flag has been superseded by the --broadcast
flag. Use --broadcast none
to disable broadcast to all nodes (see https://github.com/sigp/lighthouse/pull/4920).
The minimum supported Rust version has been updated from 1.69.0 to 1.73.0
Users who compile from source (i.e., not Docker or pre-built binary users) will receive the following error if they are using an earlier version of Rust:
lighthouse v4.6.0 (/home/sigp/lighthouse/lighthouse)` cannot be built because it requires rustc 1.73.0 or newer
Users can typically obtain the latest version of Rust by running rustup update
.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium | Medium |
Non-Staking Users | Medium | --- |
See Update Priorities more information about this table.
The Beacon Node must be running v4.4.1 or later to support a VC running this release. We recommend updating both the VC and BN to the same release.
This release is high-priority for Sepolia, Holesky and Chiado users. Those users must update both the VC and BN.
A full list of changes can be viewed at: https://github.com/sigp/lighthouse/compare/v4.5.0...v4.6.0.
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v4.6.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.6.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.6.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v4.6.0 | sigp/lighthouse |
:warning: You should not run this alpha release supporting mainnet validators :warning:
If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.
This is an alpha release of upcoming changes to Lighthouse which improve disk usage and state management.
We are making this alpha release so that expert users may help us test these improvements. It is not backwards-compatible and not recommended for mainnet validators. Our current plan is to stabilise these changes shortly after the Deneb hard fork on mainnet.
For the adventurous, the main benefits are:
--reconstruct-historic-states
.We hope that this is useful for running block explorers and supporting other beacon chain analytics. We are using it internally at SigP to run some of our analytics.
This release includes all the latest changes from v4.6.0-rc.0 including Deneb-on-Goerli and a fix for the networking OOM. Check out the release notes for v4.6.0-rc.0 for more information.
In terms of tree-states specific changes, we have:
This release is backwards compatible with v4.5.444-exp, v4.5.222-exp and v4.4.111-exp.
This release is not backwards compatible with stable Lighthouse or tree-states
releases prior to v4.4.111-exp. It uses a different database schema (v24) for which no automatic upgrade or downgrade is implemented. We intend to implement an automatic upgrade process once the new schema is finalized. A re-sync might be required to run future versions of tree-states
. This release's schema might be the final iteration.
Please only run this release if you are willing to re-sync now, and again in several weeks/months.
There are several breaking changes to CLI flags:
--unsafe-and-dangerous-mode
must be supplied. This is to prevent accidental upgrades to the release by users who don't know what they're getting themselves into. Unfortunately we found that far too many people accidentally ran previous tree-states
releases on mainnet.--slots-per-restore-point
and --historic-state-cache-size
are deprecated and no longer necessary due to the freezer database using hierarchical diffs.--db-migration-period
from tree-states
v4.2.0-999-exp release is gone and has been replaced by --epochs-per-migration
(same name as stable
).Expect a few sharp edges. Some things you may run into:
WARN Parent state is not advanced
is logged excessively during sync. This is harmless, albeit annoying.If you observe any panics, crashes or major performance regressions, please open an issue!
Build the v4.6.111-exp
tag.
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v4.6.111-exp-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.111-exp-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.111-exp-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.111-exp-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.6.111-exp-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.6.111-exp-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.111-exp-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.6.111-exp-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v4.6.111-exp | sigp/lighthouse |