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

Jump to bottom

Slashing #2078

Open
5 of 8 tasks
kostko opened this issue Sep 11, 2019 · 2 comments
Open
5 of 8 tasks

Slashing #2078

kostko opened this issue Sep 11, 2019 · 2 comments
Labels
c:consensus/tendermint Category: Tendermint-based consensus c:roothash Category: root hash service c:security Category: security issues epic Epic (costed tracking issue)

Comments

@kostko
Copy link
Member

kostko commented Sep 11, 2019 •
edited

Slashing should be implemented based on the set of slashing conditions. Ideally there should be E2E tests that verify that slashing functions correctly (e.g., using the byzantine node to invoke incorrect behavior).

Slashing conditions

  • Runtimes / Compute committee
    • Compute/sign/send a wrong result
    • Sign two commitments for the same round but different I/O root/state root/message root.
  • Runtimes / Storage committee
    • Return a wrong result to read request
    • Longer-term loss of availability
  • Consensus committee
@kostko kostko added c:roothash Category: root hash service c:consensus/tendermint Category: Tendermint-based consensus epic Epic (costed tracking issue) labels Sep 11, 2019
@kostko kostko added the c:security Category: security issues label Sep 19, 2019
@kostko kostko mentioned this issue Oct 16, 2019
Merged
4 tasks
@kostko
Copy link
Member Author

kostko commented Nov 21, 2019

All runtime-related slashing conditions (and thresholds to run nodes) should probably be configurable per-runtime.

@kostko kostko mentioned this issue Jan 3, 2020
Closed
@kostko kostko mentioned this issue Feb 8, 2020
Closed
@kostko
Copy link
Member Author

kostko commented Jun 30, 2020

In addition to slashing, misbehaving nodes should also be frozen (similar to how validators are frozen for double signing), with freezing maybe being configurable per runtime (maybe in addition to there being global parameters?).

@kostko kostko mentioned this issue Sep 29, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c:consensus/tendermint Category: Tendermint-based consensus c:roothash Category: root hash service c:security Category: security issues epic Epic (costed tracking issue)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kostko