lighthouse 5.0.0 #163659
Merged
lighthouse 5.0.0 #163659
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
rust
chenrui333
added
the
CI-no-fail-fast
chenrui333
force-pushed
the
bump-lighthouse-5.0.0
branch
from
7b8fd7c to
ad0b0f5
Compare
Contributor
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a |
Member
Author
|
Contributor
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a |
Contributor
michaelsproul
left a comment
michaelsproul
left a comment
There was a problem hiding this comment.
@chenrui333 To fix the startup failure add this flag to lighthouse bn:
--allow-insecure-genesis-sync
That is required when syncing from genesis now.
lighthouse: update sleep lighthouse: update test Co-authored-by: Rui Chen <[email protected]>
bevanjkay
force-pushed
the
bump-lighthouse-5.0.0
branch
from
ad0b0f5 to
60e9b14
Compare
bevanjkay
added
ready to merge
p-linnane
approved these changes
Feb 28, 2024
Contributor
|
🤖 An automated task has requested bottles to be published to this PR. |
github-actions
bot
added
the
CI-published-bottle-commits
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.release notes
Any node which is not updated to a Lighthouse v5.x.x release by this time will stop following the chain and will need to be resynced. For stakers, this would result in missed rewards and penalties.
All Mainnet Lighthouse users must update their BNs and VCs to v5.0.0 by March 13, 2024, 01:55:35pm UTC.
This release also contains various bug-fixes, optimisations and new features:
--builder-proposals(#5151)distributedflag to VC to enable support for DVT (#4867)There are a few breaking changes. Please see the section on Breaking Changes below.
Mainnet Deneb/Cancun ("Dencun") Upgrade
The Deneb/Cancun ("Dencun") upgrade will occur on mainnet at:
All Lighthouse Beacon Nodes and Validator Clients must be upgraded to a v5.x.x release to ensure they follow the correct chain. The following table demonstrates which releases are reliable, Dencun-ready releases:
To be Dencun ready, user will need to:
There are no new flags to be added or removed for the Dencun upgrade, simply upgrade and wait.
Lighthouse will start periodically emitting the following logs two weeks before the Dencun upgrade (28th of February):
Not ready for Denebif Lighthouse has detected that the execution engine is too outdated to support Cancun.Ready for Denebif Lighthouse has detected a modern execution engine release.Just because Lighthouse is logging
Ready for Denebdoes not indicate that your execution engine is on the correct version. There is no way for Lighthouse to determine this exactly and users are responsible for ensuring that their execution engine is using the latest release.Note that with blobs (EIP-4844) being added in Dencun, each node is expected to consume additional disk space, with an expected average of 50 GiB, up to a maximum of 103GiB for blobs.
Fix bug in VC flag
--builder-proposals(#5151)There was a bug in the logic for the
--builder-proposalsVC flag introduced in Lighthouse v4.6.0. Rather than setting the boost to 0 whenbuilder-propsalswas false, it was setting it to 0 whenbuilder-proposalswas true. Users have been using--builder-boost-factor 100as a workaround until now.This issue has been resolved and the preference can now be enabled with the
--builder-proposals.See sigp/lighthouse#5151.
:warning: Breaking Changes :warning:
This release contains breaking changes, all of which are detailed below.
Validator Liveness endpoint now accepts string encoded indices
The standard liveness endpoint (
/eth/v1/validator/liveness) was introduced in the previous version of Lighthouse but did not accept string-encoded validator indices, which is part of the specification. This has been fixed and will require updating both BN and VC to the latest version.See sigp/lighthouse#5184.
Minimum Supported Rust Version 1.75.0
The minimum supported Rust version (MSRV) has been updated to 1.75.0. Users who compile from source (i.e., not Docker or pre-built binary users) will receive the following error if they are using an earlier version of Rust:
Users can typically obtain the latest version of Rust by running
rustup update.Deleted custom endpoint
lighthouse/beacon/states/{state_id}/sszThis endpoint is redundant and no longer required, because equivalent endpoints now exist in the standard beacon API.
See sigp/lighthouse#5065.
New mandatory
--checkpoint-blobsflag for manual checkpoint syncingFor users checkpoint syncing manually (previously using
--checkpoint-blockand--checkpoint-state), there is now an additional mandatory--checkpoint-blobsflag for users to supply the checkpoint blobs. Users using the--checkpoint-syncflag are not affected.See sigp/lighthouse#5252.
Deprecated BN flag
--disable-duplicate-warn-logsThis BN flag was introduced in Lighthouse v4.6.0. It has now become the default behaviour in this version, where gossipsub duplicate logs are
debuglevel instead ofwarn, thus deprecating this flag.See sigp/lighthouse#5163.
Update Priority
This table provides priorities for which classes of users should update particular components.
See Update Priorities more information about this table.
All Changes
distributedflag to VC to enable support for DVT (#4867)curve25519-dalekpatch (#5214)prune-states(#5142)blobs_by_root_requestrpc limit. (#5181)--builder-proposals(#5151)Binaries
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key:
15E66D941F697E28F49381F426416DC3F30674B0