Substrate and Polkadot Stack Exchange is a question and answer site for developers building blockchains with the Substrate SDK. It only takes a minute to sign up.
Sign up to join this community
I would like to use the sudo pallet instead of the democracy pallet.
Now I would like to force the sudo user to wait three months until a runtime upgrade can be applied. So, that there is no way to execute a runtime upgrade before this period of three months has passed (not even an emergency upgrade). How is this possible?
What transactions should be filtered, so that this rule can't be avoided by the sudo user?
What transactions should be filtered, so that this rule can't be avoided by the sudo user?
You do not force sudo to do anything. Sudo is the force.
Sudo::sudo results in Root and can arbitrarily change your runtime, eg. via set_code, thereby removing any call filters.
Sudo is the wrong approach here. Is a way too powerful tool for the job. You need a very restricted origin that can do JUST that. Queueing runtime upgrades with a 3 months lead. I think Gov V2 has the tools for that. Not sure about how it would look like with the current gov.
