HackMD
Lighthouse v2.5.1 [DRAFT RELEASE NOTES]
Summary
This high-priority release contains important fixes for mainnet users.
There were two separate bugs introduced into fork choice in v2.4.0 and v2.5.0.
The first bug results in a steady memory footprint increase of 100MB per month. It has been less than two weeks since that release so it's unlikely that a significant memory increase can be observed, yet. It was fixed in #3408.
The second bug can result in an error during fork choice. This error will only be triggered in rare timing-based circumstances and will resolve itself within seconds. It was fixed in #3402.
Furthermore, an incompatibility between Lighthouse VCs running v2.5.0 and BNs running a version prior to v2.5.0 was detected and fixed in #3410.
Breaking Changes
There are no breaking changes in this release. If users have not already upgraded to v2.5.0 they should read the v2.5.0 release notes for the breaking changes in that release.
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 | Low Priority |
| Non-Staking Users | High Priority | –- |
The Beacon Node may be updated without the Validator Client, however we recommend updating both components.
See Update Priorities for more information about this table.
All Changes
- Release v2.5.1 (#3406)
- Ignore RUSTSEC-2022-0040 -
owning_refsoundness (#3415) - Restore backwards compatibility when using older BNs (#3410)
- Make fork choice prune again (#3408)
- Ensure FC uses the current slot from the store (#3402)
- Fix a few typos in option help strings (#3401)
- Add list of DB migrations to docs (#3399)
- Tidy eth1/deposit contract logging (#3397)
