Original Post: Commonwealth
Proposal #548, to Allow Levana Contracts to be uploaded by a whitelisted address has seen strong opposition due to the fact that the initial contracts to be uploaded will not have their code visible prior to upload. The opposition stance is, that in order for validators and community members to ensure code is safe prior to upload (and can be publicly inspected) the code must be visible before being uploaded on chain. If code is not visible prior, it should not be approved by governance.
This has lead to discussion around the idea of making Osmosis a permissionless chain for contract/code uploads by teams. A stance which may be opposed by many due to Osmosis specifically positioning itself for contracts and applications with a focus or utility around DeFi to deploy on chain, not others. This can also ensure that products which launch on Osmosis are of sufficient quality.
Currently multiple teams can upload contracts to the Osmosis chain (some of specific nature) without further governance approval, if they are uploaded by a particular address which is whitelisted. The following proposals show the teams and addresses allowed to upload contracts:
Interchain Explorer by Cosmostation Apollo DAO
Interchain Explorer by Cosmostation Calc Finance
Interchain Explorer by Cosmostation Levana - (Subject to proposal passing)
Currently, these teams do not require any sort of publicly visible code as part of their agreement with the Osmosis community to be whitelisted for contract uploads (without needing to seek further approval).
This discussion around proposal #548, spearheaded by teams such as Notional DAO, has made us aware of the following inconsistency:
Validators and community members previously approving whitelisted addresses to upload contracts (without a formalised agreement on-chain for future contracts to be public visible), however not approving of proposal #548 on the basis of contract code not being visible before upload.
Therefore Stakecito would like to suggest possible remedies and also ignite discussion around whether or not the Osmosis community would like to see further stipulations for teams uploading contracts to Osmosis.
Signalling proposal to require all teams whitelisted for contract uploads (without needed further approval from governance) to make code publicly visible X days prior to upload, with failure to do so resulting in revoked rights to upload code without governance approval.
Or/And future governance proposals pertaining to contract uploads from external teams, with the stipulation that future uploads do not require approval from governance to have a further stipulation that contract uploads be made publicly visible X amount of days prior to upload.
Some Initial thoughts are that option 1 would be sufficient to apply to all past and future contract upload & address whitelisting proposals, formalising the need for code to be publicly visible prior to upload. However, there may be a better solution, or it may be that the Osmosis community does not feel the need to impose these rules on teams uploading code without future governance approval.