-
Notifications
You must be signed in to change notification settings - Fork 680
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: punishment on repeated dispute initiations (stale) #785
Comments
11 tasks
Considering #784, is this still relevant? |
claravanstaden
pushed a commit
to Snowfork/polkadot-sdk
that referenced
this issue
Dec 8, 2023
* make directory before copying * added cumulus build step * fixed path * launch statemint and bridge hub * fixed whitespace * fixed versions * add cumulus bin to envrc-template * removed snowbridge * generate bridge hub chain specs * remove uneeded mutations in the spec * use snowbridge cumulus fork * removed sub beefy magefile command * set version to snowbridge branch * updated README * removed commented out code * updated node info * update collator names * changed para id's * updated spec * changed runtime version * uncomment channel setup
Will be solved by the new disabling strategy. 0% slashes dispensed for validators voting invalid on valid will cause disablement. Disablement has opportunity cost which should be enough of deterrent. |
Overkillus
changed the title
disputes: escalate punishment on repeated dispute initiations
disputes: punishment on repeated dispute initiations (stale)
Jan 17, 2024
helin6
pushed a commit
to boolnetwork/polkadot-sdk
that referenced
this issue
Feb 5, 2024
Bumps [cranelift-codegen](https://github.com/bytecodealliance/wasmtime) from 0.85.1 to 0.85.3. - [Release notes](https://github.com/bytecodealliance/wasmtime/releases) - [Changelog](https://github.com/bytecodealliance/wasmtime/blob/main/docs/WASI-some-possible-changes.md) - [Commits](https://github.com/bytecodealliance/wasmtime/commits) --- updated-dependencies: - dependency-name: cranelift-codegen dependency-type: indirect ... 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
As of paritytech/polkadot#5535, we don't disable validators for "against valid" disputes. But based on the number of disputes initiated by a validator within a session, we might want to disable it if it reaches a certain threshold. Since submitting more such disputes wastes the network bandwidth "for free".
We can also consider doing exponential slashing or slashing up to a certain number or what's suggested by @burdges in #790.
But disabling a validator would have a greater short-term impact since slashes are only applied after a bonding period.
The text was updated successfully, but these errors were encountered: