I know that it is possible to create a 2-2 multsig using Taproot by combining both private keys into one public key and defining that as the key path spend. I also know that it is possible to use Tapscript to do the same thing with a script path spend using OP_CHECKSIGADD.

Is it also possible to use key aggregation in the script path spend, by just providing a public key and signature but doing the same key aggregation as in the key path spend? If so, would it ever make sense to use a "normal" OP_CHECKSIGADD operation in the case of multisig (not threshold signatures).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.