prysm

mirror of https://github.com/OffchainLabs/prysm.git synced 2026-02-13 06:25:06 -05:00

Author	SHA1	Message	Date
Bastin	bd12ae5d2a	Fix gen-logs.sh - gitignore bug (#16328 ) What does this PR do? Why is it needed? `gen-logs.sh` was skipping `cmd/beacon-chain/execution/` due to a rule in `.gitignore`. Added a fix in `gen-logs.sh` to ignore `.gitignore` entries by specification.	2026-02-12 23:17:34 +01:00
Potuz	f3fca87410	Remove unused map in forkchoice (#16329 ) nodeByPayload was not being used.	2026-02-12 23:17:34 +01:00
Bastin	7bc7e556f7	Fix logging issue (#16322 ) What does this PR do? Why is it needed? This PR, in an attempt to fix the logging issue described in #16314, does the following: - Adds a new field `Identifier` to the `WriterHook` struct, and filters out log entries that have the key `log_target` and the value of the hook's `Identifier`. For now the identifiers are `ephemeral` and `user`, differentiating between the user facing terminal/log file, and the debugger facing ephemeral log file. - Stores the value of the `--verbosity` and `--log.vmodule` flags in `io/logs`, so it can be accessed by packages that need to know the verbosity they're logging with. (note that since #16272 each package can have a different verbosity, so verbosity is now defined per package instead of globally) - Improves the calculation of the global logging level by ignoring the `ephemeralLogFileVerbosity` when the `--disable-ephemeral-log-file` flag is enabled. - Uses these added logic to fix the problem in `logStateTransitionData()` (described in #16314) Note: since we're saving this new data in `io/logs`, we should refactor `prefixFormatter` to read the data from here. but that creates a circular import error. I will try to fix this and refactor the formatter in a future PR. --------- Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com>	2026-02-12 23:17:34 +01:00
Justin Traglia	ddc11cf0a8	Improve ethspecify integration (#16304 ) What type of PR is this? Documentation What does this PR do? Why is it needed? * Move the ethspecify config from `/specrefs/.ethspecify` to `/.ethspecify`. * This allows developers to use inline specrefs (eg spec functions in godoc comments). * To do this, simply add a spec tag and run `ethspecify` to populate it. * Clean up specref exceptions; organize by upgrade & put items in the correct section. * Update a few godoc comments to use the new inline specref feature. * Update check-specrefs GitHub action so that it enforces up-to-date godocs. * Standardize specref naming; requiring a `#fork` tag for everything. * Add new specrefs (which haven't been implemented yet) which were missing. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: james-prysm <90280386+james-prysm@users.noreply.github.com>	2026-02-12 23:17:33 +01:00
james-prysm	a4d3e94fbe	node fallback cleanup (#16316 ) What type of PR is this? Other What does this PR do? Why is it needed? Follow up to https://github.com/OffchainLabs/prysm/pull/16215 this pr improves logging, fixes stuttering in package naming, adds additional unit tests, and deduplicates fallback node code. Which issues(s) does this PR fix? fixes a potential race if reconnecting to the same host very quickly which has a stale connection still. Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
Aarsh Shah	9811ccc179	fix: Set Beacon Node Options after reading the config file (#16320 ) What type of PR is this? Bug fix What does this PR do? Why is it needed? This PR ensures that we set the beacon node options AFTER reading the config file (if one is given to override the defaults). Which issues(s) does this PR fix? It fixes the issue that Barnabas reported around the "MIN_EPOCHS_FOR_DATA_COLUMN_SIDECARS_REQUESTS" override not being respected (and potentially other issues resulting from setting the options before reading the config). Fixes # Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
Preston Van Loon	c3c3f826f4	golangci-lint: Remove test exclusion from formatting (#16318 ) What type of PR is this? > Other What does this PR do? Why is it needed? Which issues(s) does this PR fix? Follow up to #16311 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
james-prysm	ed9bff51ad	grpc fallback improvements (#16215 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? ## Summary This PR implements gRPC fallback support for the validator client, allowing it to automatically switch between multiple beacon node endpoints when the primary node becomes unavailable or unhealthy. ## Changes - Added `grpcConnectionProvider` to manage multiple gRPC connections with circular failover - Validator automatically detects unhealthy beacon nodes and switches to the next available endpoint - Health checks verify both node responsiveness AND sync status before accepting a node - Improved logging to only show "Found fully synced beacon node" when an actual switch occurs (reduces log noise) I removed the old middleware that uses gRPC's built in load balancer because: - gRPC's pick_first load balancer doesn't provide sync-status-aware failover - The validator needs to ensure it connects to a fully synced node, not just a reachable one ## Test Scenario ### Setup Deployed a 4-node Kurtosis testnet with local validator connecting to 2 beacon nodes: ```yaml # kurtosis-grpc-fallback-test.yaml participants: - el_type: nethermind cl_type: prysm validator_count: 128 # Keeps chain advancing - el_type: nethermind cl_type: prysm validator_count: 64 - el_type: nethermind cl_type: prysm validator_count: 64 # Keeps chain advancing - el_type: nethermind cl_type: prysm validator_count: 64 # Keeps chain advancing network_params: fulu_fork_epoch: 0 seconds_per_slot: 6 ``` Local validator started with: ```bash ./validator --beacon-rpc-provider=127.0.0.1:33005,127.0.0.1:33012 ... ``` ### Test 1: Primary Failover (cl-1 → cl-2) 1. Stopped cl-1 beacon node 2. Validator detected failure and switched to cl-2 Logs: ``` WARN Beacon node is not responding, switching host currentHost=127.0.0.1:33005 nextHost=127.0.0.1:33012 DEBUG Trying gRPC endpoint newHost=127.0.0.1:33012 previousHost=127.0.0.1:33005 INFO Failover succeeded: connected to healthy beacon node failedAttempts=[127.0.0.1:33005] newHost=127.0.0.1:33012 previousHost=127.0.0.1:33005 ``` Result: ✅ PASSED - Validator continued submitting attestations on cl-2 ### Test 2: Circular Failover (cl-2 → cl-1) 1. Restarted cl-1, stopped cl-2 2. Validator detected failure and switched back to cl-1 Logs: ``` WARN Beacon node is not responding, switching host currentHost=127.0.0.1:33012 nextHost=127.0.0.1:33005 DEBUG Trying gRPC endpoint newHost=127.0.0.1:33005 previousHost=127.0.0.1:33012 INFO Failover succeeded: connected to healthy beacon node failedAttempts=[127.0.0.1:33012] newHost=127.0.0.1:33005 previousHost=127.0.0.1:33012 ``` Result: ✅ PASSED - Circular fallback works correctly ## Key Log Messages \| Log Level \| Message \| Source \| \|-----------\|---------\|--------\| \| WARN \| "Beacon node is not responding, switching host" \| `changeHost()` in validator.go \| \| INFO \| "Switched gRPC endpoint" \| `SetHost()` in grpc_connection_provider.go \| \| INFO \| "Found fully synced beacon node" \| `FindHealthyHost()` in validator.go (only on actual switch) \| ## Test Plan - [x] Verify primary failover (cl-1 → cl-2) - [x] Verify circular failover (cl-2 → cl-1) - [x] Verify validator continues producing attestations after switch - [x] Verify "Found fully synced beacon node" only logs on actual switch (not every health check) What does this PR do? Why is it needed? Which issues(s) does this PR fix? Fixes # https://github.com/OffchainLabs/prysm/pull/7133 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> Co-authored-by: Radosław Kapka <rkapka@wp.pl> Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com>	2026-02-12 23:17:33 +01:00
terence	d4054e7823	Run go fmt (#16311 ) Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com>	2026-02-12 23:17:33 +01:00
Jun Song	cad32dffe0	Add docs for SSZ Query package (#16299 ) What type of PR is this? Documentation What does this PR do? Why is it needed? Although godoc and comments are well-written in `encoding/ssz/query` package, we (@rkapka, @fernantho, @syjn99) [agreed](https://discord.com/channels/476244492043812875/1387734369527136297/1466075406523174944) that it would be great to have human-readable documentation. Which issues(s) does this PR fix? Part of #15587 & #15598 Other notes for review This documentation is first drafted by Claude Code, and then has a few rounds of self-review. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: fernantho <fernantho1@gmail.com> Co-authored-by: Radosław Kapka <radoslaw.kapka@gmail.com>	2026-02-12 23:17:33 +01:00
Justin Traglia	29c4093717	Add ability to download nightly tests from a specific night (#16298 ) What type of PR is this? Feature What does this PR do? Why is it needed? This PR allows devs to test against a specific run of the nightly reference test generator. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
Justin Traglia	d5f4293c56	Add a README for specrefs (#16302 ) What type of PR is this? Documentation What does this PR do? Why is it needed? This PR adds a basic README for the specrefs. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
terence	6eae3678b6	gloas: sample PTC per committee (#16293 ) This PR updates `get_ptc` construction to sample ptc committee-by-committee instead of concatenating all beacon committees into a large slice. No functional changes to payload attestation verification	2026-02-12 23:17:33 +01:00
james-prysm	65b255cfea	Update health endpoint to include sync and optimistic checks (#16294 ) What type of PR is this? Other What does this PR do? Why is it needed? Which issues(s) does this PR fix? Fixes # Other notes for review a node that is in syncing or optimistic status isn't fully ready yet. we don't have a is ready endpoint, but I think having the gRPC match more closely to [/eth/v1/node/health](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Node/getHealth) would be good. This endpoint is only used internally as far as I can tell. this is prerequisite to https://github.com/OffchainLabs/prysm/pull/16215 tested via grpcurl against a syncing hoodi node Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
fernantho	22c60c731a	SSZ-QL: custom Generic Merkle Proofs building the tree and collecting the hashes in one sweep (#16177 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Feature What does this PR do? Why is it needed? This PR replaces the previous PR https://github.com/OffchainLabs/prysm/pull/16121, which built the entire Merkle tree and generated proofs only after the tree was complete. In this PR, the Merkle proof is produced by collecting hashes while the Merkle tree is being built. This approach has proven to be more efficient than the one in https://github.com/OffchainLabs/prysm/pull/16121. - ProofCollector: - New `ProofCollector` type in `encoding/ssz/query/proof_collector.go`: Collects sibling hashes and leaves needed for Merkle proofs during merkleization. - Multiproof-ready design with `requiredSiblings`/`requiredLeaves` maps for registering target gindices before merkleization. - Thread-safe: read-only required maps during merkleization, mutex-protected writes to `siblings`/`leaves`. - `AddTarget(gindex)` registers a target leaf and computes all required sibling gindices along the path to root. - `toProof()` converts collected data into `fastssz.Proof` structure. - Parallel execution in `merkleizeVectorBody` for composite elements with worker pool pattern. - Optimized container hashing: Generalized `stateutil.OptimizedValidatorRoots` pattern for any SSZ container type: - `optimizedContainerRoots`: Parallelized field root computation + level-by-level vectorized hashing via `VectorizedSha256`. - `hashContainerHelper`: Worker goroutine for processing container subsets. - `containerFieldRoots`: Computes field roots for a single container using reflection and SszInfo metadata. - `Prove(gindex)` method in `encoding/ssz/query/merkle_proof.go`: Entry point for generating SSZ Merkle proofs for a given generalized index. - Testing - Added `merkle_proof_test.go` and `proof_collector_test.go` to test and benchmark this feature. The main outcomes of the optimizations are here: ``` ❯ go test ./encoding/ssz/query -run=^$ -bench='Benchmark(OptimizedContainerRoots\|OptimizedValidatorRoots\|ProofCollectorMerkleize)$' -benchmem goos: darwin goarch: arm64 pkg: github.com/OffchainLabs/prysm/v7/encoding/ssz/query cpu: Apple M2 Pro BenchmarkOptimizedValidatorRoots-10 3237 361029 ns/op 956858 B/op 6024 allocs/op BenchmarkOptimizedContainerRoots-10 1138 969002 ns/op 3245223 B/op 11024 allocs/op BenchmarkProofCollectorMerkleize-10 522 2262066 ns/op 3216000 B/op 19000 allocs/op PASS ok github.com/OffchainLabs/prysm/v7/encoding/ssz/query 4.619s ``` Knowing that `OptimizedValidatorRoots` implements very effective optimizations, `OptimizedContainerRoots` mimics them. In the benchmark we can see that `OptimizedValidatorRoots` remain as the most performant and tit the baseline here: - `ProofCollectorMerkleize` is ~6.3× slower, uses ~3.4× more memory (B/op), and performs ~3.2× more allocations. - `OptimizedContainerRoots` sits in between: it’s ~2.7× slower than `OptimizedValidatorRoots` (and ~3.4× higher B/op, ~1.8× more allocations), but it is a clear win over `ProofCollectorMerkleize` for lists/vectors: ~2.3× faster with ~1.7× fewer allocations (and essentially the same memory footprint). The main drawback is that `OptimizedContainerRoots` can only be applied to vector/list subtrees where we don’t need to collect any sibling/leaf data (i.e., no proof targets within that subtree); integrating it into the recursive merkleize(...) flow when targets are outside the subtree is expected to land in a follow-up PR. Which issues(s) does this PR fix? Partially https://github.com/OffchainLabs/prysm/issues/15598 Other notes for review In this [write-up](https://hackmd.io/@fernantho/BJbZ1xmmbg), I depict the process to come up with this solution. Future improvements: - Defensive check that the gindex is not too big, depicted [here]( https://github.com/OffchainLabs/prysm/pull/16177#discussion_r2671684100). - Integrate optimizedContainerRoots into the recursive merkleize(...) flow when proof targets are not within the subtree (skip full traversal for container lists). - Add multiproofs. - Connect `proofCollector` to SSZ-QL endpoints (direct integration of `proofCollector` for BeaconBlock endpoint and "hybrid" approach for BeaconState endpoint). Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: Radosław Kapka <radoslaw.kapka@gmail.com> Co-authored-by: Jun Song <87601811+syjn99@users.noreply.github.com>	2026-02-12 23:17:33 +01:00
Victor Farazdagi	2af65aca75	fix: bazel build failure on macOS (hashtree patch) (#16281 ) What type of PR is this? Bug fix What does this PR do? Why is it needed? It appears that #16216 introduced hashtree integration but broke builds on macOS Intel (darwin_amd64). ``` Error: Undefined symbols for architecture x86_64: "_github.com/OffchainLabs/hashtree.HashtreeHash" ``` The Bazel patch for hashtree was missing `wrapper_darwin_amd64.s`. So, `//go:noescape` in `bindings.go` assumes that symbols are available elsewhere, and while on other platforms optimized version is used, on Darwin we have stub (symbol still must be available), which needs to be referenced -- hence, this PR. Other notes for review I've re-checked using `bazel clean && bazel build //cmd/beacon-chain` -- it was failing before, works now. cc @potuz as original patch author Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). Co-authored-by: Potuz <potuz@prysmaticlabs.com>	2026-02-12 23:17:33 +01:00
terence	86e37e0d8a	gloas: add duty timing BPS and fork epoch gating (#16291 ) This PR adds gloas specific time basis points for validator duties (attestation, aggregation, and sync contribution) and wires the validator client to use them once `GloasForkEpoch` is active. For now, `GloasForkEpoch` is set to far-future so behavior is unchanged until the fork epoch is configured Note to the rev: today sync message duty uses `waitOneThirdOrValidBlock` which shares with attestation dead line, that's why sync message bps is not used	2026-02-12 23:17:33 +01:00
Potuz	85654caad5	Hdiff start database (#16203 ) Initialize state-diff database on new node startup When starting a node with --enable-state-diff feature flag, the database is now initialized appropriately based on the startup scenario: - New database + checkpoint sync: Set offset to checkpoint state slot, save checkpoint state as full snapshot - New database + genesis sync: Set offset to 0, save genesis state as full snapshot - Existing database without state-diff: Log warning that feature is ignored due to old schema - Existing database with state-diff: Return error (restarts will be handled in a future PR) Review after #16049 has merged --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Bastin <43618253+Inspector-Butters@users.noreply.github.com>	2026-02-12 23:17:33 +01:00
Bastin	04e8dd6f6a	add path field for ephemeral log file initialization (#16289 ) What does this PR do? Why is it needed? Add a field `path` to the initialization log of ephemeral-logfile feature: before: ``` [2026-01-26 19:49:34.64] DEBUG Ephemeral log file initialized ``` after: ``` [2026-01-26 19:49:34.64] DEBUG Ephemeral log file initialized path=../eth/datadir/logs/beacon-chain.log ```	2026-02-12 23:17:33 +01:00
terence	8e5ec719b0	gloas: add new payload attestation processing (#15650 ) This PR implements [process_payload_attestation](https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md#new-process_payload_attestation) and spec tests	2026-02-12 23:17:33 +01:00
james-prysm	764f7429f2	adding gloas block support to /eth/v2/beacon/blocks/{block_id} and /eth/v1/beacon/blocks/{block_id}/root (#16278 ) What type of PR is this? Feature What does this PR do? Why is it needed? adding gloas block return on `/eth/v2/beacon/blocks/{block_id}` endpoint - [/eth/v1/beacon/blocks/{block_id}/root](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getBlockRoot) should inherit this as well reference https://github.com/ethereum/beacon-APIs/pull/552/files#r2722805266 Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
Potuz	7f1dd63093	Fix arm64 hashtree builds (#16288 ) This PR fixes release builds that fail because of hashtree's patch. Should be in conjunction with #16281 --------- Co-authored-by: Preston Van Loon <preston@pvl.dev>	2026-02-12 23:17:33 +01:00
Bastin	cf392ff8fe	Add `cmd/` to `gen-logs.sh` (#16285 ) What does this PR do? Why is it needed?* This PR adds the `cmd` directory and all it's subcategories to the `hack/gen-logs.sh`. meaning that they will now have a `log.go` file and a `package` field. see the list of added packages below. some of them had different names, which has been added to the `prefixReplacements` map. packages added: "cmd" "cmd/validator/web" "cmd/validator/wallet" "cmd/validator/slashing-protection" "cmd/validator/db" "cmd/validator/accounts" "cmd/prysmctl" "cmd/prysmctl/weaksubjectivity" "cmd/prysmctl/validator" "cmd/prysmctl/testnet" "cmd/prysmctl/p2p" "cmd/prysmctl/db" "cmd/prysmctl/checkpointsync" "cmd/client-stats" "cmd/beacon-chain" "cmd/beacon-chain/storage" "cmd/beacon-chain/jwt" "cmd/beacon-chain/genesis" "cmd/beacon-chain/flags" "cmd/beacon-chain/db"	2026-02-12 23:17:33 +01:00
terence	10e73cc7c1	core: move EL requests to core/requests (#16280 ) This PR moves consolidation and withdrawal request processing into neutral package: `beacon-chain/core/requests`, such that they can be shared between fork Why? Today our core packages are mixed between two workflows: older forks calling into newer forks, and newer work calling back into older fork code. No matter which direction we settle on long-term, a clear first step is to move shared cross-fork functionality into a neutral place so we can reuse it later such that if fork A and fork B interleave each other, they can become clear abstractions Why git mv wasn’t used for consolidations? Withdrawals lived in a clean, dedicated file so it was moved with git mv. Consolidation logic was interleaved with other Electra code and needed extraction/refactor, so a pure git mv would not have preserved meaningful history	2026-02-12 23:17:33 +01:00
Bastin	4aef4817ab	Fix bug in check-logs (#16287 ) What does this PR do? Why is it needed? Fixing a bug in `check-logs.sh` where untracked files were ignored. for example PR #16216 passed the check while it shouldn't have. this change fixes the problem.	2026-02-12 23:17:33 +01:00
Bastin	24e51f283b	Add startup version log (#16283 ) What does this PR do? Why is it needed? Adds a log mentioning the name and the version of the app: Beacon-chain: ``` [2026-01-26 12:03:12.91] INFO main: Prysm Beacon Chain started. [Prysm/Unknown/Local build. Built at: Moments ago] prefix=main ``` Validator: ``` [2026-01-26 12:00:07.38] INFO main: Prysm Validator started. [Prysm/v7.1.2/7950a249266a692551e5a910adb9a82a02c92040. Built at: 2026-01-06 18:47:23+00:00] prefix=main ``` Note: I've removed the previous two logs that mentioned version in favor of these new ones. I've also moved the initialization logs of persistent log file and ephemeral log file to DEBUG. Which issues(s) does this PR fix? Fixes #16259	2026-02-12 23:17:33 +01:00
james-prysm	f8c14e5682	removing duplicate logic in /eth/v1/beacon/blocks/{block_id}/root by using blocker lookup (#16279 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Other What does this PR do? Why is it needed? [/eth/v1/beacon/blocks/{block_id}/root](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getBlockRoot) updated logic so that it uses the blocker lookup instead of mostly duplicated logic - The new implementation returns an error if no canonical block exists at a slot, while the old one would return a non-canonical block's root - adds justified as an option for block id Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: Radosław Kapka <rkapka@wp.pl>	2026-02-12 23:17:33 +01:00
terence	2e9a557026	Refactor expected withdrawals helpers (#16282 ) This refactors `ExpectedWithdrawals` to use shared helpers for pending partial withdrawals and the validator sweep. The goal is to keep the logic spec-aligned while making it easier to reuse across future forks. ``` Example (Gloas expected withdrawals order): builder withdrawals pending partial withdrawals builder sweep withdrawals validator sweep withdrawals ``` Note to reviewers: the helpers take a `[]enginev1.Withdrawal` so we can append efficiently without returning/re-appending slices.	2026-02-12 23:17:33 +01:00
terence	5ceecf69fd	Move deposit helpers out of blocks to break blocks <-> gloas cycle (#16277 ) - moves deposit-related helpers (deposit signature verification, batch verification, merkle proof verification, and activation helper) from `beacon-chain/core/blocks` into `beacon-chain/core/helpers` - updates call sites (Altair/Electra) to use helpers Why? - In gloas, the blocks package needs to call into gloas logic (e.g. clearing builder pending payments/withdrawals on proposer slashing) - gloas also introduces deposit-request processing which needs deposit signature verification previously located in blocks. That creates a Bazel/Go dependency cycle (blocks -> gloas -> blocks) - the natural layering is for blocks and fork logic to depend on a lower level util package for deposit verification, so moving deposit helpers to core/helpers breaks the cycle	2026-02-12 23:17:33 +01:00
Bastin	2e95c5fc04	logging: per package verbosity (#16272 ) What type of PR is this? Feature What does this PR do? Why is it needed? This PR adds a `--log.vmodule` flag to the beacon-chain and validator apps, that allows setting a different verbosity for every* package. *: not every package, but most packages. (all packages that define their logger variable with a `package` field) Combined with the `--verbosity` flag this allows users to control exactly what they see. This affects both the terminal and the log file (`--log-file`), but not the ephemeral debug log file. example usage: ``` ./beacon-chain --log.vmodule=beacon-chain/p2p=info,beacon-chain/sync=error,beacon-chain/sync/initial-sync=debug ``` There are improvements to be done later, like accepting just the package name instead of the full path, etc.	2026-02-12 23:17:33 +01:00
Bastin	6f68848ecd	add `NewBeaconStateGloas()` (#16275 ) What does this PR do? Why is it needed? adds `util.NewBeaconStateGloas()` also adds a missing fulu test.	2026-02-12 23:17:33 +01:00
satushh	915e4468f7	Close opened file in defer in data_column.go (#16274 ) What type of PR is this? Bug fix What does this PR do? Why is it needed? Closes an opened file which was left open. Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [ ] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [ ] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:33 +01:00
satushh	07719d8337	Add missing fulu presets to beacon config (#16170 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Feature What does this PR do? Why is it needed? Added some missing constants of fulu to beacon config so that beacon api returns expected values Which issues(s) does this PR fix? Fixes https://github.com/OffchainLabs/prysm/issues/16138 Other notes for review Acknowledgements - [ ] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [ ] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
james-prysm	4e3f6f67a7	constants update for ethspecify phase 0 (#16273 ) What type of PR is this? Other What does this PR do? Why is it needed? mapping ethspecify items that we have implemented but missing from ethspecify for constants Which issues(s) does this PR fix? follow up on https://github.com/OffchainLabs/prysm/pull/16194 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Manu NALEPA	e4be24a94a	Allow a flag to be hidden and hide the `--disable-get-blobs-v2` flag. (#16265 ) What type of PR is this? Other What does this PR do? Why is it needed? Allow a flag to be hidden and hide the `--disable-get-blobs-v2` flag. This flag is still usable, but does not show up any more in the help. This flag is used for internal purpose only, so no need to expose it publicly. Why do we need to modify the `cli.HelpPrinter` function whereas other flags like `--aggregate-first-interval` are hidden just by using the `Hidden: true` property? The `Hidden: true` property on the flag definition doesn't work by itself because `usage.go` uses a custom help template that bypasses the standard urfave/cli help rendering. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: Bastin <bastin.m@proton.me>	2026-02-12 23:17:32 +01:00
terence	90734e30c5	gloas: add modified proposer slashing processing (#16212 ) This PR implements [process_proposer_slashing](https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md#modified-process_proposer_slashing) alongside spec tests	2026-02-12 23:17:32 +01:00
james-prysm	2e62e9c5e7	adding in mid epoch timeout for e2e head synced evaluator (#16268 ) What type of PR is this? tests What does this PR do? Why is it needed? reduce e2e flakes by adding a mid epoch check for headslot sync Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
terence	9cc59a3222	gloas: add modified slot processing (#15730 ) This PR implements [process_slot](https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md#modified-process_slot) and spec tests	2026-02-12 23:17:32 +01:00
Luca \| Serenita	77b933bc9d	fix: typo in AggregateDueBPS (#16194 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Bug fix What does this PR do? Why is it needed? This PR fixes a typo which resulted in a wrong variable name to be returned on the Beacon API `/eth/v1/config/spec` endpoint: ``` curl http://127.0.0.1:49183/eth/v1/config/spec {"data":{"AGGREGRATE_DUE_BPS":"6667", [...] ``` I discovered the discrepancy while testing the change to these "BPS" values in the Vero VC which checks spec values against the ones it ships with. Which issues(s) does this PR fix? N/A Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: james-prysm <90280386+james-prysm@users.noreply.github.com>	2026-02-12 23:17:32 +01:00
terence	5b65f15378	gloas: add new pending payment processing (#15655 ) This PR implements [process_builder_pending_payments](https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md#new-process_builder_pending_payments) and spec tests.	2026-02-12 23:17:32 +01:00
Maxim Evtush	99780d61d7	Fix authentication bypass for direct `/v2/validator/` endpoints (#16226 ) This PR fixes a security vulnerability where authenticated endpoints could be accessed without authorization by using direct `/v2/validator/` paths instead of `/api/v2/validator/`. The `AuthTokenHandler` middleware only checked for authentication on requests containing `/api/v2/validator/` or `/eth/v1` prefixes, but the same handlers are also registered for direct `/v2/validator/` routes. This allowed attackers to bypass authentication by simply removing the `/api` prefix from the URL. --------- Co-authored-by: james-prysm <90280386+james-prysm@users.noreply.github.com>	2026-02-12 23:17:32 +01:00
Manu NALEPA	65c05155b6	Stop batching of KZG verification for incoming via gossip data column sidecars (#16240 ) What type of PR is this? Optimisation What does this PR do? Why is it needed? This is an alternate take of: - https://github.com/OffchainLabs/prysm/pull/16220 Test configuration: - Using the `--disable-get-blobs-v2` and `--supernode` flags - On [VPS 3000 G11](https://www.netcup.com/en/server/vps) 4H average \| Impl. \| CPU usage\| Sidecar gossip verif. dur. \| DA waiting time \| Chain service proc. time \| Total \| \|--------\|--------\|--------\|--------\|--------\|--------\| \| `develop` \| 132% \| 185 ms \| 82.2 ms \| 457 ms \| 539 ms \| \| https://github.com/OffchainLabs/prysm/pull/16220 \| 144% \| 76.5 ms \| 21.7 ms \| 473 ms \| 495 ms \| \| This PR \| 117% \| 26 ms \| 16.3 ms \| 479 ms \| 495 ms \| Before this PR: <img width="950" height="1296" alt="image" src="https://github.com/user-attachments/assets/1fb45282-a9c8-4543-adb3-39b04b79eab2" /> With this PR: <img width="950" height="1301" alt="image" src="https://github.com/user-attachments/assets/993feb49-ef38-4052-9cb4-aebe93456eba" /> Metrics: - `beacon_data_column_sidecar_gossip_verification_milliseconds` - `da_waited_time_milliseconds` Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Preston Van Loon	4c01c2e580	Fix issue : Prevent makeslice panic from invalid Count values (#16227 ) What type of PR is this? Bug fix What does this PR do? Why is it needed? Add defensive checks to prevent panic from large Count values that could result from unsigned integer underflow: 1. In batch.blockRequest() and batch.blobRequest(): Return Count=0 when end <= begin, preventing the underflow at the source. 2. In SendBeaconBlocksByRangeRequest(): Cap slice capacity to MaxRequestBlock before allocation to prevent panic even if upstream code produces invalid values. Which issues(s) does this PR fix? Fixes #16223 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Manu NALEPA	e87302a740	Remove unused delay parameter from `fetchOriginDataColumnSidecars` function. (#16262 ) What type of PR is this? Other What does this PR do? Why is it needed? Remove unused delay parameter from `fetchOriginDataColumnSidecars` function. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
willian.eth	f2c8c5204e	Add shell completion for beacon-chain and validator CLI (#16245 ) What type of PR is this? Feature What does this PR do? Why is it needed? Introduces a `completion` subcommand to `beacon-chain` and `validator` that outputs shell completion scripts. Supports Bash, Zsh, and Fish shells. ```bash # Load completions in current session source <(beacon-chain completion bash) # Persist for future sessions beacon-chain completion zsh > "${fpath[1]}/_beacon-chain" validator completion fish > ~/.config/fish/completions/validator.fish ``` Once loaded, users can press TAB to complete subcommands, nested commands, and flags. Flag completion supports prefix matching (e.g., typing `--exec<TAB>` suggests `--execution-endpoint`, `--execution-headers`). Which issues(s) does this PR fix? Fixes #16244 Other notes for review The implementation adds three files to the existing `cmd` package: - `completion.go` - Defines `CompletionCommand()` returning a `cli.Command` with `bash`, `zsh`, `fish` subcommands - `completion_scripts.go` - Contains the shell script templates - `completion_test.go` - Unit tests for command structure and script content Changes to `beacon-chain` and `validator`: - Import `cmd.CompletionCommand("binary-name")` in the Commands slice - Set `EnableBashCompletion: true` on the cli.App to activate urfave/cli's `--generate-bash-completion` hidden flag The shell scripts call the binary with `--generate-bash-completion` appended to get context-aware suggestions. This means completions automatically reflect the current binary's flags and commands. Acknowledgements* - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). Signed-off-by: Willian Paixao <willian@ufpa.br>	2026-02-12 23:17:32 +01:00
Bastin	574b7fb520	state-diff small changes (#16260 ) What does this PR do? small touch ups on state diff code.	2026-02-12 23:17:32 +01:00
satushh	db727a9bf4	Print commitments instead of indices (#16258 ) What type of PR is this? Other What does this PR do? Why is it needed? Print commitments instead of indices in `missingCommitError` function Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [ ] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [ ] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
terence	e290c7ba6b	gloas: add new execution payload bid processing (#15638 ) This PR implements [process_execution_payload_bid](https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md#new-process_execution_payload_bid) and spec tests	2026-02-12 23:17:32 +01:00
Preston Van Loon	6f5a01b232	CI: Add gazelle update-repos check (#16257 ) What type of PR is this? Other What does this PR do? Why is it needed? This wont pass til #16252 merges Which issues(s) does this PR fix? Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Victor Farazdagi	12616a0695	fix: use input genesis.json timestamp in prysmctl (#16239 ) What type of PR is this? Bug fix What does this PR do? Why is it needed? - When no `--genesis-time` is provided we default to `now()`, instead of using `timestamp` from provided `--geth-genesis-json-in` input file - This results in inconsistencies, especially, if the input file is not overwritten using `--geth-genesis-json-out` (say, the generator is used to produce the `genesis.ssz` file only, as described in the original issue) Which issues(s) does this PR fix? Fixes #16002 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Victor Farazdagi	775f75dcac	refactor: remove gometalinter refs (#16229 ) What type of PR is this? Refactor/Cleanup What does this PR do? Why is it needed? - [gometalinter](https://github.com/alecthomas/gometalinter) project is deprecated (has been forever so) - in #2100 it has been removed from the Prysm project - while not being used `gometalinter` references still existed in Bazel config. Since `gometalinter.json` was removed in PR-2100, the `bazel run //:gometalinter` will err unless config file re-created, hence it appears we have a dead code. Which issues(s) does this PR fix? No issue, simple cleanup Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Preston Van Loon	be9982b719	Update go-ethereum to v1.16.8 (security fix release) (#16252 ) What type of PR is this? Other What does this PR do? Why is it needed? Updating our internal geth dependency after today's release. Which issues(s) does this PR fix? Other notes for review No known security issues in Prysm. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Galoretka	ae489ed1df	fix: stop SlotIntervalTicker goroutine leaks (#16241 ) `SlotIntervalTicker` was created in `prepareForkChoiceAtts` and in the fork-choice attestation processing routine without ever calling `Done()` when the service context was cancelled. Once the consuming goroutine exits on `ctx.Done()`, the ticker keeps running and eventually blocks on sending to its channel, leaving a leaked goroutine behind. This change wires the lifetime of the `SlotIntervalTicker` to the corresponding service contexts by calling `ticker.Done()` on `ctx.Done()` in both call sites. This keeps the behaviour of the routines unchanged while ensuring the ticker goroutines exit cleanly on shutdown, consistent with how regular `SlotTicker` is handled elsewhere in the codebase.	2026-02-12 23:17:32 +01:00
Manu NALEPA	902fda92d0	Add metrics monitoring blob count per block (#16254 ) What type of PR is this? Feature What does this PR do? Why is it needed? Add metrics monitoring blob count per block for block received via gossip <img width="954" height="659" alt="image" src="https://github.com/user-attachments/assets/ae9ff9ed-06ae-473b-bb4e-f162cf17702b" /> Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
satushh	dc209fa7c5	Avoid unnecessary heap allocation (#16251 ) What type of PR is this? Micro optimisation What does this PR do? Why is it needed? Avoids unnecessary allocation Acknowledgements - [ ] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [ ] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
james-prysm	8ca3a374b3	adding cache for attestation data so we don't call it multiple times (#16236 ) What type of PR is this? Other What does this PR do? Why is it needed? post electra attestation data calls are the same in a slot because committee information is 0, we can save some api calls by caching the attestation data per slot. Which issues(s) does this PR fix? Fixes # https://github.com/OffchainLabs/prysm/issues/16228 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:32 +01:00
Potuz	958f8351a1	Use dependent root when validating data column (#16250 ) This PR uses the head state to validate data column in more places than we currently do. When the parent state is from the previous epoch and is the head (for example at slot 0) instead of replaying slot and doing an epoch transition, we use the head state directly. Another change is that instead of replaying until the parent state in the case of a head miss, we only replay until the target checkpoint state, which is more likely to be a checkpoint state in the epoch boundary cache. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-12 23:17:32 +01:00
Nina	28d93bdf10	docs: fix broken links (#15856 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Documentation What does this PR do? Why is it needed? Fixes broken and old links in documentation following code standards and to avoid possible future problems with redirects Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description to this PR with sufficient context for reviewers to understand this PR. --------- Co-authored-by: james-prysm <90280386+james-prysm@users.noreply.github.com>	2026-02-12 23:17:32 +01:00
james-prysm	ec3b224392	fulu e2e (#15640 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Feature What does this PR do? Why is it needed? - upgrading go ethereum to 1.16.7 - enabling fulu e2e - added new e2e field params and build option - removes github.com/MariusVanDerWijden/FuzzyVM v0.0.0-20240516070431-7828990cad7d and github.com/MariusVanDerWijden/tx-fuzz v1.4.0 what changed - e2e config on slots per epoch increased to match minimum 6->8 a 33% increase in run time ( this is needed because field params only have minimum presets and proposer look ahead feature uses it, so if it doesn't match it fails) - reduce presubmit epochs from 18 -> 10 and only run for electra -> fulu - moves bellatrix -> fulu post merge test to post submit Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description to this PR with sufficient context for reviewers to understand this PR. --------- Co-authored-by: Preston Van Loon <preston@pvl.dev> Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com> Co-authored-by: Radosław Kapka <rkapka@wp.pl> Co-authored-by: Potuz <potuz@prysmaticlabs.com>	2026-02-12 23:17:32 +01:00
Potuz	dfdc3967c1	Migrate to cold with state diffs (#16049 ) This PR adds the logic to migrate to cold when the database has the hdiff feature. The main difference is that the boundary states have to have the right slot therefore they need to be advanced and aren't necessarily the post-state of a given beacon block root. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-12 23:17:32 +01:00
Potuz	3251f1c6fa	Hashtree from source (#16216 ) A try to #14524 without using the syso files --------- Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-12 23:17:32 +01:00
Manu NALEPA	59f5c040c9	Earliest available slot at node start: Use the justified checkpoint. (#16230 ) What type of PR is this? Bug fix What does this PR do? Why is it needed? Before this PR: When starting the node with the `--[semi-]supernode` flag with an already existing DB, the new value of the earliest available slot was set to the slot of the latest finalized checkpoint. ==> Between the latest finalized checkpoint and the slot where Prysm starts to actually sync (the justified checkpoint) after the reboot, Prysm advertises a higher `cgc` than it should. With this PR: If, at node start, the node needs to increase its `cgc`, then it uses the latest justified checkpoint (+ 1) for the new `eas`. Which issues(s) does this PR fix? - https://github.com/OffchainLabs/prysm/issues/16066 Example of a test case: 1. Start the node with an empty DB, without any validator connected. ``` [2026-01-09 13:38:21.77] DEBUG db: Custody info earliestAvailableSlot=2145952 groupCount=4 ``` 2. Try: ``` curl http://localhost:3500/eth/v1/beacon/blobs/2145952 \| jq { "message": "Not found: the node does not custody enough data columns to reconstruct blobs - please start the beacon node with the `--semi-supernode` flag to ensure this call to succeed", "code": 404 } ``` ==> This is expected, since `cgc=4 < 64` 3. After a few epochs, add a few validators (< 64): ``` [2026-01-09 13:43:21.77] DEBUG db: Custody info earliestAvailableSlot=2146066 groupCount=10 ``` 4. Try: ``` curl http://localhost:3500/eth/v1/beacon/blobs/2146066 \| jq { "message": "Not found: the node does not custody enough data columns to reconstruct blobs - please start the beacon node with the `--semi-supernode` flag to ensure this call to succeed", "code": 404 } ``` ==> This is expected, since `cgc=10 < 64` 5. After a few epochs, restart the node: ``` [2026-01-09 13:46:44.09] DEBUG db: Custody info earliestAvailableSlot=2146066 groupCount=10 ``` ==> OK (No change) 6. Restart the node with the `--semi-supernode` flag. ``` [2026-01-09 13:49:26.14] DEBUG db: Custody info earliestAvailableSlot=2146049 groupCount=64 ``` The `eas` goes backward which is expected, since the node restarts syncing from the latest justified checkpoint, which in this case is lower than the slot where we added validators during step `3.`. Try: ``` curl http://localhost:3500/eth/v1/beacon/blobs/2146049 \| jq ==> OK ``` The whole `eas/cgc` advertisement management should probably be re-thinked, for example by using what the node actually has in its DB to decide what `eas/cgc` should be advertised. (With a particular attention to the full node case until https://github.com/OffchainLabs/prysm/issues/16065 is fixed.) However, this PR fixes the linked issue, so it's a good fix until a deeper redesign is done. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Potuz	ed3d3bfa2b	Update Spectests to v1.7.0.alpha-1 (#16246 )	2026-02-12 23:17:31 +01:00
Jun Song	b4ba3c7042	feat: generalize proof generation for beacon state fields (#15443 ) What type of PR is this? Feature What does this PR do? Why is it needed? Which issues(s) does this PR fix? This PR is the part of EPF6 project: [Merkle Proofs of Everything](https://github.com/eth-protocol-fellows/cohort-six/blob/master/projects/project-ideas.md#prysm-merkle-proofs-of-everything). Other notes for review You can see some rationale and future TODOs in [my HackMD post](https://hackmd.io/@junsong/SJGze5cNxg). The main next task is following: (excerpted from the post) > More generally speaking, we should find a way to prove for an item with generalized index more than 128. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description to this PR with sufficient context for reviewers to understand this PR. --------- Co-authored-by: Radosław Kapka <rkapka@wp.pl>	2026-02-12 23:17:31 +01:00
Potuz	14597d9cf6	Add feature flag to verify signatures before proposing (#15920 ) Adds a feature flag `--enable-proposer-preprocessing` to verify individual signatures in the block right before proposing to fallback to empty fields in case of failure. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-12 23:17:31 +01:00
Potuz	33b1842664	Add --low-valcount-sweep feature flag for withdrawal sweep bound (#16231 ) Gate the withdrawal sweep optimization (using min of validator count and MaxValidatorsPerWithdrawalsSweep) behind a hidden feature flag that defaults to false. Enable the flag for spectests to match consensus spec. The backported changes were from [4788](https://github.com/ethereum/consensus-specs/pull/4788) Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-12 23:17:31 +01:00
Bastin	c11fa183b9	Ephemeral debug logfile (#16108 ) What type of PR is this? Feature What does this PR do? Why is it needed? This PR introduces an ephemeral log file that captures debug logs for 24 hours. - it captures debug logs regardless of the user provided (or non-provided) `--verbosity` flag. - it allows a maximum of 250MB for each log file. - it keeps 1 backup logfile in case of size-based rotations. (as opposed to time-based) - this is enabled by default for beacon and validator nodes. - the log files live in `datadir/logs/` directory under the names of `beacon-chain.log` and `validator.log`. backups have a timestamp in their name as well. - the feature can be disabled using the `--disable-ephemeral-log-file` flag.	2026-02-12 23:17:31 +01:00
Bastin	a8f46703ba	Set logging verbosity per writer hook instead of globally (#16106 ) What type of PR is this? Feature What does this PR do? Why is it needed? This PR sets the logging verbosity level per writer hook (per output: terminal, log file, etc) rather than setting a global logrus level which limits customizing each output. it set the terminal and log file output to be the same as the user provided `--verbosity` flag. so nothing changes in reality. it also introduces a `SetLoggingLevel()` to be used instead of `logrus.SetLeveL()` in order for us to be able to set a different baseline level later on if needed. (my next PR will use this). I'm only making this change in the `beacon-chain` and `validator` apps, skipping tools like `bootnode` and `client-stats`.	2026-02-12 23:17:31 +01:00
terence	e66918ba97	gloas: add builders registry and update state fields (#16164 ) This pr implements the Gloas builder registry and related beacon state fields per the spec, including proto/SSZ updates and state-native wiring for builders, payload availability, pending payments/withdrawals, and expected withdrawals. This aligns BeaconState with the Gloas container changes and adds supporting hashing/copy helpers. Spec ref: https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md	2026-02-12 23:17:31 +01:00
Preston Van Loon	ca0c4072f0	Changelog for v7.1.2 (#16225 ) What type of PR is this? Documentation What does this PR do? Why is it needed? Which issues(s) does this PR fix? Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
satushh	0fb4cecaf1	Use copy() instead of byte-by-byte loop (#16222 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Optimisation What does this PR do? Why is it needed? use copy() instead of byte-by-byte loop which isn't required. Which issues(s) does this PR fix? Fixes # Other notes for review Acknowledgements - [ ] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [ ] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Potuz	e19adbe489	update spectests (#16219 )	2026-02-12 23:17:31 +01:00
james-prysm	8f54f01c70	changing isHealthy to isReady (#16167 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Bug fix What does this PR do? Why is it needed? validator fallbacks shouldn't work on nodes that are syncing as many of the tasks validators perform require the node to be fully synced. - 206 or any other code is interpreted as "not ready" - 200 interpreted as "ready" Which issues(s) does this PR fix? continuation of https://github.com/OffchainLabs/prysm/pull/15401 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Preston Van Loon	8550b64934	Tests: Add require.Eventually and fix a few test flakes (#16217 ) What type of PR is this? Other What does this PR do? Why is it needed? This is a better way to wait for a test condition to hit, rather than time.Sleep. Which issues(s) does this PR fix? Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Jonny Rhea	1d3d5168d1	WithMaxExportBatchSize is specified twice (#16211 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? > Bug fix What does this PR do? Why is it needed? It's just a simple fix. I was looking at how prysm uses OpenTelemetry and I noticed it. Which issues(s) does this PR fix? Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Manu NALEPA	c632e51e61	Add the `--disable-get-blobs-v2` flag and fixes #16171 (#16155 ) What type of PR is this? Feature + Bugfix What does this PR do? Why is it needed? Starting at Fusaka, the beacon node can pull blobs with the `engine_getBlobsV2` API from the execution layer. This reduces by a lot the burden on the beacon node. However, the beacon node should be able to work 100% correctly without this execution layer help. This PR introduces the `--disable-get-blobs-v2` flag to simulate a 0% success rate of this engine API. This PR also fixes: - https://github.com/OffchainLabs/prysm/issues/16171 Please read commit by commit with commit messages. How to test it: For the `--disable-get-blobs-v2` part: Run the beacon node with the `--disable-get-blobs-v2` flag in DEBUG mode. For every block with commitments, the following log should be displayed: ``` [2025-12-19 15:36:25.49] DEBUG sync: No data column sidecars constructed from the execution client ... ``` And the following log should never be displayed: ``` [2026-01-05 10:19:00.55] DEBUG sync: Constructed data column sidecars from the execution client count=... ``` For the #16171 part: - No ERROR log showed in the linked issue should never be displayed. Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Preston Van Loon	6bce4dbdbc	Added changelog for v7.1.1 (#16161 ) <!-- Thanks for sending a PR! Before submitting: 1. If this is your first PR, check out our contribution guide here https://docs.prylabs.network/docs/contribute/contribution-guidelines You will then need to sign our Contributor License Agreement (CLA), which will show up as a comment from a bot in this pull request after you open it. We cannot review code without a signed CLA. 2. Please file an associated tracking issue if this pull request is non-trivial and requires context for our team to understand. All features and most bug fixes should have an associated issue with a design discussed and decided upon. Small bug fixes and documentation improvements don't need issues. 3. New features and bug fixes must have tests. Documentation may need to be updated. If you're unsure what to update, send the PR, and we'll discuss in review. 4. Note that PRs updating dependencies and new Go versions are not accepted. Please file an issue instead. 5. A changelog entry is required for user facing issues. --> What type of PR is this? Documentation What does this PR do? Why is it needed? v7.1.1 release is coming today Which issues(s) does this PR fix? Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Aarsh Shah	91376f8f6b	p2p: batch publish data column sidecars (#16183 ) What type of PR is this? Feature What does this PR do? Why is it needed? This PR takes @MarcoPolo 's PR at https://github.com/OffchainLabs/prysm/pull/16130 to completion with tests. The description on his PR: """ a relatively small change to optimize network send order. Without this, network writes tend to prioritize sending data for one column to all peers before sending data for later columns (e.g for two columns and 4 peers per column it would send A,A,A,A,B,B,B,B). With batch publishing we can change the write order to round robin across columns (e.g. A,B,A,B,A,B,A,B). In cases where the process is sending at a rate over the network limit, this approach allows at least some copies of the column to propagate through the network. In early simulations with bandwidth limits of 50mbps for the publisher, this improved dissemination by ~20-30%. """ See the issue for some more context. Which issues(s) does this PR fix? Fixes https://github.com/OffchainLabs/prysm/issues/16129 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: Marco Munizaga <git@marcopolo.io> Co-authored-by: Kasey Kirkham <kasey@users.noreply.github.com> Co-authored-by: kasey <489222+kasey@users.noreply.github.com> Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com> Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com>	2026-02-12 23:17:31 +01:00
Bastin	b249803a06	Logrus hooks for terminal vs log-file output (#16102 ) ## Review after #16059 What type of PR is this? Feature What does this PR do? This PR introduces logrus writer hooks into the logging of prysm. when log-format is text: - set the default logrus output to be `io.Discard` - create a writer hook for terminal, with formatting and coloring enabled. - create a separate writer hook for log-file (if enabled), without coloring. This immediately allows for having formatted/colored terminal logs, while keeping the log-file clean.	2026-02-12 23:17:31 +01:00
Bastin	4b42c5373e	Switch logging from using prefixes to the new package path format (#16059 ) #### This PR sets the foundation for the new logging features. --- The goal of this big PR is the following: 1. Adding a log.go file to every package: [_commit_](`54f6396d4c`) - Writing a bash script that adds the log.go file to every package that imports logrus, except the excluded packages, configured at the top of the bash script. - the log.go file creates a log variable and sets a field called `package` to the full path of that package. - I have tried to fix every error/problem that came from mass generation of this file. (duplicate declarations, different prefix names, etc...) - some packages had the log.go file from before, and had some helper functions in there as well. I've moved all of them to a `log_helpers.go` file within each package. 2. Create a CI rule which verifies that: [_commit_](`b799c3a0ef`) - every package which imports logrus, also has a log.go file, except the excluded packages. - the `package` field of each log.go variable, has the correct path. (to detect when we move a package or change it's name) - I pushed a commit with a manually changed log.go file to trigger the ci check failure and it worked. 3. Alter the logging system to read the prefix from this `package` field for every log while outputing: [_commit_](`b0c7f1146c`) - some packages have/want/need a different log prefix than their package name (like `kv`). This can be solved by keeping a map of package paths to prefix names somewhere. --- Some notes: - Please review everything carefully. - I created the `prefixReplacement` map and populated the data that I deemed necessary. Please check it and complain if something doesn't make sense or is missing. I attached at the bottom, the list of all the packages that used to use a different name than their package name as their prefix. - I have chosen to mark some packages to be excluded from this whole process. They will either not log anything, or log without a prefix, or log using their previously defined prefix. See the list of exclusions in the bottom. - I fixed all the tests that failed because of this change. These were failing because they were expecting the old prefix to be in the generated logs. I have changed those to expect the new `package` field instead. This might not be a great solution. Ideally we might want to remove this from the tests so they only test for relevant fields in the logs. but this is a problem for another day. - Please run the node with this config, and mention if you see something weird in the logs. (use different verbosities) - The CI workflow uses a script that basically runs the `hack/gen-logs.sh` and checks that the git diff is zero. that script is `hack/check-logs.sh`. This means that if one runs this script locally, it will not actually _check_ anything, rather than just regenerate the log.go files and fix any mistake. This might be confusing. Please suggest solutions if you think it's a problem. --- A list of packages that used a different prefix than their package names for their logs: - beacon-chain/cache/depositsnapshot/ package depositsnapshot, prefix "cache" - beacon-chain/core/transition/log.go — package transition, prefix "state" - beacon-chain/db/kv/log.go — package kv, prefix "db" - beacon-chain/db/slasherkv/log.go — package slasherkv, prefix "slasherdb" - beacon-chain/db/pruner/pruner.go — package pruner, prefix "db-pruner" - beacon-chain/light-client/log.go — package light_client, prefix "light-client" - beacon-chain/operations/attestations/log.go — package attestations, prefix "pool/attestations" - beacon-chain/operations/slashings/log.go — package slashings, prefix "pool/slashings" - beacon-chain/rpc/core/log.go — package core, prefix "rpc/core" - beacon-chain/rpc/eth/beacon/log.go — package beacon, prefix "rpc/beaconv1" - beacon-chain/rpc/eth/validator/log.go — package validator, prefix "beacon-api" - beacon-chain/rpc/prysm/v1alpha1/beacon/log.go — package beacon, prefix "rpc" - beacon-chain/rpc/prysm/v1alpha1/validator/log.go — package validator, prefix "rpc/validator" - beacon-chain/state/stategen/log.go — package stategen, prefix "state-gen" - beacon-chain/sync/checkpoint/log.go — package checkpoint, prefix "checkpoint-sync" - beacon-chain/sync/initial-sync/log.go — package initialsync, prefix "initial-sync" - cmd/prysmctl/p2p/log.go — package p2p, prefix "prysmctl-p2p" - config/features/log.go -- package features, prefix "flags" - io/file/log.go — package file, prefix "fileutil" - proto/prysm/v1alpha1/log.go — package eth, prefix "protobuf" - validator/client/beacon-api/log.go — package beacon_api, prefix "beacon-api" - validator/db/kv/log.go — package kv, prefix "db" - validator/db/filesystem/db.go — package filesystem, prefix "db" - validator/keymanager/derived/log.go — package derived, prefix "derived-keymanager" - validator/keymanager/local/log.go — package local, prefix "local-keymanager" - validator/keymanager/remote-web3signer/log.go — package remote_web3signer, prefix "remote-keymanager" - validator/keymanager/remote-web3signer/internal/log.go — package internal, prefix "remote-web3signer- internal" - beacon-chain/forkchoice/doubly... prefix is "forkchoice-doublylinkedtree" List of excluded directories (their subdirectories are also excluded): ``` EXCLUDED_PATH_PREFIXES=( "testing" "validator/client/testutil" "beacon-chain/p2p/testing" "beacon-chain/rpc/eth/config" "beacon-chain/rpc/prysm/v1alpha1/debug" "tools" "runtime" "monitoring" "io" "cmd" ".well-known" "changelog" "hack" "specrefs" "third_party" "bazel-out" "bazel-bin" "bazel-prysm" "bazel-testlogs" "build" ".github" ".jj" ".idea" ".vscode" ) ```	2026-02-12 23:17:31 +01:00
Manu NALEPA	66a5721926	Summarize "Accepted data column sidecars summary" log. (#16210 ) What type of PR is this? Other What does this PR do? Why is it needed? Before: ``` [2026-01-02 13:29:50.13] DEBUG sync: Accepted data column sidecars summary columnIndices=[0 1 6 7 8 9 10 11 12 13 14 15 16 18 23 28 29 31 32 35 37 38 39 40 41 42 43 45 47 48 49 50 51 52 55 58 59 60 62 65 66 68 70 73 74 75 76 78 79 81 83 84 88 89 90 93 94 95 96 98 99 103 105 106 107 108 109 110 111 113 114 115 117 118 119 121 122] gossipScores=[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] peers=[rjzcRC oxj6o4 HCT2LE HCT2LE oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 HCT2LE HCT2LE aZAzfp HCT2LE HCT2LE oxj6o4 oxj6o4 oxj6o4 HCT2LE oxj6o4 oxj6o4 HCT2LE oxj6o4 HCT2LE oxj6o4 oxj6o4 oxj6o4 HCT2LE oxj6o4 oxj6o4 HCT2LE HCT2LE oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 HCT2LE oxj6o4 HCT2LE oxj6o4 oxj6o4 HCT2LE aZAzfp oxj6o4 oxj6o4 YdJQCg oxj6o4 oxj6o4 oxj6o4 HCT2LE oxj6o4 HCT2LE HCT2LE 5jMhEK HCT2LE oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 oxj6o4 HCT2LE rjzcRC oxj6o4 HCT2LE oxj6o4 oxj6o4 HCT2LE oxj6o4 oxj6o4 HCT2LE HCT2LE HCT2LE oxj6o4] receivedCount=77 sinceStartTimes=[869.00ms 845.00ms 797.00ms 795.00ms 805.00ms 906.00ms 844.00ms 849.00ms 843.00ms 844.00ms 821.00ms 796.00ms 794.00ms 796.00ms 838.00ms 842.00ms 843.00ms 848.00ms 795.00ms 820.00ms 797.00ms 830.00ms 801.00ms 794.00ms 925.00ms 924.00ms 935.00ms 843.00ms 802.00ms 796.00ms 802.00ms 798.00ms 794.00ms 796.00ms 796.00ms 843.00ms 802.00ms 830.00ms 826.00ms 796.00ms 819.00ms 801.00ms 852.00ms 877.00ms 876.00ms 843.00ms 843.00ms 844.00ms 1138.00ms 843.00ms 886.00ms 805.00ms 794.00ms 844.00ms 909.00ms 845.00ms 889.00ms 798.00ms 792.00ms 843.00ms 878.00ms 802.00ms 798.00ms 849.00ms 826.00ms 815.00ms 844.00ms 797.00ms 795.00ms 798.00ms 843.00ms 844.00ms 845.00ms 845.00ms 867.00ms 805.00ms 800.00ms] slot=2095599 validationTimes=[399.00ms 423.00ms 470.00ms 472.00ms 463.00ms 362.00ms 423.00ms 419.00ms 425.00ms 423.00ms 446.00ms 471.00ms 473.00ms 471.00ms 429.00ms 425.00ms 424.00ms 419.00ms 471.00ms 448.00ms 470.00ms 437.00ms 467.00ms 472.00ms 342.00ms 343.00ms 332.00ms 424.00ms 465.00ms 471.00ms 465.00ms 469.00ms 473.00ms 470.00ms 470.00ms 424.00ms 466.00ms 438.00ms 442.00ms 471.00ms 448.00ms 467.00ms 416.00ms 390.00ms 392.00ms 424.00ms 425.00ms 423.00ms 140.00ms 424.00ms 381.00ms 462.00ms 473.00ms 423.00ms 359.00ms 423.00ms 378.00ms 469.00ms 475.00ms 425.00ms 390.00ms 465.00ms 469.00ms 419.00ms 442.00ms 452.00ms 423.00ms 470.00ms 473.00ms 469.00ms 424.00ms 423.00ms 423.00ms 423.00ms 400.00ms 462.00ms 467.00ms] ``` After: ``` [2026-01-02 16:48:48.61] DEBUG sync: Accepted data column sidecars summary count=31 indices=0-1,3-5,7,21,24,27,29,36-37,46,48,55,57,66,70,76,82,89,93-94,97,99-101,113,120,124,126 root=0x409a4eac4761a3199f60dec0dfe50b6eed91e29d6c3671bb61704401906d2b69 sinceStartTime=[min: 512.181127ms, avg: 541.358688ms, max: 557.074707ms] slot=2096594 validationTime=[min: 13.357515ms, avg: 55.1343ms, max: 73.909889ms] ``` Distributions are still available on metrics: <img width="792" height="309" alt="image" src="https://github.com/user-attachments/assets/15128283-6740-4387-b205-41fb18205f54" /> <img width="799" height="322" alt="image" src="https://github.com/user-attachments/assets/e0d602fa-db06-4cd3-8ec7-1ee2671c9921" /> Which issues(s) does this PR fix? Fixes: - https://github.com/OffchainLabs/prysm/issues/16208 Other notes for review Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:31 +01:00
Potuz	eb2b2f706f	Use proposer lookahead for data column verification (#16202 ) Replace the proposer indices cache usage in data column sidecar verification with direct state lookahead access. Since data column sidecars require the Fulu fork, the state always has a ProposerLookahead field that provides O(1) proposer index lookups for current and next epoch. This simplifies SidecarProposerExpected() by removing: - Checkpoint-based proposer cache lookup - Singleflight wrapper (not needed for O(1) access) - Target root computation for cache keys 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-12 23:17:31 +01:00
Manu NALEPA	2d59dd5cc5	Data columns cache warmup: Parallelize computation of all files for a given epoch. (#16207 ) What type of PR is this? Other What does this PR do? Why is it needed? Before this PR, all `.sszs` files containing the data column sidecars were read an process sequentially, taking some time. After this PR, every `.sszs` files of a given epoch (so, up to 32 files with the current `SLOT_PER_EPOCHS` value) are processed in parallel. Which issues(s) does this PR fix? - https://github.com/OffchainLabs/prysm/issues/16204 Tested on - [Netcup VPS 4000 G11](https://www.netcup.com/en/server/vps). Before this PR (3 trials): ``` [2026-01-02 08:55:12.71] INFO filesystem: Data column filesystem cache warm-up complete elapsed=1m22.894007534s [2026-01-02 12:59:33.62] INFO filesystem: Data column filesystem cache warm-up complete elapsed=42.346732863s [2026-01-02 13:03:13.65] INFO filesystem: Data column filesystem cache warm-up complete elapsed=56.143565960s ``` After this PR (3 trials): ``` [2026-01-02 12:50:07.53] INFO filesystem: Data column filesystem cache warm-up complete elapsed=2.019424193s [2026-01-02 12:52:01.34] INFO filesystem: Data column filesystem cache warm-up complete elapsed=1.960671225s [2026-01-02 12:53:34.66] INFO filesystem: Data column filesystem cache warm-up complete elapsed=2.549555363s ``` Acknowledgements - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).	2026-02-12 23:17:30 +01:00

2 changed files with 1 additions and 10 deletions

									
										9

beacon-chain/blockchain/process_block.go
									
												View File
												
				@@ -106,12 +106,7 @@ func (s *Service) postBlockProcess(cfg *postBlockProcessConfig) error {

					// Pre-Fulu the caches are updated when computing the payload attributes

					if cfg.postState.Version() >= version.Fulu {

						go func() {

							ctx, cancel := context.WithTimeout(s.ctx, slotDeadline)

							defer cancel()

							cfg.ctx = ctx

							s.updateCachesPostBlockProcessing(cfg)

						}()

						go s.updateCachesPostBlockProcessing(cfg)

					}

					return nil

				}

				@@ -934,8 +929,6 @@ func (s *Service) lateBlockTasks(ctx context.Context) {

						// After Fulu, we can update the caches asynchronously after sending FCU to the engine

						defer func() {

							go func() {

								ctx, cancel := context.WithTimeout(s.ctx, slotDeadline)

								defer cancel()

								lastState.CopyAllTries()

								if err := transition.UpdateNextSlotCache(ctx, lastRoot, lastState); err != nil {

									log.WithError(err).Debug("Could not update next slot state cache")

									
										2

changelog/potuz_fcu_ctx.md
									
												View File
											
				@@ -1,2 +0,0 @@

				### Changed

				- Use a separate context when updating the slot cache.

Compare commits

83 Commits

v7.1.3-rc. ... manu

9

beacon-chain/blockchain/process_block.go

View File

2

changelog/potuz_fcu_ctx.md

View File

Compare commits

83 Commits v7.1.3-rc. ... manu

9 beacon-chain/blockchain/process_block.go Unescape Escape View File

2 changelog/potuz_fcu_ctx.md Unescape Escape View File

83 Commits

v7.1.3-rc. ... manu

9

beacon-chain/blockchain/process_block.go

View File

2

changelog/potuz_fcu_ctx.md

View File