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
@wighawag This indeed seems the reason. We need to change the way we handle reverted calls. We are currently a bit busy with 0xcert framework v2 so it may take a while for us to come to this. For this reason we would appreciate any help on this.
I have an ERC721 contract on the mainnet at : 0x266003AfA9976D72565cac0bd840C276b01aE34f
and when I test it against the validator at https://erc721validator.org/?address=0x266003AfA9976D72565cac0bd840C276b01aE34f
It shows that balanceOf(address(0)) does not throw/
But when I execute the eth_call myself to an infura node with
It gives me
which is a revert-reason string so the call indeed revert
In comparison the 0xcert implementation when called with the same request,
I get
which is also the response (albeit different) corresponding to a revert/throw
Maybe it is the web3
estimateGas
call that does not error out here :https://github.com/0xcert/erc721-validator/blob/master/src/validator.ts#L47
because it does not consider the error-reason string as an error
See also ethereum/go-ethereum#19027
The text was updated successfully, but these errors were encountered: