# Make Osmosis PERMISSIONLESS **URL:** \ **Category:** Proposal Discussion\ **Created:** [August 3, 2024, 5:35am UTC](https://forum.osmosis.zone/t/make-osmosis-permissionless/3027 "2024-08-03T05:35:34Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![JohnnyWyles](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/johnnywyles/32/3114_2.png) [@JohnnyWyles](https://forum.osmosis.zone/u/JohnnyWyles)\ **Post date:** [August 5, 2024, 8:41am UTC](https://forum.osmosis.zone/t/make-osmosis-permissionless/3027/2 "2024-08-05T08:41:32Z")
Linking the two previous discussion threads for context: > [@\[DED\] Permissionless CosmWasm](https://forum.osmosis.zone/t/ded-permissionless-cosmwasm/247): > > notice of abandonment I think that it is highly unlikely that this proposal would pass so I don’t think there’s a lot of sense in putting it on the chain. I am very open to exploring this path in the future however, because it makes me profoundly uncomfortable to approve contract addresses instead of contracts, and to say yes to anything that is not open and fully auditable. For the time being, notional will be voting no or veto on closed source contracts, to avoid even the slightest hint of e… > [@Permissionless Cosmwasm v2](https://forum.osmosis.zone/t/permissionless-cosmwasm-v2/436): > > Raising this discussion again with some further viewpoints that have emerged since the last time it was raised here: New discussion points Curation vs Aggregation Stargaze is also a focused appchain but is currently having a vote to enable permissionless CosmWasm ([Mintscan](https://www.mintscan.io/stargaze/proposals/226)) Further discussion on that proposal here: [https://gov.stargaze.zone/discussion/13347-enabling-permissionless-smart-contract-deployment](https://gov.stargaze.zone/discussion/13347-enabling-permissionless-smart-contract-deployment) Not all Dapps on chain need to be promoted by each frontend and both Stargaze and Os… This vote comes down to comparing the risk of permissionless cosmwasm to causing a potential security issue when a bug is discovered and not fixed immediately vs the barrier that permissioned cosmwasm causes to development. In my view, the barrier is incredibly low since Osmosis has never rejected an upload key to a team that went to the chain to ask for one, but there is a barrier that may deter casual developers from deploying. Conversely, the risk is far greater despite permissionless upload being available on the mentioned chains. Cosmos has just had the IBC hooks bug that was enabled by Terra having permissionless upload enabled. > The next step of the process was to upload the malicious contract used to manipulate the IBC timeouts as `code id 3114` and then subsequently instantiate the contract two times. > [Terra IBC Hooks Exploit Analysis - Range Security](https://www.range.org/blog/terra-ibc-hooks-exploit-analysis) There was also a high severity patch for CosmWasm in January of this year that was specifically called out to only impact Permissionless chains and required urgent upgrades on all other chains: > **[High severity security patch upcoming on Wed 10th: CWA-2023-004 (brought to...](https://forum.cosmos.network/t/high-severity-security-patch-upcoming-on-wed-10th-cwa-2023-004-brought-to-you-by-certik-and-confio/12840)** > > Dear community, on Wednesday, January 10th between 10:00 and 12:00 Berlin time Confio will release a fix for a high severity security issue in the CosmWasm virtual machine tracked as CWA-2023-004. The patch for this issue will be distributed and... There is a time for Permissionless CosmWasm, but that comes after: - There have been no high-severity instances for much longer - We have more precise rate limiting implemented to control the risk An alternative solution may be to authorize a subDAO to allocate these upload keys rather than relying entirely on governance. This would make the barrier to upload almost non-existent for anyone who can prove that they are working on a viable project and shorten the cycle time for getting this upload key—although an 8-day delay on deployment doesn’t seem excessive since it is one-time only. --- _[View the full topic](https://forum.osmosis.zone/t/make-osmosis-permissionless/3027)._