Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Implement: Provisioner #1436

Closed
rphmeier opened this issue Jul 20, 2020 · 2 comments · Fixed by #1473
Closed

Implement: Provisioner #1436

rphmeier opened this issue Jul 20, 2020 · 2 comments · Fixed by #1473
Assignees
Labels
S1-implement PR/Issue is in the implementation stage
Milestone

Comments

@rphmeier
Copy link
Contributor

The provisioner is responsible for answering requests for data from the block authorship proposer. It will largely serve as a go-between that fetches data from the Candidate Backing subsystem at first. This will probably also come with some changes to the candidate backing subsystem and guide.

@rphmeier rphmeier added the S1-implement PR/Issue is in the implementation stage label Jul 20, 2020
@rphmeier rphmeier added this to the Twinbrook milestone Jul 20, 2020
@rphmeier
Copy link
Contributor Author

The main complication here is going to be around handling occupied-core-assumptions. We might have candidates that are only includable when some bitfields are included. And we might have candidates that are not includable when certain bitfields are included.

When we're choosing bitfields to include, the rule should be simple: maximize availability. So basically, include all bitfields. And then choose a coherent set of candidates along with that.

@coriolinus coriolinus assigned coriolinus and unassigned coriolinus Jul 24, 2020
@coriolinus
Copy link
Contributor

I'm sketching out some work on this, but it's very likely that not much will get finished today, and much of Monday is going to be taken responding to reviews of #1458 and #1466. If someone else wants to work on this before then, then they should feel free.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
S1-implement PR/Issue is in the implementation stage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants