mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-07-15 03:15:44 +00:00

Files

T

eskimor b0c7a1571d Update disputes subsytems section. (#6329 )

* Update disputes subsytems section.

* Update roadmap/implementers-guide/src/node/disputes/README.md

Co-authored-by: Andrei Sandu <54316454+sandreim@users.noreply.github.com>

* Update roadmap/implementers-guide/src/node/disputes/README.md

Co-authored-by: Andrei Sandu <54316454+sandreim@users.noreply.github.com>

* Update roadmap/implementers-guide/src/node/disputes/README.md

Co-authored-by: ordian <write@reusable.software>

* Update roadmap/implementers-guide/src/node/disputes/README.md

Co-authored-by: ordian <write@reusable.software>

* Review feedback.

Co-authored-by: eskimor <eskimor@no-such-url.com>
Co-authored-by: Andrei Sandu <54316454+sandreim@users.noreply.github.com>
Co-authored-by: ordian <write@reusable.software>

2022-12-27 12:27:55 +01:00

804 B

Raw Blame History

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.

804 B Raw Blame History

Disputes Subsystems

804 B

Raw Blame History