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.

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

Open
14 tasks done
eskimor opened this issue Dec 5, 2022 · 0 comments
Open
14 tasks done

Disputes Slashing/Hardening #750

eskimor opened this issue Dec 5, 2022 · 0 comments
Assignees
Labels
I6-meta A specific issue for grouping tasks or bugs of a specific category.

Comments

@eskimor
Copy link
Member

eskimor commented Dec 5, 2022

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:

  • 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)

Plan Details

@eskimor eskimor changed the title Improving Disputes Slashing + Improving Disputes Dec 5, 2022
@eskimor eskimor changed the title Slashing + Improving Disputes Disputes Slashing/Hardening Dec 5, 2022
@Sophia-Gold Sophia-Gold transferred this issue from paritytech/polkadot Aug 24, 2023
@the-right-joyce 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
Labels
I6-meta A specific issue for grouping tasks or bugs of a specific category.
Projects
Status: In Progress
Status: In progress
Development

No branches or pull requests

4 participants