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

Handle additional Tendermint evidence types #3156

Closed
kostko opened this issue Jul 31, 2020 · 1 comment · Fixed by #3671
Closed

Handle additional Tendermint evidence types #3156

kostko opened this issue Jul 31, 2020 · 1 comment · Fixed by #3671
Assignees
@kostko
Labels
c:consensus/cometbft Category: CometBFT c:staking Category: staking

Comments

@kostko
Copy link
Member

kostko commented Jul 31, 2020 •
edited
Loading

Tendermint Core 0.34 introduces the following new kind of evidence of Byzantine behavior:

  • LIGHT_CLIENT_ATTACK

It should most likely be handled in a similar way as double signing evidence (DUPLICATE_VOTE), but with their own slashing penalty.
@kostko kostko added c:consensus/cometbft Category: CometBFT c:staking Category: staking labels Jul 31, 2020
@kostko
Copy link
Member Author

kostko commented Aug 31, 2020

Also see discussion in cosmos/cosmos-sdk#7190 (comment).

@kostko kostko self-assigned this Feb 2, 2021
@kostko kostko mentioned this issue Feb 2, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kostko kostko

Labels
c:consensus/cometbft Category: CometBFT c:staking Category: staking
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

go/consensus/tendermint: Handle LIGHT_CLIENT_ATTACK evidence oasisprotocol/oasis-core
1 participant
@kostko