mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-07-21 10:55:42 +00:00
cc650fe53d
* First iteration of message sender. * dyn Fn variant (no cloning) * Full implementation + Clone, without allocs on `Send` * Further clarifications/cleanup. * MessageSender -> NestingSender * Doc update/clarification. * dispute-coordinator: Send disputes on startup. + Some fixes, cleanup. * Fix whitespace. * Dispute distribution fixes, cleanup. * Cargo.lock * Fix spaces. * More format fixes. What is cargo fmt doing actually? * More fmt fixes. * Fix nesting sender. * Fixes. * Whitespace * Enable logging. * Guide update. * Fmt fixes, typos. * Remove unused function. * Simplifications, doc fixes. * Update roadmap/implementers-guide/src/node/disputes/dispute-coordinator.md Co-authored-by: Marcin S. <marcin@bytedude.com> * Fmt + doc example fix. Co-authored-by: eskimor <eskimor@no-such-url.com> Co-authored-by: Marcin S. <marcin@bytedude.com>
Disputes Subsystems
If approval voting finds an invalid candidate, a dispute is raised. The disputes subsystems are concerned with the following:
- Disputes can be raised
- Disputes (votes) get propagated to all other validators
- Votes get recorded as necessary
- Nodes will participate in disputes in a sensible fashion
- Finality is stopped while a candidate is being disputed on chain
- Chains can be reverted in case a dispute concludes invalid
- Votes are provided to the provisioner for importing on chain, in order for slashing to work.
The dispute-coordinator subsystem interfaces with the provisioner and chain
selection to make the bulk of this possible. dispute-distribution is concerned
with getting votes out to other validators and receiving them in a spam
resilient way.