Skip to content

Releases: sigp/lighthouse

EXPERIMENTAL Tree States v5.0.111

23 Feb 05:11
@github-actions github-actions
v5.0.111-exp
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
20f53e7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
EXPERIMENTAL Tree States v5.0.111 Pre-release
Pre-release

Disclaimer

⚠️ You should not run this alpha release supporting mainnet validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Summary

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:

  • Smaller disk footprint for archive nodes, <200GB total. Use checkpoint sync, and set the flag --reconstruct-historic-states.
  • Smaller disk footprint for regular nodes, <30GB.
  • Faster handling of re-orgs.
  • Faster restarts.
  • Less disk I/O.

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.

⚠️ Backwards Compatibility ⚠️

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:

  • The secret dummy flag --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.
  • The flags --slots-per-restore-point and --historic-state-cache-size are deprecated and no longer necessary due to the freezer database using hierarchical diffs.
  • The flag --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).

Known Issues

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.
  • Memory usage may be a bit higher when using the parallel HTTP cache (see #5112).

If you observe any panics, crashes or major performance regressions, please open an issue!

Building from source

Build the v5.0.111-exp tag.

All Changes

  • Tree states release v5.0.111-exp (#5276)
  • Fix tree-states tests (#5277)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Remove progressive balances mode (#5224)
  • Use epoch cache in block packing (#5223)
  • Delete unused epoch processing code (#5170)
  • Delete lighthouse db diff (#5171)

Binaries

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
Assets 18
Loading

Diablo Verde

21 Feb 04:02
@github-actions github-actions
v5.0.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: C850DDDF5D100807
Learn about vigilant mode.
b5bae6e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Diablo Verde

Summary

This release is mandatory for all Mainnet and Gnosis users. It enables the Deneb/Cancun ("Dencun") upgrade on:

  • Mainnet (#5233), which will occur on March 13, 2024, at 01:55:35 pm UTC; and
  • Gnosis (#5242), which will occur on March 11, 2024, at 06:30:20 pm UTC.

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:

  • Improve network parameters and increase target peer count to 100 (#5177)
  • Address high memory usage and out of memory issue (#5175,#5250)
  • Fix bug in --builder-proposals (#5151)
  • Optional slashing protection for remote keys (#4981)
  • Add distributed flag to VC to enable support for DVT (#4867)
  • Fix backfill stalling (#5192)
  • Fix off-by-one in backfill signature verification (#5120)
  • Handle unknown head during attestation publishing (#5010)

There are a few breaking changes. Please see the section on Breaking Changes below.

Mainnet Deneb/Cancun ("Dencun") Upgrade

The Deneb/Cancun ("Dencun") upgrade will occur on mainnet at:

  • Epoch 269568
  • March 13, 2024, 01:55:35pm UTC

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:

  • Upgrade their Lighthouse BN(s) to a v5.x.x release.
  • Upgrade their Lighthouse VC(s) to a v5.x.x release.
  • Upgrade their Execution Engine(s) to a Cancun-ready release:

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.

Fix bug in VC flag --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 #5151.

⚠️ Breaking Changes ⚠️

This release contains breaking changes, all of which are detailed below.

Validator Liveness endpoint now accepts string encoded indices

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 #5184.

Minimum Supported Rust Version 1.75.0

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.

Deleted custom endpoint 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 #5065.

New mandatory --checkpoint-blobs flag for manual checkpoint syncing

For 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 #5252.

Deprecated BN flag --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 #5163.

Update Priority

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.

All Changes

  • Release v5.0.0 (#5254)
  • Revert libp2p metrics (#4870) (#5265)
  • Deactivate RPC Connection Handler after goodbye message is sent (#5250)
  • Deprecate env_log flag in tracing layer (#5228)
  • Download checkpoint blobs during checkpoint sync (#5252)
  • Add Deneb fork epoch for Gnosis (#5242)
  • check the da cache and the attester cache in responding to RPC requests (#5138)
  • Verify Versioned Hashes During Optimistic Sync (#4832)
  • enable doppelganger tests for deneb (#5137)
  • Handle unknown head during attestation publishing (#5010)
  • Add distributed flag to VC to enable support for DVT (#4867)
  • Schedule Deneb on mainnet (#5233)
  • Quieten gossip republish logs (#5235)
  • Drop gossipsub stale messages when polling ConnectionHandler. (#5175)
  • validator liveness endpoint should accept string encoded indices (#5184)
  • Update to consensus spec v1.4.0-beta.6 (#5094)
  • Update to warp v0.3.6 (#5172)
  • Remove curve25519-dalek patch (#5214)
  • Improve database compaction and prune-states (#5142)
  • chore(docs): amend port guidance to enable QUIC support (#5029)
  • improve libp2p connected peer metrics (#4870)
  • Fix backfill stalling (#5192)
  • Improve network parameters (#5177)
  • increment peer per topic count on graft messages (#5212)
  • Downgrade gossipsub duplicate logs (#5163)
  • Fix failing cargo-udeps (#5203)
  • Update external LLVM version in preparation for Rust 1.76. (#5179)
  • Small typo in testing config (#5178)
  • Optional slashing protection for remote keys (#4981)
  • Remove unused js file in Lighthouse book (#5164)
  • Fix incorrect value set for blobs_by_root_request rpc limit. (#5181)
  • Fix Rust beta compiler errors (1.77) (#5180)
  • Config for web3signer keep-alive (#5007)
  • Re-disable block verification tests in debug (#5155)
  • Update gnosis bootnodes (#4986)
  • feat(config): add chiado bootnodes ENRs (#4727)
  • Properly log panics with slog (#5075)
  • Some updates in Lighthouse Book (#5000)
  • Prevent QUIC logs when quic is disabled (#5071)
  • Test backfill (#5109)
  • Add a note about validator monitoring in Lighthouse book (#5143)
  • Add gossipsub as a Lighthouse behaviour (#5066)
  • Move from igd to igd-next (#5068)
  • Update deterministic subnets upgrade to allow prefix computation (#4959)
  • Fix bug in --builder-proposals (#5151)
  • Compute recent lightclient updates (#4969)
  • Assume Content-Type is json for endpoints that require json (#4575)
  • Delete temporary mitigation for equivocation via RPC (#5037)
  • Make lcli docker image portable (#5069)
  • Update to the docs (#5106)
  • fix: update outdated links to external resources (#5018)
  • Remove custom SSZ beacon states route (#5065)
  • Fix off-by-one in backfill sig verification (#5120)
  • Increase attestation cache sizes (#5135)
  • #5102 Fix load_state_for_block_production metric mapping (#5103)
  • Update Mergify commit message template (#5126)
  • Replace backticks with single quotes (#5121)

Binaries

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 Sign...
Read more
Assets 18
Loading

EXPERIMENTAL Tree States v4.6.222

31 Jan 04:30
@github-actions github-actions
v4.6.222-exp
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
25bcd2a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
EXPERIMENTAL Tree States v4.6.222 Pre-release
Pre-release

Disclaimer

⚠️ You should not run this alpha release supporting mainnet validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Summary

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:

  • Smaller disk footprint for archive nodes, <200GB total. Use checkpoint sync, and set the flag --reconstruct-historic-states.
  • Smaller disk footprint for regular nodes, <30GB.
  • Faster handling of re-orgs.
  • Faster restarts.
  • Less disk I/O.

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:

  • Support for lighthouse db prune-states (#5097).
  • Support for changing the hierarchy-exponents after pruning states.
  • Support for hierarchy-exponents that do diffs within a single epoch (e.g. --hierarchy-exponents "0,2,4,6,8").
  • Bugfix for database corruption during backfill sync (#5144).

⚠️ Backwards Compatibility ⚠️

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:

  • The secret dummy flag --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.
  • The flags --slots-per-restore-point and --historic-state-cache-size are deprecated and no longer necessary due to the freezer database using hierarchical diffs.
  • The flag --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).

Known Issues

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.
  • Memory usage may be a bit higher when using the parallel HTTP cache (see #5112).

If you observe any panics, crashes or major performance regressions, please open an issue!

Building from source

Build the v4.6.222-exp tag.

All Changes

  • Tree states v4.6.222-exp (#5147)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • fsync during backfill to prevent DB corruption (#5144)
  • Fix tree-states sub-epoch diffs (#5097)
  • Make lcli docker image portable (#5069)
  • Update to the docs (#5106)
  • fix: update outdated links to external resources (#5018)
  • Remove custom SSZ beacon states route (#5065)
  • Fix off-by-one in backfill sig verification (#5120)
  • Increase attestation cache sizes (#5135)
  • #5102 Fix load_state_for_block_production metric mapping (#5103)
  • Fix new CLI tests for tree-states (#5132)
  • Update Mergify commit message template (#5126)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Replace backticks with single quotes (#5121)
  • Bump versions (#5123)
  • Expose additional builder booster related flags in the vc (#5086)
  • Prevent rolling file appender panic (#5117)
  • Correct multiple dial bug (#5113)
  • Fix indices filter in blobs_sidecar http endpoint (#5118)
  • Backfill blob storage fix (#5119)
  • Correct discovery logic (#5111)
  • Gossipsub fanout correction (#5110)
  • Reduce size of futures in HTTP API to prevent stack overflows (#5104)
  • Small Readability Improvement in Networking Code (#5098)
  • Upgrade shlex to 1.3.0 (#5108)
  • Stop Penalizing Peers in Parent SingleBlobLookup (#5096)
  • set deneb fork on testnets (#5089)
  • Hold HeadTracker lock until persisting to disk (#5084)
  • Fix PublishBlockRequest SSZ decoding (#5078)
  • Bump h2 (#5085)
  • Remove blobs_db when purge-db (#5081)
  • Add Deneb readiness logging (#5074)
  • Critical dependency logging (#4988)
  • add tracing metrics layer for dependency logging (#4979)
  • Fix zero port error (#5021)
  • docs: fix typos (#5059)
  • Update teku's bootnodes (#5052)
  • add content-type octet stream helper fn (#5062)
  • Fix asset paths in release CI upload job (#5056)
  • Don't error on inactive indices in att. rewards

Binaries

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
Assets 18
Loading

Time Bird

25 Jan 02:13
@github-actions github-actions
v4.6.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: C850DDDF5D100807
Learn about vigilant mode.
1be5253
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Time Bird

Summary

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:

  • Sepolia: Jan 30 2024 @ 22:51:12 (GMT+0)
  • Chiado: Jan 31 2024 @ 18:15:40 (GMT+0)
  • Holesky: Feb 7 2024 @ 11:34:24 (GMT+0)

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.

Standard block V3 endpoint

The new produce block V3 API has been standardized across clients (ethereum/beacon-APIs#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.

Known Issues 🐞

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:

  • The flag --builder-proposals is set, and
  • The --produce-block-v3 flag is set, and
  • No other flags or configuration affecting the builder-boost-factor are set, e.g. --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: #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).

Execution layer payload selection input

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 broadcast

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 #4920)

Networking Improvements

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 (#4918). An overview of the primary changes are:

  • Removed gossipsub flood publishing (#4383) - Aimed to reduce message propagation latency and lighten the memory footprint
  • Upgraded libp2p to v0.53.* (#4935)
  • Enabled concurrent discovery RPC requests
  • Improved handling of slow peers at the gossipsub level
  • Handled memory allocations in message transmission in gossipsub
  • Improved prioritisation of messages in gossipsub

Standard Liveness Endpoint

The validator client now uses the standard liveness endpoint for doppelganger protection (see #4853). This makes the Lighthouse VC's doppelganger protection compatible with any beacon node that implements the standard liveness endpoint.

Major Changes

  • Deneb support, enabled on Sepolia, Holesky and Chiado (#5089)
  • Deneb support, enabled on Goerli (#5036)
  • Fix an OOM crash caused by a build-up of messages in gossipsub send queues (#4918)
  • Changes to builder vs local block preference flags (#4629, #5086)
  • Fixes an issue with blob storage after checkpoint sync (#5119)
  • Prevent database corruption that could occur while shutting down (#5084)
  • Other networking improvements (libp2p upgrade, disable flood publishing)
  • Checkpoint sync required by default (#5038)
  • New HTTP APIs
  • Database fixes for Holesky nodes (#4820, #4985)
  • Faster fork choice by default (#4971)
  • Faster block production, decreasing the chance of being reorged (#4925)
  • Validator client broadcast feature (#4920, https://lighthouse-book.sigmaprime.io/redundancy.html#broadcast-modes)
  • More efficient subscriptions in the validator client, which reduces load on machines with large numbers of validators (#4806)
  • Attestation simulator (#4880)
  • Missed block tracking (#4731)
  • Command to prune states from the database (#4835)
  • Fixes to rewards APIs (#4807, #4877)

New HTTP APIs

The Lighthouse BN supports the following new HTTP APIs:

⚠️ Breaking Changes ⚠️

VC and BN Compatibility

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

Database Migration v19

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: #5119).

To downgrade, follow the instructions in the book for Database Migrations.

Checkpoint sync is required by default

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

Read more

Contributors

uvizhe
Assets 18
Loading

EXPERIMENTAL Tree States v4.6.111

12 Jan 04:14
@github-actions github-actions
v4.6.111-exp
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
9cd9243
This commit was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
Compare
Choose a tag to compare
EXPERIMENTAL Tree States v4.6.111 Pre-release
Pre-release

Disclaimer

⚠️ You should not run this alpha release supporting mainnet validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Summary

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:

  • Smaller disk footprint for archive nodes, <150GB total. Use checkpoint sync, and set the flag --reconstruct-historic-states.
  • Smaller disk footprint for regular nodes, <30GB.
  • Faster handling of re-orgs.
  • Faster restarts.
  • Less disk I/O.

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:

  • Bugfix to prevent database corruption caused by non-atomic writes & shutdown (#4975).
  • Optimisations for the HTTP API to better handle concurrent requests for the same data (#4879).
  • Bugfix for the rewards API (#4960).

⚠️ Backwards Compatibility ⚠️

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:

  • The secret dummy flag --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.
  • The flags --slots-per-restore-point and --historic-state-cache-size are deprecated and no longer necessary due to the freezer database using hierarchical diffs.
  • The flag --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).

Known Issues

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!

Building from source

Build the v4.6.111-exp tag.

All Changes

  • Tree states release v4.6.111-exp
  • Add cache for parallel HTTP requests (#4879)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Remove stray println
  • Restore crash safety for database pruning (#4975)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Fix cache initialization in block rewards API (#4960)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Handle out-of-order forks in epoch cache (#4881)

Binaries

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
Assets 18
Loading

Concerto

11 Jan 02:42
@github-actions github-actions
v4.6.0-rc.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: C850DDDF5D100807
Learn about vigilant mode.
2e8e160
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Concerto Pre-release
Pre-release

Disclaimer

⚠️ You should not run this pre-release supporting mainnet validators. This pre-release is, however, required for Goerli validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Something went wrong with signing this particular release, but the signatures have now been fixed and the binaries are provided in .tar.gz format as usual.

Summary

This is a pre-release that enables the Deneb hard fork on Goerli (#5036). The Deneb hard fork will occur at epoch 231680 on Goerli, which is Jan 17th, 2024 06:32:00 AM UTC.

All Goerli users must update their nodes to v4.6.0-rc.0 by Jan 17th, 2024 06:32:00 AM UTC.

This release also includes a variety of new features and a few breaking changes. Please see the section on Breaking Changes below.

Networking Improvements

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 (#4918). An overview of the primary changes are:

  • Removed gossipsub flood publishing (#4383) - Aimed to reduce message propagation latency and lighten the memory footprint
  • Upgraded libp2p to v0.53.* (#4935)
  • Enabled concurrent discovery RPC requests
  • Improved handling of slow peers at the gossipsub level
  • Handled memory allocations in message transmission in gossipsub
  • Improved prioritisation of messages in gossipsub

Standard block V3 endpoint

The new produce block V3 API has been standardized across clients (ethereum/beacon-APIs#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. With the advent of V3, the following flag will no longer be supported:

--builder-profit-threshold

Users of mev-boost can use the -min-bid flag to achieve the same functionality. An equivalent but more expressive config will be possible in an upcoming Lighthouse release (#5039). This config will also be able to restore functionality of the following flag, which is also being deprecated:

--always-prefer-builder-payload

Per-validator configuration of whether to use an external builder is still possible via the builder_proposals field. This will be extended to allow each validator to specify at what profit threshold a builder payload should be used in an upcoming release (#5039).

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.

Execution layer payload selection input

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 broadcast

Validator clients can now be configured to publish messages to all connected beacon nodes using the --broadcast flag. This allows users to improve redundency when publishing messages related to validator duties. The flag can be configured with specific message types (attestations,sync-committe,blocks, subscriptions). It can also be configured to make sure subscriptions are not sent to all beacon nodes (--broadcast none). This is equivalent to the --disable-run-on-all flag. Thanks @uvizhe for the contribution!

More information is available in the Redundancy section of the Lighthouse book.

(see #4920)

Standard Liveness Endpoint

The validator client now uses the standard liveness endpoint for doppelganger protection (see #4853). This makes the Lighthouse VC's doppelganger protection compatible with any beacon node that implements the standard liveness endpoint.

Major Changes

  • Deneb support, enabled on Goerli (#5036)
  • Fix an OOM crash caused by a build-up of messages in gossipsub send queues (#4918)
  • Other networking improvements (libp2p upgrade, disable flood publishing)
  • Checkpoint sync required by default (#5038)
  • New HTTP APIs
  • Database fixes for Holesky nodes (#4820, #4985)
  • Faster fork choice by default (#4971)
  • Faster block production, decreasing the chance of being reorged (#4925)
  • Validator client broadcast feature (#4920, https://lighthouse-book.sigmaprime.io/redundancy.html#broadcast-modes)
  • More efficient subscriptions in the validator client, which reduces load on machines with large numbers of validators (#4806)
  • Attestation simulator (#4880)
  • Missed block tracking (#4731)
  • Command to prune states from the database (#4835)
  • Fixes to rewards APIs (#4807, #4877)

New HTTP APIs

The Lighthouse BN supports the following new HTTP APIs:

⚠️ Breaking Changes ⚠️

VC and BN Compatibility

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

Database Migration v18

To support Deneb, this release includes an automatic upgrade from v17 to v18.

To downgrade, follow the instructions in the book for Database Migrations.

Checkpoint sync is required by default

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.

In order to support archive nodes via checkpoint sync, both of the following flags should be used: --reconstruct-historic-states and --genesis-backfill, along with any other flags normally used for database customization.

Removed flags

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 #4906)

Deprecated flags

The following flags should be removed from setups. If they are not removed, they will have no effect.

Deprecated: --builder-profit-threshold flag

Prefer using the -min-bid flag in mev-boost. An alternative flag in Lighthouse will be provided in an upcoming release (see #5039).

Deprecated: --always-prefer-builder-payload flag

An alternative flag in Lighthouse will be provided in an upcoming rele...

Read more

Contributors

uvizhe
Assets 18
Loading

EXPERIMENTAL Tree States v4.5.444

20 Oct 04:59
@github-actions github-actions
v4.5.444-exp
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
1aca484
This commit was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
Compare
Choose a tag to compare
EXPERIMENTAL Tree States v4.5.444 Pre-release
Pre-release

Disclaimer

⚠️ You should not run this alpha release supporting mainnet validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Summary

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:

  • Smaller disk footprint for archive nodes, <150GB total. Use checkpoint sync, and set the flag --reconstruct-historic-states.
  • Smaller disk footprint for regular nodes, <30GB.
  • Faster handling of re-orgs.
  • Faster restarts.
  • Less disk I/O.

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 important bugfixes compared to the previous v4.5.222-exp release, and a few new features:

  • Fix for 3 potential consensus faults (d4f87ef). Only one could be triggered on a real network, and to our knowledge it has not yet been triggered. We are rolling out more fuzzing to ensure the new consensus code is bug-free prior to stabilisation.
  • ARM support restored! 🎉
  • Fix for Holesky state reconstruction after checkpoint sync (#4817).
  • Even better state caching, resulting in lower memory usage and less cache misses (#4833).
  • Deneb support (from unstable).

Compared to the v4.2.990-exp release the main changes are:

  • Updates to the freezer database schema. There are now less reads required per historic state, at the cost of greater disk usage. A mainnet archive node with the default configuration is now ~140GB. Historic state loads are around 5x faster in testing: 400ms instead of 2s in the worst case. A re-sync is required due to this change.
  • Configurable storage hierarchy. Diffs can now be stored on a per-slot basis, or less frequently than every epoch. We recommend using the default configuration, and haven't done enough testing of other configurations to provide space/speed estimates. See --hierarchy-exponents in lighthouse bn --help.
  • No historic states stored by default (same as v4.4.1). Please use --reconstruct-historic-states to store historic states, even when syncing from genesis. For more information see the section of the v4.4.1 release notes on State Pruning.
  • Lots of optimisations, particularly to epoch-processing, block-processing and the underlying state library (milhouse). This release should now be on-par or faster than stable Lighthouse when it comes to importing blocks.

This release is based on v4.5.0, and also includes the other features from v4.5.0 (and v4.4.1, and v4.3.0). Please see the v4.5.0 release notes for details of breaking changes: https://github.com/sigp/lighthouse/releases/tag/v4.5.0.

⚠️ Backwards Compatibility ⚠️

This release is backwards compatible with 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:

  • The secret dummy flag --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.
  • The flags --slots-per-restore-point and --historic-state-cache-size are deprecated and no longer necessary due to the freezer database using hierarchical diffs.
  • The flag --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 upstream).

Known Issues

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!

Building from source

Build the v4.5.444-exp tag.

Binaries

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.5.444-exp-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v4.5.444-exp-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.5.444-exp-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v4.5.444-exp-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v4.5.444-exp-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 lighthouse-v4.5.444-exp-aarch64-unknown-linux-gnu-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.5.444-exp-x86_64-windows.tar.gz PGP Signature
x86_64 lighthouse-v4.5.444-exp-x86_64-windows-portable.tar.gz PGP Signature
System Option - Resource
Docker v4.5.444-exp sigp/lighthouse
Assets 18
Loading

EXPERIMENTAL Tree States v4.5.222

26 Sep 04:04
@github-actions github-actions
v4.5.222-exp
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
f1f76f2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
EXPERIMENTAL Tree States v4.5.222 Pre-release
Pre-release

Disclaimer

⚠️ You should not run this alpha release supporting mainnet validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Summary

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:

  • Smaller disk footprint for archive nodes, <150GB total. Use checkpoint sync, and set the flag --reconstruct-historic-states.
  • Smaller disk footprint for regular nodes, <30GB.
  • Faster handling of re-orgs.
  • Faster restarts.
  • Less disk I/O.

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 just a handful of changes compared to the previous v4.4.111-exp release:

  • Better state caching, resulting in lower memory usage and less cache misses (#4762)
  • Holesky 2.0 testnet support (from v4.5.0 upstream)
  • QUIC support (from v4.5.0 upstream)

Compared to the v4.2.990-exp release the main changes are:

  • Updates to the freezer database schema. There are now less reads required per historic state, at the cost of greater disk usage. A mainnet archive node with the default configuration is now ~140GB. Historic state loads are around 5x faster in testing: 400ms instead of 2s in the worst case. A re-sync is required due to this change.
  • Configurable storage hierarchy. Diffs can now be stored on a per-slot basis, or less frequently than every epoch. We recommend using the default configuration, and haven't done enough testing of other configurations to provide space/speed estimates. See --hierarchy-exponents in lighthouse bn --help.
  • No historic states stored by default (same as v4.4.1). Please use --reconstruct-historic-states to store historic states, even when syncing from genesis. For more information see the section of the v4.4.1 release notes on State Pruning.
  • Lots of optimisations, particularly to epoch-processing, block-processing and the underlying state library (milhouse). This release should now be on-par or faster than stable Lighthouse when it comes to importing blocks.

This release is based on v4.5.0, and also includes the other features from v4.5.0 (and v4.4.1, and v4.3.0). Please see the v4.5.0 release notes for details of breaking changes: https://github.com/sigp/lighthouse/releases/tag/v4.5.0.

⚠️ Backwards Compatibility ⚠️

This release is backwards compatible with 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:

  • The secret dummy flag --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.
  • The flags --slots-per-restore-point and --historic-state-cache-size are deprecated and no longer necessary due to the freezer database using hierarchical diffs.
  • The flag --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 upstream).

Known Issues

Expect a few sharp edges. Some things you may run into:

  • aarch64 (ARM) support is currently broken. As a result there are no binaries or Docker images for ARM.
  • 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!

Building from source

Build the v4.5.222-exp tag.

All Changes

  • Tree states release v4.5.222-exp (#4782)
  • Merge tag 'v4.5.0' into tree-states
  • Release v4.5.0 (#4768)
  • Fix cli options (#4772)
  • Fix release CI for self-hosted runners (#4770)
  • Move dependencies to workspace (#4650)

Binaries

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.5.222-exp-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v4.5.222-exp-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.5.222-exp-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v4.5.222-exp-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.5.222-exp-x86_64-windows.tar.gz PGP Signature
x86_64 lighthouse-v4.5.222-exp-x86_64-windows-portable.tar.gz PGP Signature
System Option - Resource
Docker v4.5.222-exp sigp/lighthouse
Assets 14
Loading

Little Dipper

25 Sep 08:13
@github-actions github-actions
v4.5.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: C850DDDF5D100807
Learn about vigilant mode.
441fc16
Compare
Choose a tag to compare
Little Dipper

Summary

This is a low-priority release which primarily contains the Holesky re-launch configurations. Some minor features and fixes are also available for mainnet and testnet users.

Feature and bugfixes include:

  • Experimental QUIC support (#4577)
  • Start the VC HTTP API before genesis (#4714)
  • More checks and logging whilst waiting for genesis (#4730)
  • More SSZ support for BN HTTP API endpoints (#4534)
  • Update Holesky configs for re-launch (#4760)
  • Fix block and state queries whilst waiting for genesis (#4761)
  • Require the --http flag (or equivalent) when dependant flags are used (#4674, #4772)
  • Update the voluntary exit HTTP API method to comply with beaconAPIs (#4679)
  • Add new mainnet Teku bootnodes (#4724)

QUIC Support

Experimental QUIC support has been added to Lighthouse with #4577.

By default Lighthouse will attempt to use QUIC on the UDP port one higher than the --port value. For example, the default value for --port is 9000, so Lighthouse will open port 9001 for QUIC. Although it's not required, we encourage users to update their port-forwarding to include this UDP port, too.

Lighthouse's use of QUIC should be transparent to users, but it maybe disabled with the --disable-quic flag.

Compiling from Source

Users who compile from source should ensure they update Rust and checkout and pull the stable branch before building:

  • Most users can update Rust with rustup update
  • Checkout and pull the stable branch with git checkout stable && git pull

Holesky Re-launch

The Holesky testnet experienced a failed genesis on the 15th of September 2023 due to a misconfiguration. The configuration issue has been fixed and a new Holesky launch is planned for September 28th 11:55am (UTC). This release contains the fixed configuration.

Users who participated in the failed Holesky launch should delete their existing data directories (e.g. ~/.lighthouse/holeksy) before running v4.5.0 otherwise they may fail to follow the new chain. It is particularily important to ensure that any existing Holesky validator slashing protection database (slashing_protection.sqlite) is removed to prevent it interfering with the new chain.

Mainnet users do not need to take any action for the Holesky relaunch.

Breaking Changes

This release contains breaking changes, all of which are detailed below.

Breaking Change: Add a data wrapper to the voluntary exit HTTP API endpoint

As per #4635, Lighthouse was divergent from the beaconAPIs specification for the /eth/v1/validator/<pubkey>/voluntary_exit endpoint. This was fixed in #4679 by ensuring the JSON response is wrapped in a top-level data object.

Breaking Change: The --http (or equivalent) flag is required if dependant flags are used

Previously, Lighthouse would allow HTTP server configurations flags like --http-address if the HTTP server was not enabled. The flags would be ignored and cause confusion for users and developers.

With #4674 Lighthosue will now return an error on startup if HTTP server configuration flags are provided when the HTTP server is not enabled. The HTTP server can be enabled using the --http, --staking or --gui flags.

Breaking Change: Minimum Supported Rust Version 1.69.0

The minimum supported Rust version has been set to 1.69.0. See "Compiling from Source" for directives.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Beacon Node Validator Client
Staking Users Low Low
Non-Staking Users Low ---

See Update Priorities more information about this table.

The Beacon Node may be updated without also updating the Validator Client. However we recommend upgrading both components for consistency. Holesky users must update both the BN and VC.

All Changes

  • Release v4.5.0 (#4768)
  • Fix cli options (#4772)
  • Fix release CI for self-hosted runners (#4770)
  • Move dependencies to workspace (#4650)
  • Use release workflow runners (#4765)
  • Add new teku bootnodes (#4724)
  • Update the voluntary exit endpoint to comply with the key manager specification (#4679)
  • require http and metrics for respective flags (#4674)
  • Bump quinn-proto to address rustsec vuln (#4767)
  • Update Holesky boot ENR (#4763)
  • Fix block & state queries prior to genesis (#4761)
  • Update holesky config for relaunch (#4760)
  • Add SSZ support to validator block production endpoints (#4534)
  • Fix genesis state download panic when running in debug mode (#4753)
  • Self hosted docker builds (#4592)
  • Fix local testnet to generate keys in the correct folders (#4752)
  • Update local testnet script (#4733)
  • Add more checks and logging before genesis (#4730)
  • Reuse fork choice read lock instead of re-acquiring it immediately (#4688)
  • Prevent port re-use in HTTP API tests (#4745)

Binaries

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.5.0-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v4.5.0-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.5.0-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v4.5.0-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v4.5.0-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 lighthouse-v4.5.0-aarch64-unknown-linux-gnu-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.5.0-x86_64-windows.tar.gz PGP Signature
x86_64 lighthouse-v4.5.0-x86_64-windows-portable.tar.gz PGP Signature
System Option - Resource
Docker v4.5.0 sigp/lighthouse
Assets 18
Loading

EXPERIMENTAL Tree States v4.4.111

14 Sep 01:52
@github-actions github-actions
v4.4.111-exp
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
1b4bc88
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
EXPERIMENTAL Tree States v4.4.111 Pre-release
Pre-release

Disclaimer

⚠️ You should not run this alpha release supporting mainnet validators ⚠️

If you are looking for the latest Lighthouse release please go to https://github.com/sigp/lighthouse/releases/latest.

Summary

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:

  • Smaller disk footprint for archive nodes, <150GB total. Use checkpoint sync, and set the flag --reconstruct-historic-states.
  • Smaller disk footprint for regular nodes, <30GB.
  • Faster handling of re-orgs.
  • Faster restarts.
  • Less disk I/O.

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.

Compared to the previous v4.2.990-exp release the main changes are:

  • Updates to the freezer database schema. There are now less reads required per historic state, at the cost of greater disk usage. A mainnet archive node with the default configuration is now ~140GB. Historic state loads are around 5x faster in testing: 400ms instead of 2s in the worst case. A re-sync is required due to this change.
  • Configurable storage hierarchy. Diffs can now be stored on a per-slot basis, or less frequently than every epoch. We recommend using the default configuration, and haven't done enough testing of other configurations to provide space/speed estimates. See --hierarchy-exponents in lighthouse bn --help.
  • Holesky testnet support (from v4.4.1 upstream).
  • No historic states stored by default (same as v4.4.1). Please use --reconstruct-historic-states to store historic states, even when syncing from genesis. For more information see the section of the v4.4.1 release notes on State Pruning.
  • Lots of optimisations, particularly to epoch-processing, block-processing and the underlying state library (milhouse). This release should now be on-par or faster than stable Lighthouse when it comes to importing blocks.

This release is based on v4.4.1, and also includes the other features from v4.4.1 (and v4.3.0).

⚠️ Backwards Compatibility ⚠️

This release is not backwards compatible with stable Lighthouse or prior tree-states releases. 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:

  • The secret dummy flag --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.
  • The flags --slots-per-restore-point and --historic-state-cache-size are deprecated and no longer necessary due to the freezer database using hierarchical diffs.
  • The flag --db-migration-period from the previous tree-states release is gone and has been replaced by --epochs-per-migration (same name as upstream).

Known Issues

Expect a few sharp edges. Some things you may run into:

  • aarch64 (ARM) support is currently broken. As a result there are no binaries or Docker images for ARM.
  • 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!

Building from source

Build the v4.4.111-exp tag.

Binaries

See pre-built binaries documentation.

A Docker image for x86_64 only is available on DockerHub as sigp/lighthouse:v4.4.111-exp.

The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0

All Changes

  • Release v4.4.111-exp (#4729)
  • Restore custom image for Cross
  • Bump schema version to v24
  • Change default epochs-per-state-diff to 16
  • Attempt to fix flaky test
  • Disable ARM docker builds
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Await listening address from libp2p in RPC tests setup (#4705)
  • Tree states to support per-slot state diffs (#4652)
  • Remove Node.js from release-tests CI job since we no longer use ganache (#4691)
  • Feat: siren faq update (#4685)
  • Fix some typos in "Advanced Networking" documentation (#4672)
  • Minor revision to Lighthouse Book on validator-manager (#4638)
  • Fix genesis state storage for genesis sync (#4589)
  • Fix deadlock in finalization migration (#4576)
  • Optimise mutations in single-pass epoch processing (#4573)
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Single-pass epoch processing (#4483)
  • Merge remote-tracking branch 'origin/tree-states' into tree-states
  • Merge remote-tracking branch 'origin/unstable' into tree-states
  • Implement activation queue cache
  • Fix EpochCache handling in ef-tests (#4454)
  • Fix EpochCache handling in ef-tests
  • Tree states optimization using EpochCache (#4429)
  • Fix db-migration-period default (#4441)

Binaries

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.4.111-exp-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v4.4.111-exp-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.4.111-exp-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v4.4.111-exp-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
x86_64 lighthouse-v4.4.111-exp-x86_64-windows.tar.gz PGP Signature
x86_64 lighthouse-v4.4.111-exp-x86_64-windows-portable.tar.gz PGP Signature
System Option - Resource
Docker v4.4.111-exp sigp/lighthouse
Assets 14
Loading