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
How can more complex gov v1 proposal types be used with the CLI?
With the wasmd upgrade to sdk 47, the v1beta1 gov proposals were deprecated. The SDK provides a "wizard" on the CLI to create json for new gov v1 proposal types. Unfortunately, the wizards does not work nicely with wasmd proposals where we submit encoded wasm files via gov or our other more complex types.
We decided to add a new command to wasmd to submit our proposal types as gov v1 but with the old CLI params. That is a workaround. A solution in the SDK that also works for (test-) scripts would be preferred.
The text was updated successfully, but these errors were encountered:
The "wizard" is definitely for now very basic. I have that somewhere in my todos a task for improving it for complexer types. However, in the general, AFAIK, the idea, is that module configure themselves a CLI for submitting a gov proposal for their messages.
There are helpers for that now: #14700. So basically, like you did in wasmd is the correct way to do it.
EDIT: Maybe this is something that it worth a quick tutorial actually, so this is said and explained more officially somewhere.
Thanks for the infos and confirmation! A tutorial or implementation guide can be very useful.
Not sure how you want to track that work, but it would be ok to close this issue, now.
Summary
How can more complex gov v1 proposal types be used with the CLI?
With the wasmd upgrade to sdk 47, the v1beta1 gov proposals were deprecated. The SDK provides a "wizard" on the CLI to create json for new gov v1 proposal types. Unfortunately, the wizards does not work nicely with wasmd proposals where we submit encoded wasm files via gov or our other more complex types.
We decided to add a new command to wasmd to submit our proposal types as gov v1 but with the old CLI params. That is a workaround. A solution in the SDK that also works for (test-) scripts would be preferred.
The text was updated successfully, but these errors were encountered: