Multisig

[James-Mart]

Specification(s)

Dependency

• Use schema to go from Fracpack to JSON (in Rust) #832

Msig auth service

The auth service should allow for transactions with 0 claims. Rather than confirming appropriate claims, it simply checks that the transaction ID has been approved in the msig table by the necessary threshold of signers according to the msig config for the sender account.

Offline msig tx support?

Unsure what would be needed to also allow for a tx to contain N claims, where the threshold is N/M. This is more complicated since we can't assume each account specified in the msig configuration uses the same kind of claims (could use any auth service).

Msig verify service

(There is none)

Msig UX

A user may enable administration mode in their account settings, which stores a client-side flag in their transact plugin. This flag causes transact to wrap the transaction (in JSON) proposed by a plugin function execution as a parameter to an msig:propose action. Ideally, this should also follow a manual-transaction-submission flow so that the sender explicitly confirms that they are intending to submit an msig proposal (in case they forget they turned on administration mode).

Then, other administrators configured in the msig are notified, can visit the msig UI, and see the proposed transactions which are relevant to them, and can simply submit an action to "accept" or "reject" the transaction.

Once there are a threshold number of accounts who have accepted the msig proposal, anyone (including non-admins) can submit the originally proposed transaction with no claims/proofs in order to execute it.