Create non-standard
class to handle non-standard but common token read methods
#837
Labels
non-standard
class to handle non-standard but common token read methods
#837
Per the conversation here, we are failing to properly return values for contracts that contain methods like
name()
,symbol()
,tokenURI()
anddecimals()
that do not fully conform to one of the 3 major token standards we currently support (ERC20, ERC721, ERC1155). We should create a backstop to return these values regardless of whether they are part of a standard contract.The text was updated successfully, but these errors were encountered: