Implement PeerDAS subnet decoupling (aka custody groups) #6736
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.
Issue Addressed
#6709
Spec: ethereum/consensus-specs#3832
Proposed Changes:
On startup, we construct
NetworkGlobals
and compute sampling subnets and sampling columns fromNodeId
- this remains the same but the computation logic has been updated to compute these from custody groups. (node_id
=>custody_groups
=>subnets
andcolumns
)custody_subnet_count
(csc
) tocustody_group_count
(cgc
) inMetaData
andENR
. (spec)sampling_size
computation logic is has been updated to be base on custody groups instead of custody subnets. code (spec update)sampling_size
andcustody_group_count
logic intoChainSpec
to keep them in one place.