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

Automated Token Buyback and Burn - 400 #3

Open
Ivan-Ivanitskiy opened this issue May 23, 2024 · 2 comments
Open

Automated Token Buyback and Burn - 400 #3

Ivan-Ivanitskiy opened this issue May 23, 2024 · 2 comments

Comments

@Ivan-Ivanitskiy
Copy link
Contributor

Implement contracts that automatically buy and burn a portion of the token supply when certain on-chain metrics are met, such as protocol revenue reaching a predefined threshold (come up with a metric that would make sense).

@rotcivegaf
Copy link

Hi @Ivan-Ivanitskiy I would like to take this issue, I have some questions:

  1. Is this contract an ERC20 itself or does it have a balance of ERC20?
  2. About the metrics, is it a single metric or can there be more than one?

I think I can start with these answers

@Ivan-Ivanitskiy
Copy link
Contributor Author

Ivan-Ivanitskiy commented Jun 20, 2024

Hey @rotcivegaf ! Thanks for the questions.

  1. Both options are valid. To me, it seems a better option if this is a separate contract with a balance of ERC-20 - from the modularity standpoint. We can call it a Treasury contract. You can use any of the existing ERC-20 tokens depoloyed on Sepolia Testnet or depoly one yourself.
  2. It might be a single metric, or there can be more - what makes sense for you from a business logic standpoint. If there is more than one valid application for this particular type of bounty, the one that is more sophisticated and makes more sense will win.

Sorry for the late reply and please let me know if you have any more questions. I will be more responsive, I just didn't know people would reach out to us here, in issues. Feel free to ask questions in our Telegram developer chat, too.

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

No branches or pull requests

2 participants