--- Log opened Fri Feb 14 00:00:41 2020
01:30 -!- evoskuil[m] [evoskuilma@gateway/shell/matrix.org/x-icpnifrywzlrijxm] has joined ##taproot-bip-review
05:30 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 245 seconds]
09:49 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
09:58 -!- belcher [~belcher@unaffiliated/belcher] has joined ##taproot-bip-review
10:18 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined ##taproot-bip-review
10:19 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
10:55 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined ##taproot-bip-review
11:25 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
11:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##taproot-bip-review
12:36 -!- jeremyrubin [~jr@c-67-180-60-249.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds]
12:37 -!- jeremyrubin [~jr@c-67-180-60-249.hsd1.ca.comcast.net] has joined ##taproot-bip-review
15:35 < jeremyrubin> harding: I think the thing that's not clear to me is that the single sig majority will continue
15:36 < jeremyrubin> E.g., one could imagine once lightning is deployed fully, then I would expect the majority of transactions to be lightning channel closes
15:36 < jeremyrubin> Or at least envision that being the case
15:37 < jeremyrubin> Because there is really no reason to ever close a channel if the LN is working well (strong claim)
15:37 < jeremyrubin> So the only time you would close would be for contested close
15:37 < jeremyrubin> So then that would be the dominant case on the network
15:37 < jeremyrubin> And Taproot would be costing those users a bit extra
15:38 < jeremyrubin> We won't have evidence for that for like a decade so :shrug: overall
15:38 < jeremyrubin> But it's not clear to me that the priors are really that strong
15:39 < jeremyrubin> And that we won't see some big sampling bias on actual on-chain behavior (the ones that can be a single sig never need to go on chain)
15:50 < maaku> jeremyrubin: there are many reasons to close a LN channel even when it is working. not all use cases are payments...
15:51 < maaku> but that doesn't affect the general point you're making
15:52 < jeremyrubin> maaku: such as? And it doesn't need to be exclusively for payments, just needs to be the most frequent
15:55 < maaku> well, like movement of colored coin assets that are sign-to-contract committed to a LN channel, or moving coins in-out of a consensus-enforced vault construct
15:55 < maaku> but unless there's a long tail of these esoteric use cases, which I'm not ready to argue, then you're right about the most common use cases
15:56 < maaku> so it doesn't really impact your argument. i was being pedantic
15:56 < jeremyrubin> maaku: so for colored coin LN does that require moving out?
15:56 < jeremyrubin> maaku: and for vault-y stuff I would expect that to not be single sig anyways
15:56 < jeremyrubin> anyways we can take it out of band
16:32 -!- gmaxwell [gmaxwell@wikimedia/KatWalsh/x-0001] has left ##taproot-bip-review []
16:58 -!- achow101_ [~achow101@unaffiliated/achow101] has joined ##taproot-bip-review
16:59 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Remote host closed the connection]
16:59 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
17:02 -!- dr-orlovsky [~dr-orlovs@ip216.ip-54-36-238.eu] has quit [Ping timeout: 262 seconds]
17:04 -!- dr-orlovsky [~dr-orlovs@ip216.ip-54-36-238.eu] has joined ##taproot-bip-review
17:56 -!- harding [~quassel@li1228-87.members.linode.com] has quit [Quit: tired of arguing]
20:09 -!- pinheadmz_ [~matthewzi@184.170.246.237] has joined ##taproot-bip-review
20:12 -!- pinheadmz [~matthewzi@pool-100-33-69-78.nycmny.fios.verizon.net] has quit [Ping timeout: 248 seconds]
20:12 -!- pinheadmz_ is now known as pinheadmz
21:06 -!- pinheadmz [~matthewzi@184.170.246.237] has quit [Quit: pinheadmz]
22:14 -!- achow101_ is now known as achow101
--- Log closed Sat Feb 15 00:00:39 2020