Closed DerXanRam closed 1 year ago
Hey @DerXanRam. uint
is just alias for uint256
. I think the ABI expects the int types to not be aliases. Try this signature instead: allPairs(uint256)
References:
Hey @DerXanRam.
uint
is just alias foruint256
. I think the ABI expects the int types to not be aliases. Try this signature instead:allPairs(uint256)
References:
so when i incode ABI i always need to replace uint by uint256. right?
so when i incode ABI i always need to replace uint by uint256. right?
Correct, uint
-> uint256
and int
-> int256
Hello bro.... To day i was testing the ABI encoder using this code
The generated hex is
0xe9e0f23f0000000000000000000000000000000000000000000000000000000000000002
when i send this to
eth_call
RPC, the generated RPC response is{"error":{"code":-32000,"message":"execution reverted"},"id":0,"jsonrpc":"2.0"}
But when i use https://abi.hashex.org/ to generate the ABI, the ABI hex is
0x1e3dd18b0000000000000000000000000000000000000000000000000000000000000002
and when i send it to The RPC, the same way i sent the above ABI data, The RPC response is
{"id":0,"jsonrpc":"2.0","result":"0x00000000000000000000000012ede161c702d1494612d19f05992f43aa6a26fb"}
which is success. As u can see the ABI generated by the code and by the website, The difference is found only in the first 10 digits. Can u look at it please? Thanks :pray: