Summary
This release contains an important bug fix to the Beacon Node (lighthouse bn) and should be considered high priority for all stakers.
An additional validation condition is applied to aggregated attestations which prevents incorrect attestations from filling up the operations pool (#2306). Additionally, #2307 provides improvments to block-packing which will result in better block rewards for stakers.
Update now for safety and profit.
Outdated Lighthouse Intances
Analysis of the network shows a concerning portion of users are running Lighthouse with a version prior to v1.2.0. These users are exposed to a vulnerability in the core cryptography library of Lighthouse (and other Eth2 clients). See this blst security advisory for more information. It is critically important to keep Lighthouse updated when high priority updates are announced!
Breaking Changes
This release contains a very minor breaking change to the CLI interface. We do not expect any users to be affected by this change, but please read this section before updating.
The --disable-enr-auto-update value previously accepted a value that was ignored, only the presence of the flag had an effect. See the following examples:
- Worked before this release, will continue to work.
lighthouse bn --disable-enr-auto-update
- Worked before this release, will not work after this release.
lighthouse bn --disable-enr-auto-update yeslighthouse bn --disable-enr-auto-update nolighthouse bn --disable-enr-auto-update meow
For more detail, see #2303.
Update Priority
This table provides priorities for which classes of users should update particular components.
| User Class | Beacon Node | Validator Client |
|---|---|---|
| Staking Users | ⚠️ High Priority ⚠️ | No Action Required |
| 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
- v1.3.0 (#2310)
- Pack attestations into blocks in parallel (#2307)
- Add specific log and metric for delayed blocks (#2308)
- Add check for aggregate target (#2306)
- Clean up warnings (#2240)
- Correcting
disable-enr-auto-updateflag definition (#2303) - Avoid BeaconState clone during metrics scrape (#2298)
- Correcting command example validator exit (#2291)
- Use generic BLS object instead of BLST (#2290)
- Fix local testnet scripts (#2229)
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.3.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v1.3.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v1.3.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v1.3.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
| aarch64 | lighthouse-v1.3.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
| aarch64 | lighthouse-v1.3.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
| System | Option | - | Resource |
| Docker | v1.3.0 | sigp/lighthouse |