From 0f5c1af7f808b4b0e217a15f9eedfb0fc537b667 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=96zg=C3=BCn=20=C3=96zerk?= Date: Mon, 18 Dec 2023 21:07:58 +0300 Subject: [PATCH] improve multisig documentation for niche details (#67) --- docs/modules/ROOT/pages/pallets/multisig.adoc | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/modules/ROOT/pages/pallets/multisig.adoc b/docs/modules/ROOT/pages/pallets/multisig.adoc index 53d07aa..686e43c 100644 --- a/docs/modules/ROOT/pages/pallets/multisig.adoc +++ b/docs/modules/ROOT/pages/pallets/multisig.adoc @@ -229,12 +229,8 @@ A real use case scenario could be for example a business that has a bank account ** If the approver wants to dispatch the call as well, they should use `as_multi` instead. ** *Niche Details:* - *** if a signatory tries to call `approve_as_multi` after the threshold is surpassed, they will get an error: - *** because, it is meaningless, and even harmful to allow this behavior - *** `approve_as_multi` does not dispatch the call - *** and, if someone approves the call (`as_multi` also counts as an approval), they cannot approve again - *** so, if the last signatory calls `approve_as_multi`, and if succeeds, the multisig operation is stuck (has to be cancelled and re-created). - *** Hence, it is creating an error to call `approve_as_mutli` after the threshold is surpassed. + *** If a signatory tries to call `approve_as_multi` after the threshold is surpassed, they will get an error: `AlreadyApproved`, because this action is meaningless. + *** A signatory can call `as_multi` to dispatch the call, even if they approved the same multisig before. * `1-out-of-n multisig account` example: ** Alice, Bob, and Charlie want to create a shared account, and the threshold for this shared account should be 1 (any person can spend from this account, without any approval).