Bot releases are hidden (Show)
Published by michaelsproul about 1 year ago
This is a low-priority release. It contains several minor bug fixes and performance improvements which we recommend rolling out on mainnet nodes at your convenience. This release also includes support for the Holešky testnet, with genesis on 15 September 2023.
Note that there is no v4.4.0 release due to a bug found late in the release cycle. The bug was fixed in PR #4687, which is included in this release.
The highlights of v4.4.1 are:
lighthouse validator-manager
command for managing validators on a running validator client. Documentation can be found in a new chapter of the Lighthouse book: https://lighthouse-book.sigmaprime.io/validator-manager.html.--network holesky
(#4653).--network chiado
(#4530).We have identified a minor bug in the code related to state pruning that can cause an error message to be logged for a limited time after upgrading:
ERRO Missing chunk in forwards iterator
It can be safely ignored, as it does not impact the node's ability to follow the chain or perform validator duties. However, API queries for historic blocks & states may fail until the issue resolves itself. This only affects nodes with an existing database. Nodes with lower --slots-per-restore-point
will heal faster, and we expect the maximum time to heal to be around 8192 slots (~27 hours). The issue is being tracked in https://github.com/sigp/lighthouse/issues/4697.
Newly synced nodes will no longer store historic states by default. This applies both to checkpoint sync and genesis sync. Node operators may opt-in to historic state storage by reconstructing states with the --reconstruct-historic-states
flag.
Existing nodes will continue storing historic states newer than the checkpoint from which they synced. We are working on a command to prune historic states from existing nodes, which will likely be available in the next release.
The pruned status of a node can be determined using the /lighthouse/database/info
API, which will show the value of state_upper_limit
as 18446744073709551615
. For more details see #4610, #4663.
Support for the phase0
hard fork was added to the attestation rewards API. This required the addition of a new field for the inclusion_delay
, which has been standardised upstream in beacon-APIs
: https://ethereum.github.io/beacon-APIs/#/Rewards/getAttestationsRewards.
See #4474, #4520 for details.
Lighthouse will now return an HTTP 202 ACCEPTED
response when attempting to publish a block that is already known. This behaviour goes against the current beacon-APIs
spec, but is likely better for the majority of API consumers. Previously, a 400 BAD REQUEST
response could cause the caller (usually a validator client) to think that block publication had failed when it had not. We have begun a discussion to change the spec to allow the new error code.
The status code can also be set to a custom value using the flag --http-duplicate-block-status
. See https://github.com/sigp/lighthouse/pull/4655 for details.
The Lighthouse BN supports the following new HTTP APIs:
POST /eth/v{1,2}/beacon/blocks
(#4479).POST /eth/v{1,2}/beacon/blinded_blocks
(#4504).POST /eth/v1/validator/liveness/{epoch}
(#4343).GET /eth/v1/builder/states/{state_id}/expected_withdrawals
(#4390).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.
web3signer_tests
timeouts (#4662)--gui
flag in help text (#4660)ForkChoice
: remove an impossible case for parent_checkpoints
(#4626)metrics::VALIDATOR_DUTIES_SYNC_HTTP_POST
for post_validator_duties_sync
(#4617)attester_duties
: remove unnecessary case (#4614)head_block_root
field (#4590)maybe_update_best_child_and_descendant
: remove an impossible case (#4583)concurrency
property to cancel workflows (#4572)init_from_beacon_node
(#4613)optional_eth2_network_config
(#4611)state.get_validator
(#4608)BeaconProcessor
for API requests (#4462)validator-manager
(#3502)exchangeTransitionConfiguration
functionality (#4517)lcli::generate_bootnode_enr
and some tests (#4485)--epochs-per-migration
(#4236)BeaconProcessor
into a new crate (#4435)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.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.4.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.4.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.4.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.4.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v4.4.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.4.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v4.4.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v4.4.1 | sigp/lighthouse |
Published by paulhauner almost 2 years ago
This release is a low-priority release for all users, except those using the Gnosis Chain.
For Gnosis users, this release includes the Gnosis Merge parameters. Gnosis users will need to update to this release before November 30th or they will fail to go through the merge transition and will be left following the wrong chain. Therefore, this release is high-priority for Gnosis users.
Ethereum mainnet and Ethereum testnet (e.g., Goerli, Sepolia) users may choose to update to this release, but it is low-priority.
Alongside the Gnosis changes, this release includes:
--checkpoint-sync-url-timeout
flag (#3710)To support new features the database schema has been upgraded to v13. The schema upgrade will be applied automatically upon upgrading and should not take more than a few seconds.
To downgrade, follow the instructions in the book for Database Migrations.
The signing of sync committee messages by the validator client has been improved in a way that is incompatible with old versions of the Lighthouse beacon node. We do not expect many users to be affected because only versions prior to v3.0.0 are incompatible.
For details please see: https://github.com/sigp/lighthouse/pull/3624
Gnosis chain is merging! 🎉
The expected timeline is:
You must update both the Lighthouse beacon node and validator client before November 30. Failure to update will result in missed validator rewards and a corrupt beacon node database (requiring a re-sync).
You must also ensure you're running a compatible verison of Nethermind (v1.14.6 or newer) and that it is correctly connected to your Lighthouse beacon node. For further instructions please see:
We are pleased to announce the readiness of deposit snapshot sync, which enables nodes to quickly sync the deposit contract.
When setting up a new Lighthouse node using checkpoint sync, a snapshot of the deposit contract will be downloaded from the checkpoint sync provider. Initially the only supported provider is Lighthouse v3.3.0, although we expect checkpointz
and the other clients soon will roll out support soon.
If the checkpoint sync provider does not support the feature you'll see a pair of warning logs:
WARN Remote BN does not support EIP-4881 fast deposit sync
WARN Failed to finalize deposit cache
These warnings are harmless, and Lighthouse will gracefully fallback to syncing the deposit contract cache from the execution node.
Depsosit snapshot support is the result of many months of work by @ethDreamer, who not only implemented the feature in Lighthouse but also wrote the spec for it, EIP-4811.
For further details on the implementation see: https://github.com/sigp/lighthouse/pull/2915
This table provides priorities for which classes of mainnet users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Low Priority | Low Priority |
Non-Staking Users | Low Priority | --- |
Note: this update is high-priority for Gnosis chain users.
The Beacon Node may be updated without the Validator Client, however we recommend updating both components for completeness. Gnosis users must update both the beacon node and the validator client.
See Update Priorities for more information about this table.
mut
(#3736)Published by michaelsproul about 2 years ago
This medium-priority release is a patch release for the recently released v3.2.0, fixing a performance regression.
Please see the release notes for v3.2.0 for a summary of included features and breaking changes:
https://github.com/sigp/lighthouse/releases/tag/v3.2.0
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium Priority | Medium Priority |
Non-Staking Users | Low Priority | --- |
The Beacon Node may be updated without the Validator Client and vice versa, as long as both BN and VC are running a v3.x release.
Beacon nodes and validator clients on pre-v3.0.0 versions have been unable to follow the chain since September 6 2022 when the Bellatrix hard fork was activated.
See Update Priorities for more information about this table.
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v3.2.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v3.2.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v3.2.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v3.2.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v3.2.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v3.2.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v3.2.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v3.2.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v3.2.1 | sigp/lighthouse |
Published by paulhauner almost 4 years ago
This minor release contains some important protection from excessive resource consumption in some uncommon cases (#2130). We recommend all users update both their BNs and VCs to this version.
The breaking changes in this release should be insignificant for most, see below for more information.
The most notable feature is the new "validator monitor" that allows a BN to provide additional logging and metrics for specific validators.
This provides the long-awaited "validator balance" metric and many, many others.
Additionally, you get additional logs about your validators activities (e.g. attestation inclusion in blocks).
See the validator monitor docs for more information.
Breaking changes are fairly minor in this release, but may have edge-case impacts for those running custom or non-Lighthouse validator clients.
AttestationData
via the API for slots earlier than the head. This is a fast patch to an immediate issue, in the future we plan to implement a more flexible solution with #2169.--beacon-node
to --beacon-nodes
(#2145)end_slot
returns incorrect value (#2138)test_decode_malicious_status_message
improvements (#2104)ssz_snappy.rs
comment (#2103)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v1.1.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.1.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.1.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.1.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.1.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.1.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.1.0 | sigp/lighthouse |
Published by michaelsproul almost 4 years ago
We recommend all users upgrade to v1.0.4
, particularly users who have previously experienced database corruption, or who are running a slasher. Please see below for details of breaking changes, including removal of the websocket server.
--eth1-purge-cache
flag that can be used to clean out the Eth1 cache without a resync. This should only be used if your node is unable to recover from an error like FailedToInsertDeposit(NonConsecutive {..})
. The flag is supplied to the beacon node command like so: lighthouse bn --eth1-purge-cache
(#2039).NEW in this release: multi-arch Docker images. Thanks to amazing work by @realbigsean in #2065,
our Docker Hub images are now capable of running on x86_64 or ARM64! That includes
the Raspberry Pi 4 🎉
You can get the latest release via the :latest
or :v1.0.4
tags:
The latest dev build is available via the :latest-unstable
tag:
For the multi-arch build, please use :latest
rather than :v1.0.4
.
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
Published by paulhauner almost 4 years ago
We recommend all users to upgrade to v1.0.3
, especially if they're experiencing timeouts with their eth1 endpoint.
Users may see a new log message:
Nov 30 21:04:28.268 WARN Syncing eth1 block cache est_blocks_remaining: initializing deposits, msg: sync can take longer when using remote eth1 nodes, service: slot_notifier
This log indicates that your beacon node is downloading blocks and deposits from your eth1 node. When the est_blocks_remaining
is initializing_deposits
, your node is downloading deposit logs. It may stay in this stage for several minutes. Once the deposits logs are finished downloading, the est_blocks_remaining
value will start decreasing.
It is perfectly normal to see this log when starting a node for the first time or after being off for more than several minutes.
If this log continues appearing sporadically during operation, there may be an issue with your eth1 endpoint.
lighthouse bn --private
flag which zeros-out graffiti and does not publish client information in the identify protocol.See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
Published by AgeManning almost 4 years ago
We recommend all users to upgrade to v1.0.2
, especially if they're intending to stake with a genesis validator.
This release updates core dependencies in Lighthouse and is highly encouraged for all nodes to run for mainnet.
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
Published by paulhauner almost 4 years ago
We recommend all users to upgrade to v1.0.1
, especially if they're intending to stake with a genesis validator.
Since this release affects lockfiles, users should be especially cautious that there is no other lighthouse vc
process running on the same host when upgrading to this release. Running two validator clients at the same time, with the same keys can lead to slashing.
flock
-based lockfiles which alleviates the need for users to run with --delete-lockfiles
after an abrupt shutdown.--eth1-endpoints
flags which alllows for redundant eth1 nodes.--metrics
flag (and other related flags) to lighthouse vc
, allowing for Prometheus metrics.
Published by paulhauner almost 4 years ago
This release marks Lighthouse transitioning into a production/stable development phase.
We recommend all users to upgrade to v1.0.0
, especially if they're intending to stake with a genesis validator.
lighthouse
binary.--testnet
flag has been replaced with --network
medalla
to mainnet
Published by paulhauner almost 4 years ago
This release is recommended for all users. Due to API updates, it's essential that you restart both the beacon node and validator client after updating.
--testnet pyrmont
flag has been added, providing full support for the Prymont testnet.Published by michaelsproul almost 4 years ago
This release provides many incremental improvements to networking, storage and the HTTP API as we prepare for mainnet.
It is recommended for all users running on the Medalla testnet. Due to API updates, it's essential that you restart both the beacon node and validator client after updating.
--testnet mainnet
flag, for monitoring of the deposit contract before genesis. With your beacon node connected to a mainnet Eth1 node you can watch the deposits stream in 🎉 Although this is our first release with some mainnet compatibility, it is not intended for making mainnet deposits or running a validator on mainnet. We will ship a v1.0.0 release closer to genesis, as described in our v1.0.0 release schedule here: https://lighthouse.sigmaprime.io/update-32.html
MESH_N_LOW
many peers (#1886)Published by michaelsproul almost 4 years ago
This release includes numerous networking stability improvements and fixes, and new HTTP API features.
Critically, it fixes an issue with the included bootnode addresses that prevented nodes from finding peers when starting a beacon node from scratch on v0.3.2 (#1849).
It also adds a long-awaited command for submitting voluntary exits, documented here: https://lighthouse-book.sigmaprime.io/voluntary-exit.html
Finally, if you run on a VPS and had trouble with the optimized v0.3.2 build, it might be worth trying again, as we've fixed a false positive in our detection of CPU features (#1846).
Due to the API changes, it is essential to restart both the validator client and beacon node after upgrading.
FixedVector
and VariableList
(#1794)Published by paulhauner almost 4 years ago
We recommend that all users upgrade their software to this latest release as it contains important interoperability improvements.
Published by AgeManning about 4 years ago
This release provides breaking changes in the networking layer and in the db schema.
This version upgrades the discovery mechanism of Lighthouse to Discovery v5.1. This means Lighthouse will not be able to discover peers with previous versions of Lighthouse. There has also been a DB schema update. Running v0.3.1 on an older database will cause Lighthouse to migrate the older db to the new version. Users will not be able to downgrade their db after this.
We encourage all Medalla users to upgrade to this version to participate in the new networking changes and to improve peer discovery.
Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.Note: we do not yet provide binaries for MacOS or Windows native.
Published by paulhauner about 4 years ago
This is a major release which contains breaking features. The breaking features require users to perform:
v0.2.x
are incompatible v0.3.0
The directory structure has changed, such that the ~/.lighthouse
dir (AKA "datadir") now contains one sub-directory for each --testnet
value. What was previously ~/.lighthouse/beacon
is now ~/.lighthouse/medalla/beacon
or ~/.lighthouse/altona/beacon
.
If you have an existing ~/.lighthouse
directory you will need to move it into a sub-directory that matches the testnet name.
Assume there is an existing ~/.lighthouse
directory for Medalla:
.lighthouse
|- beacon
|- validators
|- secrets
The directory should be re-arranged as such:
.lighthouse
|- medalla
|- beacon
|- validators
|- secrets
Note: you will likely need to edit the validators/validator_definitions.yml
file to reflect the additional directory nesting.
5052
). Metrics must be enabled with the --metrics
flag and their address/port/CORS settings are managed separately to the API.~/.lighthouse
directory structure has changed (mentioned earlier in the release notes).--delete-lockfiles
flag can be used to recover from a scenario where the validator client detects existing lockfiles from a previous crash. Use --delete-lockfiles
with caution and read the CLI help first.slashing_protection.sqlite
to ~/.lighthouse/medalla/validators/slashing_protection.sqlite
(or $datadir/validators/slashing_protection.sqlite
). More information here: https://lighthouse-book.sigmaprime.io/slashing-protection.html#misplaced-slashing-database
--testnet zinken
option, with full support for the upcoming testnet.--wss-checkpoint
flag has been added to protect against weak subjectivity attacks. Users are not expected to require this flag until after mainnet launch.Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.Note: we do not yet provide binaries for MacOS or Windows native.
Published by AgeManning about 4 years ago
This release updates Lighthouse for the upcoming Spadina testnet launch.
Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.Note: we do not yet provide binaries for MacOS or Windows native.
Published by paulhauner about 4 years ago
This release contains new features and a fix to an error introduced in the previous release (v0.2.11
).
--testnet spadina
flag.--staking
flag to the beacon node which enables the API and Eth1 syncing.--staking
flag (#1641)update_pubkey_cache
(#1626)safe_sum
and use it in state_processing (#1620)Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.Note: we do not yet provide binaries for MacOS or Windows native.
Published by paulhauner about 4 years ago
Solves an issue which caused the beacon node to resume from the database using a canonical head that is no longer consistent with fork choice. The canonical head is now derived from fork choice when resuming from DB.
Also adds the new "trusted peers" feature (#1640).
Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.Published by paulhauner about 4 years ago
Solves an issue which caused some nodes to stall during sync.
Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.Published by paulhauner about 4 years ago
This release contains new user facing functionality (key recovery) and fixes an issue which cause validators to produce attestations which would not be included on chain. We have observed significant improvement in rewards using this release.
Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu
: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu
: 64bit ARM processors (Raspberry Pi 4)Additionally there is also a -portable
suffix which indicates if the portable
feature is used:
portable
: uses modern CPU instructions to provide the fastest signature verification times (may cause Illegal instruction
error on older CPUs)portable
: approx. 20% slower, but should work on all modern 64-bit processors.