--- Log opened Tue Feb 25 00:00:06 2020
00:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined ##taproot-bip-review
01:01 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds]
01:02 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds]
01:56 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined ##taproot-bip-review
03:06 < ghost43> aj: oh indeed, no need for checksigadd for n of n.
03:07 < ghost43> I wonder what the reason is for including the tapleaf in the sighash. I mean, at least with SIGHASH_ALL, I can't see what harm it could do to replace which leaf the sig is for.
05:02 -!- mol [~molly@unaffiliated/molly] has joined ##taproot-bip-review
05:21 -!- belcher [~belcher@unaffiliated/belcher] has joined ##taproot-bip-review
05:44 < ghost43> I would argue that if you don't want the sig used for a different leaf, you should not reuse the pubkey between the leaves. it's the user's responsibility then. e.g. there might be a leaf with some timelock acting as a backout policy, and another leaf with a multisig. you might want to presign only the backout leaf. in that case, use different pubkeys. it's too restrictive to also sign which leaf you want to be executed imho. but maybe
05:44 < ghost43> I am missing something
06:20 < pinheadmz> kanzure: re: malleability (and someone correct me if I'm wrong) but I think Tapscript also consensus-enforces a few rules that were formerly just standardness rules, like NULLFAIL and MINIMALIF
07:26 -!- pinheadmz [~matthewzi@5.181.234.220] has quit [Read error: Connection reset by peer]
07:26 -!- pinheadmz [~matthewzi@5.181.234.220] has joined ##taproot-bip-review
07:39 < sipa> ghost43: malleability
07:40 < sipa> not being able to rebind a signature created for one script to the same key used in another branch
07:41 < sipa> as it's reasonable to reuse keys across scripts
07:41 < ghost43> well okay, but I am arguing for malleability here; I guess. I saying exactly that in some cases you might not care which script get executed, only that some UTXO get spent to some particular new outputs
07:41 < ghost43> like the above mentioned k of n multisig example
07:42 < ghost43> but I get it that one could argue either way
07:44 < ghost43> only entities that know the other tapleaves could malleate, which most often are only the actual participants
07:45 < ghost43> I guess this can be swept under the rug with "maybe with another sighash flag sometime in the future" (aka "go away") :)
07:46 < sipa> i don't think the malleability itself you can get from that is a useful feature... but the effifiency optimizations may be (so that you don't need one signature peotocol instance per potential branch)
07:47 < ghost43> well it's definitely a useful feature not to have to pre-select who the other signers will be as part of a multisig if you are the first signer
07:48 < ghost43> in fact that is how current CHECKMULTISIG works, i.e. doing combinatorial tapleaves with k-of-k multisig to hide unused pubkeys in a generic k-of-n does come at a cost
07:53 < sipa> yup, and within a script that property is maintained
08:57 -!- mol [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
10:43 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
10:44 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##taproot-bip-review
11:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
11:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##taproot-bip-review
11:57 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 252 seconds]
14:16 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
17:33 -!- mol [~molly@unaffiliated/molly] has joined ##taproot-bip-review
22:52 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
22:53 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##taproot-bip-review
23:53 -!- molly [~molly@unaffiliated/molly] has joined ##taproot-bip-review
23:56 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
--- Log closed Wed Feb 26 00:00:06 2020