What todo with the sudo pallet

[Janislav]

During the last weeks, we created our own governance pallet to replace the sudo pallet. For some parts, it would be cool if we still have the capabilities of the sudo pallet (mostly for development purposes). We have basically two options now:

1. Keep the sudo pallet and remove the sudo account in the genesis config for production
2. Remove the sudo pallet completely and build some dev capabilities into the governance pallet

Pls, let me know whats you're thoughts on this. I talked to different people and have the feeling that we're not all on the same track.

[kylezs]

I think 1. It's got the capabilities of 2 but with much less work. Might this also be a question for the SBP? Whether there are any risks / downsides to keeping Sudo in the runtime but without Sudo accounts?

[Janislav]

I think this question is one of the disadvantages of keeping the sudo module. I would say not, but who knows :D. I would prefer to avoid doing crazy stuff with the root account or the sudo pallet.

[dandanlen]

• Remove the sudo pallet completely and build some dev capabilities into the governance pallet

What would this involve concretely? Is it effectively the same as having a single-member governance set?

Yes, but only for development, or?

[dandanlen]

What would this involve concretely? Is it effectively the same as having a single-member governance set?

Yes, but only for development, or?

Yes, agree, only for development!

[dandanlen]

We would have a governance extrinsic that is call_as_sudo(sudo_call: Call) that just delegates to an arbitrary sudo call?

Should be basically possible. The question is if want to have this OOTB sudo call functionality, or?

I don't see the point in having the sudo functionality as implemented in the sudo pallet, it's basically duplicating something we can implement in a few lines in the governance pallet. I vote for removing sudo.

[kylezs]

it's basically duplicating something we can implement in a few lines in the governance pallet. I vote for removing sudo.

If we're going to be duplicating, and it's simple to implement then yeah, I'd change my vote

[andyjsbell]

I'm for 2. Seems slightly scary saying we use Sudo for debugging.

[Janislav]

Cool, so we all agree on removing the sudo pallet. Apart from that, shall we implement the call_as_sudo(sudo_call: Call) @dandanlen suggested in the governance pallet (or somewhere else)? Would solve a few problems, but also gives access to potentially every sudo call.