Is it necessary to add a string in the smartcontracts to identify the contract's type?

Protocol Features & Updates
1

There are different type of contracts, is it necessary to add a string in the smartcontracts to identify the contract’s type? @philipp.chain @bruteforce.chain

Such as AEX-9 for the fungible tokens, AEX-n for the polls, so we can decode the contarcts’ data directly according to the contract’s type.

1 Like
2

AEX-9 includes a aex9_extensions() function in the standard for this use-case, as described here AEXs/aex-9.md at master · mradkov/AEXs · GitHub

Otherwise I agree it could be helpful to have such a function on every contract if you want it to be publicly identifiable. Maybe you can work on an aextension for this?

3 Likes