-
Notifications
You must be signed in to change notification settings - Fork 57
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
Routine Simultaneous Validator Jailings #374
Comments
Occurred again |
It is always the same list. I suspect some issue with gorc setup. |
some more logs leading to jailing - does not seem to indicate anything in particular
|
|
3025818 - 2995816 = 30002 next jailing at 3055820? |
Had to upgrade geth to v1.10.17 to get it syncing. gorc is waiting now. Will give more feedback when sync is up to date. |
Sorry for the delayed response. Currently on mainnet the slashing penalty is zero and staking rewards haven't been enabled yet, so while being jailed is annoying, it shouldn't negatively impact you. The only protocol-specific conditions where validators are slashed are if they fail to submit signatures for Gravity Bridge batches or valset updates. This is likely due to either running the wrong version of gorc (current is 0.3.9), having it misconfigured, or not having your delegate keys set appropriately. |
We have an upcoming release of new major versions of the Sommelier binary and the Gravity Bridge, which we will be communicating out to validators in the coming days, that should hopefully be a good point to ensure everyone is running the correct software and configs. |
Agreed. We have been running under this assumption of "slashing penalty is zero and staking rewards haven't been enabled" and just periodically unjail the node when needed. Look forward to the new release! |
Confirmed after geth+gorc are configured correctly that jailing issue goes away. (geth 1.10.17, gorc 0.3.8) Would be good to have a way to test this prior to being jailed. :) Less critical now since there are no penalties but we're assuming that new validators would appreciate the ability to verify their setup prior to slashing. (or even existing validators after a machine migration) |
We have noticed recurring instances of multiple validators being jailed on sommelier.
It is typically unlikely for multiple validators to all fail on the same block due to mismanagement.
This may point to a p2p-network-issue typically associated with unbalanced vote power where most of the validators votes are not necessary for consensus and the network proceeds "without lower powered validators"
A foundation delegation to most validators to "even out" the delegated power may help until the network becomes more stable at which point delegation can be removed.
Jailing on block 2898376:
"2898376 BOND_STATUS_BONDED 1784658893 polkachu.com"
"2898376 BOND_STATUS_BONDED 18714137555 MetaRats 🐀"
"2898376 BOND_STATUS_BONDED 2249847859 Bi23 Labs"
"2898376 BOND_STATUS_BONDED 386000000 Chill Validation"
"2898376 BOND_STATUS_BONDED 695988539618 Standard Crypto"
"2898376 BOND_STATUS_UNBONDING 15682946864 Forbole"
Jailing on block 2955077:
"2955077 BOND_STATUS_BONDED 18509187555 MetaRats 🐀"
"2955077 BOND_STATUS_BONDED 2350658893 polkachu.com"
"2955077 BOND_STATUS_BONDED 386000000 Chill Validation"
"2955077 BOND_STATUS_UNBONDING 2708409660 Bi23 Labs"
"2955077 BOND_STATUS_UNBONDING 695984928611 Standard Crypto"
The text was updated successfully, but these errors were encountered: