Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement PeerDAS Subnet Sampling #6409

Closed
jimmygchen opened this issue Sep 18, 2024 · 1 comment
Closed

Implement PeerDAS Subnet Sampling #6409

jimmygchen opened this issue Sep 18, 2024 · 1 comment
Assignees
Labels
das Data Availability Sampling

Comments

@jimmygchen
Copy link
Member

jimmygchen commented Sep 18, 2024

Description

ethereum/consensus-specs#3870

This consensus PR covers subnet sampling and is targeted for peerdas-devnet-2. It was an oversight on my part to think that the PR only removes peer sampling, hence it has not yet been implemented in Lighthouse.

This should be a simple change to subscribe to 4 additional column subnets and require all samples from those topics to be validated before making a block available. The additional column subnets are for the purpose of subnet sampling only:

  • the extra sampling subnets does not need to be advertised.
  • the samples from this subnet does not need to be stored, as peers should never query for these columns.
@jimmygchen jimmygchen added the das Data Availability Sampling label Sep 18, 2024
@jimmygchen jimmygchen self-assigned this Sep 18, 2024
@jimmygchen
Copy link
Member Author

Completed in #6410.
Raised #6465 to potentially exclude storing sampling columns, in case we end up going live with subnet sampling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
das Data Availability Sampling
Projects
None yet
Development

No branches or pull requests

1 participant