-
-
Notifications
You must be signed in to change notification settings - Fork 12.9k
lighthouse 7.0.0 #220922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lighthouse 7.0.0 #220922
Conversation
|
I'm looking into this. Can't reproduce on my arm64 Mac running macOS 15.3.2 One difference I noticed in the build output is My
I also had a look at the Rust tools for determining whether to supply The |
Still not able to repro on macOS 15.4.1 with this version of
|
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 |
849ec9d
to
dfc9853
Compare
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 |
@chenrui333 Can you add the help-wanted label? I can try to take a look at this today, but it may be easier for someone more familiar with Homebrew's compiler stack |
I managed to reproduce the failure locally with:
and seemingly I can prevent the failure using
|
It seems like this might be a problem with Homebrew's This is the #!/usr/bin/env bash
echo "clang invoked with args $@"
/usr/bin/clang "$@"
result="$?"
echo "with result $result"
exit "$result" |
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 |
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 |
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 |
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
:warning: Deprecated CLI Flags :warning:
The following beacon node flags have been deprecated. You should remove them, but the beacon node will still start if they are provided.
--light-client-server
:crab: Minimum Supported Rust Version :crab:
We have updated the Minimum Supported Rust Version (MSRV) for this release from 1.80.0 to 1.83.0.
This is only relevant to users compiling Lighthouse from source.
You can update your Rust compiler using:
IPv6 by Default
Lighthouse will now automatically listen on IPv6 if it detects a globally-routable address. We expect for the majority of users with IPv4-only setups that this change will have no effect, but that it will benefit users with correctly configured IPv6 stacks.
The default IPv6 listening port has been changed from port 9090 to port 9000 (same as IPv4) to make firewalling easier. The IPv6 port can be adjusted using the flag
--port6
.You can opt-out of IPv6 using the flag
--disable-ipv6
.For more information, see the Lighthouse blog:
Gas Limit Enforcement
Lighthouse BN now enforces gas limit preferences when validating execution payloads from external builders (e.g.
mev-boost
relays). You can configure the gas limit for all validators connected to a VC using--gas-limit
, or set individual limits in thevalidator_definitions.yml
, or using the VC HTTP API.:zap: Electra :zap:
The Electra hard fork, paired with the Prague hard fork on the execution layer – together known as Pectra – brings several new features to Ethereum.
The headline change is known as Max EB, and raises the maximum effective balance a single validator may wield from 32 ETH to 2048 ETH. Once adopted, this will allow the network to run more efficiently with a lower validator count, while retaining the same level of security. Max EB even removes some centralisation vectors from staking incentives so that solo validators are able to tap into the compounding rewards previously enjoyed exclusively by large operators.
The process of switching a validator's max effective balance is a consolidation, which transfers stake from one validator to another. Consolidations are triggered via a smart contract call, and are fully opt-in and voluntary. If you are a solo operator with a small number of validators, there is no need to consolidate, although you may choose to do so.
Information about consolidation tooling has been added to the Lighthouse book:
Bug Fixes
InsufficientPeers
errors.New Features
redb
. This is still experimental and only reccommended for expert users.--network hoodi
).Optimisations
BlocksByRange
/BlobsByRange
during non-finality.Update Priority
This table provides priorities for which classes of users should update particular components.
See Update Priorities for more information about this table.
All Changes
/eth/v2/beacon/pool/attestations
honorscommittee_index
(#7298)light_client/updates
endpoint returns spec compliant SSZ data (#7230)cargo audit
failure (#7313)pending_consolidations
Beacon API endpoint (#7290)--invalid-block-roots
(#7042)RUSTSEC-2024-0437
(#7114)epochs-per-blob-prune
default to 256 (#7113)RUSTSEC-2025-0009
(#7086)sync_tolerance_epochs
flag to control the proposer prep routines (#7044)--long-timeouts-multiplier
CLI flag (#7047)--disable-attesting
flag to validator client (#7046)SYNC_TOLERANCE_EPOCHS
for range sync testing (#7030)trivial
andready-for-merge
labels to satisfy if base is notstable
(#6997)GET v2/validator/aggregate_attestation
is backwards compatible (#6984)RUSTSEC-2025-0006
(#6972)SingleAttestation
conversion (#6934)POST /eth/v2/beacon/pool/attestations
bugfixes (#6867)rust_eth_kzg
(#6848)node/identity
API (#6827)SingleAttestation
implementation (#6488)getBlobs
race condition (#6756)v1.5.0-beta.0
(#6731)--datadir
flag is present (#6748)getBlobSidecars
support for PeerDAS (#6755)getBlobs
or reconstruction (#6686)ZeroizeString
in favour ofZeroizing<String>
(#6661)Binaries
See pre-built binaries documentation.
The binaries are signed with Sigma Prime's PGP key:
15E66D941F697E28F49381F426416DC3F30674B0