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
Then, since 1244282937 is still within the bounds of 32-bit int, that's the result of casting -4976622813127 into a 32-bit integer. That 1244282937 is what explorer lists as Treestakers proposer priority for that block.
If it were larger (it'll never be smaller because the sign-bit is now zero), we would want to xor it with 4294967295, add one, then put a negative sign on it.
I'm not sure how much I trust it since I'm pretty rusty with bit math, but it's correct for all the ones I've tried so far. I wouldn't be surprised if I made it harder than it needed to be though.
Summary of Bug
On the block page, (e.g. 18318664), the "Proposer Priority" values do not match what the
provenanced q comet-validator-set
has for each validator.Steps to Reproduce
That pbvalcons14z3qgnjh3d2gexl33gzrcrk70y9cscllksn89r is TreeStaker.
If you look at the block page, it'll show that TreeStaker's "Proposer Priority" for that block was
1244282937
(instead of-4976622813127
).Then, since
1244282937
is still within the bounds of 32-bit int, that's the result of casting-4976622813127
into a 32-bit integer. That1244282937
is what explorer lists as Treestakers proposer priority for that block.If it were larger (it'll never be smaller because the sign-bit is now zero), we would want to xor it with
4294967295
, add one, then put a negative sign on it.E.g.
Those
5719164737899
and-1731700373
are Treestaker's proposer priority for block 18318663 (actual and display respectively).For Admin Use
The text was updated successfully, but these errors were encountered: