Open lispc opened 6 months ago
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)
hm, but it seems to still work when calling solc generated contracts
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?