From 572cc6763232bcc697bb638a9de697ae59f6fc67 Mon Sep 17 00:00:00 2001 From: bkchr Date: Sun, 18 Feb 2024 00:52:33 +0000 Subject: [PATCH] deploy: bcca93886c04fc78da17056a155ebb1c9b2e12c2 --- new/0074-stateful-multisig-pallet.html | 6 ++++++ print.html | 6 ++++++ searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 14 insertions(+), 2 deletions(-) diff --git a/new/0074-stateful-multisig-pallet.html b/new/0074-stateful-multisig-pallet.html index 1671086..3283d1b 100644 --- a/new/0074-stateful-multisig-pallet.html +++ b/new/0074-stateful-multisig-pallet.html @@ -234,6 +234,12 @@

We believe as well that the stateless multisig is not efficient in terms of block footprint as we'll show in the performance section.

Pure Proxy

Pure proxy can achieve having a stored and determinstic multisig account from different users but it's unneeded complexity as a way around the limitations of the current multisig pallet. It doesn't also have the same fine grained control over the multisig account.

+

Other points mentioned by @tbaut

+

Requirements

Basic requirements for the Stateful Multisig are: