You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After declaring a candidate, the validator node runs well with expected voting power. I then declared another candidate on the same node. Here are the results.
Validator node address: 217763B77127EBA9C94F76F4BBD7457C059B5B69
First candidate address: B6834D914FE50F0C743E6A012AB20438CFADFB95
Second candidate address: 99FFAEE5BF6040EADA2F26548C4A702619797C9F
The candidate being declared successfully.
I can query that 2nd candidate with correct assets.
The voting power of the validator node is still the same as what has been bonded by the 1st candidate.
Amount of coins from the 2nd candidate account has been deducted.
Don't know where the voting power has gone.
The text was updated successfully, but these errors were encountered:
Cool - this is a bug as no two candidates are permitted to use the same pubkey - the fact that the transaction went through is the bug here
rigelrozanski
changed the title
Unexpected results when declaring more than one candidate on the same validator node (gaia-5001)
No two validators should be permitted to use the same pubkey
May 16, 2018
After declaring a candidate, the validator node runs well with expected voting power. I then declared another candidate on the same node. Here are the results.
Validator node address:
217763B77127EBA9C94F76F4BBD7457C059B5B69
First candidate address:
B6834D914FE50F0C743E6A012AB20438CFADFB95
Second candidate address:
99FFAEE5BF6040EADA2F26548C4A702619797C9F
Don't know where the voting power has gone.
The text was updated successfully, but these errors were encountered: