-
Notifications
You must be signed in to change notification settings - Fork 102
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
add fail-safe mode by default to avoid double-sign when the new pod started while the old one is terminating but is still up #317
Comments
I remember I was using this script for Crypto Org chain for checking the last N signatures.
Check if validator is signing the blocks:
|
Looks a awesome! |
The only caveat is that one would have to use some known RPC node to query as one can't just query itself I am wondering, maybe tendermint already has this kind of check built-in? |
yeah, it looks like exactly that! thank you! https://docs.tendermint.com/v0.34/tendermint-core/configuration.html
|
For nodes on Akash , this is an important parameter, as validators run the risk of being permanently banned. |
I don't think the ban is permanent. Validator can always issue the |
A double signature is punishable by an eternal ban, it looks like the date unjail 9999-12-31 |
For some reason some had a problem with that option ( https://discord.com/channels/747885925232672829/751246770885099533/968578447884550146 |
I've just tested it with
|
Add fail-safe mode by default to avoid double-sign when the new pod started while the old one is terminating but is still up for any reason.
The fail-safe mode would check whether the last few recent blocks (5, 10 or 50) haven't been signed by the validator before starting it.
And if it does sign the recent blocks, it would then fail safely with some message such as:
echo "WARNING!!! There is an active validator with the same pubkey is validating the blocks! Safely exiting..."
It has happened to Dimokus as he woke up to a jailed validator because of that.
The text was updated successfully, but these errors were encountered: