--- Day changed Thu Oct 15 2020 00:15 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 264 seconds] 00:46 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 01:03 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 01:07 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 01:08 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 01:37 -!- da39a3ee5e6b4b0d [~textual@67.23.55.162] has joined #bitcoin-core-pr-reviews 01:42 -!- jonatack [~jon@109.202.107.147] has quit [Ping timeout: 260 seconds] 01:47 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has quit [Ping timeout: 264 seconds] 02:02 -!- musdom [~Thunderbi@2001:f40:904:bb14:e1a7:624e:2e60:d878] has quit [Ping timeout: 260 seconds] 02:07 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 240 seconds] 02:12 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 02:15 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 02:16 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 02:21 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-pr-reviews 02:22 -!- jonatack [~jon@213.152.161.211] has joined #bitcoin-core-pr-reviews 02:33 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 02:38 -!- jonatack [~jon@213.152.161.211] has quit [Ping timeout: 265 seconds] 02:38 -!- da39a3ee5e6b4b0d [~textual@67.23.55.162] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 02:40 -!- jonatack [~jon@37.172.104.51] has joined #bitcoin-core-pr-reviews 02:43 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 02:46 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 258 seconds] 02:47 -!- jonatack [~jon@37.172.104.51] has quit [Ping timeout: 240 seconds] 02:50 -!- jonatack [~jon@213.152.161.10] has joined #bitcoin-core-pr-reviews 02:58 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 03:14 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 03:18 -!- Audreanne40Powlo [~Audreanne@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 03:23 -!- Audreanne40Powlo [~Audreanne@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 246 seconds] 03:23 -!- jonatack [~jon@213.152.161.10] has quit [Ping timeout: 272 seconds] 03:23 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 03:24 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 03:25 -!- jonatack [~jon@37.172.104.51] has joined #bitcoin-core-pr-reviews 03:28 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-pr-reviews 03:35 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving] 03:37 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 03:38 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 03:38 -!- aj [aj@cerulean.erisian.com.au] has quit [Ping timeout: 260 seconds] 03:39 -!- jonatack [~jon@37.172.104.51] has quit [Read error: Connection reset by peer] 03:40 -!- jonatack_ [~jon@37.172.104.51] has joined #bitcoin-core-pr-reviews 03:41 -!- jonatack_ [~jon@37.172.104.51] has quit [Read error: Connection reset by peer] 03:41 -!- jonatack__ [~jon@37.172.104.51] has joined #bitcoin-core-pr-reviews 03:53 -!- jonatack [~jon@37.164.124.179] has joined #bitcoin-core-pr-reviews 03:55 -!- jonatack__ [~jon@37.172.104.51] has quit [Ping timeout: 260 seconds] 04:04 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 04:09 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 260 seconds] 04:17 -!- musdom [~Thunderbi@202.184.183.249] has joined #bitcoin-core-pr-reviews 04:17 -!- jonatack [~jon@37.164.124.179] has quit [Ping timeout: 264 seconds] 04:21 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 04:22 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 04:23 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 04:24 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 04:25 -!- aj [aj@cerulean.erisian.com.au] has joined #bitcoin-core-pr-reviews 04:32 -!- tralfaz [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-pr-reviews 04:32 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 04:33 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 04:34 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 05:04 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-pr-reviews 05:04 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 05:44 < pinheadmz> https://github.com/bitcoin/bitcoin/pull/19953 merged! WE DID IT REVIEW CLUB 05:44 < emzy> \o/ 05:52 -!- willcl_ark is now known as [github-bot] 05:55 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 05:57 -!- molz_ [~mol@unaffiliated/molly] has quit [Remote host closed the connection] 05:57 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 05:57 -!- [github-bot] is now known as wilcl_ark 05:58 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 06:00 < michaelfolkson> Everything I looked at over a long period of time was an ACK. But there could still easily be something I missed or didn't understand. I guess that is where we are leaning on the long term reviewers 06:01 < michaelfolkson> It would never get merged if waited until all of us were 100 percent sure 06:03 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-pr-reviews 06:04 < michaelfolkson> If you had to put percent on it based on your personal review (not all the long term reviewers ACKs) that there were no problems with it what percent would you give? 06:04 < emzy> Using tabroot is optional, so it will anyway take time until widely used. So still time to fix stuff on the way. Sure best to don't have to. 06:05 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 06:06 < michaelfolkson> It is optional until activation. But I guess this feeds into the activation discussion. How sure do we personally want to be before it is activated? 06:07 < michaelfolkson> It is probably ok if someone like me is 80 percent sure and long term reviewers are 95-99 percent sure 06:10 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 246 seconds] 06:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 06:21 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-pr-reviews 06:21 < emzy> I think there is no absulut 100% anyway. 06:21 < michaelfolkson> Of course not. That's why I said 95-99 percent even for long term reviewers 06:23 < emzy> right 06:23 < jonatack> zero bugs? close to zero chance :D 06:24 < jonatack> but the next 6 weeks are a good time to find and fix them 06:25 < michaelfolkson> Right. Even though merged needs attention as much as ever 06:26 -!- tralfaz is now known as davterra 06:29 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Quit: ZNC 1.7.5 - https://znc.in] 06:31 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 06:31 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #bitcoin-core-pr-reviews 06:33 -!- shesek [~shesek@164.90.217.137] has joined #bitcoin-core-pr-reviews 06:33 -!- shesek [~shesek@164.90.217.137] has quit [Changing host] 06:33 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-pr-reviews 06:33 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 06:36 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 06:38 -!- jonatack [~jon@109.232.227.138] has joined #bitcoin-core-pr-reviews 06:41 < jonatack> once merged, it's much easier to continue testing it every day and some issues become more clear/more quickly 06:43 < jonatack> (a nice upside as long as the issues aren't critical) 06:45 < emzy> Is it activated on testnet or signet? 06:45 -!- glozow [uid453516@gateway/web/irccloud.com/x-gxlwpojdyoxusxnv] has joined #bitcoin-core-pr-reviews 06:54 < jonatack> emzy: i was offline and missed some of the discussion, but with "once merged..." i meant in general 06:59 < michaelfolkson> emzy: Testnet no. I'm not sure on latest status of Taproot on Signet 06:59 < kallewoof> emzy: if it was activated on signet, and we realized it was broken, we would brush the activation under the carpet and re-activate a fixed version. that's the power of a centralized test net. 07:00 < jonatack> kallewoof: starting the 11413 follow-ups tomorrow. will ping 07:01 < emzy> Right, so kallewoof just activate it :) 07:01 < pinheadmz> emzy well i think part of the test is testing the activation 07:02 < pinheadmz> so i think we need to wait until activation logic is decided, maybe even merged (?) but with earlier activation params for test/signet 07:02 < kallewoof> yeah, i was initially thinking of activating it in a couple of days, but maybe we do want to test the activation part as well 07:02 < emzy> pinheadmz: But maybe more fitting for that is the testnet. 07:02 < pinheadmz> kallewoof youd have to activate it on a fork? 07:02 < emzy> just do both :) 07:02 < pinheadmz> bypass the inevitable bikeshedding over bip8 params 07:03 < pinheadmz> (fork, code fork not blockchain fork) 07:03 < kallewoof> anyone can take bitcoin master, modify like 3 lines of code, and start up a taproot enabled signet today. 07:03 < pinheadmz> add a deployment 07:03 < michaelfolkson> How much of a pain is it to reset Signet? You mean start from genesis again by reset kallewoof? 07:03 < kallewoof> and what's interesting is that, with the current code base, everyone would happily relay taproot transactions 07:04 < pinheadmz> yeah bc we dont discourage witness versions any more 07:04 < pinheadmz> i sent btc to a v1 address a few months ago 07:04 < pinheadmz> michaelfolkson the cool thing is you can have as many signets as you want! 07:04 < pinheadmz> dont even have to reset "the" signet 07:04 < kallewoof> michaelfolkson: depends. if we end up changing taproot in a non-compatible way, we can pretend signet activated later than it did and avoid the pesky non-compatible spends of the past. 07:05 < michaelfolkson> pinheadmz: Right. But we want a "default" one too :) Any of my questions are related to default Signet 07:05 < kallewoof> so we activate taproot on block #10000. we then find horrible soul eating bugs. we then "adjust" the activation to start at block #20000, and tada, all those pesky little weirdos are just OP_TRUEs. 07:05 < kallewoof> i think it's OP_SUCCESS nowadays, actually 07:08 < michaelfolkson> This confused me for ages. On mainnet this happens https://bitcoin.stackexchange.com/questions/99429/what-is-stopping-a-taproot-spend-following-old-taproot-rules-initially-treated 07:09 < michaelfolkson> On default Signet we have this option: https://bitcoin.stackexchange.com/questions/98642/can-we-experiment-on-signet-with-multiple-proposed-soft-forks-whilst-maintaining 07:11 < michaelfolkson> But presumably this OP_SUCCESS option is to have multiple activation dates so Taproot spends with soul eating bugs can be treated as OP_TRUE if they were between Activation date 1 and Activation date 2 07:12 < michaelfolkson> Confused me for aaaages haha 07:16 < michaelfolkson> And at this early stage in default Signet history we could just throw it all away and start from genesis again if things got really messy 07:16 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 07:16 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-pr-reviews 07:24 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has joined #bitcoin-core-pr-reviews 07:31 < kallewoof> yeah, i've done that too many times already tho, so i'm hopeful we can avoid that :P 08:05 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has joined #bitcoin-core-pr-reviews 08:06 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 08:06 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has quit [Remote host closed the connection] 08:07 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has joined #bitcoin-core-pr-reviews 08:12 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 258 seconds] 08:44 -!- kristapsk___ is now known as kristapsk 08:55 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 09:13 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has joined #bitcoin-core-pr-reviews 09:15 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 260 seconds] 09:17 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 09:21 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews 09:50 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 11:05 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 11:06 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-pr-reviews 12:04 < robot-dreams> Following up on the tapscript / sighash discussion from yesterday, I'm trying to understand the sighash performance improvements from both segwit and tapscript. Is this an accurate summary? 12:05 < robot-dreams> legacy: for each txin, we need to hash (a modified version of) the entire transaction 12:05 < robot-dreams> segwit V0: for each txin, we don't need to hash the entire transaction, but we do need to hash the entire scriptCode (i.e. witness script) 12:05 < robot-dreams> tapscript: for each txin, we don't need to hash the entire scriptCode because we use a tapleaf hash instead; now there's just a constant amount of hashing 12:05 < sipa> seems right 12:07 < robot-dreams> Woo, thanks! And congrats on the merge :) 12:18 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer] 12:19 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-pr-reviews 12:31 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 260 seconds] 12:36 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 13:12 -!- Sound [a0272ec7@dyn-160-39-46-199.dyn.columbia.edu] has joined #bitcoin-core-pr-reviews 13:45 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 13:58 -!- Sound [a0272ec7@dyn-160-39-46-199.dyn.columbia.edu] has quit [Remote host closed the connection] 14:00 -!- wilcl_ark is now known as willcl_ark 14:40 -!- rabidus [~rabidus@85.76.51.88] has joined #bitcoin-core-pr-reviews 15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 15:40 -!- musdom [~Thunderbi@202.184.183.249] has quit [Ping timeout: 265 seconds] 16:40 -!- fjahr_ is now known as fjahr 17:11 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has joined #bitcoin-core-pr-reviews 17:15 -!- instagibbs [~instagibb@pool-100-15-139-5.washdc.fios.verizon.net] has quit [Ping timeout: 272 seconds] 17:39 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 17:39 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 17:52 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 17:52 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 17:58 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 18:00 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 240 seconds] 18:07 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-pr-reviews 18:24 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 240 seconds] 18:24 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-pr-reviews 18:30 -!- glozow [uid453516@gateway/web/irccloud.com/x-gxlwpojdyoxusxnv] has quit [Quit: Connection closed for inactivity] 18:31 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has quit [Ping timeout: 258 seconds] 18:33 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has joined #bitcoin-core-pr-reviews 18:49 -!- seven__ [~seven@cpe-90-157-197-248.static.amis.net] has joined #bitcoin-core-pr-reviews 18:52 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has quit [Ping timeout: 258 seconds] 19:47 -!- seven__ [~seven@cpe-90-157-197-248.static.amis.net] has quit [Read error: Connection reset by peer] 20:39 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has joined #bitcoin-core-pr-reviews 21:25 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 260 seconds] 21:29 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 21:31 -!- musdom [~Thunderbi@202.184.183.249] has joined #bitcoin-core-pr-reviews 21:39 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has joined #bitcoin-core-pr-reviews 21:41 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has quit [Client Quit] 21:52 -!- jesseposner [~jesse@98.37.146.62] has joined #bitcoin-core-pr-reviews 22:14 -!- da39a3ee5e6b4b0d [~textual@n11211935170.netvigator.com] has joined #bitcoin-core-pr-reviews 22:53 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 22:53 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews 23:38 -!- musdom [~Thunderbi@202.184.183.249] has quit [Ping timeout: 240 seconds] 23:45 -!- jesseposner [~jesse@98.37.146.62] has quit [Ping timeout: 265 seconds] 23:56 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 23:56 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-pr-reviews 23:59 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 23:59 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-pr-reviews