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

Custom Treasury - Burn Unwanted Native Tokens #822

Open
hard-nett opened this issue Apr 24, 2024 · 3 comments
Open

Custom Treasury - Burn Unwanted Native Tokens #822

hard-nett opened this issue Apr 24, 2024 · 3 comments

Comments

@hard-nett
Copy link
Contributor

After some discussion in the Juno Dev Department meetings, a DAO that only accepts a list of native tokens could benefit the DAO by not accumulating & having to manage internally unwanted tokens sent to the treasury.

I have implemented this feature, with use of the x/clock module, and want to see if this is a feature that would be desirable to add to the core contracts.

A possible issue with this implementation would be that it would not work on chains DAODAO is deployed on that do not have the clock module implemented, however by default this feature is disabled, and is only triggered by a sudo entry point so it may not cause issues ultimately

@hard-nett
Copy link
Contributor Author

seems like the query mentioned in #754 would be able to improve the UX if a dao proposed to enable this feature on a chain without the clock module

@hard-nett
Copy link
Contributor Author

Custom Treasury Notes

  • do we need to figure out a way to make use of limit in balance queries?
  • do we burn native tokens?can we send them to community pool?

@JakeHartnell
Copy link
Member

This might make more sense as a frontend feature. CC @NoahSaso.

Unfortunately, unlike cw20s, there is no way to block native tokens.

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