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
In ValidatorManager.sol, NodeID is defined as bytes (a dynamically-sized type). I understand that this is probably done for future-proofing. However, when events are emitted like:
Its misleading, because the actual NodeID is not emitted, as Solidity will keccak the bytes to get a 32-byte hash to put in the event. So at a minimum I would suggest renaming it to NodeIDHash which would make it clear its not the actual nodeid.
Alternatively, I think if indexed is removed, the full value would be placed in the event log.
The text was updated successfully, but these errors were encountered:
I definitely see how this isn't super user-friendly. @cam-schultz would it make sense to use a bytes32 for all sizes? I think the bytes20 should just get padded?
I still think that bytes is the most future-proofed option, as it's the most in line with the ACP-77 spec. Removing indexed (and indexing one of the other fixed size parameters instead) sounds like a reasonable workaround to me. The other suggestion to rename to NodeIDHash would clarify the output value, but wouldn't do much to make the event more useful.
In ValidatorManager.sol,
NodeID
is defined asbytes
(a dynamically-sized type). I understand that this is probably done for future-proofing. However, when events are emitted like:Its misleading, because the actual NodeID is not emitted, as Solidity will keccak the bytes to get a 32-byte hash to put in the event. So at a minimum I would suggest renaming it to
NodeIDHash
which would make it clear its not the actual nodeid.Alternatively, I think if
indexed
is removed, the full value would be placed in the event log.The text was updated successfully, but these errors were encountered: