--- Log opened Sat May 16 00:00:22 2020
01:13 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-rqvyjjlwqqisisoh] has joined ##taproot-bip-review
02:30 -!- jonatack [~jon@37.173.34.185] has quit [Ping timeout: 256 seconds]
02:31 -!- jonatack [~jon@213.152.161.239] has joined ##taproot-bip-review
02:56 -!- belcher [~belcher@unaffiliated/belcher] has joined ##taproot-bip-review
04:19 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-bip-review
04:22 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 272 seconds]
05:42 < harding> Posting here in case it helps anyone avoid spending a couple hours going down a mental blind alley.  aj wrote about how committing to Coin.nHeight would be an anti-feature in https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-May/017813.html
05:42 < harding> I had what I thought was a clever idea of only making such a commitment if that input's nSequence used a BIP68-restricted value, i.e. the UTXO couldn't be spent in the same block as its parent anyway.
05:42 < harding> That works great if you're signing after the parent is confirmed, but it wasn't until I'd spent a bunch of time describing the benefits of this idea for anti fee sniping that I realized it doesn't work for presigned transactions, e.g. in contract protocols like LN or in the recent vault proposals.  Anyway, lesson learned: listen to aj when he says something isn't worth adding.  :-)
05:44 < harding> presigned transactions [that use BIP68]*
06:02 -!- jonatack [~jon@213.152.161.239] has quit [Ping timeout: 240 seconds]
06:05 -!- jonatack [~jon@37.173.217.56] has joined ##taproot-bip-review
06:07 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 265 seconds]
06:33 -!- mol [~mol@unaffiliated/molly] has joined ##taproot-bip-review
06:41 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-bip-review
06:41 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
06:44 -!- molz_ [~mol@unaffiliated/molly] has joined ##taproot-bip-review
06:47 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
07:26 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 265 seconds]
08:00 -!- mol [~mol@unaffiliated/molly] has joined ##taproot-bip-review
09:11 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
09:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-bip-review
09:16 < ghost43> harding: also, a reorg of the parent tx could invalidate the child tx :/
09:20 < harding> ghost43: right, that I at least did think about and my aborted email noted that required careful consideration especially in the context of contract protocols (it was actually that thought that lead me to it breaking presigned BIP68-using txes).  However, that it's that exact disadvantage which also provided its advantage for anti fee sniping.  Unlike existing anti fee sniping where a dishonest miner can still get the
09:20 < harding> transaction fee (they just can't bury high-fee transactions as far back as they'd like), anti fee sniping based on a commitment to the header hash of the block including the UTXO would invalidate the child tx and completely deny the dishonest mine any revenue from it.
09:27 < harding> ghost43: here's what I had written by the point I realized the flaw, in case it's useful or you just want to see how foolish I am  :-)  https://gist.github.com/harding/e1316f2e012a354decef939ca6cd82cc
11:34 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-bip-review
11:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds]
11:39 -!- lukedashjr is now known as luke-jr
15:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 256 seconds]
15:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-bip-review
16:48 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-bip-review
16:51 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
16:57 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
17:06 -!- mol [~mol@unaffiliated/molly] has joined ##taproot-bip-review
17:20 -!- mol [~mol@unaffiliated/molly] has quit [Read error: Connection reset by peer]
17:21 -!- mol [~mol@unaffiliated/molly] has joined ##taproot-bip-review
17:56 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds]
18:00 -!- jonatack_ [~jon@37.165.91.121] has joined ##taproot-bip-review
18:04 -!- jonatack [~jon@37.173.217.56] has quit [Ping timeout: 265 seconds]
18:04 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-bip-review
19:31 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 252 seconds]
19:43 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined ##taproot-bip-review
21:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
21:35 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##taproot-bip-review
22:34 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-bip-review
22:37 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 265 seconds]
--- Log closed Sun May 17 00:00:23 2020