feat: Add A New Message For Storing A Code and Instantiating A Contract With It #154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9 tasks
brew0722
reviewed
Apr 27, 2021
loloicci
force-pushed
the
loloicci/v2/feat/add-store-instantiate-msg
branch
from
ffe1df0
to
06df152
Compare
|
Sorry, using force push to rebase it to v2/develop. |
|
The author of this PR, loloicci, is not an activated member of this organization on Codecov. |
loloicci
force-pushed
the
loloicci/v2/feat/add-store-instantiate-msg
branch
from
c2b7d09
to
297e227
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds a new message MsgStoreCodeAndInstantiateContract and its handler. This is for storing a WASM code and instantiate a contract from it in one message (tx).
This is the stargate version of #122
closes: #111
(tests for CLI/REST are not included. The former will be added after adding linkwasmd for stargate, the latter will be added if we need REST.)
docs/) or specification (x/<module>/spec/) (There are no docs)godoccomments.Unreleasedsection inCHANGELOG.md(It will be generated with script)Files changedin the Github PR explorerCodecov Reportin the comment section below once CI passes