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
What we could do is deprecate the int64 field, and create a new uint64 field in QueryAccountAddressByIDRequest. If the user queries the address using either one of those, then return the corresponding address. We only return an error if the user populates both fields with different values.
However, it's also low priority IMO, as we should still have some margin before acc nums overflow 2^63-1.
Summary of Bug
int64
range :-2^63
to2^63-1
uint64
range:0
to2^64-1
https://github.com/cosmos/cosmos-sdk/blob/main/x/auth/keeper/grpc_query.go#L22-L38
Here we are converting (ingnoring -ve values) the
int64
values touint64
, that limits the range to 0 to 2^63-1Version
main
Steps to Reproduce
The text was updated successfully, but these errors were encountered: