12019-12-15T00:30:38  *** Guest54499 has quit IRC
 22019-12-15T00:31:43  *** daniel has joined ##taproot-bip-review
 32019-12-15T00:32:07  *** daniel is now known as Guest79518
 42019-12-15T01:57:17  *** jeremyrubin has quit IRC
 52019-12-15T01:57:41  *** jeremyrubin has joined ##taproot-bip-review
 62019-12-15T04:36:01  *** mol has joined ##taproot-bip-review
 72019-12-15T08:33:57  *** davterra has quit IRC
 82019-12-15T08:34:32  *** davterra has joined ##taproot-bip-review
 92019-12-15T09:04:18  *** belcher has quit IRC
102019-12-15T09:07:56  *** belcher has joined ##taproot-bip-review
112019-12-15T10:46:59  *** jonatack has quit IRC
122019-12-15T11:32:06  *** jonatack has joined ##taproot-bip-review
132019-12-15T12:13:52  *** b10c has joined ##taproot-bip-review
142019-12-15T13:22:52  *** molly has joined ##taproot-bip-review
152019-12-15T13:25:57  *** mol has quit IRC
162019-12-15T13:34:15  *** dr-orlovsky has quit IRC
172019-12-15T13:34:38  *** dr-orlovsky has joined ##taproot-bip-review
182019-12-15T13:57:00  *** ZmnSCPxj has joined ##taproot-bip-review
192019-12-15T14:20:40  *** dr-orlovsky has quit IRC
202019-12-15T14:43:05  *** davterra has quit IRC
212019-12-15T14:43:25  *** davterra has joined ##taproot-bip-review
222019-12-15T14:54:42  <pinheadmz> Question about the script tree diagram in https://github.com/sipa/bips/blob/bip-schnorr/bip-taproot.mediawiki#constructing-and-spending-taproot-outputs
232019-12-15T14:55:05  <pinheadmz> the node labeled "AB=0x71" -- is that not also a hash-TapBranch like the CD and CDE nodes?
242019-12-15T15:03:20  *** andytoshi has joined ##taproot-bip-review
252019-12-15T15:03:20  *** andytoshi has joined ##taproot-bip-review
262019-12-15T15:12:11  *** andytoshi has quit IRC
272019-12-15T15:26:28  <pinheadmz> ooh I see its explained in the comments, but maybe add that to the diagram?
282019-12-15T15:31:33  *** davterra has quit IRC
292019-12-15T15:32:02  *** davterra has joined ##taproot-bip-review
302019-12-15T16:53:45  *** dr-orlovsky has joined ##taproot-bip-review
312019-12-15T16:57:03  *** b10c has quit IRC
322019-12-15T16:57:04  *** dr-orlovsky has joined ##taproot-bip-review
332019-12-15T17:08:56  <sipa> pinheadmz: both the merkle branches in spv proofs and here are serialized bottom to top
342019-12-15T17:16:44  <sipa> oh, no
352019-12-15T17:16:48  <sipa> sorry!
362019-12-15T17:20:25  <sipa> in bip37 things are indeed serialized top down
372019-12-15T17:24:34  *** jonatack has quit IRC
382019-12-15T17:26:31  *** jonatack has joined ##taproot-bip-review
392019-12-15T17:27:24  *** davterra has quit IRC
402019-12-15T17:39:58  *** dr-orlovsky has quit IRC
412019-12-15T17:40:20  *** dr-orlovsky has joined ##taproot-bip-review
422019-12-15T17:46:56  *** dr-orlovsky has quit IRC
432019-12-15T17:47:29  *** dr-orlovsky has joined ##taproot-bip-review
442019-12-15T17:58:53  *** dr-orlovsky has quit IRC
452019-12-15T17:59:12  *** orlovsky has joined ##taproot-bip-review
462019-12-15T18:04:52  *** davterra has joined ##taproot-bip-review
472019-12-15T18:37:02  *** dr-orlovsky has joined ##taproot-bip-review
482019-12-15T18:37:23  *** orlovsky has quit IRC
492019-12-15T18:38:47  <pinheadmz> sipa: are you referring to my PR this morning? re: example order of hashes in the control block?
502019-12-15T18:42:46  <sipa> yeah
512019-12-15T19:37:09  *** b10c has joined ##taproot-bip-review
522019-12-15T19:45:06  *** dr-orlovsky has quit IRC
532019-12-15T19:46:07  *** dr-orlovsky has joined ##taproot-bip-review
542019-12-15T19:46:33  *** davterra has quit IRC
552019-12-15T19:47:22  *** dr-orlovsky has quit IRC
562019-12-15T19:49:13  <pinheadmz> yeah taproot is inside out :-) I dunno why I kept expecting to see the hashes left-to-right... dummies like me gonna need an example
572019-12-15T19:51:43  <sipa> i never realized that the encoding in bip37 and bip-taproot is the reverse order, despite having designed both :)
582019-12-15T19:51:50  *** dr-orlovsky has joined ##taproot-bip-review
592019-12-15T19:52:07  <sipa> it just seems so natural to do it bottom up, as that's what the verifier needs
602019-12-15T19:54:00  <pinheadmz> right and the algo starts with k0 being the leaf we execute, so it wouldnt make sense the other way
612019-12-15T20:10:22  *** orlovsky has joined ##taproot-bip-review
622019-12-15T20:12:29  *** dr-orlovsky has quit IRC
632019-12-15T22:22:33  <ZmnSCPxj> Really old backreading from 2019-11-22: <nickler> so you can run different lightning implementations in parallel and both have to sign for an update (transparently, without telling the other node that you're doing that)
642019-12-15T22:23:00  <ZmnSCPxj> Context is discussion about MuSig-in-MuSig i.e. composable MuSig
652019-12-15T22:23:42  <ZmnSCPxj> It seems not possible to not telling the other node about this, as both signatures need to have the same `R` so you can combine their `s` together, I think...?
662019-12-15T22:24:09  <ZmnSCPxj> ...unless you feed an `R` to both implementations, I suppose.
672019-12-15T23:28:10  *** orlovsky has quit IRC
682019-12-15T23:28:15  *** dr-orlovsky has joined ##taproot-bip-review