-
Notifications
You must be signed in to change notification settings - Fork 400
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
Instantiate contract process ordering #292
Milestone
Comments
yun-yeo
changed the title
Instantiate contract store & dispatch message ordering
Instantiate contract process ordering
Oct 16, 2020
Good point. So the messages sent out can refer back to the newly instantiated contract. Will add to next release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem State
As you can see in terra-money/classic-core#399
If you store the instantiated contract after dispatching all messages, it will block the messages to use instantiated contract.
wasmd/x/wasm/internal/keeper/keeper.go
Lines 242 to 250 in ff37dc6
Proposed solution
So recommend to store the instantiated contract data and dispatch response messages later.
The text was updated successfully, but these errors were encountered: