Simplified attestation subnet mapping #3735
Open
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
AgeManning
force-pushed
the
simplified-subnet-mapping
branch
from
fea5847
to
6194a23
Compare
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.
Overview
This is a continuation of #3623 and linked PR's and issues.
There is quite a bit of complexity in how we should map a node-id to a backbone gossipsub topic. I think a number of future PRs are required in to address each complexity in turn.
In Lighthouse, we plan to adopt this simple approach, whilst discussion can continue on potentially more complex forms of this mapping. This approach simplifies the current state of the mapping and allows us to take advantage of improved discovery searches, which is the primary motivation behind this.