Thank you for initiating this much-needed discussion on the future of CosmWasm (CW) deployment on the Cosmos Hub. We appreciate the clarity in outlining the current limitations and strategic options under consideration.
After reviewing the context and available paths, we wish to express our support for Strategy 2:
“Keep CosmWasm on the Hub, and create a permissionless EVM chain governed by the Hub with ATOM as the gas token.”
This path aligns with the following key objectives:
1. Preserve Strategic Value
CosmWasm is deeply integrated in the Cosmos ecosystem and remains a critical component of ongoing projects like Hydro. Removing it from the Hub could create unnecessary fragmentation and weaken the Hub’s technical role.
2. Enable Growth Without Delay
A permissionless EVM chain governed by the Hub offers immediate utility for developers and users. It can be implemented quickly, at low cost, and will strengthen the ATOM economy through exclusive gas usage.
3. Balance Trust and Flexibility
Keeping CosmWasm permissioned on the Hub ensures high-trust deployments for public-good infrastructure. In parallel, the new EVM environment will support permissionless experimentation. This dual architecture balances the need for security and developer freedom.
4. Security Risks Are Manageable
Neutron has demonstrated that permissionless CW environments can operate safely under proper validator and governance oversight. Should future demand grow, we can reassess policies on CW deployment on the Hub itself.
Why Not Strategy 1 or 3?
- Strategy 1 (removing CW entirely) would undercut active projects and diminish the Hub’s technical relevance.
- Strategy 3 (launching two new chains) may be viable long-term, but introduces unnecessary delay and complexity at this stage.
Recommendation
We recommend that the community prioritize Strategy 2 and begin exploring next steps toward its implementation. We would also suggest continued improvements to the CosmWasm permissioning process on the Hub, such as:
- More granular deployment approvals (e.g. KYC or contract-level governance)
- Improved timelines and review structures for proposal-based onboarding
- Optional pseudonymous developer interactions via reputable actors’ multisig or legal wrappers
We thank the contributors for framing this discussion and welcome continued engagement to ensure this roadmap leads to sustainable activity.
Thank you for reading,
Govmos.
