Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling Strategy Implementers Guide #2955

Merged
merged 19 commits into from
May 10, 2024
Merged

Disabling Strategy Implementers Guide #2955

Changes from 1 commit
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
2f27a54
init
Overkillus Nov 21, 2023
d0ed868
init
Overkillus Nov 21, 2023
7d0fde4
Background and Risks draft
Overkillus Nov 23, 2023
abb996e
Risks expanded, overview and TODOs
Overkillus Dec 15, 2023
06096b6
mitigation, duration, economics, simplifications, extra types
Overkillus Jan 16, 2024
680e791
implementation details
Overkillus Jan 17, 2024
03abe5d
minor changes
Overkillus Jan 17, 2024
06d24fc
GRANDPA fixes
Overkillus Jan 17, 2024
e354e21
ordering and nits
Overkillus Jan 23, 2024
4708404
review nits
Overkillus Jan 23, 2024
691d175
more nits
Overkillus Jan 23, 2024
85bc546
Review feedback, approval slashes clarifications, typos, beefy clarif…
Overkillus May 9, 2024
2669cbc
fmt
Overkillus May 9, 2024
28a1110
punishment table, fmt core features update
Overkillus May 10, 2024
82b48c4
reverting commit mistake (accidental code change)
Overkillus May 10, 2024
6bf9d00
Revert "reverting commit mistake (accidental code change)"
Overkillus May 10, 2024
e89abe9
erroneous file removal
Overkillus May 10, 2024
899b249
Merge branch 'master' into mkz-disabling-guide
Overkillus May 10, 2024
879e8d4
table fmt
Overkillus May 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
table fmt
  • Loading branch information
@Overkillus
Overkillus committed May 10, 2024
commit 879e8d41c3cdd32823b37000dc5361346c129610
26 changes: 14 additions & 12 deletions polkadot/roadmap/implementers-guide/src/protocol-validator-disabling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -360,21 +360,25 @@ re-enabling is launched approval voter slashes can be re-instated. Numbers need
between 0-2% are reasonable. 0% would still disable which with the opportunity cost consideration should be enough.

> **Note:** \
> Spammy approval checkers are in fact not a big issue as a side effect of the offchain-disabling introduced by the Defense Against Past-Era Dispute Spam (**Node**) [#2225](https://github.com/paritytech/polkadot-sdk/issues/2225). It makes it so all validators loosing a dispute are locally disabled and ignored for dispute initiation so it effectively silences spammers. They can still no-show but the damage is minimized.
> Spammy approval checkers are in fact not a big issue as a side effect of the offchain-disabling introduced by the
> Defense Against Past-Era Dispute Spam (**Node**) [#2225](https://github.com/paritytech/polkadot-sdk/issues/2225). It
> makes it so all validators loosing a dispute are locally disabled and ignored for dispute initiation so it effectively
> silences spammers. They can still no-show but the damage is minimized.


## Interaction with all types of misbehaviors

With re-enabling in place and potentially approval voter slashes enabled the overall misbehaviour-punishment system can be as highlighted in the table below:
With re-enabling in place and potentially approval voter slashes enabled the overall misbehaviour-punishment system can
be as highlighted in the table below:

| Misbehaviour | Slash % | Onchain Disabling | Offchain Disabling | Chilling | Reputation Costs |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | --- |
| Backing Invalid | 100% | Yes (High Prio) | Yes (High Prio) | No | No |
| ForInvalid Vote | 2% | Yes (Mid Prio) | Yes (Mid Prio) | No | No |
| AgainstValid Vote | 0% | Yes (Low Prio) | Yes (Low Prio) | No | No |
| GRANDPA / BABE / BEEFY Equivocations | 0.01-100% | Yes (Varying Prio) | No | No | No |
| Seconded + Valid Equivocation | - | No | No | No | No |
| Double Seconded Equivocation | - | No | No | No | Yes |
|Misbehaviour |Slash % |Onchain Disabling |Offchain Disabling |Chilling |Reputation Costs |
|------------ |------- |----------------- |------------------ |-------- |----------------- |
|Backing Invalid |100% |Yes (High Prio) |Yes (High Prio) |No |No |
|ForInvalid Vote |2% |Yes (Mid Prio) |Yes (Mid Prio) |No |No |
|AgainstValid Vote |0% |Yes (Low Prio) |Yes (Low Prio) |No |No |
|GRANDPA / BABE / BEEFY Equivocations |0.01-100% |Yes (Varying Prio) |No |No |No |
|Seconded + Valid Equivocation |- |No |No |No |No |
|Double Seconded Equivocation |- |No |No |No |Yes |


*Ignoring AURA offences.
Expand Down Expand Up @@ -431,5 +435,3 @@ Implementation of the above design covers a few additional areas that allow for
1. Re-enable small offender when approaching BZT (**Runtime**) #TODO
- When BZT limit is reached and there are more offenders to be disabled re-enable the smallest offenders to disable
the biggest ones