pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-05-01 15:57:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Extract Assignments and Approval guide text to an Approval informational section (#1638)

Browse Source 
* move validity module to disputes module

* prepare a section on approvals

* extract approval/assignments text to an overview section

* Apply suggestions from code review

Spelling

Co-authored-by: Fedor Sakharov <fedor.sakharov@gmail.com>
This commit is contained in:
Robert Habermeier
2020-08-31 10:57:51 +02:00
committed by GitHub
parent bcafc81d9f
commit d246a2889e
8 changed files with 63 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files
polkadot/roadmap/implementers-guide/src/node/utility/provisioner.md
+1 -1
View File
@@ -26,7 +26,7 @@ Note that there is no mechanism in place which forces a block author to include
The dispute inherent is similar to a misbehavior report in that it is an attestation of misbehavior on the part of a validator or group of validators. Unlike a misbehavior report, it is not self-contained: resolution requires coordinated action by several validators. The canonical example of a dispute inherent involves an approval checker discovering that a set of validators has improperly approved an invalid parachain block: resolving this requires the entire validator set to re-validate the block, so that the minority can be slashed.
Dispute resolution is complex and is explained in substantially more detail [here](../../runtime/validity.md).
Dispute resolution is complex and is explained in substantially more detail [here](../../runtime/disputes.md).
> TODO: The provisioner is responsible for selecting remote disputes to replay. Let's figure out the details.