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
This issue is to request that the parameter list is able to be added to or removed from by a governance proposal that submits a single address to change the status of.
AnyOfAddresses is a parameter list in the wasm module that allows a chain to have permissioned upload with exceptions for certain addresses building on the platform.
The way this is being modified on permissioned chains right now is by resubmitting the entire list with each parameter change proposal.
This relies on:
Teams applying to be aware of this requirement and submit the correct addresses
Proposals to modify this not to overlap or to assume that previous proposals will pass based on quorum at the time of submission.
This isn't hugely sustainable as more and more teams get access and we have run into #2 a few times already on Osmosis as teams coincidentally want to deploy at the same time.
This feature makes a lot of sense. Thanks for bringing this up!
I would suggest that we support adding/removing multiple addresses in a single message. Although there can be multiple messages in a v1 gov proposal, our command supports only 1.
Adding a duplicate address or removing a non existing address should be silently ignored and not fail the proposal. This are edge cases but there can be multiple in-flight proposals that eventually become persistent
This issue is to request that the parameter list is able to be added to or removed from by a governance proposal that submits a single address to change the status of.
AnyOfAddresses is a parameter list in the wasm module that allows a chain to have permissioned upload with exceptions for certain addresses building on the platform.
The way this is being modified on permissioned chains right now is by resubmitting the entire list with each parameter change proposal.
This relies on:
This isn't hugely sustainable as more and more teams get access and we have run into #2 a few times already on Osmosis as teams coincidentally want to deploy at the same time.
The text was updated successfully, but these errors were encountered: