mradkov / aeternity-fungible-token

Aeternity blockchain Fungible Token reference implementation. The implementation is based on the proposed AEX9 standard for creating and usage of Sophia smart contract-based fungible tokens.

Privacy is necessary for an open society in the electronic age. Privacy is not secrecy. A private matter is something one doesn't want the whole world to know, but a secret matter is something one doesn't want anybody to know. Privacy is the power to selectively reveal oneself to the world.

---

A Cypherpunk's Manifesto, Eric Hughes, Cypherpunk Manifesto

aeternity-fungible-token's Issues

consider adding a transfer payload/identifier

Add explanation and suggestion for `mint` limit

write tests

Match allowance docs and implementation

implement reset allowance

Iris compatibility

Spell check

Balance interface lacks paging

there is a problem with balances, it does not support paging. With thousands or even tens of thousands of accounts, it is impossible to obtain all accounts.

Account instead of owner

Use account instead of owner in the naming.

aeternity-fungible-token/contracts/fungible-token.aes

Line 85 in 5bf2d91

entrypoint balance(owner: address) : option(int) =

Lack of require function

The contract seems to be missing a require function.

I tried to send an excess token in the Go SDK and it was successfully packaged.

Discuss differences with AEX-11

https://forum.aeternity.com/t/aex-9-fungible-token/3565/51

maybe combining (as extension) or making them compatible would be viable

check if current allowance implementation works around known erc20 frontrunning issues

https://blog.smartdec.net/erc20-approve-issue-in-simple-words-a41aaf47bca6

consider development of companion JS-Lib or sample js-sdk code

refactor test cases

migration to native tokens

Discuss allowing future extensions

allow "" as token name and symbol?

update sdk to latest

move travis to gh-actions

simplify aeproject config

Consider adding version/extensions indicator

optimize reference implementation for gas use

publish as npm package

Allow for swap from remote contract

• (option 1) provide example to allow for token swaps using burn calls from a remote interface in the new contract
• (option 2) burn and add to burn event state, add claim function to be called by remote contract

Wrong interface for AEX-9

The interface declaration is not entirely correct as the stateful modifier is missing, therefore when trying to use it to call an existing contract, the transaction is not being send as the function is considered static.

https://github.com/mradkov/aeternity-fungible-token/blob/master/contracts/fungible-token-full-interface.aes

check test coverage

Use Contract.creator

We can use Contract.creator instead of having owner field in the state.

Add option int initial owner supply