Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flexible total supply compatible with ERC20 standard ? #12

Open
virgile-dev opened this issue Jul 2, 2018 · 3 comments
Open

Flexible total supply compatible with ERC20 standard ? #12

virgile-dev opened this issue Jul 2, 2018 · 3 comments
Assignees
Labels

Comments

@virgile-dev
Copy link
Member

Following the discussions during the offsite, I'd like to have a technical validation that we can implement a flexible total supply when using the ERC20 standard.

Here are the links I've been checking that makes think it's possible :

@aecc
Copy link
Collaborator

aecc commented Jul 2, 2018

Setting a total supply is a hard constraint. So we definitely need to set one, however what we can do, after we (the owner of the contract) deploy the contract is to mint new tokens, therefore, increasing the total supply. We have to do this manually though every time. Not having a fixed supply could affect thr legitimicy of the system, because it wouldn't be clear for the token holders how the supply will be increased. So maybe we can set some pre defined constraints for us to increase the supply hard coded in the contract: something like e.g. 10% max supply increase per year, etc. What do u guys think?

@virgile-dev
Copy link
Member Author

Yeah, means we to define a monetary policy ahead.
@aecc is minting new tokens is a function we can use or does it mean we need to redeploy the contract ?

@aecc
Copy link
Collaborator

aecc commented Jul 11, 2018

We can just use a function to update/increase the total supply, there is no need to redeploy contract

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants