Summary
This update to Lighthouse contains the following notable changes:
- Support for the Altair upgrade on the Prater testnet (scheduled for the 2nd of September, 2021).
- A fix to a recent issue where a drop in peer count resulted in sub-optimal attestation performance.
- The fork schedule API has been updated for Altair (see #2524)
Prater Altair Upgrade
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.
Peer drop resulting in sub-optimal attestation performance
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.
Known Issues
- Unable to restart lighthouse if altair fork is missed (#2526)
Note: There are no known issues affecting mainnet.
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 | Medium Priority |
| Non-Staking Users | Medium Priority | --- |
Note: this update is "high priority" for all Prater users due to the upcoming Altair fork,
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
- b0ac346 v1.5.1 (#2544)
- 4405425 Expand gossip duplicate cache time (#2542)
- 9fb94fb Add Altair fork epoch for Prater (#2537)
- 3fdad38 Remove penality for duplicate attestation from same validator (#2540)
- 09545fe Increase maximum gossipsub subscriptions (#2531)
- d3b4cbe Packet filter cli option (#2523)
- aca49fc Security update for openssl (#2539)
- 5b8436e Fork schedule api (#2525)
- bc05992 Windows binaries (#2492)
- 02fd54b Refactor discovery queries (#2518)
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-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 |