-
Notifications
You must be signed in to change notification settings - Fork 102
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 more points to MIGRATING.md #499
Conversation
- CosmWasm gas values were reduced by a factor of 1000, so each instruction now | ||
consumes 150 CosmWasm gas instead of 150000. This should be taken into account | ||
when converting between CosmWasm gas and Cosmos SDK gas. |
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.
I was unsure whether to include this here, since the change itself was done in cosmwasm-vm
, but it seems highly relevant to users of wasmvm, so I did include it.
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.
This is very important since this needs to be changed in wasmd and other callsers. See DefaultGasMultiplier uint64 = 140_000_000
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.
LGTM 👍
- CosmWasm gas values were reduced by a factor of 1000, so each instruction now | ||
consumes 150 CosmWasm gas instead of 150000. This should be taken into account | ||
when converting between CosmWasm gas and Cosmos SDK gas. |
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.
This is very important since this needs to be changed in wasmd and other callsers. See DefaultGasMultiplier uint64 = 140_000_000
variant instead of just the data inside the `Ok`. This was previously only the | ||
case for `IBCPacketReceive`. It is important to note that this means contract | ||
errors are no longer returned in the `error` return value. Instead, the `Err` | ||
field should be checked for errors. |
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.
The way I like to think about this change is preserving nested results instead of flattening two levels if errors.
This should cover everything done on main since the 1.5 release.