You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or issue you encountered? Please describe.
CosmWasm is one of the most popular smart contract VM in Cosmos and therefore it makes sense that Ignite CLI simplifies the process of building a chain with CosmWasm enabled
Right now we already have this issue created: #1837 which is about dynamically importing the wasm module
This task is about a simpler implementation where chain are scaffolded initially with wasm module. Therefore with a specific template for wasm enabled chains
This issue is similar to this one for EVM: #2633 but for wasm
Describe the solution you'd like
Adding a flag --wasm in scaffold chain to let chains include the wasm module when scaffolded
ignite scaffold chain planet --wasm
Ideally a chain could be scaffolded with evm and wasm
ignite scaffold chain planet --wasm --evm
Once the chain is scaffolded, regular CLI commands can work for custom modules
Going further
We could consider scaffolding in the chain source an environment for CosmWasm contract development like Beaker from Osmosis: https://github.com/osmosis-labs/beaker
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem or issue you encountered? Please describe.
CosmWasm is one of the most popular smart contract VM in Cosmos and therefore it makes sense that Ignite CLI simplifies the process of building a chain with CosmWasm enabled
Right now we already have this issue created: #1837 which is about dynamically importing the
wasm
moduleThis task is about a simpler implementation where chain are scaffolded initially with
wasm
module. Therefore with a specific template for wasm enabled chainsThis issue is similar to this one for EVM: #2633 but for wasm
Describe the solution you'd like
Adding a flag
--wasm
inscaffold chain
to let chains include thewasm
module when scaffoldedIdeally a chain could be scaffolded with
evm
andwasm
Once the chain is scaffolded, regular CLI commands can work for custom modules
Going further
We could consider scaffolding in the chain source an environment for CosmWasm contract development like Beaker from Osmosis: https://github.com/osmosis-labs/beaker
The text was updated successfully, but these errors were encountered: