Bot releases are visible (Hide)
Published by github-actions[bot] over 2 years ago
This is a release candidate. It is not production-ready and not recommended for mainnet use.
Whilst we do not recommend this release for critical and/or mainnet use, we would appreciate help testing this release on testnets.
For more information on release candidates, see: https://lighthouse-book.sigmaprime.io/advanced-release-candidates.html
This release candidate introduces support for the Ropsten Beacon Chain, among other changes.
The Ropsten Beacon Chain will launch on Monday, May 30th, 2022 3:00:00 PM +UTC. The long-standing Ropsten testnet is expected to undergo "the merge" in early June 2022. Any user that wishes to participate in the Ropsten merge must use this release candidate (or any following release).
Use the --network ropsten
flag to join the Ropsten testnet.
This release contains a backwards-incompatible database schema migration for any network that has undergone "the merge" (see #3157). At the time of writing, this includes Kiln and Kintsugi but excludes Prater and Mainnet. For clarity:
v2.3.0-rc.0
are able to downgrade to v2.2.x
and v2.1.x
releases.v2.3.0-rc.0
are not able to downgrade to any prior releasePayloadIdUnavailable
(#3190)TaskExecutor
to be used in async
tests (#3178)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.3.0-rc.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.3.0-rc.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.3.0-rc.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.3.0-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.3.0-rc.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.3.0-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.3.0-rc.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.3.0-rc.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.3.0-rc.0 | sigp/lighthouse |
Published by github-actions[bot] over 2 years ago
This release fixes a bug in Lighthouse v2.2.0 that prevented some nodes from completing sync.
The majority of nodes running v2.2.0 will not have been affected by the bug, but nodes attempting to sync from genesis would get stuck at slot 0 forever, and nodes performing checkpoint sync would fail to download blocks from before the Altair hard fork (Oct 2021). The bug occurred as a result of changes made to RPC limits in preparation for the Merge, and has been fixed in PR https://github.com/sigp/lighthouse/pull/3146. Please see that pull request for more detail.
Users upgrading from v2.1 should also read the release notes for v2.2.0 to understand a new protocol feature called proposer boost which has been enabled in v2.2: https://github.com/sigp/lighthouse/releases/tag/v2.2.0
This release is fully backwards-compatible with the previous releases v2.2.0 and v2.1.x.
Downgrading from v2.2.1 to v2.1.x is also supported without any manual intervention.
This update is a Medium Priority update for users of Lighthouse v2.2.0, and a Low Priority update for v2.1.x.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Low Priority* | Low Priority* |
Non-Staking Users | Low Priority* | --- |
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-v2.2.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.2.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.2.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.2.1 | sigp/lighthouse |
Published by github-actions[bot] over 2 years ago
This release includes a minor protocol upgrade named proposer boost, which is designed to mitigate several attacks against fork choice.
It is recommended that all users upgrade over the course of the next few weeks.
Proposer boost mitigates attacks involving the delayed publishing of blocks and attestations. By creating disagreement amongst honest nodes, an attacker could frustrate consensus and cause re-orgs. For more detail on the attacks mitigated, please see Three Attacks on Proof-of-Stake Ethereum by researchers from the Ethereum Foundation and Stanford University.
Proposer boost mitigates the attacks by granting additional power to the proposer of each block, equal to 70% of the weight of the attesters in a single slot. This 70% "boost" is only granted to timely blocks, which prevents the delayed-publishing attack while also incentivizing on-time block publication in general. For more information please see the accompanying pull request to the beacon chain specification: https://github.com/ethereum/consensus-specs/pull/2730.
By virtue of being a protocol change, proposer boost needs to be rolled out by a large fraction of the nodes on the network in order to be effective. This Lighthouse release is coordinated with forthcoming releases from the other consensus clients.
Although it's best for all nodes on the network to adopt proposer boost within a short time frame, we estimate that the impact of upgrades spaced over the course of a few weeks will be minimal. For more detailed analysis please see https://github.com/sigp/lighthouse/pull/3131.
In addition to theoretical analysis and unit testing, proposer boost has also undergone extensive testing on the Prater testnet, where it has been enabled for several months.
This release is fully backwards-compatible with the previous release.
Downgrading from v2.2.0 to v2.1.x is also supported without any manual intervention.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Low priority | Low priority |
Non-Staking Users | Low priority | --- |
See Update Priorities for more information about this table.
lighthouse db
command (#3129)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.2.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.2.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.2.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.2.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.2.0 | sigp/lighthouse |
Published by github-actions[bot] over 2 years ago
This is a security-focussed release to address a denial-of-service vulnerability in OpenSSL (CVE-2022-0778).
Lighthouse does not rely on OpenSSL for any of its P2P functionality, but does make use of OpenSSL TLS when making HTTPS connections. We recommend that users upgrade to this release from v2.1.4 if they are using HTTPS URLs in their configuration and are concerned about the denial-of-service risk, see below for details.
If configured, Lighthouse will use HTTPS to connect to URLs passed to --eth1-endpoints
, --checkpoint-sync-url
or --beacon-nodes
(from the validator client). These URLs typically correspond to servers trusted by the user, but still pose a denial-of-service risk if the connection is intercepted by an intermediary (e.g. an ISP or public hotspot router). We believe that attacks are unlikely to occur in practice, and that their impact would be relatively minor — lighthouse
would hang, but there would be no slashing risk nor risk of signing keys being compromised.
For more information please see:
Other than the OpenSSL fix, this release is functionally equivalent to the previous release, and is 100% backward compatible.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Low priority | Low priority |
Non-Staking Users | Low priority | --- |
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-v2.1.5-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.5-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.5-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.5-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.5-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.5-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.5-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.5-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.5 | sigp/lighthouse |
Published by github-actions[bot] over 2 years ago
This release contains optimisations to P2P networking to improve validator performance. It also contains new functionality for The Merge and out-of-the-box support for the Kiln testnet via the --network kiln
flag.
This release will increase the default peer count from 50 to 80. Users who don't specify a custom --target-peers
value should see an increased peer count after updating. This is normal and expected.
Other notable features include:
--validator-dir
alias, to aid usability (#3034)Ensuring peak performance on the P2P network frequently involves trade-offs between bandwidth usage and ensuring there is a diverse and useful set of peers. The trade-off space varies over time as the network increases in size and as different implementations evolve.
As described in this comment, increasing the default peer count from 50 to 80 has shown to provide significant benefits in peer management whilst making a less significant impact on network bandwidth.
The upside of this change is that we expect less "InsufficientPeers" errors, therefore reducing penalties caused by missed/late attestations or sync messages. The downside is that we expect users to notice a ~50% increase in bytes transmitted on the network and a ~15% increase in bytes recieved (mileage may vary).
Users who prefer minimal bandwidth are free to use --target-peers 50
and maintain the status-quo. That being said, we expect most users will be happy with the new default value of 80.
In #3032, Lighthouse now ignores non-globally-routable IP addresses during discovery. This prevents some cloud providers (e.g., Hetzner) from banning Lighthouse under the (false) premise that it is maliciously scanning the private network.
We only expect this to impact developers running local testnets and enterprise users with sophisticated internal P2P routing. This change can be reverted by adding the --enable-private-discovery
flag to the BN.
The Kintsugi testnet is not supported by this release. Users should prefer Kiln.
The VC and BN between this release and the previous are compatible. You may update them independently.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Low Priority | Low Priority |
Non-Staking Users | Low Priority | --- |
See Update Priorities for more information about this table.
debug!
logs to trace!
(#3053)status
lock in the VC (#3022)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.1.4-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.4-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.4-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.4-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.4-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.4-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.4-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.4-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.4 | sigp/lighthouse |
Published by github-actions[bot] over 2 years ago
This release addresses a bug in rust-libp2p
which has been causing the Lighthouse networking stack to perform poorly since the v2.1.0 release.
This bug-fix significantly improves peer stability and is recommended for any user who is seeing an erratic peer-count and/or missing attestations due to InsufficientPeers
.
rust-libp2p
Since the v2.1.0 release, users have been reporting issues with peer stability manifesting as missed attestations.
After months of developer hours investigating this issue and making peer stability improvements via other methods, we are relieved to have identified an obscure but impactful bug in rust-libp2p
.
Whilst user feedback will be the ultimate indicator of success, we are confident that this release will represent a major improvement in peer stability.
Lighthouse relies on a regular "heartbeat" from rust-libp2p
in order to perform many critical tasks. An unfortunate regression in rust-libp2p
caused the heartbeat to become irregular and stretch from a 700ms interval to several minutes. We have raised this issue with the rust-libp2p
developers who have been receptive and are working on a fix. To provide relief to our users, Lighthouse is using a Sigma Prime fork of rust-libp2p
with a hot-fix applied.
The Pyrmont network is no longer natively supported by Lighthouse (#2543). This means that the --network pyrmont
flag will no longer work.
Since the Pyrmont testnet is abandoned and in a state of disarray, we do not expect this to be of concern to our users. The Prater testnet has superseded the Pyrmont testnet.
Users can still opt to use the --testnet-dir
flag to manually sync the Prymont network, if desired.
The VC and BN between this release and the previous are compatible. You may update them independently.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium Priority | Low Priority |
Non-Staking Users | Medium Priority | --- |
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-v2.1.3-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.3-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.3-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.3-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.3-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.3-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.3-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.3-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.3 | sigp/lighthouse |
Published by github-actions[bot] over 2 years ago
This release significantly improves peer stability and is recommended for any user who is seeing an erratic peer-count and/or missing attestations due to InsufficientPeers
.
In addition to peer stability improvements, this release also contains:
--network gnosis
(#2931)There appears to be a significant portion of peers which are transmitting late messages on the p2p gossip network. The cause is yet to be determined and it's clear that more time will be required to investigate. The late messages are not likely to consume a significant amount of system or network resources, so it seems beneficial to network stability to temporarily tolerate peers who exhibit this behaviour (see (#2976). Once the cause(s) of the late messages is/are determined, we will revisit the peer-scoring parameters.
If you are running Lighthouse under Docker on a modern CPU then you can probably upgrade to the latest-modern
tag for a 20-30% speed-up on signature verification.
If you are running the Lighthouse image manually, use latest-modern
or v2.1.2-modern
in your docker
commands, e.g.
docker run sigp/lighthouse:latest-modern
If you are using lighthouse-docker then you can upgrade by setting LIGHTHOUSE_VERSION=latest-modern
in your .env
file.
To check whether your CPU is compatible with the optimized image, see Portability in the book. For more information on all the available images, see Available Docker Images.
The VC and BN between this release and the previous are compatible. You may update them independently.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium Priority | Low Priority |
Non-Staking Users | Low Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.1.2-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.2-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.2-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.2-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.2-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.2-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.2-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.2-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.2 | sigp/lighthouse |
Published by github-actions[bot] almost 3 years ago
This update addresses a bug that can cause missed attestations accompanied by a Could not publish message error: InsufficientPeers
log. We recommend all users update to this release, at their convenience. Even users who are not affected by the bug immediately will likely experience it to some degree, eventually.
The bug fix is relevant to the BN and users are not strictly required to update the VC as well. However, we still recommend updating the VC to this version.
Notable changes include:
Could not publish message error: InsufficientPeers
log (#2948).The validator client compatibility changes inadvertently introduced a bug that results in a panic when a Lighthouse v2.1.1 validator client (VC) connects to a Lighthouse beacon node (BN) of version v2.0.1 or earlier. If you update your beacon node(s) and validator client(s) to v2.1.1 then your setup will be unaffected, the panic will only occur if a beacon node is kept back on v2.0.1 or earlier. We have confirmed that Infura beacon nodes are also unaffected. For more information please see https://github.com/sigp/lighthouse/pull/2957.
There are no breaking changes between v2.1.0 and v2.1.1.
Users upgrading from a version prior to v2.1.0 should be sure to read the v2.1.0 release notes and understand the breaking changes involved.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium Priority | Low Priority |
Non-Staking Users | Low Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.1.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.1 | sigp/lighthouse |
Published by github-actions[bot] almost 3 years ago
This update provides significant optimisations and bug-fixes for mainnet users.
We recommend all users update to this release, at their convenience. Users
need to update both their Beacon Node (BN) and Validator Client (VC) when
updating.
Notable changes include:
--datadir
(#2682, #2846).Users should expect this release candidate to provide more stability, reduced resource consumption
and better validator performance.
During testing, some nodes exhibited a temporarily increased beacon node memory
footprint of about 150% (~3GB) after upgrading from v2.0.1
to v2.1.0
. The memory usage returns to normal after the first restart.
This increased footprint occurs during a recent database migration. The
migration causes memory fragmentation which increases the overall memory
footprint.
Users who observe an increased memory footprint can choose to restart their
beacon node to get the "normal" footprint again. Users who don't mind the
increased footprint can leave their node running with no harm.
Since the migration only happens once (i.e. the first time running v2.1.0
or
later) and the memory usage is within reasonable bounds, the developers have
opted to leave the migration as-is.
Connecting a Lighthouse validator client to a Teku (or Infura) beacon node produces a warning:
WARN Beacon node config does not match exactly, advice: check that the BN is updated and configured for any upcoming forks
This is due to some minor differences in how the two clients serve data on the /config/spec
endpoint when new hard forks are defined. The warning is cosmetic (if annoying), and the two clients will continue to function in its presence.
The VC from this release (v2.1.0
) is not compatible with Lighthouse BNs from prior versions.
Users MUST update both Lighthouse BNs and VCs to v2.1.0
.
Lighthouse now requires libclang
when building from source. For details on the packages to install for different platforms please see the updated Building from Source section of the book.
Some changes have been made to Lighthouse's database schema to support "the merge", proposer
boosting, and other optimisations. The database schema upgrade will be applied automatically upon
upgrading. Once a beacon node's database has been upgraded by Lighthouse v2.1.0 it will no longer be
compatible with any v2.0.x release, meaning that if you want to revert to a previous version of
Lighthouse you will have to re-sync. We anticipate that this will not be necessary, but Checkpoint
Sync is a good way to re-sync quickly if required.
The following section is relevant only to users running a slasher.
The slasher's underlying database has been upgraded to MDBX in
order to address disk usage issues with LMDB (https://github.com/sigp/lighthouse/issues/2538).
Combined with more efficient attestation storage, this should result in around 5-10x less disk space
being used over a long period.
The upgrade to MDBX will happen automatically and destructively upon running v2.1.0. Any previous
LMDB database will be deleted and replaced with a fresh MDBX database. We made the decision to
delete the database rather than copy it, in order to reduce complexity and to avoid running out of
space while copying hundreds of gigabytes of data. Although some LMDB slasher databases had
ballooned to 800GB+ they still only contained data from the last 18 days (4096 epochs) and will be
rebuilt to an equivalent smaller database after running the new release for 18 days.
If you are concerned about everyone upgrading at the same time you could choose to wait a random
number of days between 1 and 18 before upgrading. However we suspect that this is not necessary due
to the presence of Prysm slashers on the network, and the natural staggering of upgrades amongst
users.
In this release, a bug with parsing the --datadir
flag resulted in relative paths being relative
to the users home directory, rather than to the present working directory. This has been fixed in
#2682 and #2846.
Backwards compatibility is maintained by opening the path relative to the home directory, if it
exists. If that path does not exist, the path is assumed to be relative to the present working
directory.
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 | Medium Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
sha2
(#2896)enable-enr-auto-update
and disable-packet-filter
(#2887)?
debug formatting for block roots in beacon_chain.rs (#2890)lcli
Dockerfile (#2876)mallinfo2
behind feature flag (#2864)ChainSpec
(#2798)BeaconChainHarness
tests for The Merge (#2661)Transactions
type (#2649)execution_layer
(#2635)map_fork_name!
(#2745)next_fork_subscriptions
correctly (#2688)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.1.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.0 | sigp/lighthouse |
Published by github-actions[bot] almost 3 years ago
This is a release candidate. It is not production-ready and not recommended for mainnet use.
Whilst we do not recommend this release for critical and/or mainnet use, we would appreciate help testing this release on testnets.
For more information on release candidates, see: https://lighthouse-book.sigmaprime.io/advanced-release-candidates.html
Users need to update both their Beacon Node (BN) and Validator Client (VC) when updating.
Notable changes include:
--datadir
(#2682, #2846).Users should expect this release candidate to provide more stability, reduced resource consumption
and better validator performance.
Note: the v2.1.0-rc.0
version was not released due to CI failures. Use v2.1.0-rc.1
instead.
The VC from this release (v2.1.0-rc.1
) is not compatible with Lighthouse BNs from prior versions.
Users MUST update both Lighthouse BNs and VCs to v2.1.0
.
Some changes have been made to Lighthouse's database schema to support "the merge", proposer
boosting, and other optimisations. The database schema upgrade will be applied automatically upon
upgrading. Once a beacon node's database has been upgraded by Lighthouse v2.1.0 it will no longer be
compatible with any v2.0.x release, meaning that if you want to revert to a previous version of
Lighthouse you will have to re-sync. We anticipate that this will not be necessary, but Checkpoint
Sync is a good way to re-sync quickly if required.
The GET eth/v1/config/spec
endpoint has been modified to support new constants introduced in
Bellatrix (a.k.a. "the merge"). Since v2.1.0-rc.1
, VCs will expect some Bellatrix constants to be
present in the spec endpoint. Using a v2.1.0-rc.1
VC with an earlier version BN will produce
errors logs similar to "missing field `TERMINAL_TOTAL_DIFFICULTY`".
The following section is relevant only to users running a slasher.
The slasher's underlying database has been upgraded to MDBX in
order to address disk usage issues with LMDB (https://github.com/sigp/lighthouse/issues/2538).
Combined with more efficient attestation storage, this should result in around 5-10x less disk space
being used over a long period.
The upgrade to MDBX will happen automatically and destructively upon running v2.1.0. Any previous
LMDB database will be deleted and replaced with a fresh MDBX database. We made the decision to
delete the database rather than copy it, in order to reduce complexity and to avoid running out of
space while copying hundreds of gigabytes of data. Although some LMDB slasher databases had
ballooned to 800GB+ they still only contained data from the last 18 days (4096 epochs) and will be
rebuilt to an equivalent smaller database after running the new release for 18 days.
If you are concerned about everyone upgrading at the same time you could choose to wait a random
number of days between 1 and 18 before upgrading. However we suspect that this is not necessary due
to the presence of Prysm slashers on the network, and the natural staggering of upgrades amongst
users.
In this release, a bug with parsing the --datadir
flag resulted in relative paths being relative
to the users home directory, rather than to the present working directory. This has been fixed in
#2682 and #2846.
Backwards compatibility is maintained by opening the path relative to the home directory, if it
exists. If that path does not exist, the path is assumed to be relative to the present working
directory.
sha2
(#2896)enable-enr-auto-update
and disable-packet-filter
(#2887)?
debug formatting for block roots in beacon_chain.rs (#2890)lcli
Dockerfile (#2876)mallinfo2
behind feature flag (#2864)ChainSpec
(#2798)BeaconChainHarness
tests for The Merge (#2661)Transactions
type (#2649)execution_layer
(#2635)map_fork_name!
(#2745)next_fork_subscriptions
correctly (#2688)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.1.0-rc.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-rc.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-rc.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-rc.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.0-rc.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.1.0-rc.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-rc.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.1.0-rc.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.1.0-rc.1 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This release contains a fix for a runtime panic in peer discovery that can cause Lighthouse to shutdown unexpectedly (#2711). It is recommended for all users.
Any user that is running a version prior to v2.0.0
must update before the Altair upgrade on the 27th of October. Nodes running v2.0.0
are fully Altair-ready. However, nodes running any release prior to v2.0.1
will not be patched against the panic fixed in #2711.
Other notable features in this release include:
We recommend updating both the Beacon Node (BN) and Validator Client (VC), however there are no known incompatibilities between v2.0.0
and v2.0.1
. Users upgrading from a release prior to v2.0.0
must update both the BN and VC together.
Users upgrading from a release prior to v2.0.0
are advised to read the v2.0.0
Release Notes as they contain important information about breaking changes.
This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Medium Priority | Low Priority |
Non-Staking Users | Low Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
BeaconChainHarness::builder
(#2707)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.0.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.0.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.0.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.1-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.1-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.0.1 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
Lighthouse v2.0.0 is a mandatory upgrade release for all mainnet users. It contains the activation schedule for the beacon chain's first hard-fork: Altair, occurring in around 3 weeks on the 27th of October.
In addition, Lighthouse v2.0.0 includes several new features and optimisations which are described below.
The v2.0.0 series sets the fork epoch for the Altair upgrade on mainnet, which is scheduled for epoch 74240, i.e. Oct 27, 2021, 10:56:23am UTC. All mainnet users must upgrade to v2.0.0 before this date. Any validators that do not upgrade will cease to follow the chain, will miss 100% of their assigned attestations and blocks, and will be penalised for inactivity.
You must update both the beacon node and validator client together, so that both are aware of the fork.
Lighthouse beacon nodes can now be synced in a matter of minutes using the new Checkpoint Sync feature. Checkpoint sync accelerates sync by downloading a finalized checkpoint state from an existing beacon node via HTTP, and syncing forward from that point. Checkpoint sync is a first-class Lighthouse feature, and can be used for both staking and archive nodes.
See the docs in the Lighthouse book for more details: https://lighthouse-book.sigmaprime.io/checkpoint-sync.html
The checkpoint sync feature required a small change to Lighthouse's database schema, which will be applied automatically upon upgrading. Once a beacon node's database has been upgraded by Lighthouse v2.0.0 it will no longer be compatible with any v1.x release, meaning that if you want to revert to a previous version of Lighthouse you will have to re-sync from genesis.
An optimisation providing a substantial speed-up to attestation verification has been merged in PR #2399 and is enabled by default. We have observed significant reductions in CPU usage and attestation processing times on both Prater and mainnet.
The optimisation works by grouping the signatures of up to 64 attestations for verification in bulk, which is faster than verifying each signature individually. The batching is opportunistic and will take effect only when 2 or more attestations are queued. In the case of invalid signatures it degrades gracefully to verifying signatures individually, as before. You can read more about this optimisation in the implementation pull request: #2399.
Lighthouse's validator client has been extended with support for the Web3Signer remote signer from Consensys. Using a remote signer allows the validator client to defer responsibility for signing to an external service, which can be administered and audited independently. This is mostly of interest to validators operating at scale, and we are looking forward to seeing the integrations that will be built on top of this feature in the coming weeks and months.
Documentation for using Web3Signer with Lighthouse can be found here: https://lighthouse-book.sigmaprime.io/validator-web3signer.html
Several improvements have been made to Lighthouse's networking stack, including an upgrade to a more efficient version of discv5
(#2577), and changes to make Lighthouse's peering more robust and resilient (#2530, #2604, #2650).
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 | Medium Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
The full list of changes since v1.5.2 is:
BlockTimesCache
to allow additional block delay metrics (#2546)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.0.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.0.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.0.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.0.0 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This is a pre-release. It is not production-ready and not recommended for mainnet use.
Whilst we do not recommend this release for critical and/or mainnet use, we would appreciate help testing this release on testnets.
For more information on pre-releases, see: https://lighthouse-book.sigmaprime.io/advanced-pre-releases.html
This is the first pre-release for Lighthouse v2.0.0, which includes several new major features. Please read the following sections closely, as this release includes a database schema migration that prevents downgrading after upgrading.
The v2.0.0 series sets the fork epoch for the Altair upgrade on mainnet, which is scheduled for epoch 74240, i.e. Oct 27, 2021, 10:56:23am UTC. All mainnet users will have to upgrade to the final v2.0.0 release before this date, but should not upgrade to this pre-release right now. The final v2.0.0 release is scheduled for the week after this pre-release, allowing at least 3 weeks for all stakers to upgrade.
Lighthouse beacon nodes can now be synced in a matter of minutes using the new Checkpoint Sync feature. Checkpoint sync accelerates sync by downloading a finalized checkpoint state from an existing beacon node via HTTP, and syncing forward from that point. Checkpoint sync is a first-class Lighthouse feature, and can be used for both staking and archive nodes.
See the docs in the Lighthouse book for more details: https://lighthouse-book.sigmaprime.io/checkpoint-sync.html
The checkpoint sync feature required a small change to Lighthouse's database schema, which will be applied automatically upon upgrading. Once a beacon node's database has been upgraded by Lighthouse v2.0.0 it will no longer be compatible with any v1.x release, meaning that if you want to revert to a previous version of Lighthouse you will have to re-sync.
An optimisation providing a substantial speed-up to attestation verification has been merged in PR #2399 and is enabled by default. We have observed significant reductions in CPU usage and attestation processing times on both Prater and mainnet.
The optimisation works by grouping the signatures of up to 64 attestations for verification in bulk, which is faster than verifying each signature individually. The batching is opportunistic and will take effect only when 2 or more attestations are queued. In the case of invalid signatures it degrades gracefully to verifying signatures individually, as before. You can read more about this optimisation in the implementation pull request: #2399.
Lighthouse's validator client has been extended with support for the Web3Signer remote signer from Consensys. Using a remote signer allows the validator client to defer responsibility for signing to an external service, which can be administered and audited independently. This is mostly of interest to validators operating at scale, and we are looking forward to seeing the integrations that will be built on top of this feature in the coming weeks and months.
Documentation for using Web3Signer with Lighthouse can be found here: https://lighthouse-book.sigmaprime.io/validator-web3signer.html
Several improvements have been made to Lighthouse's networking stack, including an upgrade to a more efficient version of discv5
(#2577), and changes to make Lighthouse's peering more robust and resilient (#2530, #2604, #2650).
The full list of changes, including some not covered above is below:
BlockTimesCache
to allow additional block delay metrics (#2546)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v2.0.0-rc.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-rc.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-rc.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.0.0-rc.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v2.0.0-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-rc.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v2.0.0-rc.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v2.0.0-rc.0 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This release contains useful optimizations for mainnet and testnet users. It also contains improvements to logging, tightened file permissions and usability improvements.
Mainnet users will benefit from #2547, which reduces the time it takes to set a block as the canonical head. This reduces the likelihood of late-to-arrive blocks causing missed head votes for attesters. This should see a marginal increase in validator rewards.
Prater and Prymont users will benefit from #2560 which greatly reduces the load during block processing. This will help overloaded nodes run more smoothly. Any Prater or Pyrmont user running v1.5.1 or earlier should update at their next convenience. This optimization was included in v1.5.2-rc.0, so there is no pressing need to update testnet nodes running that release-candidate.
Cross-compatibility between Lighthouse and Teku has been improved by #2587. This will benefit Infura users across mainnet and testnets.
The breaking changes listed here are introduced between v1.5.1 and this this release. No breaking changes have been introduced since v1.5.2-rc.0.
The log file generated with the --logfile
flag will now have tighter file permissions (600
). Previously, all users had read permissions. Now, read permissions are only granted to the user running the lighthouse
binary. Since the log file is created anew on each restart, these permissions will take affect immediately after updating.
The API token files generated by the lighthouse vc
will also be created with the same restricted file permissions (600
). If the API token files already exist, no changes will be made to their permissions.
Restricting access to log files and API tokens is a security best-practice.
The lighthouse remote_signer
command has been removed. This feature was incomplete and has been archived. At present, there are no plans to reinstate it. Once #2522 is complete, Lighthouse will support remote signing via Web3Signer.
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 | Medium Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
Changes are since the v1.5.1 release.
process_attestation
with active balance cache (#2560)remote_signer
code (#2559)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.5.2-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.2-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.2-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.5.2 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This is a pre-release. It is not production-ready and not recommended for mainnet use.
Whilst we do not recommend this release for critical and/or mainnet use, we do recommend that users upgrade their Prater nodes to this version.
For more information on pre-releases, see: https://lighthouse-book.sigmaprime.io/advanced-pre-releases.html
The motivation for this release candidate is to apply an optimization to Prater nodes (#2560). Without this optimization, a significant increase in block import and API response times will be observed for all blocks since the Altair fork on Prymont (2020/09/02). Whilst this does not represent a consensus bug, it may cause increased CPU load and decreased performance for attesters and API consumers.
Updating to this release (or later) will be required for all Prater users. However, since Prater is a testnet, we do not consider this an urgent priority. We kindly request that users update their Prater nodes at their next convenience.
There is no action required for mainnet users. Do not use this release candidate on mainnet.
The log file generated with the --logfile
flag will now have tighter file permissions (600
). Previously, all users had read permissions. Now, read permissions are only granted to the user running the lighthouse
binary. Since the log file is created anew on each restart, these permissions will take affect immediately after updating.
The API token files generated by the lighthouse vc
will also be created with the same restricted file permissions (600
). If the API token files already exist, no changes will be made to their permissions.
Restricting access to log files and API tokens is a security best-practice.
The lighthouse remote_signer
command has been removed. This feature was incomplete and has been archived. At present, there are no plans to reinstate it. Once #2522 is complete, Lighthouse will support remote signing via Web3Signer.
process_attestation
with active balance cache (#2560)remote_signer
code (#2559)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.5.2-rc.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-rc.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-rc.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.2-rc.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.2-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-rc.0-x86_64-windows.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.2-rc.0-x86_64-windows-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.5.2-rc.0 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This update to Lighthouse contains the following notable changes:
All Prater users must upgrade their VC and BN prior to 02/09/2021, 12:24:00 pm (UTC). Nodes that do not upgrade to v1.5.1
or later before that time will be unable to follow the head and will require a re-sync in order to rejoin the network.
Prater users must upgrade both the VC and BN to v1.5.1
or later, otherwise the VC will log warnings about "incompatibility" with the BN.
Users have reported occurrences of a combination of "Prior attestation known" debug logs, drops in peer counts and sub-optimal attestation performance.
Our investigations have found instances of old attestations (32-33 slots old) circulating on the network. Whilst we do not believe that these messages should be on the network (i.e., they are a useless burden), Lighthouse was being overzealous in banning peers who were sending these messages.
Thanks to changes introduced in #2540 and #2542, Lighthouse will not ban peers for this behaviour.
The Lighthouse team will continue to investigate why these old messages are still circulating on the network.
Note: There are no known issues affecting mainnet.
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 | Medium Priority | --- |
Note: this update is "high priority" for all Prater users due to the upcoming Altair fork,
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
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.5.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.1-x86_64-windows.tar.gz (Beta) | PGP Signature | |
x86_64 | lighthouse-v1.5.1-x86_64-windows-portable.tar.gz (Beta) | PGP Signature | |
System | Option | - | Resource |
Docker | v1.5.1 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This is a substantial update to Lighthouse which contains many new features, performance improvements and fixes. Importantly, due to added support for the Altair hard-fork, this release is not backwards-compatible with v1.4.0 or earlier. You can safely upgrade to this release without re-syncing the chain, but will need to re-sync to downgrade (see Breaking Changes below).
With this caveat clearly stated, the Lighthouse team is proud to present this release which contains:
reorg
event has been added to the HTTP API./lighthouse/validator_inclusion
endpoints have been modified to be Altair-compatible. See #2416 for detail.The validator client is incompatible with Teku beacon nodes on Prater due to a difference in how Prater configuration is represented. If you are running a Lighthouse validator client with a Teku beacon node on Prater (including via Infura) we recommend remaining on v1.4.0 until the incompatibility is resolved. Mainnet and Pyrmont are unaffected. More information here.
There are a couple of Altair-related issues that do not affect mainnet, and will be fixed in the next release. Importantly, if you run a Pyrmont node and didn't update to a v1.5.0 release candidate before the Altair fork, then issue #2526 means that upgrading now will be ineffective. We plan to have this fixed in the next release.
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 | Medium Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
state.inactivity_scores
(#2504)AttesterCache
for attestation production (#2478)http-address
flag to VC (#2467)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.5.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.5.0 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This is a pre-release. It is not production-ready and not recommended for mainnet use.
Whilst we don't recommend this release for critical and/or mainnet use, we do recommend that users upgrade their Pyrmont and Prater nodes to this version. We assume that nothing critical is occurring on these testnets.
For more information on pre-releases, see: https://lighthouse-book.sigmaprime.io/advanced-pre-releases.html
Compared to v1.5.0.-rc.0
, this pre-release contains three fixes:
The most notable of these changes is (3), it addresses an issue on an Altair devnet where we saw a significant number of peer disconnections due to early sync committee messages. Although these messages shouldn't occur in theory, they are occurring in practice. As such, we recommend that all Pyrmont users should upgrade to this release before the Altair fork at 2021-08-19 12:00:07Z.
Users upgrading from v1.4.0
or earlier read the release notes in v1.5.0.-rc.0
to understand the breaking changes introduced there.
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.5.0-rc.1-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-rc.1-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-rc.1-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-rc.1-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.0-rc.1-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.0-rc.1-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.5.0-rc.1 | sigp/lighthouse |
Published by github-actions[bot] about 3 years ago
This is a pre-release. It is not production-ready and not recommended for mainnet use.
Whilst we don't recommend this release for critical and/or mainnet use, we do recommend that users upgrade their Pyrmont and Prater nodes to this version. We assume that nothing critical is occurring on these testnets.
For more information on pre-releases, see: https://lighthouse-book.sigmaprime.io/advanced-pre-releases.html
This update is mandatory for all nodes on the Pyrmont testnet. At 2021-08-19 12:00:07Z, Pyrmont will undergo an irregular state transition to upgrade to the Altair specification (i.e., there will be a hard fork).
Users running Lighthouse v1.4.0
or earlier will fail to undergo this state-transition and will be left on the wrong side of history.
The Eth2 developers (including the Lighthouse team) are upgrading Pyrmont in anticipation for the same upgrade on mainnet. Failing to upgrade your Pyrmont nodes will impede their efforts to deliver a smooth upgrade on mainnet. Please upgrade your Pyrmont nodes!
To be clear, mainnet users should not implement this release-candidate version. Prater users may upgrade, but are not required to.
This is a substantial update to Lighthouse with two important caveats:
v1.5.0-rc.0
VCs and BNs are incompatible. This only applies to Pyrmont, other networks are not affected.Failing to upgrade both the BN and VC on Pyrmont will result in the VC declaring the BN to be "incompatible". The solution is simple; update and restart both processes.
With the caveats clearly stated, the Lighthouse team is proud to present this release which contains:
reorg
event has been added to the HTTP API.v1.5.0-rc.0
nodes (including freshly-synced nodes and those upgraded from earlier versions) is not compatible with earlier versions of Lighthouse. This was mentioned earlier.v1.5.0-rc.0
. Earlier versions are not compatible with v1.5.0-rc.0
./lighthouse/validator_inclusion
endpoints have been modified to be Altair-compatible. See #2416 for detail.state.inactivity_scores
(#2504)AttesterCache
for attestation production (#2478)http-address
flag to VC (#2467)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.5.0-rc.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-rc.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-rc.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.5.0-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.0-rc.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.5.0-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.5.0-rc.0 | sigp/lighthouse |
Published by github-actions[bot] over 3 years ago
This is a low-priority update. It primarily contains optimizations which reduce the impact of the Beacon Node on RAM, CPU, disk I/O and Eth1 nodes.
Whilst we suggest all users update to this release at their convenience, there is no pressing reason to do so unless they are concerned that the resource requirements of Lighthouse are outpacing their hardware.
Notable features in this release are:
As mentioned in the "Memory Allocator Tuning" section, some users running Linux without glibc
may need to apply the --disable-malloc-tuning
CLI flag to lighthouse bn
(the Beacon Node) in order to avoid a panic at startup. We expect this scenario to be very rare and have not encountered it during internal testing or during external release candidate testing. We only recommend using this flag if you experience a failure as it will substantially increase memory usage. We only expect to see this issue on obscure Linux installations; MacOS, Ubuntu, Amazon Linux and other common operating systems are unaffected.
404
.lighthouse/health
HTTP API endpoint.--eth1-endpoints
flag enables syncing the Eth1 chain. This fixes a regression in a previous release.This table provides priorities for which classes of users should update particular components.
User Class | Beacon Node | Validator Client |
---|---|---|
Staking Users | Low Priority | Low Priority |
Non-Staking Users | Low Priority | --- |
Staking users are those who use lighthouse bn
and lighthouse vc
to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn
for non-staking purposes (e.g., data analysis or applications).
High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).
With #2299, Lighthouse now automatically configures the GNU Memory Allocator at startup to provide a more optimal memory footprint.
This alone reduces the memory consumption of Lighthouse by at least 50%. However, some Linux systems may have an incompatible memory allocator. This will cause Lighthouse to panic and exit at startup (only at startup, never after it has begun operation).
If users experience a panic and instant exit during startup, do not fear. Simply provide the --disable-malloc-tuning
flag to completely disable this new feature.
For example:
lighthouse --disable-malloc-tuning bn --staking
If you do experience this error, please raise an issue. We are eager to ensure Lighthouse runs on all platforms by default.
We have never seen this panic during our testing or on the release candidate, but we are aware it is possible on some obscure platforms.
Since Lighthouse Update #36 announced a list of features and a timeline for v1.4.0
, the development team has decided to split the features into two, separate releases:
v1.4.0
: to be released approximately one week earlier than scheduled, but only containing:
v1.5.0
: to be release late June, containing:
--eth1-endpoints
flag (#2392)SensitiveUrl
to redact user secrets from endpoints (#2326)See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
Windows for Lighthouse is still in beta and binaries are not yet provided.
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-v1.4.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.4.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.4.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
x86_64 | lighthouse-v1.4.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.4.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
aarch64 | lighthouse-v1.4.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
System | Option | - | Resource |
Docker | v1.4.0 | sigp/lighthouse |