Summary
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:
- Fix for increased frequency of missed attestations accompanied by a
Could not publish message error: InsufficientPeerslog (#2948). - Compatibility between Lighthouse VCs and Nimbus beacon nodes (#2940, #2943, #2952).
- Fix to HTTP query string parsing (#2908).
Known Issues
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 #2957.
Breaking Changes
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.
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 | --- |
User 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
- 5f628a7 v2.1.1 (#2951)
- 69288f6 VC: don't warn if BN config doesn't match exactly (#2952)
- b9b3ea7 Fix metric name for monitoring (#2950)
- ca29b58 Increase target subnet peers (#2948)
- f35a337 Quote validator indices when posting duties (#2943)
- 799aedd Add default config options for transition constants (#2940)
- f0f327a Removed all disable_forks (#2925)
- fc7a1a7 Allow disconnected states to introduce new peers without warning (#2922)
- a8ae9c8 Add linkcheck workflow (#2918)
- 0116c8d Change type of extra fields in ConfigAndPreset (#2913)
- d06f874 Support duplicate keys in HTTP API query strings (#2908)
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.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 |