Add Enhanced Multisig Pallet to System chains

polkadot-fellows / RFCs

Proposals for change to standards administered by the Fellowship.

https://polkadot-fellows.github.io/RFCs/

Creative Commons Zero v1.0 Universal

109 stars 47 forks source link

Add Enhanced Multisig Pallet to System chains #74

Open asoliman92 opened 4 months ago

asoliman92 commented 4 months ago

This RFC proposes adding an enhanced Multisig pallet to System chains for both better footprint on the blockchain and better enhanced control and ergonomics.

asoliman92 commented 4 months ago

I actually had it as an open question to begin with and then moved it to subject as a suggestion. I did it by process of elimination of other system chains. But now that you mention it, I notice that the original multisig is available on all system chains. What are your thoughts?

-- We discussed offline and @xlc also thinks that having it on all system chains makes sense.

asoliman92 commented 4 months ago

afaiu RFC is not about implementation detail (although in some special cases it can be) but high level technical design decisions. I would like to see more examples/evidences of why stateful multisig would be significant improvement over stateless multisig such that it warrants the existing system chains to add a new pallet in its runtime. Introducing this pallet for new runtimes probably needs much less convincing.

So in your opinion the enhanced functionality, ease of use and less footprint (from quadratic to linear) are not enough? Or you think that these evidences are lacking enough backing from the RFC as is?

gavofyork commented 3 months ago

Some things which should be mentioned in drawbacks:

adding a new pallet which can control accounts across system chains substantially increases attack surface.
stateful code is especially hard to analyse fully.
multisig/pure proxy support is already patchy at best; adding another way of doing the same thing could stoke fragmentation with different UIs supporting different multisig configurations.