You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
General goal of disputes improvements is to make them more spam resilient.
Slashing
Overall Strategy
Designing slashing systems is a very complex topic and pretty much impossible to get 100% right, especially if you consider real world issues, like machines not being equal, bugs, load variance, hardware faults, ... Therefore we need to be able to rely on governance for fixing any faulty slashes. By being able to rely on governance in extreme edge cases we can err on making the system more secure.
For this we need to ensure/overall strategy:
Unjustified slashes won't have a significant impact on validators, if reverted by governance. In particular validators should not lose their nominators.
Disabling of honest validators (due to unjustified slashes), will never be threatening the system's security. (Security over liveness.)
Make handling of time more deterministic/robust (outside of scope for this ticket, will be a separate project: time disputes)
Add all of this to the guide (describe the overall strategy for handling slashing)
* test: speed up e2e
* fix for mac osx
* Bump to resolve conflicts & supress warning
* Add rpc def when initialize to suppress warning
* Removes unnecessary beacon relay check. Adds total time printout for start-services at the end of the script. (paritytech#750)
Co-authored-by: claravanstaden <Cats 4 life!>
* minor fix
Co-authored-by: Clara van Staden <[email protected]>
helin6
pushed a commit
to boolnetwork/polkadot-sdk
that referenced
this issue
Feb 5, 2024
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.
Board here.
Disputes
General goal of disputes improvements is to make them more spam resilient.
Slashing
Overall Strategy
Designing slashing systems is a very complex topic and pretty much impossible to get 100% right, especially if you consider real world issues, like machines not being equal, bugs, load variance, hardware faults, ... Therefore we need to be able to rely on governance for fixing any faulty slashes. By being able to rely on governance in extreme edge cases we can err on making the system more secure.
For this we need to ensure/overall strategy:
Plan Details
Test the limits of the slashing logic in substrate [don't merge] zombienet slashing test polkadot#5978(no longer necessary now that chilling has been removed)The text was updated successfully, but these errors were encountered: