qoire/ats

Aion Token Standard (AIP#2)

ats's Issues

Constructor does not allocate totalSupply to msg.sender balance

There may be a slight oversight. After the removal of the concept of specialAddress, the constructor does not allocate the totalSupply to the address that deploys the contract.

Initialize function calling contract address rather than msg.sender

Created a pull request #7 to fix the issue, as well as calling the initialize function within the constructor.

Functionality in the interim (without ContractInterfaceRegistry)

The ContractInterfaceRegistry that is required to determine whether a recipient or sender contract/account is a compatible contract is not yet available. In the absense of that function, we need to propose alternative functionality to ensure that the token is still usable. Whether it adheres directly to aionnetwork/AIP#4, would be an open question.

Changes would mainly be:

• Disable (for now) the ability for a contract to execute contract from or to a sender and recipient.

Update to AIR

See: aionnetwork/AIP#11, for specifics. We should be following this proposal.

Filler due to lack of assembly functionality

Reminder here:

• We currently lack the ability to facilitate the detection of contracts due to lack of assembly functionality. This means we may have to change the behaviour of the contract in cases where the supported account is not detected.