You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently signing store code transactions with multisigs can only be done if you use non-ledger keys due to the memory limit on such devices it makes impossible for signers and for this reason I think it would be very useful to have a contract upload authorization for authz.
Authorize grantee to upload any contract (although this can already be achieved by the generic grant authorization)
Authorize grantee to upload any contract from a list of given hashes so the granter can verify and be confident the grantee only uploads pre-approved contracts,
This can even be useful for DAOs or CW4 multisigs giving access to an uploader by creating a custom authorization.
The text was updated successfully, but these errors were encountered:
jhernandezb
changed the title
Custom ContractUpload Authorization for authz module
Custom StoreCode Authorization for authz module
Aug 29, 2023
This is a good idea!
Would it make sense to have the same for migration?
On store code, an instantiateAccess configuration can be set. Is this something that you want to ensure by the grant as well? I does not seem required but I want to bring this up.
This would make it a lot easier for permissioned chains like stargaze and osmosis where it has a set of uploaders only but dealing with store codes and multisigs is a bit of a pain.
Currently signing store code transactions with multisigs can only be done if you use non-ledger keys due to the memory limit on such devices it makes impossible for signers and for this reason I think it would be very useful to have a contract upload authorization for authz.
This can even be useful for DAOs or CW4 multisigs giving access to an uploader by creating a custom authorization.
The text was updated successfully, but these errors were encountered: