Support ERC-20 extensions, like ERC-223

[jmank88]

GO/ERC-20 token contracts are recognized and displayed differently in the interface:

https://explorer.gochain.io/addr/0x37C93A80b5702A820CbC3050f0e9eC48a1D5e738

The ERC223 token standard is a superset of ERC20, so it should display as a token in the interface as well, and it should be trivial to do so. There are other similar token standards as well, can we support them all automatically?

Here is an ERC223

'Final' ERCs:

• 20
• 165 ERC-165 #215
• 721 Add automatic GO-721 / ERC-721 support #225

'Draft' ERCs:

• 223
• 621
• 777
• 827
• 884

[BeenOnChain]

[jmank88]

Many of these are still in 'draft' status, but we will keep an eye on them. Regardless, I would think that we could recognize at least the ERC/GO-20 subset of the interface, and work with that.

[BeenOnChain]

Some of their interfaces like the 621 and 777, could be usedful.

• Blacklisting their funds, also an option to destroy them(also decreasing supply option ;ERC621). Then replacing the amount by destroying those funds and creating new ones(also increasing Supply option ;ERC621).

• There has to be some major governance on this though, as bad parties could increase and decrease supply whenever they feel like it. Blacklist and destroy whomever account they want, and simply generate new tokens for their own will.

• Blacklisting an address could work in the case of someone hacking an exchange and trying to send those Go Tokens to an GO based DEX. As soon as the blacklisted address touches the DEX, it'll automatically be notified of a blacklisted address and the blacklisted address blocked from use on the DEX.

[bergauz]

@jmank88 @treeder should we close this issue or will be updated periodically?

[treeder]

We can open separate ones for any others we want to support. Nice work!