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

Governance proposal to remove allowed denom #1172

Closed
4 tasks
Tracked by #972
ryanchristo opened this issue Jun 8, 2022 · 1 comment
Closed
4 tasks
Tracked by #972

Governance proposal to remove allowed denom #1172

ryanchristo opened this issue Jun 8, 2022 · 1 comment
Assignees
Labels
Scope: x/ecocredit Issues that update the x/ecocredit module Type: Feature New feature or request

Comments

@ryanchristo
Copy link
Member

ryanchristo commented Jun 8, 2022

Summary

Reference: #1170 (comment)

We intend to provide a governance proposal to remove an allowed denom after we update to sdk v0.46 and we fully migrate to ORM tables for governance parameters (#729).

In the current implementation, we have a propsal to add an allowed denom. Do we want/need a governance proposal to remove an allowed denom included in v4.0 or can we assume that this will not be needed in the short-term?

Problem Definition

We currently have the ability to add an allowed denom in v4.0 but no convenient way to remove an allowed denom. It is possible to tag a small minor release that would include a software upgrade to remove an allowed denom if it was critical.

Proposal

Add proposal to remove allowed denom or wait until we fully migrate to ORM tables for governance parameters (#729).


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@ryanchristo
Copy link
Member Author

Closed via #1346

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: x/ecocredit Issues that update the x/ecocredit module Type: Feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants