[PROPOSAL 1007][PASSED] Enable Permissionless CosmWasm Smart Contract Deployment on Cosmos Hub

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…

Excerpt (1194 of 4354 characters). Read the whole post on the forum ↗

I fully support this proposal.

Voting yes, finally hopefully hub will do something useful.

This is an excellent idea — thank you for putting forward such a thoughtful and necessary proposal. Here are my reasons why permissionless CosmWasm deployment on the Cosmos Hub makes perfect sense:

1. Faster Innovation
   Developers can deploy instantly without waiting for governance votes, speeding up experimentation and product launches.

2. More Developer Engagement
   Making the Hub more accessible will attract builders who currently prefer platforms like Neutron or Osmosis.

3. Reduced Governance Overhead
   Governance shouldn’t have to approve every single contract deployer — it’s inefficient and not scalable.

4. Real Ecosystem Growth
   More deployments = more use cases, more users, more ATOM burned, and ultimately, a stronger, more active chain.

5. Security Doesn’t Disappear
   Permissionless doesn’t mean unsecure — other Cosmos chains have proven that open deployment works without leading to chaos.

Let’s make the Hub developer-friendly and future-ready. Full support from me!

Let’s go ! Voting yes

Well written. Full support. Even if concerns in terms of exploits, hacks, rugpulls still holds - that’s part of the game. Besides security, “value” should be weighed in. A 100% secured chain with nearly 0.01% possibilities of value creation for builders, it’s worthless.

Our 2 cents

Fully supporting this, when will this be posted on-chain?

Voting will begin at the beginning of the coming week

Nice! Tokenfactory will be next? Thanks for not giving up, Guinch!

I made a ping for ICL to know if it is planed to add it. If they don’t answer this, I could make a signaling proposal next week .

You have our support

Full support on the prop. Lets get this passed asap.

Hey guys, jumping in here as a creative director and product owner who’s bootstrapped a few startups in the web3 space - think UX-driven DeFi tools and NFT platforms that actually feel fun to use, not like clunky spreadsheets from the 90s. I’ve been lurking on Cosmos stuff for a while 'cause I’m all about ecosystems that empower builders without the red tape. This proposal? Total game-changer . I’m voting YES all the way, and here’s why, plus some brainstorm vibes to amp it up. First off, massive props to your Cosmos crew for laying this out so clean. The current permissioned setup is like asking artists to submit a portfolio just to buy paint - sure, it weeds out some bad apples, but it kills the vibe for everyone else. I’ve seen it firsthand: teams ghost on projects 'cause “governance roulette” isn’t exactly investor catnip. Permissionless CW on the Hub? That’s flipping the script to “build first, shine later.” It’d spark that flywheel - more devs tinkering, more apps popping up, blocks filling up, ATOM burning brighter. Love how you tied it to real wins like Neutron’s chill deployment scene; no chaos, just steady growth. And yeah, the security angle’s solid—ICL’s got the…

Excerpt (1194 of 2454 characters). Read the whole post on the forum ↗

I think we have a lot of resources in the hub community, and soon, thanks to this vote, which we hope will be voted YES, the large cosmos community that has drifted away over time, will come back with more ideas, more knowledge and experience, to build on a more secure, more reputable platform, this will make noise! A lot of people have had ideas about apps that could be launched here, and app launchpads with interesting mechanisms, @agentkwosh has had some good ideas lately and I think we need to develop in his direction and in yours to allow for fast and well-organized development. Let’s take things in order, let’s make this prop 1007 the proposal that will revolutionize the usefulness of ATOM for its close community, that will allow DEFIHUB, etc… the hub is the heart of the cosmos, and thanks to this proposal, it would become the heart + the brain. next step: EVM pss, then multiVM support in the AEZ. let any developer in the world come and build on ATOM, and scale thanks to IBC eureka.

This is a good idea, but why was CosmWasm was not originally launched permissioniess? Really only because of fear of scum?

Security related, and Neutron was the PSS chain with permissionless CW. Right now, Neutron is no more Atom aligned, then ATOM community needs to move forward, and fast.

POSTHUMAN voted YES on this proposal

We belive it will attract more builders on Cosmos Hub

100% YES. Especially now that Neutron is no longer on ICS (or won’t be in the future). This opens the door for countless dApps that want to build in Cosmos but are forced onto other chains (like Neutron and Osmosis) and then IBC their way back to ATOM. Enabling permissionless contracts on Hub would make Cosmos Hub the natural home for these builders.

Next step after that should definitely be x/tokenfactory.

yes yes yes full support let’s make hub great again

well done, i support this

I’m for it, it will benefit the ecosystem.

What security measures or monitoring will be in place once permissionless deployment is enabled to prevent malicious or vulnerable contracts from causing harm?

if CosmWasm becomes permissionless on the Hub, what safeguards (audits, monitoring, circuit breakers) would exist to mitigate risks of malicious contracts being deployed?