find_in_pageToken standard

Network: Connecting...

Token examples

0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7
0xD8912C10681D8B21Fd3742244f44658dBA12264E
0xAf30D2a7E90d7DC361c8C4585e9BB7D2F6f15bc7


standard signature of function/event adherence value
ERC20 function totalSupply()
ERC20 function balanceOf(address) N.A.
ERC20 function transfer(address,uint256) N.A.
ERC20 function transferFrom(address,address,uint256) N.A.
ERC20 function approve(address,uint256) N.A.
ERC20 function allowance(address,address) N.A.
ERC20 event Transfer(address,address,uint256) N.A.
ERC20 event Approval(address,address,uint256) N.A.
HumanStandard function name()
HumanStandard function decimals()
HumanStandard function symbol()
HumanStandard function version()
HumanStandard function approveAndCall(address,uint256,bytes) N.A.
HumanStandard function receiveApproval(address,uint256,address,bytes) N.A.
Others function standard()

Standards

ERC20
HumanStandard
Others

Adherence check

By querying the remote node from infura.io, the bytecode for the token can be found and the respective function/event signatures can be searched to determine if that function/event exists for the token. However, do note that this method has its limitation - it is possible to obstrucate such that the function/event exists in the token but its signature does not show up in the bytecode. Similarly, matching the signature does not show what the function/event does, which might differ from the standards.