[Merged by Bors] - Altair consensus changes and refactors #2279
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
SignedBeaconBlock failing due to INT_MAX slot issue TreeHashing for BeaconState failing Cached tree hashing for BeaconState currently disabled
This comment has been minimized.
This comment has been minimized.
…/lighthouse into altair-process-epoch � Conflicts: � consensus/state_processing/src/per_epoch_processing/base.rs
michaelsproul
commented
Mar 26, 2021
…ir-process-epoch
Member
Author
|
Will fix merge conflicts here shortly before merging (in order to reduce churn in all the downstream PRs) |
[Altair] Update to latest spec v1.1.0-alpha.6
Update to spec v1.1.0-alpha.7
This was referenced Jul 7, 2021
Member
Author
|
Can't quite believe it... let's try this bors r+ 🎉 |
michaelsproul
added
ready-for-merge
bors bot
pushed a commit
that referenced
this pull request
Jul 9, 2021
## Proposed Changes Implement the consensus changes necessary for the upcoming Altair hard fork. ## Additional Info This is quite a heavy refactor, with pivotal types like the `BeaconState` and `BeaconBlock` changing from structs to enums. This ripples through the whole codebase with field accesses changing to methods, e.g. `state.slot` => `state.slot()`. Co-authored-by: realbigsean <[email protected]>
|
Pull request successfully merged into unstable. Build succeeded: |
bors
bot
changed the title
bors bot
pushed a commit
that referenced
this pull request
Aug 4, 2021
## Issue Addressed Resolves #2278 ## Proposed Changes Implements the networking components for the Altair hard fork https://github.com/ethereum/eth2.0-specs/blob/dev/specs/altair/p2p-interface.md ## Additional Info This PR acts as the base branch for networking changes and tracks #2279 . Changes to gossip, rpc and discovery can be separate PRs to be merged here for ease of review. Co-authored-by: realbigsean <[email protected]>
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.
Proposed Changes
Implement the consensus changes necessary for the upcoming Altair hard fork.
Additional Info
This is quite a heavy refactor, with pivotal types like the
BeaconStateandBeaconBlockchanging from structs to enums. This ripples through the whole codebase with field accesses changing to methods, e.g.state.slot=>state.slot().