We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
So recommend to store the instantiated contract data and dispatch response messages later.
The text was updated successfully, but these errors were encountered:
Good point. So the messages sent out can refer back to the newly instantiated contract. Will add to next release
Sorry, something went wrong.
alpe
Successfully merging a pull request may close this issue.
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: