Skip to content
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

Upgrade wasmvm to 0.15.0 #532

Closed
webmaster128 opened this issue Jun 10, 2021 · 2 comments · Fixed by #548
Closed

Upgrade wasmvm to 0.15.0 #532

webmaster128 opened this issue Jun 10, 2021 · 2 comments · Fixed by #548
Assignees
Milestone

Comments

@webmaster128
Copy link
Member

Not yet released. Will follow shortly after https://github.com/CosmWasm/cosmwasm/milestone/17 is done.

@webmaster128 webmaster128 added this to the v0.18.0 milestone Jun 10, 2021
@webmaster128
Copy link
Member Author

v0.15.0-rc1 is available for integration. The changes can be seen here: CosmWasm/wasmvm#225

@webmaster128
Copy link
Member Author

wasmvm 0.15.0 is released. The full diff containing the Go changes is here: CosmWasm/wasmvm@v0.14.0...v0.15.0

Some notes on the update:

  • Messages and submessages are merged; the replyOn type now got a new "never" case for the fire and forget messages
  • replyOn is not an integer but supports the Stringer interface (i.e. .String())
  • The interface version was bumped from interface_version_5 to interface_version_6 such that CosmWasm 0.15.0 contracts need to be used
  • In some Wasm messages "send" was renamed to "funds" for consistency
  • The IBC acknowledgement type was changed slightly
  • There is a new Gov message (MsgVote) that needs to be connected
  • Deserializing contract results now cost gas. This needs to be configured in a new argument of vm.Execute and friends. We messed up storing the value in the vm instance, such that it needs to be passed to every call. Sorry for that! The deserialization cost is in gas per byte. It is a fraction, so you can use 20/1, 10/1, 1/1, 1/2, 1/30, ... in there.
  • Contract responses now contain events. The exiting Attributes should go into a main wasm event as before. All other events should be added with a wasm- prefix on the event type.

@alpe alpe self-assigned this Jun 25, 2021
@ethanfrey ethanfrey mentioned this issue Jul 21, 2021
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants