-
Notifications
You must be signed in to change notification settings - Fork 819
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
Investigate better types for max len of bounded storage items #290
Labels
Comments
Generally speaking, I realized again that For example, if you put a |
6 tasks
related issue #244 |
claravanstaden
pushed a commit
to Snowfork/polkadot-sdk
that referenced
this issue
Dec 8, 2023
jonathanudd
pushed a commit
to jonathanudd/polkadot-sdk
that referenced
this issue
Apr 10, 2024
* Update open ethereum. * Remove extra line break. * Remove branch comment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently, bounded storage items require a type that implements
Get
for its max length. This permits the user to configure the type as something that can be modified at runtime.Modifying the bounds at runtime is a foot gun for chain builders. For example, it could render some storage items non-decodable or break assumptions used to create weights and soften DDoS vectors.
We should look into forcing the bound to be a
const
or something similiarThe text was updated successfully, but these errors were encountered: