mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-07-08 06:37:23 +00:00
asynchronous rob
fc4b04db20
* explicitly tag network requests with version * fmt * make PeerSet more aware of versioning * some generalization of the network bridge to support upgrades * walk back some renaming * walk back some version stuff * extract version from fallback * remove V1 from NetworkBridgeUpdate * add accidentally-removed timer * implement focusing for versioned messages * fmt * fix up network bridge & tests * remove inaccurate version check in bridge * remove some TODO [now]s * fix fallout in statement distribution * fmt * fallout in gossip-support * fix fallout in collator-protocol * fix fallout in bitfield-distribution * fix fallout in approval-distribution * fmt * use never! * fmt
Backing Subsystems
The backing subsystems, when conceived as a black box, receive an arbitrary quantity of parablock candidates and associated proofs of validity from arbitrary untrusted collators. From these, they produce a bounded quantity of backable candidates which relay chain block authors may choose to include in a subsequent block.
In broad strokes, the flow operates like this:
- Candidate Selection winnows the field of parablock candidates, selecting up to one of them to second.
- Candidate Backing ensures that a seconding candidate is valid, then generates the appropriate
Statement. It also keeps track of which candidates have received the backing of a quorum of other validators. - Statement Distribution is the networking component which ensures that all validators receive each others' statements.
- PoV Distribution is the networking component which ensures that validators considering a candidate can get the appropriate PoV.