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
{{ message }}
This repository was archived by the owner on Aug 31, 2021. It is now read-only.
Looks like (maybe?) large ints are just being converted to a big.Int, which can cause problems since a very large uint256 has the same hex representation as a corresponding negative int256. Would be good to double check that both of these cases are handled correctly by the converter
Looks like (maybe?) large ints are just being converted to a
big.Int, which can cause problems since a very largeuint256has the same hex representation as a corresponding negativeint256. Would be good to double check that both of these cases are handled correctly by the converter