You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: