Conversation
* feat(beacon): broadcast data column sidecars from proposer * feat: add e2e test for multihop, address ef-test fail
- include develop in pull request branch filters - enable Rust, documentation, interop, and PR title checks for develop-based PRs - keep push workflows restricted to master
* feat(beacon): integrate data column sidecars with availability checks - add pending data availability tracking for beacon blocks - defer block import until all required data columns are available - validate and persist incoming data column sidecars - resume pending block import when availability requirements are met - backfill columns stored before their corresponding block arrives - prune stale pending entries using finality and the configured retention window - preserve pending blocks after the finalized checkpoint slot - prevent imported blocks from recreating orphan availability entries - harden data column sidecar gossip validation - add regression tests for finalized-slot and retention-boundary pruning * test(beacon): verify blob blocks finalize after data availability - reuse the data column propagation scenario for finality coverage - enable data availability checks explicitly for the Electra-based E2E fixture - wait until the blob block epoch is finalized on both beacon nodes - assert the finalized canonical chain contains the propagated blob block - keep production data availability checks gated by the configured Fulu fork * fix(networking): initialize KZG before sidecar validation - initialize the KZG trusted setup before processing data column gossip - prevent the first sidecar validation from exceeding gossipsub cache retention - rename the multi-hop propagation test to avoid overlapping Cargo test filters * fix(beacon): stabilize data column availability handling - persist data column sidecars atomically to prevent partial reads during concurrent writes - allow tests to override gossipsub history length for slow CI validation - extend relay message retention in the multi-hop propagation test - validate EF data column fixtures before storing them - require EF blocks to be fully imported instead of treating pending availability as success - key EF sidecars by their signed block root and column index - remove unused fork-choice KZG dependencies * test(beacon): stabilize data availability finality test - route all validators through a single canonical beacon node - keep the second node as a peer for sidecar propagation and storage checks - avoid unrelated unknown-parent forks preventing finality * fix(test): apply finality validator setup to the correct flow - restore the standard block production test setup - use a single canonical validator endpoint for the DA finality test - fix clippy and cargo-udeps compilation * fix(beacon): use configured data column retention window - read the sidecar retention period from BeaconNetworkSpec - remove the duplicated consensus constant - keep the availability boundary test independent of network defaults
jsonwebtoken 11 requires exactly one of the `rust_crypto` or `aws_lc_rs` features;
its default feature set (`use_pem`) includes neither, so since the 9.3.1 -> 11.0.0
bump no crypto provider has been compiled in and every engine API request panics
while signing the JWT:
Could not automatically determine the process-level CryptoProvider
from jsonwebtoken crate features.
Beacon nodes talking to an execution client therefore fail authentication, receive
no payloads, produce no blocks, and the devnet5 serial tests time out waiting for
the head to advance past slot 0.
Prefer the pure-Rust provider: `ream-consensus-beacon` depends on
`ream-execution-engine` and is built for the riscv32im zkVM targets, where a C
library dependency would not build. `default-features` is disabled because only
`EncodingKey::from_secret` (HS256) is used and no PEM parsing is needed.
* fix: support checkpoint sync and P2P handshake on post-Fulu networks * fix: use current_epoch for data column sidecar broadcast fork digest
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.