mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-07-09 21:07:31 +00:00
prospective-parachains: respond with multiple backable candidates (#3160)
Fixes https://github.com/paritytech/polkadot-sdk/issues/3129
This commit is contained in:
@@ -187,16 +187,16 @@ this process is a vector of `CandidateHash`s, sorted in order of their core inde
|
||||
|
||||
#### Required Path
|
||||
|
||||
Required path is a parameter for `ProspectiveParachainsMessage::GetBackableCandidate`, which the provisioner sends in
|
||||
Required path is a parameter for `ProspectiveParachainsMessage::GetBackableCandidates`, which the provisioner sends in
|
||||
candidate selection.
|
||||
|
||||
An empty required path indicates that the requested candidate should be a direct child of the most recently included
|
||||
An empty required path indicates that the requested candidate chain should start with the most recently included
|
||||
parablock for the given `para_id` as of the given relay parent.
|
||||
|
||||
In contrast, a required path with one or more entries prompts [prospective
|
||||
parachains](../backing/prospective-parachains.md) to step forward through its fragment tree for the given `para_id` and
|
||||
relay parent until the desired parablock is reached. We then select a direct child of that parablock to pass to the
|
||||
provisioner.
|
||||
relay parent until the desired parablock is reached. We then select the chain starting with the direct child of that
|
||||
parablock to pass to the provisioner.
|
||||
|
||||
The parablocks making up a required path do not need to have been previously seen as included in relay chain blocks.
|
||||
Thus the ability to provision backable candidates based on a required path effectively decouples backing from inclusion.
|
||||
|
||||
Reference in New Issue
Block a user