-
Notifications
You must be signed in to change notification settings - Fork 316
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
Double signing documentation is confusing #100
Comments
Interesting, assuming you got that from here https://github.com/cosmos/cosmos/blob/master/VALIDATORS_FAQ.md I think this is confusing and needs to be reworded/made more explicit. Within the current definition, I think double signing is not in reference to signing two different chains - that would be acceptable behaviour as the chains are distinct (but possible sharing a validator set, these are complex but potentially allowable arrangements). Within the cosmos double signing typically refers two signing and broadcasting two different pieces of information (for instance a proposed block) for the same height for the same chain. Hope this helps. Going to rename this issue to bring clarity to this point in the docs |
@rigelrozanski U got me,thank you. look forward to getting more information in updating docs. |
yeah many of the docs are not in cosmos-sdk aka https://github.com/cosmos/cosmos-sdk/tree/develop/docs |
This is to prevent the "nothing-At-stake" scenario, essentialy forcing the validator to choose one chain to prolong |
What is the meaning of Double Signing exactly?
Double signing: If someone reports on chain A that a validator signed two blocks at the same height on chain A and chain B, this validator will get slashed on chain A
And why be punished with it?
The text was updated successfully, but these errors were encountered: