You are viewing a single comment's thread from:
RE: Reflections on two methods of multisig transactions
I'm not sure what the uses cases are for multi-auth that are satisfied by shipping keys around. If you have a third party to store N keys, why couldn't they store just 1 key?
That is, if your model is that an intermediate collects keys and then signs, wouldn't it be strictly better to give the intermediate a single key and collect authorizations (signatures) instead? (I guess the intermediate could lose the key in this case.)
Well, one way to do second-level key security is to have the program collect keys and then forget them after it uses them. That way rather than having one master key in permanent storage where it can be compromised we have no access to the account except during the extremely-brief period when it has enough keys to do a sign.