Change log
- 2025-07-30 Created initial post
Summary
Enable Permissionless CosmWasm Smart Contract Deployment on Cosmos Hub
Details
Today, CosmWasm (CW) is permissioned on the Cosmos Hub. This means that in order to deploy a contract, an address must first be whitelisted via an on-chain vote. Once whitelisted, that address can deploy as many contracts as it wants without going through governance again unless its permission is later revoked.
Current situation:
Very few deployments are happening on the Hub.
Suspected reasons:
-
A project needs visibility and certainty to get started. Itâs hard to convince investors with a pitch like: âWeâll build for months, but weâre not sure if weâll be allowed to deploy.â
-
The process is too slow and clunky, due to slow or inefficient governance.
-
Teams are sometimes reluctant to expose themselves publicly or be judged in a vote.
-
The whitelisting mechanism lacks granularity: once approved, an actor can deploy unlimited contracts without further review.
-
The Hub isnât seen as a developer-friendly environment compared to simpler and faster alternatives (Neutron, Osmosis, etc.).
-
Low current activity creates a loop of inertia: low usage = low attractiveness.
The current Cosmwasm parameters on the Hub are:
{
"code_upload_access": {
"permission": "AnyOfAddresses",
"addresses": [
"cosmos1raa4kyx5ypz75qqk3566c6slx2mw3qzs5ps5du",
"cosmos19pmppgpqnjkvjp6mx8q2dpuy382g4hhxatt9sk",
"cosmos1559zgk3mxm00qtr0zu2x5n4rh5vw704qaqj6ap"
]
},
"instantiate_default_permission": "Everybody"
}
Why CosmWasm?
-
Several well-known Cosmos teams want to deploy on the Hub.
-
CosmWasm is part of the native Cosmos stack, with a well-equipped ecosystem (IBC integration, CosmJS, etc.).
-
Some live applications are becoming critical (e.g. Hydro).
-
The Hub could attract meaningful use cases if development becomes easier.
-
CosmWasm enables strong modularity and security through smart contracts.
Historical concerns:
The main worry has always been security: risks of exploits, hacks, rug pulls, etc.
What community knows:
Neutron, a permissionless CosmWasm chain, shows that:
-
Deployment volume remains reasonable.
-
No major incidents have occurred to date.
-
Permissionlessness hasnât led to overload or chaos.
Furthermore, in the current case of permissioned CW on the hub, a previously whitelisted address can deploy a multitude of contracts without authorization, which would be at risk in the case of an unperformed audit. Ultimately, the current permissioned CW only bottlenecks development on the cosmos hub.
If an issue were to arise, ICL (in charge of Hub software) could respond quickly.
Proposed idea:
Enable permissionless CosmWasm SC deployment on the Hub.
The updated Cosmwasm parameters on the Hub would be:
{
"@type": "/cosmos.wasm.v1.MsgUpdateParams",
"authority": "cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn",
"params": {
"code_upload_access": {
"permission": "Everybody"
},
"instantiate_default_permission": "Everybody"
}
}
In conclusion:
By allowing permissionless Cosmwasm SC deployment, we will make the hub attractive to developers, enable the development of multiple aligned ATOM applications, create on-chain activity, and therefore, fill the blocks that remain empty, and burn atoms to finally reduce inflation. A better asset to invest in, more useful, less inflationary.
Forum post link
Governance votes
The following items summarize the voting options and what it means for this proposal:
YES - Cosmwasm will become permissionless on the Cosmos Hub
NO - Permissioned Cosmwasm will remain on the hub
NO WITH VETO - A âNoWithVetoâ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of âNoWithVetoâ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.
ABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal.
well done, i support this