-
Notifications
You must be signed in to change notification settings - Fork 54
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
feat: integrate wasmd to support CosmWasm #135
Conversation
# Conflicts: # app/app_test.go # app/sim_test.go # app/test_helpers.go # app/upgrades/mainnet/v4/upgrade.go # cmd/crescentd/cmd/root.go # x/liquidfarming/client/testutil/suite.go # x/liquidity/client/testutil/suite.go # x/liquidstaking/client/testutil/suite.go
d84cc33
to
ed6ff72
Compare
ed6ff72
to
2fc9984
Compare
Problem (Fixed)It is quite difficult to debug why this particular simulation test DebugAs you can see,
The panic comes from worker 3 [W3]. When I open the stdout file, the following logs can be found.
SolutionThis is due to using the same directory |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
This PR adds the
wasmd
module to support CosmWasm in Crescent blockchain.closes: #132
Notes
This PR is intended to be merged for v5.
Tasks
wasmd
inStoreUpgrades
for v5UpgradeHandler
for v5.Design Decision
References
Tests
In order to use the following commands, you must spin up a full node with the
config-test.toml
using Ignite CLI in your local machine with this branch.Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes