Dispute slashing/hardening

[ordian]

The Vision

Polkadot is a sharded blockchain. Some validators check some of the parachain blocks. When there's a disagreement about validity of parachain block, a dispute process starts. The checks will escalate to every validator. Once the dispute is resolved, we need to slash and disable validators accordingly to their misbehavior.

The Plan

• Current-session disputes slashing runtime/disputes: slashing #5535.
• Test the limits of the slashing logic in substrate [don't merge] zombienet slashing test #5978
• Ensure there are no disputes due to bugs on Kusama Make Kusama dispute free polkadot-sdk#783
• Enable slashing on Kusama kusama: enable dispute slashes #5974
• Enable slashing on Polkadot
• Past-session disputes slashing disputes: implement past session slashing #5947
• Validator disabling disputes: implement validator disabling polkadot-sdk#784
• Escalate punishment on repeated disputes disputes: punishment on repeated dispute initiations (stale) polkadot-sdk#785
• Enable past-session slashing and disabling on Kusama
• Enable past-session slashing and disabling on Polkadot

Open Questions

• There's some consideration about numbers for slashing and correlated slashing: Stop inclusion on too many disputes polkadot-sdk#790.

[eskimor]

Closed in favor of (and merged into): paritytech/polkadot-sdk#750 (duplicate).