@fbsobreira @Maik @MathijsBok
We both recently discussed that Klever Radar sometimes provides incorrect information about missing blocks for jailed validators. (This is not the case for every jail.)
My question is:
With the upcoming mainnet update, will the information in the peer list show the validators elected for the current epoch but jailed as elected, or will they continue to be shown as jailed?
(https://node.mainnet.klever.org/validator/peers)
If I understand you correctly, a validator who has been jailed is still part of the consensus until the new elections.
Otherwise, I will have to build in a fallback function that contains a separate list of elected but jailed validators in the epoch.
Currently, I will not be able to know without prior information about the elections that an jailed validator is currently elected.
With best regards
Marco
Hi Marco,
The upcoming mainnet update will not change the current behavior — jailed validators will continue to appear only as jailed in the peer list, without explicitly showing that they were elected in the current epoch.
If you need to distinguish between elected but jailed and not elected, you have two options:
-
Track state changes yourself
– Keep a record of the validator’s last status before the transition to jailed.
– This way you know whether they were elected at the moment they got jailed.
-
Check success metrics in the same API
– Look at ValidatorSuccessRate, LeaderSuccessRate, or TempRating.
– Only currently running (elected) validators will have those fields populated.
– Jailed validators will not, which makes it possible to filter them.
That should let you reliably tell who is elected but jailed even though the peer list itself won’t explicitly state it.
Best regards,
Fernando
3 Likes
Thank you very much. Point 2 is the best solution for me to independently determine who is still elected.
1 Like