We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uint
https://github.com/ethereum/tests/blob/1c23e3c27ac53b794de0844d2d5e19cd2495b9d8/src/GeneralStateTestsFiller/Cancun/stEIP1153-transientStorage/15_tstoreCannotBeDosdFiller.yml#L27C16-L27C44
0x883264e8 is the keccak of doCall(uint). While the solidity spec claimed
0x883264e8
doCall(uint)
uint, int: synonyms for uint256, int256 respectively. For computing the function selector, uint256 and int256 have to be used.
So is this correct? Should use doCall(uint256) for signature?
doCall(uint256)
The text was updated successfully, but these errors were encountered:
hm, but it seems to still work when calling solc generated contracts
Sorry, something went wrong.
No branches or pull requests
https://github.com/ethereum/tests/blob/1c23e3c27ac53b794de0844d2d5e19cd2495b9d8/src/GeneralStateTestsFiller/Cancun/stEIP1153-transientStorage/15_tstoreCannotBeDosdFiller.yml#L27C16-L27C44
0x883264e8
is the keccak ofdoCall(uint)
. While the solidity spec claimedSo is this correct? Should use
doCall(uint256)
for signature?The text was updated successfully, but these errors were encountered: