Summary
This release is a low-priority release for all users (including mainnet), except for those using the Sepolia test network
For Sepolia users, this release includes the Capella fork parameters. Sepolia will undergo the Capella upgrade (a.k.a "hardfork") on 2023/2/28 at 4:04:48 AM UTC. Sepolia users must update to this version or later before the Capella upgrade. Users that fail to upgrade will cease to follow the chain and will be required to resync.
Ethereum mainnet, Ethereum testnet (e.g., Goerli, Ropsten) and Gnosis users may choose to update to this release, but it is low-priority.
Alongside the Sepolia changes, this release includes:
- ⚠️ Database schema upgrade to v15 ⚠️
- HTTP API returns 404 rather than 405 for an unknown route (#3836)
- Add CLI flag to specify the format of logs written to the logfile (#3839)
- Switch allocator to jemalloc (#3697)
- Implement new rewards APIs (#3822, #3903, #3907)
- Add attestation duty slot metric (#2704)
- Reduce some EE and builder related ERRO logs to WARN (#3966)
- Use Local Payload if More Profitable than Builder (#3934)
Breaking Changes
⚠️ Breaking Change: Database Schema v15 ⚠️
To support Capella the database schema has been upgraded to v15. The schema upgrade will be applied automatically upon upgrading and should not take more than a few seconds.
To downgrade, follow the instructions in the book for Database Migrations.
Users may downgrade anytime before the Capella upgrade. Prior Lighthouse releases are not compatible with Capella, so downgrading is fundamentally impossible after the upgrade occurs.
⚠️ Breaking Change: Minimum Supported Rust Vesion ⚠️
Users building from source will have to update their Rust compiler version to at least 1.65.0 using a command like:
rustup update stable
Newer versions of the compiler including the latest (v1.67.1 at time of writing) will also work.
Older versions will log an error during compilation.
Breaking Change: HTTP API Unknown Routes
Previously, the Beacon Node HTTP would return 405 (method not allowed) for an unknown route (e.g. http://localhost:5052/not_a_real_route). Lighthouse will now return a 404 (not found) error.
Sepolia Capella Hard Fork
Sepolia is upgrading to Capella on 2023/2/28 at 4:04:48 AM UTC! 🎉
Sepolia users must update both the Lighthouse beacon node and validator client before February 28. Failure to update will result in missed validator duties and a corrupt beacon node database (requiring a re-sync).
Sepolia users must also ensure they are running a compatible execution engine. The Ethereum Foundation Sepolia Shapella Annoucement contains more information and a list of compatible execution layer releases.
Lighthouse will emit INFO Ready for Capella logs when both itself and the execution engine are ready for the Capella upgrade. Conversely, Lighthouse will emit WARN Not ready for Capella logs when it detects a misconfiguration.
Known Issues
The optimised maxperf profile is currently not working on Windows due to a suspected regression in the Rust compiler. The pre-compiled Windows binaries have been built with the release profile instead and may exhibit slightly reduced performance compared to previous versions. See #3964 for details.
Update Priority
This table provides priorities for which classes of mainnet users should update particular components.
| User Class | Beacon Node | Validator Client |
|---|---|---|
| Staking Users | Low Priority | Low Priority |
| Non-Staking Users | Low Priority | --- |
Note: this update is high-priority for Sepolia users.
The Beacon Node may be updated without the Validator Client, however we recommend updating both components for completeness. Sepolia users must update both the beacon node and the validator client.
See Update Priorities for more information about this table.
All Changes
This release contains the Capella functionality (#3763), which has been the result of several months of work. To ensure rightful attribution to its contributors, we have elected to perform a merge commit rather than our usual squash-merge. This has created an unusually complex history on the stable branch, so we have omitted the full list of changes in this release.
The full list of commits between this version (v3.5.0) and the previous version (v3.4.0) can be viewed on Github.
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-v3.5.0-x86_64-apple-darwin.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v3.5.0-x86_64-apple-darwin-portable.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v3.5.0-x86_64-unknown-linux-gnu.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v3.5.0-x86_64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
| aarch64 | lighthouse-v3.5.0-aarch64-unknown-linux-gnu.tar.gz | PGP Signature | |
| aarch64 | lighthouse-v3.5.0-aarch64-unknown-linux-gnu-portable.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v3.5.0-x86_64-windows.tar.gz | PGP Signature | |
| x86_64 | lighthouse-v3.5.0-x86_64-windows-portable.tar.gz | PGP Signature | |
| System | Option | - | Resource |
| Docker | v3.5.0 | sigp/lighthouse |