Skip to content

Commit

Permalink
Disabling Strategy Implementers Guide (paritytech#2955)
Browse files Browse the repository at this point in the history
  • Loading branch information
Overkillus authored and TarekkMA committed Aug 2, 2024
1 parent 0dec4e9 commit 651c4c8
Show file tree
Hide file tree
Showing 3 changed files with 441 additions and 3 deletions.
1 change: 1 addition & 0 deletions polkadot/roadmap/implementers-guide/src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@
- [Disputes Process](protocol-disputes.md)
- [Dispute Flow](disputes-flow.md)
- [Chain Selection and Finalization](protocol-chain-selection.md)
- [Validator Disabling](protocol-validator-disabling.md)
- [Architecture Overview](architecture.md)
- [Messaging Overview](messaging.md)
- [PVF Pre-checking](pvf-prechecking.md)
Expand Down
6 changes: 3 additions & 3 deletions polkadot/roadmap/implementers-guide/src/protocol-disputes.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@ All parachain blocks that end up in the finalized relay chain should be valid. T
only backed, but not included.

We have two primary components for ensuring that nothing invalid ends up in the finalized relay chain:
* Approval Checking, as described [here](./protocol-approval.md) and implemented according to the [Approval
Voting](node/approval/approval-voting.md) subsystem. This protocol can be shown to prevent invalid parachain blocks
from making their way into the finalized relay chain as long as the amount of attempts are limited.
* Approval Checking, as described [here](./protocol-approval.md) and implemented accordingly in the [Approval
Voting](node/approval/approval-voting.md) subsystem. This protocol can be shown to prevent invalid parachain blocks
from making their way into the finalized relay chain as long as the amount of attempts are limited.
* Disputes, this protocol, which ensures that each attempt to include something bad is caught, and the offending
validators are punished. Disputes differ from backing and approval process (and can not be part of those) in that a
dispute is independent of a particular fork, while both backing and approval operate on particular forks. This
Expand Down
Loading

0 comments on commit 651c4c8

Please sign in to comment.