Release v1.3.0-alpha.1 -- capella and 4844 prelease #3116
Merged
Conversation
This file contains 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
…ined in EIP PR 5707 (fee market update)
This also introduces an `ENABLE_WITHDRAWALS` feature-flag to allow implementers test EIP-4844 without including Capella-specific state changes.
Co-authored-by: Hsiao-Wei Wang <hsiaowei.eth@gmail.com>
And remove the ENABLE_WITHDRAWALS feature-flag. The Testing section in the spec has been updated to specify how withdrawals is to be disabled
Co-authored-by: Alex Stokes <r.alex.stokes@gmail.com>
In light client tests, a variable is named `finality_header` but everywhere else it is called `finalized_header`. Rename for consistency.
For LC gossip, the documentation did not specify what slot number to use for deriving the gossip objects. This missing documentation is now added to document using `attested_header.slot`.
A few LC functions were not yet updated to use a more concise function for computing sync committee period for a slot. Updating to that func.
Add more detailed LC object documentation to explain that the various merkle proofs are relative to the beacon block's state root. Likewise, clarify that sync committees relate to the finalized header (not to the optimistic header, which can be a period ahead).
Currently, `test_single_merkle_proof` only supports `BeaconState` tests. For future tests, different object classes are desirable. Update format to allow testing other objects as well.
Future light client tests will also incorporate execution payload data. To avoid confusion, rename the current `root` check to `beacon_root`. Doing this now, as #3066 already requires LC test runners to update.
Consistent variable name in LC test
Consistently use `compute_sync_committee_period_at_slot`
Clarify where LC proofs are rooted
Rename LC test check from `root` to `beacon_root`
`remerkleable` was updated to address potentially incorrect computation of `hash_tree_root` against default-initialized `Vector` objects. Switching to the fixed version.
Moving the `is_post_xxx` functions to a separate module allows `genesis` to also use them (cyclic import from `context` prevented this before). This allows removing `FORKS_BEFORE_ALTAIR` and `FORKS_BEFORE_BELLATRIX` constants and adding a more general `is_post_fork` function that needs less maintenance. This then allows definition of `with_all_phases_from` to streamline the implementation of the `with_xxx_and_later` decorators.
EIP4844: Remove signed blobs
Fix `latest_execution_payload_header` field in eip4844 state upgrade
Allow extending LC merkle proof tests
clarify deprecation of `beacon_block` gossip topic in 4844
Rebase EIP-4844 on Capella
…ossip Make `validate_blobs_sidecar` a gossip condition
Add EIP4844 to testgen and add more Capella+EIP4844 random fork tests
Fix --preset-list argument and enhance error output
bump VERSION.txt
Add more double/duplicate operations tests
EIP4844: Refactor `verify_kzg_proof()` to receive bytes (used in precompile)
Add EIP4844 sync tests
hwwhww
changed the title
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
todo: