-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add Ability to Change max-wasm-size via Governance #137
Conversation
LGTM but wouldn't this have to be changed again once we migrate to collections? |
Yeah there'd be some structural changes, but mostly around keeper. |
if m.GetAuthority() != req.Authority { | ||
return nil, fmt.Errorf("invalid authority; expected %s, got %s", m.GetAuthority(), req.Authority) | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v0.50 recommends that we validate message here
} | ||
|
||
ctx := sdk.UnwrapSDKContext(goCtx) | ||
if err := m.SetParams(ctx, req.Params); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
validate params before setting?
Overview
This PR attempts to achieve the followings:
max-wasm-size
at compile timemax-wasm-size
via governanceCloses #62