Skip to content

assemble and send inherent data #4532

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

Open
1 task
EclesioMeloJunior opened this issue Feb 11, 2025 · 0 comments
Open
1 task

assemble and send inherent data #4532

EclesioMeloJunior opened this issue Feb 11, 2025 · 0 comments
Assignees
Labels
C-complex Complex changes across multiple modules. Possibly will require additional research.

Comments

@EclesioMeloJunior
Copy link
Member

EclesioMeloJunior commented Feb 11, 2025

Description

The ProvisionerInherentData struct is composed of: bitfields, candidates, disputes, the unique information that is tracked under provisioner state per relay block is the bitfields.

So we need to collect the other components before sending them, this task can take some time, so we should spawn a goroutine to unblock the provisioner subsystem, placing a timeout so we don't let the goroutine to run forever.

Here is what we should query/compute before sending the inherents

  1. Request availability cores
  2. Select the disputes
  3. Select availability bitfields
  4. Select candidates

Links

Acceptance Criteria

  • Include metrics
@EclesioMeloJunior EclesioMeloJunior added the C-complex Complex changes across multiple modules. Possibly will require additional research. label Feb 11, 2025
@axaysagathiya axaysagathiya self-assigned this May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-complex Complex changes across multiple modules. Possibly will require additional research.
Projects
None yet
Development

No branches or pull requests

2 participants