Planetina
Summary
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:
- Fixes to the standard API (#2712)
- More resilient slashing protection imports (#2598)
- A reduction in validator monitor logging verbosity (#2606)
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.
Update Priority
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 | --- |
Users Classes and Priorities
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).
All Changes
- Release v2.0.1 (#2726)
- Correct peer connection transition logic (#2725)
- Add Altair tests to op pool (#2723)
- Update to consensus-spec-tests v1.1.3 (#2722)
- Reduce lock contention in backfill sync (#2716)
- Change "too many resources" to "insufficient resources" in eth2_libp2p (#2713)
- Allow custom certificates when connecting to BN (#2703)
- Update discovery (#2711)
- Quoted altair fields (2.0) (#2712)
- Get arbitrary check passing (2.0) (#2710)
- Add
BeaconChainHarness::builder
(#2707) - Make slashing protection import more resilient (#2598)
- Reduce validator monitor logging verbosity (#2606)
- Add TLS capability to the beacon node HTTP API (#2668)
- Refactor Peerdb and PeerManager (#2660)
- Fix cargo audit warns for nix, psutil, time (#2699)
- Avoid negative values in malloc_utils metrics (#2692)
- Update broken api links (#2665)
- Don't log errors on resubscription of gossip topics (#2613)
- Add test_logger as feature to logging (#2586)
- Fix name collision in script (#2678)
Binaries
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0
System | Architecture | Binary | PGP Signature |
---|---|---|---|
x86_64 | lighthouse-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 |