-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal description max length should match the max length set in the SDK #1871
Comments
Chris mentioned that there is only an implicit max length. |
what does that mean? |
There is only a max length per transaction in total. |
what is it? let's ensure that the description field is as large as can be to fit within this limit. |
@cwgoes what is the max size of tx? The max length of a description is the max size of the tx minus the length of the title minus the length of the fees string etc. etc. |
I am not sure the SDK will directly enforce a maximum size (Tendermint does, but it is quite high) - rather, the maximum size will be set implicitly by a gas limit and gas charged proportional to size. We can very easily add a separate maximum length just for validator descriptions, and that probably makes sense from the UX perspective too: cosmos/cosmos-sdk#3420 - if you would like a particular maximum length, please comment. |
Thx @cwgoes for creating the issue. |
Maybe subtract a heuristic of the size of the rest of the transaction from the max transaction size. @ebuchman what is the max transaction size? |
Just as reminder @jbibla made a nice experiment with 2 messages of length:
|
new length limits are:
|
it would be nice if this matched the size from the SDK. but we can adjust later.
Originally posted by @jbibla in #1807
The text was updated successfully, but these errors were encountered: