-
Notifications
You must be signed in to change notification settings - Fork 666
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.
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
Disputes Slashing/Hardening #750
Labels
I6-meta
A specific issue for grouping tasks or bugs of a specific category.
Comments
11 tasks
This was referenced May 22, 2023
the-right-joyce
added
the
I6-meta
A specific issue for grouping tasks or bugs of a specific category.
label
Oct 9, 2023
claravanstaden
added a commit
to Snowfork/polkadot-sdk
that referenced
this issue
Dec 8, 2023
* 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
Bumps [styfle/cancel-workflow-action](https:/styfle/cancel-workflow-action) from 0.9.1 to 0.10.0. - [Release notes](https:/styfle/cancel-workflow-action/releases) - [Commits](styfle/cancel-workflow-action@0.9.1...0.10.0) --- updated-dependencies: - dependency-name: styfle/cancel-workflow-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: