Integrate CosmWasm #115
Assignees
Labels
kind/new-feature
Propose the addition of a new feature that does not yet exist
Comments
RiccardoM
added
the
kind/new-feature
|
I was in their community call today. The current design of CosmWASM is to have its own state for each smart contract. I think this is very good when we have different dapps running on Desmos. Even for the flagging issue, different dapps can keep their states whether a post should be visible or not. I have also asked the upgradability of the contracts and they are tracking this feature here. |
This is great! |
RiccardoM
added
the
status/specification
RiccardoM
removed
the
status/specification
|
This should be doable now, I can follow the wasmd example which is already compatible with stargate. |
19 tasks
mergify bot
pushed a commit
that referenced
this issue
Jan 18, 2022
## Description Closes: #115. This PR integrate the CosmWasm module into Desmos. At the current stage, no rules are applied to the smart contracts store/instantiate flow and any kind of contract can be deployed on the network if we will update the testnet as it is. I think that for testing purposes this is the best choice, however, I will work on an ADR for permissioned contracts and contracts limitations soon. Since Desmos is a social network related project, contracts deployment should be limited to contracts that are social-related. --- ### Author Checklist *All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.* I have... - [x] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] added `!` to the type prefix if API or client breaking change - [x] targeted the correct branch (see [PR Targeting](https://github.com/desmos-labs/desmos/blob/master/CONTRIBUTING.md#pr-targeting)) - [x] provided a link to the relevant issue or specification - [x] followed the guidelines for [building modules](https://docs.cosmos.network/v0.44/building-modules/intro.html) - [ ] included the necessary unit and integration [tests](https://github.com/desmos-labs/desmos/blob/master/CONTRIBUTING.md#testing) - [x] added a changelog entry to `CHANGELOG.md` - [ ] included comments for [documenting Go code](https://blog.golang.org/godoc) - [ ] updated the relevant documentation or specification - [x] reviewed "Files changed" and left comments if necessary - [x] confirmed all CI checks have passed ### Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... - [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] confirmed `!` in the type prefix if API or client breaking change - [ ] confirmed all author checklist items have been addressed - [ ] reviewed state machine logic - [ ] reviewed API design and naming - [ ] reviewed documentation is accurate - [ ] reviewed tests and test coverage - [ ] manually tested (if applicable)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to allow custom applications to implement their features the best way possible without having to fork the Desmos chain, I think we should start taking a look at CosmWasm.
This Cosmos module, developed by Ethan Frey, allows anyone to write smart contracts that can later run on the chain itself.
This could be particularly useful for example when integrating custom posts reporting logics as described inside #50.
The text was updated successfully, but these errors were encountered: