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
Two new required fields have been added to MsgSubmitProposal in cosmos sdk v0.47 - title and summary (link). Given the intention to support multiple chains, ideally we would support both v0.46 and v0.47.
This would most likely require updating @regen-network/api to the latest proto files, which are non-breaking API changes, and maybe adding additional information to chain info that specifies which sdk version is being used and handling accordingly.
This feature was proposed in conversation with @gjermundgaraba.
The text was updated successfully, but these errors were encountered:
We are starting to work on the groups UI from our end, but figuring out this one, in particular, would go a long way to make sure we make changes that are "upstreamable".
Is the proposed solution of updating @regen-network/api something that can be done in a reasonable amount of time, or do you have other ideas in mind on how to solve this?
Updating the api package should be pretty straightforward. We'll need to test though and make sure it's backwards compatible, i.e. a chain running v0.46 can use the v0.47 api without any issues.
Two new required fields have been added to
MsgSubmitProposal
in cosmos sdkv0.47
-title
andsummary
(link). Given the intention to support multiple chains, ideally we would support bothv0.46
andv0.47
.This would most likely require updating
@regen-network/api
to the latest proto files, which are non-breaking API changes, and maybe adding additional information to chain info that specifies which sdk version is being used and handling accordingly.This feature was proposed in conversation with @gjermundgaraba.
The text was updated successfully, but these errors were encountered: