gov: replace Content and Proposal handlers in other modules with messages

[cmwaters]

Summary

Ref: #9438

Update: For v0.46.0, we are only doing MsgSoftwareUpgrade and MsgCancelUpgrade. Other Msgs will be added in future releases

This is a follow up issue on the use of an arbitrary array of messages in the proposal (#9810). Existing modules that use governance are still defining proposals as a Content and a proposal Handler. This needs to be replaced with their respective sdk.Msg type and a whitelist filter that only allows the governance module account to execute them. The following is a list of modules and the new messages:

• x/distribution: CommunityPoolSpend. This could also be configured as the distribution module giving authorization to the governance module and then proposals would just be a regular spend from the distribution account to the recipients account.
• x/params: ParameterChange. There is ongoing work to change this, so I'm not sure what the current status is.
• x/upgrade: Upgrade & CancelUpgrade

cc: @blushi, @aaronc

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[cmwaters]

Update: We are going to keep Content and ProposalHandler's in the new design to allow for backwards compatibility. We should still try to convert the existing ones in the SDK to having their own messages but this can be pushed back to a later release if need be. Also there are going to be changes to x/params and potentially to x/distribution (see #10811) hence we should focus on x/upgrade first

[alexanderbez]

We should still try to convert the existing ones in the SDK to having their own messages but this can be pushed back to a later release if need be.

I'm not sure we should even bother. What's the rationale behind that?

Also, why do we need to touch x/params at all?

[amaury1093]

I'm not sure we should even bother. What's the rationale behind that?

We can provide an example (say in the docs) on how to create a Msg-based software upgrade proposal. To showcase the new proposal.

I'd say let's see next week how gov/group work advances. If the blocker is group, then we can include MsgSoftwareUpgrade into v0.46 in the meantime.

[alexanderbez]

We can provide an example (say in the docs) on how to create a Msg-based software upgrade proposal. To showcase the new proposal.

Yes and leave the old ones as deprecated IMO.