search

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.
ISC License
6 stars 13 forks source link

consider adding a transfer payload/identifier #9

Closed thepiwo closed 5 years ago

mradkov commented 5 years ago

Can you clarify/extend your idea?

From what I understand you mean something like this:

stateful entrypoint transfer(to_account: address, value: int, payload: option(string))

I assume the use-cases of this would be for example to specify payment reason e.g. invoice number?

thepiwo commented 5 years ago

I think this was proposed by robert and we were just opening as issue, to not forget about it.

His idea was that a transfer payload as described by you can be used for various things, e.g. legal requirement in some cases.

I think afterwards Robert was working on a separate token standard that focuses more on legal compliance, so I don't know if we should still include this here

thepiwo commented 5 years ago

to implement a basic fungible token contract we won't need this and save on gas costs for users in default situations.