Freeze Code ID Proposal

[jhernandezb]

With permissioned CosmWasm chains, it would be nice to freeze code ids from being instantiated.

Example: There is a security bug in a code id and a new one is deployed but you want to prevent the old one from being instantiated but at the same time keep previously instantiated contracts to keep running.

[ethanfrey]

We have a field that controls who can instantiate a given CodeID, called InstantiateConfig. Typically it is "Everybody", but could be set to "Nobody" as is sometimes done in permissioned environments, to only allow the governance mechanism to instantiate that codeID.

If we allowed modifying that field by a gov proposal, that should satisfy your request, right? It would also allow making a restricted codeID free to instantiate by anyone, which is more a permissioned use-case, but nice that one concept can cover a range of uses.

[jhernandezb]

Yes! modifying that value through a gov proposal will totally work

[alpe]

Thanks for bringing this up. I really like the idea of freezing a code id and releasing it. 💯
As Ethan pointed out, this would work with existing authz schema.

I don't have the steps to implement this well documented but as a start these are the high level steps, in case somebody want to give it a try already:

• Add new type to proposal.proto
• Run make proto-all to generate types from proto

Implementation on the server side:

• Register and implement interface methods in proposal.go
• Add proposal handler.
• Add to codec
• Add integration test
• Add to doc

Client side:

• Add to list of ProposalHandlers
• Add cli command
• Verify cli command is in list of wasmd tx gov submit-proposal -h
• Add legacy REST support

Manual testing

• Build a wasmd binary via make install
• Start local instance (see contrib/local)
• Setup system under test and submit proposal

[jhernandezb]

I can probably work on this, how this proposal should be called? It's actually updating instantiation permissions so UpdateInstantiatePermissions ?

[alpe]

💪 great!
The proposal would update the InstantiateConfig on CodeInfo. Technically it is not just the "permission" but can also be an address that was accept-listed.
I don't have a strong opinion on the naming. UpdateInstantiateConfig or SetInstantiateConfig came to my mind.

[jhernandezb]

UpdateInstantiateConfig sounds good to me will start working on it this week.