Replies: 1 comment 1 reply
-
Currently, it is a parameter, so chains can still increase the maximum metadata length. What is the advantage of completely removing that constraint? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
UPDATE: didn't notice the limit is a configurable parameter
Currently, there is a 255 character limit on the governance proposal's
metadata
field:cosmos-sdk/x/gov/keeper/keeper.go
Lines 222 to 229 in 22dfa11
This forces proposals to be put off-chain (e.g. on IPFS) as any meaningful proposal would certainly require a description that's longer than a tweet.
I think this is a wrong decision. Users can decide to put proposals off-chain if they want to, but they should also have the option to put proposals on-chain. The SDK shouldn't force them one way or the other.
Personally, I consider governance proposals an important part of a chain's history and should be maintained as permanent on-chain records.
My suggestions:
Any
as metadata instead of a string.Beta Was this translation helpful? Give feedback.
All reactions