--- Log opened Tue Aug 25 00:00:59 2020
00:03 -!- marcoagner [~user@bl11-17-219.dsl.telepac.pt] has joined #bitcoin-core-dev
00:08 -!- jonatack [~jon@37.166.120.102] has quit [Ping timeout: 240 seconds]
00:23 -!- jonatack [~jon@37.166.201.6] has joined #bitcoin-core-dev
00:23 -!- jonatack [~jon@37.166.201.6] has quit [Client Quit]
00:23 -!- jonatack [~jon@37.166.120.102] has joined #bitcoin-core-dev
00:28 -!- jonatack [~jon@37.166.120.102] has quit [Ping timeout: 256 seconds]
00:32 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-dev
00:34 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:59c6:e98a:11fc:9abe] has quit [Remote host closed the connection]
00:35 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:59c6:e98a:11fc:9abe] has joined #bitcoin-core-dev
00:39 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:59c6:e98a:11fc:9abe] has quit [Ping timeout: 244 seconds]
00:40 < sipa> my calendar claims there is a p2p meeting in 20 minutez
00:40 < sipa> i assume i just entered that incorrectly
00:40 < fanquake> your calendar is probably  wrong
00:40 < fanquake> as the meetings are never at a convenient time for me 
00:40 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!]
00:40 < hebasto> isn't p2p meeting at 15 utc?
00:40 < fanquake> I have the meeting happening in 7hr20m
00:40 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:883b:e4e7:631f:cc18] has joined #bitcoin-core-dev
00:41 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-dev
00:42 < aj> fanquake: when sipa says there's a p2p meeting in 20 minutes, you say "yes sir!" !
00:42 < hebasto> :D
00:43 < fanquake> aj: heh. I guess he has already committed 
00:44 < sipa> if i want to be awake for the *other* p2p meeting in 7h17h, maybe i should skip this one
00:52 < aj> dangit
00:54 < aj> fanquake: we'll never trick ppl into holding meetings at convenient times at this rate
00:55 < kallewoof> haha
01:01 < fanquake> aj: sorry. I forgot about that master plan
01:07 -!- cato_ [~cato@gateway/tor-sasl/alec] has quit [Ping timeout: 240 seconds]
01:09 -!- cato_ [~cato@gateway/tor-sasl/alec] has joined #bitcoin-core-dev
01:09 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
01:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
01:14 < aj> oops, apparently it was sydney socratic in 80 minutes, not p2p in 20 minutes
01:15 < fanquake> aj: hah. Thanks for the reminder. I normally forget to listen in
01:17 -!- bosch [74cee564@116.206.229.100] has quit [Quit: Ping timeout (120 seconds)]
01:22 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
01:26 < jnewbery> fanquake: if you're still around, #19601 seems RFM. ACKs from me, fjahr, jonatack and instagibbs
01:26 < gribble> https://github.com/bitcoin/bitcoin/issues/19601 | Refactoring CHashWriter & Get{Prevouts,Sequence,Outputs}Hash to SHA256 (Alternative to #18071) by JeremyRubin · Pull Request #19601 · bitcoin/bitcoin · GitHub
01:28 < jeremyrubin> jnewbery: I'd maybe like to see ACK from sipa maybe? But I agree he has had chance to NACK it so probably RFM.
01:30 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:883b:e4e7:631f:cc18] has quit [Remote host closed the connection]
01:31 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:883b:e4e7:631f:cc18] has joined #bitcoin-core-dev
01:31 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
01:31 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:2987:8fdb:3142:872a] has joined #bitcoin-core-dev
01:34 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:2987:8fdb:3142:872a] has quit [Remote host closed the connection]
01:34 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:2987:8fdb:3142:872a] has joined #bitcoin-core-dev
01:35 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:883b:e4e7:631f:cc18] has quit [Ping timeout: 244 seconds]
01:38 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:2987:8fdb:3142:872a] has quit [Ping timeout: 240 seconds]
01:40 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
01:40 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
01:43 < jnewbery> jeremyrubin: sipa already has those commits in a branch he's PR'ed. Seems like an implicit ACK to me. Also: https://github.com/bitcoin/bitcoin/pull/19601#issuecomment-668785825
01:43 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
01:43 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer]
01:56 < fanquake> jnewbery: it’s on my list. Got stuck with sed
01:58 < jnewbery> thanks!
02:00 -!- Mister_X1 [~Mister_X@84.39.117.57] has quit []
02:02 -!- kexkey [~kexkey@89.36.78.166] has quit [Read error: Connection reset by peer]
02:05 -!- vincenzopalazzo [~vincent@host-82-55-18-31.retail.telecomitalia.it] has joined #bitcoin-core-dev
02:15 -!- palazzovincenzo [~vincent@host-79-26-113-47.retail.telecomitalia.it] has joined #bitcoin-core-dev
02:16 -!- vincenzopalazzo [~vincent@host-82-55-18-31.retail.telecomitalia.it] has quit [Ping timeout: 260 seconds]
02:18 -!- palazzovincenzo [~vincent@host-79-26-113-47.retail.telecomitalia.it] has quit [Client Quit]
02:19 -!- palazzovincenzo [~vincent@host-79-26-113-47.retail.telecomitalia.it] has joined #bitcoin-core-dev
02:21 -!- fnichol [~fnichol@84.39.117.57] has joined #bitcoin-core-dev
02:22 -!- palazzovincenzo [~vincent@host-79-26-113-47.retail.telecomitalia.it] has quit [Client Quit]
02:22 -!- vincenzopalazzo [~vincent@host-79-26-113-47.retail.telecomitalia.it] has joined #bitcoin-core-dev
02:25 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 246 seconds]
02:25 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
02:25 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Client Quit]
02:26 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
02:32 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:28d5:898e:cad9:43d9] has joined #bitcoin-core-dev
02:35 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:28d5:898e:cad9:43d9] has quit [Remote host closed the connection]
02:36 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:28d5:898e:cad9:43d9] has joined #bitcoin-core-dev
02:37 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
02:40 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:28d5:898e:cad9:43d9] has quit [Ping timeout: 244 seconds]
02:55 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
03:00 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
03:00 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
03:01 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
03:02 -!- fuzzing [43f725ba@cpe-67-247-37-186.nyc.res.rr.com] has quit [Quit: Ping timeout (120 seconds)]
03:06 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev
03:06 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Ping timeout: 244 seconds]
03:08 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
03:12 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
03:13 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
03:14 -!- eragmus [sid136308@gateway/web/irccloud.com/x-yijifmnndowczwot] has quit [Read error: Connection reset by peer]
03:15 -!- valwal_ [sid334773@gateway/web/irccloud.com/x-wpdtkxyyinilwsfr] has quit [Read error: Connection reset by peer]
03:15 -!- eragmus [sid136308@gateway/web/irccloud.com/x-eokjnnjhxwfwokrz] has joined #bitcoin-core-dev
03:15 -!- valwal_ [sid334773@gateway/web/irccloud.com/x-wezdtzfnojtzpvay] has joined #bitcoin-core-dev
03:16 -!- bosma [sid103570@gateway/web/irccloud.com/x-ekbzervdxnvunvsy] has quit [Ping timeout: 260 seconds]
03:16 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-zcrgwbzzktutshgw] has quit [Ping timeout: 260 seconds]
03:17 -!- bosma [sid103570@gateway/web/irccloud.com/x-hicmnupxclcgisdf] has joined #bitcoin-core-dev
03:17 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-zagxgkeksxnjlhza] has joined #bitcoin-core-dev
03:17 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
03:17 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
03:18 -!- Cary39Cormier [~Cary39Cor@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-dev
03:21 -!- arowser [~arowser1@67.230.166.11] has quit [Remote host closed the connection]
03:24 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
03:28 -!- cato__ [~cato@gateway/tor-sasl/alec] has joined #bitcoin-core-dev
03:30 -!- cato_ [~cato@gateway/tor-sasl/alec] has quit [Ping timeout: 240 seconds]
03:31 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
03:32 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
03:33 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
03:33 -!- andreacab [~andreacab@12.46.194.178.dynamic.wline.res.cust.swisscom.ch] has joined #bitcoin-core-dev
03:33 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
03:38 -!- andreacab [~andreacab@12.46.194.178.dynamic.wline.res.cust.swisscom.ch] has quit [Ping timeout: 258 seconds]
03:39 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-dev
03:40 -!- Cary39Cormier [~Cary39Cor@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 264 seconds]
03:43 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Quit: Pavlenex]
03:50 -!- jakesyl [sid56879@gateway/web/irccloud.com/x-kfkojwklepiwbotn] has quit [Ping timeout: 272 seconds]
03:50 -!- felixweis [sid154231@gateway/web/irccloud.com/x-tjakxxqoraoowpeh] has quit [Ping timeout: 244 seconds]
03:50 -!- wallet42_ [sid154231@gateway/web/irccloud.com/x-bvcnlkqxwieqjhxb] has quit [Ping timeout: 260 seconds]
03:50 -!- elichai2 [sid212594@gateway/web/irccloud.com/x-tvwaejwbstchkagt] has quit [Ping timeout: 260 seconds]
03:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
03:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:58 -!- vasild_ is now known as vasild
04:00 -!- felixweis [sid154231@gateway/web/irccloud.com/x-jlmbxhhtbxlzhkla] has joined #bitcoin-core-dev
04:00 -!- wallet42_ [sid154231@gateway/web/irccloud.com/x-rowyyzgiybpygdar] has joined #bitcoin-core-dev
04:00 -!- elichai2 [sid212594@gateway/web/irccloud.com/x-ktcafifpocehctxo] has joined #bitcoin-core-dev
04:01 -!- jakesyl [sid56879@gateway/web/irccloud.com/x-wcxpoytoutibnrpn] has joined #bitcoin-core-dev
04:12 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
04:13 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
04:13 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-dev
04:17 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Ping timeout: 272 seconds]
04:29 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
04:32 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
04:33 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
04:37 -!- Ga1aCt1Cz00__ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:2143:af3d:c6b2:a825] has joined #bitcoin-core-dev
04:37 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
04:37 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Ping timeout: 260 seconds]
04:40 -!- Ga1aCt1Cz00_ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:f14c:f5db:4d17:8747] has quit [Ping timeout: 272 seconds]
04:41 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 240 seconds]
05:00 -!- fnichol [~fnichol@84.39.117.57] has quit []
05:05 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
05:06 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
05:11 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Ping timeout: 260 seconds]
05:11 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Quit: Pavlenex]
05:19 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:19 < bitcoin-git> [bitcoin] fanquake pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/8e0f341779e1...f8462a6d2794
05:19 < bitcoin-git> bitcoin/master b475d7d Jeremy Rubin: Add single sha256 call to CHashWriter
05:19 < bitcoin-git> bitcoin/master 6510d0f Jeremy Rubin: Add SHA256Uint256 helper functions
05:19 < bitcoin-git> bitcoin/master 9ab4caf Jeremy Rubin: Refactor Get{Prevout,Sequence,Outputs}Hash to Get{Prevouts,Sequences,Outpu...
05:19 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:19 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:19 < bitcoin-git> [bitcoin] fanquake merged pull request #19601: Refactoring CHashWriter & Get{Prevouts,Sequence,Outputs}Hash to SHA256 (Alternative to #18071)  (master...refactoring-hashers-2) https://github.com/bitcoin/bitcoin/pull/19601
05:19 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:22 -!- ram1 [~ram@185.163.110.125] has joined #bitcoin-core-dev
05:25 -!- ram1 [~ram@185.163.110.125] has quit [Remote host closed the connection]
05:26 < jnewbery> thanks fanquake!
05:28 < fanquake> if only that meant the work day was over
05:28 < fanquake> odds on me not staying up for the entirety of your p2p meeting 
05:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
05:31 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
05:32 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-dev
05:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:33 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #19800: test: Mockwallet (master...2008-testMiniWallet) https://github.com/bitcoin/bitcoin/pull/19800
05:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:42 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
05:44 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
05:47 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Ping timeout: 244 seconds]
05:48 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
05:49 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
05:49 -!- troygiorshev [~troygiors@d67-193-140-136.home3.cgocable.net] has joined #bitcoin-core-dev
05:54 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
05:56 -!- fancyremarker [~fancyrema@217.146.82.202] has joined #bitcoin-core-dev
05:59 < fanquake> wumpus / sipa: can you block StanislavKlimov95 
05:59 < fanquake> spamming addresses and nonsense
06:05 < wumpus>  fanquake done
06:06 < fanquake> wumpus: thanks
06:07 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
06:07 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
06:09 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
06:09 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
06:09 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-core-dev
06:10 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
06:10 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
06:12 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
06:12 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
06:12 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
06:13 -!- tralfaz is now known as Davterra
06:16 -!- kexkey [~kexkey@89.36.78.166] has joined #bitcoin-core-dev
06:21 -!- gzhao408 [uid453516@gateway/web/irccloud.com/x-eujonyheguhhaxjc] has joined #bitcoin-core-dev
06:22 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has joined #bitcoin-core-dev
06:22 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has quit [Ping timeout: 244 seconds]
06:22 -!- sipsorcery [~sipsorcer@37.228.243.134] has joined #bitcoin-core-dev
06:23 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b91a:d4bb:3e97:a076] has quit [Remote host closed the connection]
06:27 -!- Ga1aCt1Cz00_ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:2143:af3d:c6b2:a825] has joined #bitcoin-core-dev
06:30 -!- fancyremarker [~fancyrema@217.146.82.202] has quit [Remote host closed the connection]
06:30 -!- Ga1aCt1Cz00__ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:2143:af3d:c6b2:a825] has quit [Ping timeout: 260 seconds]
06:39 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
06:39 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
06:52 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:52 < bitcoin-git> [bitcoin] theStack opened pull request #19801: test: check for all possible OP_CLTV fail reasons in feature_cltv.py (BIP 65) (master...20200825-test-check-all-failure-reasons-for-CLTV) https://github.com/bitcoin/bitcoin/pull/19801
06:52 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:02 -!- disconnected [~disconnec@89.47.234.28] has joined #bitcoin-core-dev
07:06 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
07:07 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
07:14 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
07:14 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
07:23 -!- lightlike [~lightlike@88.116.7.34] has joined #bitcoin-core-dev
07:29 -!- lightlike_ [~lightlike@178.188.69.1] has joined #bitcoin-core-dev
07:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 265 seconds]
07:30 -!- lightlike_ [~lightlike@178.188.69.1] has quit [Client Quit]
07:32 -!- lightlike [~lightlike@88.116.7.34] has quit [Ping timeout: 256 seconds]
07:38 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
07:38 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
07:44 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
07:45 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
07:46 -!- proofofkeags [~proofofke@2601:280:c280:e500:5d75:51f7:3104:d0db] has joined #bitcoin-core-dev
07:46 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
07:53 < jnewbery> hi folks. We'll get started with the p2p meeting in a few minutes. We'll start like last week with a chance for people to share what they're working on and their priorities are, so if you're planning on attending perhaps have a think about whether there's anything you want to share.
07:56 -!- lightlike [~lightlike@178.188.69.1] has joined #bitcoin-core-dev
07:57 < sdaftuar> maybe don't need to do a roll call on everyone to share, just let people jump in on anything that has changed since last time?
08:00 -!- disconnected [~disconnec@89.47.234.28] has quit []
08:00 < jnewbery> #startmeeting
08:00 < lightningbot> Meeting started Tue Aug 25 15:00:13 2020 UTC.  The chair is jnewbery. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:00 < jonatack> hi
08:00 < hebasto> hi
08:00 < sdaftuar> hi
08:00 < troygiorshev> hi
08:00 < amiti> hi
08:00 < ajonas> hi
08:00 < fanquake> hi
08:00 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
08:00 < gzhao408> hi
08:01 < jnewbery> #bitcoin-core-dev P2P Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator aj Chris_Stewart_5 dongcarl gwillen jamesob ken281221 ryanofsky gleb moneyball kvaciral ariard digi_james 
08:01 < MarcoFalke> hi
08:01 < jnewbery> amiti fjahr jeremyrubin lightlike emilengler jonatack hebasto jb55 elichai2
08:01 < jnewbery> hi folks. Welcome to p2p meeting 2!
08:01 < sipa> hi
08:01 < jnewbery> #topic priority/focus
08:01 < jnewbery> Does anyone have any updates that they want to share since last week?
08:02 < jonatack> y
08:02 < jnewbery> feel free to jump in
08:02 < jnewbery> s/last week/last meeting/
08:02 < jonatack> My prios were BIP155, BIP324, and BIP325 implementation PRs, and they seem to be moving forward.
08:02 < hebasto> just after jon :)
08:02 < ariard> hi
08:02 < jonatack> BIP155 addrv2: #19628 has been receiving review from sipa, elichai, ryanofsky, kallewoof, sipsorceryand myself, and now has 4 ACKs; vasild is deferring further (minor) changes to the PR in order to preserve existing review, but there's no reason to not review it
08:02 < gribble> https://github.com/bitcoin/bitcoin/issues/19628 | net: change CNetAddr::ip to have flexible size by vasild · Pull Request #19628 · bitcoin/bitcoin · GitHub
08:02 < jonatack> it seems to be close
08:02 < jonatack> BIP325 signet: #18267 has been through a few more rounds of review and seems to be getting close, with recent review by fjahr, pinheadz, MarcoFalke, instagibbs, and myself
08:03 < gribble> https://github.com/bitcoin/bitcoin/issues/18267 | BIP-325: Signet [consensus] by kallewoof · Pull Request #18267 · bitcoin/bitcoin · GitHub
08:03 < jonatack> (sorry if that isn't p2p)
08:03 < aj> hi
08:03 < jonatack> BIP324 v2 p2p encrypted message transport protocol: right after the last p2p meeting, jonasschnelli rebased and updated #18242 (changes only used in tests for now) and I've begun re-reviewing it along with the BIP, which has some open questions.
08:03 < gribble> https://github.com/bitcoin/bitcoin/issues/18242 | Add BIP324 encrypted p2p transport de-/serializer (only used in tests) by jonasschnelli · Pull Request #18242 · bitcoin/bitcoin · GitHub
08:03 < jonatack> The BIP had received no new feedback since mid-June and the latest review by ariard, elichai, and realorrandom, but Lloyd Fournier just wrote a detailed comment yesterday, which I plan to go through asap: https://gist.github.com/jonasschnelli/c530ea8421b8d0e80c51486325587c52#gistcomment-3428675
08:03 < sipa> unfortunately no; i haven't gotten to rebasing/updating the tx overhaul, by being distracted on taproot and a few generic secp256k1 issues; i did reviews for 19628 though; happy to see that moving along
08:03 < jonatack> I encourage people to review BIP 324 and the PR 18242.
08:04 < nehan> hi
08:04 < jonatack> 19731 was merged yesterday, which allows some interesting possibilities for eviction tests and I have added those columns into my dev branch of cli -netinfo
08:04 < jonatack> 19643 achieved a pretty massive rough consensus with ~9/10 Concept/Approach ACKs and 6 full tested ACKs by wumpus, 0xB10C, fjahr, vasild, practicalswift and pinheadz.
08:04 < jonatack> It's an extremely useful tool for anyone rrrrunning a node, particularly developerrrs and p2p reviewerrrs, and is completely encapsulated in a single class in bitcoin-cli.cpp that is both easy to maintain and easy to rrrip out in 2 minutes if no longer wanted
08:04 < jonatack> finnaly
08:04 < sipa> jonatack: yeah, i need to respond to llfourn's comments
08:04 < jonatack> 19610 is a net processing pure refactoring and simplification with jnewbery, that splits AlreadyHave() up into AlreadyHaveTx() and AlreadyHaveBlock() since they are now two totally separate concepts; the block and transaction paths have drifted apart sufficiently that it no longer makes sense to have a common function there. The PR also simplifies CInv::type and INV/TX processing code.
08:04 < jonatack> Thanks to fjahr, jnewbery, and vasild who have reviewed it so far! Review welcome.
08:05 < jonatack> that's it for me :p
08:05 < vasild> hi
08:05 < ajonas> I've been trying to keep track of the #18044 clean-ups.
08:05 < gribble> https://github.com/bitcoin/bitcoin/issues/18044 | Use wtxid for transaction relay by sdaftuar · Pull Request #18044 · bitcoin/bitcoin · GitHub
08:05 < ajonas> I've checked in with jnewbery and amiti on them. sipa has some he's said he's going to do. instagibbs has already pushed a test. jeremy has a few that he's been discussing with amiti as well.
08:06 < ajonas> and then there are the backports
08:07 < hebasto> my prios are #17785 and #17428
08:07 < gribble> https://github.com/bitcoin/bitcoin/issues/17785 | p2p: Unify Send and Receive protocol versions by hebasto · Pull Request #17785 · bitcoin/bitcoin · GitHub
08:07 < gribble> https://github.com/bitcoin/bitcoin/issues/17428 | p2p: Try to preserve outbound block-relay-only connections during restart by hebasto · Pull Request #17428 · bitcoin/bitcoin · GitHub
08:07 < fanquake> I don't think there's any rush to do the backports until any followup discussion changes/have been finalized. Might as well backport all that's needed at once.
08:07 < sipa> ajonas: i think my followup is dome already (#19569)
08:07 < gribble> https://github.com/bitcoin/bitcoin/issues/19569 | Enable fetching of orphan parents from wtxid peers by sipa · Pull Request #19569 · bitcoin/bitcoin · GitHub
08:07 < ariard> sipa: what was llfourn main proposal of change for bip324? He didn't propose to MAC the length field, so no BIP change
08:07 < ajonas> sipa: I'll take a look. Thanks.
08:07 < MarcoFalke> The one to 0.19 should be ready, right? No other p2p backports are planned for that release and we might as well ship 0.19 after that backport
08:07 < ariard> and the DoS concern are more theoritical, given you have easier alternatives
08:08 < sipa> ariard: no changes, just commentary, iirc - but i need to go through it in more detail
08:08 < sdaftuar> i've been thinking about small topology improvements, specifically picking up the main idea of #16859
08:08 < gribble> https://github.com/bitcoin/bitcoin/issues/16859 | Syncing headers with feeler-peers · Issue #16859 · bitcoin/bitcoin · GitHub
08:09 < sdaftuar> well, that's only sort of a topology improvement, depending on implementation, actually
08:09 < sdaftuar> the main idea is to sync headers with more peers, and potentially replace peers with new ones as well
08:09 < sdaftuar> hopefully PR to come soon-ish
08:10 < sipa> are we eventually just going to split up all functionality, and have header-peers, block-peers, tx-peers, addr-peers? :)
08:10 < ariard> we might learn headers from feelers, but are we going to actively maintain connections to them if we learn about a potential better chain?
08:10 < aj> sipa: separating addr-peers sounds weird, but all the rest of it...
08:11 < sdaftuar> i don't know! :)  i have two implementations of that idea that i'm playing with, one where i introduce a new peer type (headers-sync-peer) which gets quickly dropped
08:11 < ariard> like upgrading them to block-peers and evvicting one in consequence if max outboounds reach
08:11 < sdaftuar> and the other where i treat it as an extra block-relay-only peer that can evict another block-relay peer
08:11 < aj> sipa: that segues to what i've been working on which is supporting "regular" peers and "taproot-enabled" (and "anyprevout-enabled") peers for signet, indicated via service flags...
08:12 < ariard> right, for the headers-sync-peer variant, you can store headers with addrs, and if we stale tip randomly pick up a better-chain-known-addr, open a connection with them
08:12 < ariard> though likely more compelx of implementation
08:13 < sipa> aj: just so that txn would propagate well?
08:13 < amiti> sdaftuar: you had mentioned thinking about a way to distinguish incoming block-relay-only connections. I’m guessing this has something to do with the feature negotiation topic on the mailing list? what are your current thoughts? 
08:13 < ariard> maybe not store headers, just mark them as known-as-useful-peers
08:13 < aj> sipa: s/well/at all/, yeah
08:14 < sdaftuar> oh right, now that i have clarity on how to propose new feature negotiation, yeah i'm thinking about a simple way to negotiate block-relay only connections at peer connection time, so that both sides of a connection know they can devote less resources to each other 
08:14 < sdaftuar> which is mostly a per-peer memory savings
08:14 < sdaftuar> and then hopefully we can increase the number of inbounds (specifically carve out extra inbound slots for block-relay peers)
08:15 < sdaftuar> and then increase the number of block-relay outbound connections we make too
08:15 < sdaftuar> so i'm planning to pick that up as well in the near term
08:15 < jnewbery> > now that i have clarity on how to propose new feature negotiation
08:15 < jnewbery> ^ it wasn't clear to me what the outcome of the mailing list discussion was. What are you proposing?
08:15 < sipa> aj: for segwit, this preferential peering was critical, as blocks wouldn't propagate from old modes to new ones... for the things you're talking about it's just about transactions
08:15 < fanquake> related #19723
08:15 < gribble> https://github.com/bitcoin/bitcoin/issues/19723 | Ignore unknown messages before VERACK by sdaftuar · Pull Request #19723 · bitcoin/bitcoin · GitHub
08:16 < sdaftuar> jnewbery: just accompany new features with a protocol version bump
08:16 < sdaftuar> but otherwise copy what has been done before
08:16 < sdaftuar> seems to me that path is basically unobjectionable
08:17 < sipa> it works okayish
08:17 < jnewbery> forcing protocol changes to be serial seems not as good as being able to opt in to different features
08:17 < sdaftuar> i think we can deal with that when we actually get protocol version number conflicts?
08:17 < sdaftuar> seems like it doesn't happen in practce
08:17 < aj> sipa: yeah, not much fun if your transactions don't propogate though
08:17 < sipa> sdaftuar: fair
08:18 < sdaftuar> and i don't think we can force other implementations to adopt anything generic (like i proposed)
08:18 < sdaftuar> so i think it's easy for now to accommodate those preferences
08:18 < aj> sipa: atm i'm telling it once you've got 50% peers connected, only add more outbounds if it improves your tx connectivity
08:18 < sipa> aj: yeah, and with a better separation between block and tx connections (or block-only and full connections) it may be possible to apply such peering only on the tx-carrying ones
08:19 -!- eugene48 [43f725ba@cpe-67-247-37-186.nyc.res.rr.com] has joined #bitcoin-core-dev
08:19 < sdaftuar> hm, we've not historically used service bits for tx-relay properties right?
08:19 < aj> sipa: yep. blocks-only happens after tx-carrying ones atm; which is maybe backwards?
08:19 < sipa> sdaftuar: indeed
08:19 < sipa> i'm a bit hesitant about that...
08:20 < sdaftuar> we don't have a good framework for thinking about transaction propagation imo
08:20 < ariard> right, and that's something we need for higher layer :)
08:21 < amiti> sdaftuar: care to elaborate? what would a good framework look like? or, what is something we do have a good framework for thinking about? 
08:21 < aj> is there anything that'd make more sense than service flags? i think you want something that's in addrman, in case there's 5000 nodes, and only 5 of them support the feature you want
08:21 < sipa> aj: also, this isn'ta actually specific to softforks, but to policy cjangs
08:21 < sdaftuar> sipa: exactly
08:21 < aj> sipa: yep
08:21 < sdaftuar> but i think there is something to be said for splitting up policy issues into things you can deal with, and things that are hopeless?
08:21 < sipa> so far we haven't assumed we can reasom about peer's tx policies
08:21 < sdaftuar> i don';t know
08:21 < ariard> at least there is a difference between propagation validity and ensuring your tx-propagation paths aren't intersected by malicous/buggy peers
08:22 -!- [n1x]_ [~n1x]_@s91904426.blix.com] has joined #bitcoin-core-dev
08:22 < sipa> arguably, we do already, in the form of feefilter
08:22 < sipa> that is effectively tellings peer part of our relay policy
08:23 < sipa> with automatic tx rebroadcast there may be slightly less need for this
08:23 < sdaftuar> there are so many things that can go wrong with respect to transactions you have not propagating well
08:23 < aj> perhaps it should be an entirely separate addressbook, and you have to look up via a separate seed, rather than flags in the existing address book?
08:24 < sipa> aj: i feel it's a can of worms, trying to do this well
08:24 < ariard> policy has to be hardcoded in higher layers, like minimum transaction size, unless you assume you higher stack to fetch your node to learn peer policies negotiated
08:24 < sdaftuar> automatic tx rebroadcast + tx-relay-peer rotation might be the most robust thing we can do?
08:24 < ariard> at least a subset
08:25 < sipa> plus the philosophical issue that it means assumptions on being to rely on (claimed/standardized) policy
08:25 < aj> sipa: sure. i only really care about doing it adequately at this point :)
08:25 < sipa> so, eh
08:25 < sipa> why hasn't this historically been needed?
08:25 < sdaftuar> :)
08:25 < ariard> sipa: I agree that's a philosophical issue but that was implicetely part of any payment channel design with timelocks
08:25 < aj> sipa: because everyone upgrades before the policy change activates?
08:26 < sipa> aj: right
08:26 < aj> sipa: then no one transacts with the changed policy for a while anyway
08:26 < instagibbs> none of your peers accepting a softfork policy may tell you something too :)
08:26 < ariard> wait for some LN implementation being broken for forgetting some policy check
08:26 < sipa> ariard: i feel that's a mistake, tbh
08:26 < ariard> sipa: ofc but the fact that they are not well-documented contribute to this, like no proper toolchain to test them in separation
08:27 < ariard> and you have the issue of a time-sensitive A propagating wrt to policy set X but not with policy set Y and your full-node being only connected to peers Y
08:27 < ariard> time-sensitive tx A
08:28 < sdaftuar> ariard: that could be addressed by tx-relay-peer rotation, for what it's worth
08:28 < sdaftuar> but if the miners aren't running your policy you're in trouble!
08:28 < ariard> I agree assuming you rotate quick enough with regards to security timelocks
08:28 < sipa> ariard: aren't time sensitive things done on a scale of days/weeks/..., where this should be far less of a problem?
08:29 < ariard> sdafturar: I know, LN security is in fine dependent of power miners policy, i.e the ones likely to mine a block during the timelock
08:29 < ariard> and it's kinda a black box :(
08:29 < aj> sipa: i suppose on mainnet it could be amusing to have a well-known set of nodes that allow rbf-without-pinning (ie, will relay any tx as long as it has the rbf bit set, and pays more than the tx it's replacing, no worries how many it invalidates)
08:30 < sipa> so you can even do things like warning a user their time-sensitive tx isn't confirming
08:30 < ariard> sipa: here the tradeoff, we can always pickup higher timelocks, both for punishement and cltv delta but that come at the price in case of channel failure
08:30 < ariard> you increase the timevalue of locked funds for nothing
08:30 < aj> sipa: everybody else ignores it as spam, but it still gets to miners so avoids lightning txs getting pinned or whatever
08:31 < ariard> sipa: you might be under attack in the middle of the night, I lean to assume the same kind of automatic security model we have wrt to block validation
08:31 < sipa> aj: that seems problematic
08:31 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
08:31 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
08:32 < ariard> increasing timelocks on the long-term increase cost of LN routing fees, and thus utility of the overall system
08:32 < sipa> a node's rational policy should be to try to approximate the network's behavior
08:32 < ariard> because someone has to pay for the average expected failure, even if right now it's not priced at all by routing nodes
08:32 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Quit: Pavlenex]
08:33 < ariard> sipa: I agree on this, like accept the lower bound to improve your feerate view, and also improve your local fee estimation
08:33 < ariard> thus lowering your fees, theoritically
08:33 < jnewbery> sorry, I've lost the thread a bit here. Are we specifically trying to solve a problem for taproot on signet here?
08:34 < ariard> jnewbery: thanks for the nudge, are p2p meeting for more theoritically discussions too :p ?
08:34 < troygiorshev> yeah for those of us looking to organize this, anyone want to summarize and/or give this a title?
08:35 < aj> jnewbery: allocating some service flags on signet seems to solve the problem okay on signet; trying to see if there's a better solution that usefully generalises to something that would be helpful on mainnet?
08:35 -!- Davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection]
08:35 -!- Davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev
08:35 < sipa> i think we got a bit sidetracked... i don't think we're going to solve all problems with tx relay of time-sensitive transactions in a reliable way today..
08:35 < sdaftuar> i think the general question is whether it's worth worrying about differing transaction relay policies on our p2p network, and if so, to what extent
08:35 < sipa> aj: oh, just signet?
08:36 < jnewbery> it's fine to have theoretical discussions, i'm just a little lost as to what exactly we're discussing
08:36 < sipa> aj: can't you just create a new signet with taproot from the start?
08:36 < sipa> as in separate network
08:36 < aj> sipa: just signet, and only for the period while a soft-fork is in development, retired after it activates on mainnet (or becomes obsolete)
08:36 < aj> sipa: we're working on having this work in the default signet; having custom signets is definitely an additional/alternative option
08:37 < sipa> right, makes sense
08:37 < aj> https://github.com/bitcoin/bitcoin/issues/19787 has some discussion, maybe missing some context though
08:37 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
08:38 < jnewbery> aj: do you have any code or a more concrete proposal?
08:38 < aj> jnewbery: still working on a concrete proposal; code is at https://github.com/ajtowns/bitcoin/commits/signet-tr ; obviously subject to change
08:39 < ariard> sdaftuar: I'll open an issue resuming conversation, to scope security worries ones might have with tx-relay discrepancies
08:39 < jnewbery> thanks. Are you asking for review yet?
08:39 < aj> jnewbery: it allocates service flag 32 to indicate the current version of taproot; will bump to 33 when even-R taproot happens i think
08:39 < aj> jnewbery: not really; i'm trying to get it to run on a second node of my own first
08:40 < sipa> aj: so you will do a hardfork in signet?
08:40 < sdaftuar> amiti: i realized i never answered your question before, but i think that we don't even know exactly what our tx-relay goals are, let alone how to measure our progress against those goals, or how to improve things.
08:40 < aj> sipa: the idea is if you run "bitcoind -signet -experimental=taproot" then you'll get a hardfork event, and either have to drop the -experimental=taproot or upgrade to continue following the chain
08:41 < aj> sipa: the upgraded code will have taproot activate at a later mediantime so any prior transactions will just be random garbage that didn't need to be validated
08:42 < aj> sdaftuar: "that people don't complain on twitter and reddit about their txs not confirming" ? :)
08:42  * sipa suggests hardforking in paypal support
08:42 < sdaftuar> aj: haha if that's our only goal we can just get the moderators to filter those complaints out!
08:42 < aj> sdaftuar: censorship for the win
08:42 < ariard> aj: if we were binding to twitter-driven developpement why taproot isn't already activated :) ?
08:43 < sdaftuar> TDD = twitter driven development? TIL
08:43 < instagibbs> ariard, maybe it is *spooky music*
08:43 < jnewbery> Did everyone who wanted to have a chance to share what they're working at the start of the meeting?
08:43 < jnewbery> troygiorshev, amiti, fanquake, gzhao408, MarcoFalke, nehan: did you want to share anything?
08:44 < troygiorshev> i'll jump in briefly
08:44 < troygiorshev> since last time, I hosted a PR review club on #19509 per-peer message logging.  thanks to everyone who came!  some changes have been made and a few more will be in in the next few days.
08:44 < troygiorshev> i also encourage review on 19628 (myself included...)
08:44 < gribble> https://github.com/bitcoin/bitcoin/issues/19509 | Per-Peer Message Logging by troygiorshev · Pull Request #19509 · bitcoin/bitcoin · GitHub
08:44 < troygiorshev> if anyone is looking to dive into a relatively tedious net/net_processing unraveling, #19107 is still looking for review!
08:44 < gribble> https://github.com/bitcoin/bitcoin/issues/19107 | p2p: Move all header verification into the network layer, extend logging by troygiorshev · Pull Request #19107 · bitcoin/bitcoin · GitHub
08:44 < troygiorshev> that's all :)
08:44 < jnewbery> thanks troy!
08:44 < MarcoFalke> jnewbery: thx :). I was mostly working on 100% test coverage for p2p, but then got sidetracked/slowed down. I hope to pick that up soon
08:45 < amiti> marcofalke: 100%! I like this ambition. 
08:45 < jnewbery> MarcoFalke: any PRs you want to shill, or still WIP?
08:45 < MarcoFalke> still WIP (or needing rebase)
08:45 < aj> (btw 50 days / 7 weeks 'til 0.21 feature freeze per 18947)
08:45 < nehan> jnewbery: thanks! i have a tiny PR to fix the lack of lock around vRecvGetData and orphan_work_set which I will open soon. Other than that, noting things here that need review.
08:45 < fanquake> I have nothing to share other than I’m trying to merge p2p PRs in some kind of sane order. Sorry if you have to rebase.
08:46 < jnewbery> MarcoFalke: let me know if there's any interaction/conflict with #19791
08:46 < sdaftuar> topic suggestion: 0.21 p2p goals?
08:46 < gribble> https://github.com/bitcoin/bitcoin/issues/19791 | [net processing] Move Misbehaving() to PeerManager by jnewbery · Pull Request #19791 · bitcoin/bitcoin · GitHub
08:46 < MarcoFalke> jnewbery: Shouldn't be any interaction
08:46 < jnewbery> sdaftuar: good idea. Let's see if there anyone else wants to share priorities/focus then move on to that
08:47 < ariard> wrt 0.21, tx-request overhaul? erlay?
08:47 < amiti> sdaftuar: agreed. I had spent a while trying to distill tx-relay goals, but its definitely tricky. have you seen sipa's description on #19184? it specifies a very clear list of goals 
08:47 < gribble> https://github.com/bitcoin/bitcoin/issues/19184 | Overhaul transaction request logic by sipa · Pull Request #19184 · bitcoin/bitcoin · GitHub
08:47 -!- Ga1aCt1Cz00__ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:2143:af3d:c6b2:a825] has joined #bitcoin-core-dev
08:47 < jnewbery> The thing I'd like to see prioritized in the short term are the backports: #19606 #19680 #19681
08:48 < gribble> https://github.com/bitcoin/bitcoin/issues/19606 | Backport wtxid relay to v0.20 by jnewbery · Pull Request #19606 · bitcoin/bitcoin · GitHub
08:48 < gribble> https://github.com/bitcoin/bitcoin/issues/19680 | 0.20: Add txids with non-standard inputs to reject filter by sdaftuar · Pull Request #19680 · bitcoin/bitcoin · GitHub
08:48 < gribble> https://github.com/bitcoin/bitcoin/issues/19681 | 0.19: Add txids with non-standard inputs to reject filter by sdaftuar · Pull Request #19681 · bitcoin/bitcoin · GitHub
08:48 < sdaftuar> amiti: yes i think sipa's writeup is great for what we want a single node to do, i was referring to what we want overall network behavior to look like -- i think that is a big unknown
08:48 < amiti> ahhh 
08:48 < jnewbery> and I also need to backport #19569 to v0.20 once 19606 is merged
08:48 < gribble> https://github.com/bitcoin/bitcoin/issues/19569 | Enable fetching of orphan parents from wtxid peers by sipa · Pull Request #19569 · bitcoin/bitcoin · GitHub
08:49 < jnewbery> #19680 and #19681 are very easy reviews, even if you didn't review the original PR
08:49 < gribble> https://github.com/bitcoin/bitcoin/issues/19680 | 0.20: Add txids with non-standard inputs to reject filter by sdaftuar · Pull Request #19680 · bitcoin/bitcoin · GitHub
08:49 < gribble> https://github.com/bitcoin/bitcoin/issues/19681 | 0.19: Add txids with non-standard inputs to reject filter by sdaftuar · Pull Request #19681 · bitcoin/bitcoin · GitHub
08:49 < jnewbery> and once 19681 is in, I think we can do a 0.19 release
08:49 < fanquake> jnewbery: is there any particular rush?
08:49 < fanquake> I think there’s still a few more things tagged for 0.19 before we cut a release
08:49 < jnewbery> fanquake: for 0.19 or the other ones?
08:49 < jnewbery> ah, ok
08:49 < fanquake> Either
08:49 < aj> maybe add the non-std input reject to high-pri? i thought there used to be a backports thing on that?
08:50 < jnewbery> aj: I'll add them
08:50 < jnewbery> although most of the people who'd review them are here right now :)
08:50 < jonatack> Is anyone working on overhauling peer misbehavior (e.g. measure resource usage by peers and penalise those peers consuming more of ours?) I think jnewbery is moving it into PeerManager, but besides that?
08:50 -!- Ga1aCt1Cz00_ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:2143:af3d:c6b2:a825] has quit [Ping timeout: 260 seconds]
08:51 < jnewbery> #topic 0.21 p2p goals
08:51 < sdaftuar> so i think #19184 should be a goal for 0.21
08:51 < jnewbery> sdaftuar: want to start? We only have 9 minutes left
08:51 < gribble> https://github.com/bitcoin/bitcoin/issues/19184 | Overhaul transaction request logic by sipa · Pull Request #19184 · bitcoin/bitcoin · GitHub
08:51 < sdaftuar> other than that, i don't feel strongly -- and am curious what other things people would like
08:51 < troygiorshev> jonatack: i've been working on a pr measuring per peer resource usage
08:51 < sdaftuar> i'm guessing erlay is too ambitious
08:52 < jonatack> troygiorshev: great, ty
08:52 < jnewbery> +1 for 19184. I did a quick review, but I'm holding off doing a full review until sipa says it's ready
08:52 < sdaftuar> in particular, if there are some concrete features people want added, with 7 weeks to go we should try to round up review effort
08:52 < sipa> jnewbery: will do actually soon
08:52 < aj> progress on p2p testing a la amiti/marcofalke would be nice?
08:53 < jnewbery> 19184 may be ambitious for 0.21 if it's code freeze in 7 weeks?
08:53 < ariard> especially p2p testing of the eviction logic, if we aim to improve it in the future
08:53 < sipa> wow, 7 weeks already?
08:53 < aj> jnewbery: feature freeze, not code freeze
08:53 < MarcoFalke> aj: no progress from me for now
08:53 < sipa> well, should be doable i think
08:54 < sdaftuar> i haven't been following addrv2 very much
08:54 < jonatack> I think BIP155 addrv2 is a priority, according to vasild the next steps should be smaller and easier 
08:54 < ajonas> this may have been asked elsewhere but is 19184 a requirement for taproot?
08:54 < sdaftuar> is that something that needs to be on a shorter timetable?
08:54 < jnewbery> ajonas: no
08:54 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Quit: Pavlenex]
08:54 < amiti> I'd like to see #17428 make progress. reviewers have agreed on the benefits of at least some of the changes, but momentum slowed down on some of the specifics. if anyone wants to review and weigh in :) 
08:55 < gribble> https://github.com/bitcoin/bitcoin/issues/17428 | p2p: Try to preserve outbound block-relay-only connections during restart by hebasto · Pull Request #17428 · bitcoin/bitcoin · GitHub
08:55 < amiti> ariard: p2p testing of eviction logic would be awesome. 
08:55 < jonatack> Tor v2 deprecation begins Sept 15
08:55 < sdaftuar> what's the addvr2 roadmap look like?  i don't know where we are at all.
08:56 < troygiorshev> #19031
08:56 < gribble> https://github.com/bitcoin/bitcoin/issues/19031 | Implement ADDRv2 support (part of BIP155) by vasild · Pull Request #19031 · bitcoin/bitcoin · GitHub
08:56 < troygiorshev> we're, say, a bit over half way there?
08:56 < sdaftuar> are there remaining design considerations at this point, or is it all just implementation?
08:57 < sipa> sdaftuar: i think it's just implementation work
08:57 < jonatack> amiti: is anyone working of eviction testing atm?
08:57 < sdaftuar> thanks
08:57 < amiti> jonatack: not that I know of 
08:58 < sdaftuar> so should we be aiming to get addrv2 into 0.21, or does that seem aggressive?
08:58 < jonatack> amiti: ty
08:58 < ariard> jonatack: I think we're pending on 19315 ? or make it easier with it ? need to review it to be sure
08:59 < jnewbery> seems doable. I haven't looked closely at the code but I think it's a smaller change than 19184 overhaul tx request logic
08:59 < sipa> sdaftuar: i think with #19628 we're over halfway there
08:59 < gribble> https://github.com/bitcoin/bitcoin/issues/19628 | net: change CNetAddr::ip to have flexible size by vasild · Pull Request #19628 · bitcoin/bitcoin · GitHub
08:59 < troygiorshev> sdaftuar: deprecated sept 15, and gone july 15 2021
08:59 < jonatack> addrv2 in 0.21 would be v worthwhile and agree, 19628 was probably the biggest chunk and it seems RFM 
08:59 < sdaftuar> that sounds to me like we should prioritize it
08:59 < aj> troygiorshev: so desirable for 0.21 essential for 0.22?
08:59 < jnewbery> ok, 1 minute left. Anyone have anything they wanted to share before the end?
08:59 < ariard> amiti: wrt 17428, I concede gleb last point, too much advanced for now, though that would be great to have a clear map of connection types fingerprints
09:00 < sipa> #17428
09:00 < gribble> https://github.com/bitcoin/bitcoin/issues/17428 | p2p: Try to preserve outbound block-relay-only connections during restart by hebasto · Pull Request #17428 · bitcoin/bitcoin · GitHub
09:00 < jnewbery> #endmeeting
09:00 < troygiorshev> aj: I think that's right!
09:00 < lightningbot> Meeting ended Tue Aug 25 16:00:18 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
09:00 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-08-25-15.00.html
09:00 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-08-25-15.00.txt
09:00 < lightningbot> Log:            http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-08-25-15.00.log.html
09:00 < sipa> sdaftuar: yeah, seems it also picked up a lot of momentum by the impending doom
09:00 < sdaftuar> thanks all! that was very helpful
09:01 < troygiorshev> great meeting everyone!
09:01 < jonatack> ariard: i need to review 19315, idk what's in it yet
09:01 < sdaftuar> sipa: ok good, i can take a look and try to help get it reviewed too, i have just totally lost track of the issues
09:04 -!- Mercury_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has quit [Remote host closed the connection]
09:05 < jonatack> ariard: amiti: if you work on eviction testing, happy to collaborate or look at stuff.
09:05 -!- Mercury_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has joined #bitcoin-core-dev
09:07 < aj> sipa, sdaftuar: so sounds like (ab)using some service flags in a signet specific way will be fine for an initial proposal if i can make it work, or at least that you don't have any better ideas yet?
09:07 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:07 -!- eugene48 [43f725ba@cpe-67-247-37-186.nyc.res.rr.com] has quit [Ping timeout: 245 seconds]
09:08 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:08 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
09:08 < sdaftuar> aj: for just signet i don't have a view on what testing makes sense. but i'd be hesitant to do service-flags-for-tx-relay-policy on mainnet
09:08 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:09 < vasild> sdaftuar: I like to think that BIP155 addrv2 is just an implementation at this point (no design decisions to be made). However there are two PRs that are yet to be merged into BIP155: https://github.com/bitcoin/bips/pull/907 and https://github.com/bitcoin/bips/pull/967.
09:09 < sdaftuar> vasild: thank you, i will take a look at those as well!
09:09 < vasild> I am doing the implementation as if they are merged
09:09 < aj> sdaftuar: yes, 100% on not for mainnet (though not sure there's a good reason to do it for mainnet either? we didn't come up with one did we?)
09:09 < vasild> the commits so far that were merged were agnostic to those PRs
09:10 < sdaftuar> aj: ok great. can you explain what the motivation is for doing it on signet?
09:10 < lightlike> jonatack, ariard: are you specifically talking about inbound eviction tests? I don't quite follow how 17428 (although great!) can help with that - doesn't it add new types of outbound connections to the framework?
09:10 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:11 < sdaftuar> aj: i'm just curious what the testing is aiming for
09:11 < aj> sdaftuar: so there are two ideas for "testing taproot on signet" -- one is to run a custom signet for taproot, in which case everything is easy. the other is to have the testing happen on the default signet.
09:12 < aj> sdaftuar: the/my idea is for this testing to be happening at the current stage of the code -- so it should work pretty well, but there's still potential for hard-forking changes, like the even-R change that'll happen soon
09:12 < vasild> sdaftuar: signaling of addrv2 support was decided to be done via new dedicated message (sendaddrv2), rather than service bits or protocol version bump. But you never know...
09:13 < aj> sdaftuar: the advantage of doing it on the default signet is that all the infrastructure should keep working -- the faucet, the explorer, and any wallets/lightning-clients/etc that have added support for signet, so you can see how it acts in the ecosystem, not just in purely lab conditions. so i think that's worth the extra effort
09:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:13 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/f8462a6d2794...8d6224fefe01
09:13 < bitcoin-git> bitcoin/master 1ea57ad Vasil Dimov: net: don't accept non-left-contiguous netmasks
09:13 < bitcoin-git> bitcoin/master 102867c Vasil Dimov: net: change CNetAddr::ip to have flexible size
09:13 < bitcoin-git> bitcoin/master 8d6224f MarcoFalke: Merge #19628: net: change CNetAddr::ip to have flexible size
09:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:13 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #19628: net: change CNetAddr::ip to have flexible size (master...make_CNetAddr_ip_flexible) https://github.com/bitcoin/bitcoin/pull/19628
09:13 < vasild> \o/
09:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:14 < aj> sdaftuar: given all that, then we'll ideally have bunches of non-taproot aware nodes on signet, and some handful of taproot-aware nodes as well -- including some/all of the block signers/miners
09:15 < aj> sdaftuar: the two practical problems are then working out when the soft-fork becomes active, and tx's in blocks can be validated against the rules in a way that copes reasonably cleanly with hardfork changes like even-R; and letting peers connect to each other to relay tx's to the signers (atm, there's < 8 signet nodes, so that's trivial really)
09:16 < aj> sdaftuar: (this isn't really crucial for taproot; but I think having a live net for testing eltoo operability and attacks will be a big win for making sure anyprevout is sane)
09:17 < sdaftuar> aj: yeah so i guess is there a tx-relay testing issue you're trying to solve?
09:17 < sdaftuar> i mean, why not just connect to the signers?
09:17 -!- proofofkeags [~proofofke@2601:280:c280:e500:5d75:51f7:3104:d0db] has quit [Remote host closed the connection]
09:17 -!- rojiro [~rojiro@gateway/tor-sasl/rojiro] has quit [Quit: leaving]
09:18 < aj> sdaftuar: (the activation approach i think will work is hardcoding an activation mediantime in the Signet chainparams, requiring the user to say --experimental=$forkname, and having activation happen on a retarget boundary once the mediantime has passed the constant. everyone then just has to upgrade to the new code prior the given mediantime, and everything works; and you don't need to worry about 
09:18 < aj> different custom signets activating soft-forks at different heights. once something goes live on mainnet, set the mediantime to the time it went live on mainnet, and remove the --experimental= requirement)
09:18 < sdaftuar> it just seems to me like for modeling the network behavior as a whole, we don't have a clear goal for what the topology should look like on mainnet after activation (to my knowledge -- maybe someone can think abotu that and come up with a goal)
09:19 < aj> sdaftuar: if there's more than 100 taproot nodes, you can't have everyone connect to the signers?
09:19 < sdaftuar> aj: it's possible i really have no idea what the goals of signet are. :) so apologies if my suggestions are unhelpful.
09:20 < sdaftuar> but i guess it just seems like modeling the p2p behavior of mainnet isn't something that is necessarily being aimed for?
09:20 < aj> sdaftuar: i think the goals aren't really clear to anyone yet? :)
09:20 < sdaftuar> then i feel less bad!
09:20 < sdaftuar> :)
09:20 < aj> sdaftuar: certainly the real answer to why not just connect directly to the signers is "i didn't think of it"
09:21 < sdaftuar> i was just thinking abotu the issues we had with segwit on testnet a few years ago
09:21 < aj> sdaftuar: story time?
09:21 < sdaftuar> and there were plenty of p2p connectivity issues that would happen on testnet
09:21  * aj has no recollection of testnet/segwit things
09:21 < sdaftuar> well the main issue is that if you were running a testnet node, you might not be connected to anyone with NODE_WITNESS or whatever
09:22 < sdaftuar> and so someone might relay a block, but the witness would get stripped, and a bunch of nodes would receive it without witness.
09:22 < sdaftuar> old nodes would think it was valid anyway, and old-miners would build a chain on it
09:22 < sdaftuar> new nodes would not
09:22 < sdaftuar> and so there would be these big chain splits periodically
09:22 < aj> was that with the preferential-connect-to-NODE_WITNESS or before that?
09:22 < sdaftuar> anyway long story short, it was a sort of disaster, so i can see why having a situation not be as bad as that, is a good thing
09:23 < sdaftuar> aj: the preferential peering went through a couple iterations, but probably it was done after, yet there were so few NODE_WITNESS nodes at the time of testnet activation that we still ran into problems
09:24 < aj> right, makes sense
09:24 < sdaftuar> maybe it was just because segwit was such a big change, i was focused on chain splits more than tx propagaton back then
09:25 < sdaftuar> and at any rate solving the chain split issue (maintaining a bridge between the old and new networks) also resolved the segwit tx relay concerns, if they had been raised
09:25 -!- proofofkeags [~proofofke@2601:280:c280:e500:9493:1db:50da:7239] has joined #bitcoin-core-dev
09:25 < sdaftuar> (at one point, i coded up a node to guess the coinbase witness (which is usually just a zero, the witness nonce) and resolved a giant fork that way)
09:27 < sdaftuar> anyway - if you want to preferentially peer with taproot nodes on signet so that you know your transactions are making it to the miners, who would also be running that same preferential peering code, i think that makes sense
09:27 < sdaftuar> s/miners/signers/
09:28 < jonatack> lightlike: yes, adding inbound eviction test coverage. it was one of the motivations for #19731 that was merged yesterday.
09:28 < gribble> https://github.com/bitcoin/bitcoin/issues/19731 | net, rpc: expose nLastBlockTime/nLastTXTime as last block/last_transaction in getpeerinfo by jonatack · Pull Request #19731 · bitcoin/bitcoin · GitHub
09:28 < sdaftuar> because you're basically deciding that you don't want to test transaction propagation but still be able to test that validation is working as you expect, which i think is reasonable
09:29 -!- sipsorcery [~sipsorcer@37.228.243.134] has quit [Remote host closed the connection]
09:29 < sdaftuar> i mean, you're not trying to simulate mainnet conditions with transaction propagation
09:29 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has joined #bitcoin-core-dev
09:29 < aj> sdaftuar: (atm, kalle's miner is non-taproot aware, while mine is; both refuse nonstd txs)
09:29 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:29 < jonatack> lightlike: see also https://github.com/bitcoin/bitcoin/issues/19500 and #19670
09:29 < gribble> https://github.com/bitcoin/bitcoin/issues/19670 | Protect localhost and block-relay-only peers from eviction by sdaftuar · Pull Request #19670 · bitcoin/bitcoin · GitHub
09:30 < jonatack> lightlike: and #19728
09:30 < gribble> https://github.com/bitcoin/bitcoin/issues/19728 | Increase the ip address relay branching factor for unreachable networks by sipa · Pull Request #19728 · bitcoin/bitcoin · GitHub
09:30 < aj> sdaftuar: it'd be nice if, given a large network of signet peers, tx propogation behaviour was like mainnet, i guess
09:30 < sdaftuar> aj: i feel like the lesson from testnet has been that is not really possible to achieve?  but i dunno.
09:31 < sdaftuar> or another way of putting it -- why would signet be any better than testnet?
09:31 < aj> sdaftuar: testnet is crazy though
09:31 < sdaftuar> you mean because of the reorgs?
09:32 < aj> sdaftuar: that and the rate at which blocks are found making CSV/CLTV not really sane
09:33 < aj> sdaftuar: but yeah, it's an "it'd be nice if", not a "i'm sure it'll work out this way"
09:34 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
09:35 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Client Quit]
09:35 < sdaftuar> fair enough
09:36 < aj> sdaftuar: (i mean, my daydream is along the lines: signet is stable and usable, so people run and actually maintain test services against it, so there's a whole bunch of reliable nodes and web sites and things like LN that have actual uptime on it)
09:36 -!- lnostdal [~lnostdal@cable-84-43-233-231.mnet.bg] has joined #bitcoin-core-dev
09:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:39 < bitcoin-git> [bitcoin] vasild opened pull request #19802: doc: elaborate on release notes wrt netmasks (master...elaborate_netmasks_relnotes) https://github.com/bitcoin/bitcoin/pull/19802
09:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:42 < jnewbery> aj: some may say you're a dreamer, but you're not the only one
09:42 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:43 < aj> jnewbery: someday we'll find it, over a p2p connection, the hodlers, the scammers, and me?
09:43 -!- proofofkeags [~proofofke@2601:280:c280:e500:9493:1db:50da:7239] has quit [Remote host closed the connection]
09:44 -!- proofofkeags [~proofofke@2601:280:c280:e500:9493:1db:50da:7239] has joined #bitcoin-core-dev
09:44 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:44 < aj> jnewbery: (i'm in ur earwigs upgradin' your tunez)
09:45 -!- proofofkeags [~proofofke@2601:280:c280:e500:9493:1db:50da:7239] has quit [Remote host closed the connection]
09:45 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:46 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:48 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:50 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:51 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:51 < bitcoin-git> [bitcoin] luke-jr opened pull request #19803: Bugfix: Define and use HAVE_FDATASYNC correctly outside LevelDB (master...fix_fdatasync_check) https://github.com/bitcoin/bitcoin/pull/19803
09:51 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:51 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:51 < luke-jr> fanquake: removed the no-longer-accurate commit message detail; I still don't see why the rest of #14501 shouldn't get fixed at the same time, but whatever
09:51 < gribble> https://github.com/bitcoin/bitcoin/issues/14501 | Fix possible data race when committing block files by luke-jr · Pull Request #14501 · bitcoin/bitcoin · GitHub
09:52 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:54 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:55 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:56 -!- lightlike [~lightlike@178.188.69.1] has quit [Quit: Leaving]
09:56 -!- lightlike [~lightlike@88.116.7.34] has joined #bitcoin-core-dev
09:57 -!- proofofkeags [~proofofke@2601:280:c280:e500:6c39:ead5:3c3e:20a1] has joined #bitcoin-core-dev
09:57 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:59 < aj> jnewbery: hmm, it appears to work with two nodes! if i set -maxconnections=2 the second slot gets succesffully reserved for a taproot advertising node. still doesn't have a "-experimental=taproot" flag though
09:59 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
10:01 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
10:01 -!- proofofkeags [~proofofke@2601:280:c280:e500:6c39:ead5:3c3e:20a1] has quit [Ping timeout: 244 seconds]
10:06 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
10:07 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
10:17 -!- pinheadmz [~pinheadmz@pool-100-33-69-78.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds]
10:19 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has quit [Remote host closed the connection]
10:19 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has joined #bitcoin-core-dev
10:20 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
10:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
10:22 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:22 < bitcoin-git> [bitcoin] gzhao408 opened pull request #19804: test: remove confusing p2p property (master...test-p2p-property) https://github.com/bitcoin/bitcoin/pull/19804
10:22 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:28 < bitcoin-git> [bitcoin] achow101 opened pull request #19805: wallet: Avoid deserializing unused records when salvaging (master...avoid-salvage-deser) https://github.com/bitcoin/bitcoin/pull/19805
10:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:30 -!- reallll [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
10:33 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 258 seconds]
10:39 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection]
10:39 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has joined #bitcoin-core-dev
10:39 -!- watersnake1 [~christian@98.11.149.49] has joined #bitcoin-core-dev
10:40 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has quit [Remote host closed the connection]
10:43 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
10:44 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
10:45 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
10:46 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Client Quit]
10:51 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
10:51 < luke-jr> bitcoin-qt up to 218 MB :o
10:51 < MarcoFalke> ugh why
10:51 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
10:52 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Client Quit]
10:52 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev
10:52 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Client Quit]
10:53 < luke-jr> MarcoFalke: guessing it's debugging symbols
10:53 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
10:53 < luke-jr> still bleh tho
10:54 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
10:54 < aj> luke-jr: 129M for bitcoind, 163M for bitcoin-qt for me?
10:54 < aj> luke-jr: (clang)
10:55 < luke-jr> aj: hmm, -ggdb? -fsanitize=undefined ?
10:56 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has joined #bitcoin-core-dev
10:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
10:58 < aj> luke-jr: just with-debug and with-werror (and incompatible-bdb)
10:58 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
10:59 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
11:00 -!- [n1x]_ [~n1x]_@s91904426.blix.com] has quit []
11:00 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:00 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has quit [Ping timeout: 240 seconds]
11:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
11:02 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
11:02 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:04 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:10 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
11:10 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
11:12 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
11:12 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev
11:12 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:21 -!- rlaager [~rlaager@37.120.203.188] has joined #bitcoin-core-dev
11:22 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:23 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:23 -!- nkuttler [~nkuttler@unaffiliated/nkuttler] has joined #bitcoin-core-dev
11:26 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has joined #bitcoin-core-dev
11:27 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 240 seconds]
11:29 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:30 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
11:30 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:32 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
11:35 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has joined #bitcoin-core-dev
11:43 -!- pinheadmz [~pinheadmz@2600:380:5a69:ca33:8cfb:3982:2322:fe8f] has joined #bitcoin-core-dev
11:43 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:48 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has quit [Ping timeout: 244 seconds]
11:48 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:49 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
11:50 < bitcoin-git> [bitcoin] jamesob opened pull request #19806: validation: UTXO snapshot activation (master...2020-08-au.activate) https://github.com/bitcoin/bitcoin/pull/19806
11:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
11:50 -!- wallet42_ [sid154231@gateway/web/irccloud.com/x-rowyyzgiybpygdar] has quit [Ping timeout: 272 seconds]
11:51 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has joined #bitcoin-core-dev
11:51 -!- jakesyl [sid56879@gateway/web/irccloud.com/x-wcxpoytoutibnrpn] has quit [Ping timeout: 244 seconds]
11:51 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:51 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:52 -!- jakesyl [sid56879@gateway/web/irccloud.com/x-gntvfqouzyoqmzvm] has joined #bitcoin-core-dev
11:53 -!- wallet42_ [sid154231@gateway/web/irccloud.com/x-hwhlmefxzyxrngtu] has joined #bitcoin-core-dev
11:53 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:54 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:56 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:57 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:58 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has quit [Remote host closed the connection]
12:01 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
12:01 -!- pinheadmz [~pinheadmz@2600:380:5a69:ca33:8cfb:3982:2322:fe8f] has quit [Quit: pinheadmz]
12:01 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 246 seconds]
12:01 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
12:03 -!- troygiorshev [~troygiors@d67-193-140-136.home3.cgocable.net] has quit [Ping timeout: 240 seconds]
12:05 -!- troygiorshev [~troygiors@d67-193-140-136.home3.cgocable.net] has joined #bitcoin-core-dev
12:06 -!- lightlike [~lightlike@88.116.7.34] has quit [Quit: Leaving]
12:09 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev
12:12 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
12:13 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
12:15 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
12:22 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
12:23 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
12:27 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
12:28 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
12:30 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
12:31 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
12:32 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
12:32 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-dev
12:33 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has joined #bitcoin-core-dev
12:33 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
12:36 -!- proofofkeags_ [~proofofke@2601:280:c280:e500:8cb9:2687:f7cd:9ee6] has joined #bitcoin-core-dev
12:39 -!- shesek [~shesek@164.90.217.137] has joined #bitcoin-core-dev
12:39 -!- shesek [~shesek@164.90.217.137] has quit [Changing host]
12:39 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
12:42 -!- xurzua [~xurzua@181.74.31.104] has joined #bitcoin-core-dev
12:46 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds]
12:52 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
12:59 -!- reallll is now known as belcher
13:00 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
13:00 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
13:01 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has joined #bitcoin-core-dev
13:02 -!- proofofkeags [~proofofke@2601:280:c280:e500:dc20:3961:41cf:8311] has quit [Remote host closed the connection]
13:04 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
13:05 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
13:05 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
13:06 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
13:09 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!]
13:12 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev
13:15 -!- lnostdal [~lnostdal@cable-84-43-233-231.mnet.bg] has quit [Ping timeout: 240 seconds]
13:26 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 240 seconds]
13:28 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
13:28 -!- lnostdal [~lnostdal@cable-84-43-233-231.mnet.bg] has joined #bitcoin-core-dev
13:30 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Remote host closed the connection]
13:33 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev
13:38 -!- proofofkeags__ [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev
13:38 -!- pinheadmz [~pinheadmz@pool-100-33-69-78.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
13:40 -!- proofofkeags_ [~proofofke@2601:280:c280:e500:8cb9:2687:f7cd:9ee6] has quit [Ping timeout: 260 seconds]
13:42 -!- proofofkeags__ [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Client Quit]
13:42 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev
13:46 -!- proofofk_ [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev
13:50 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
13:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
13:50 < bitcoin-git> [bitcoin] practicalswift opened pull request #19809: log: Prefix log messages with function name if -logfunctionnames is set (master...logfunctionnames) https://github.com/bitcoin/bitcoin/pull/19809
13:50 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Read error: Connection reset by peer]
13:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
13:51 -!- proofofk_ [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Ping timeout: 265 seconds]
13:53 -!- filchef [~filchef@212.104.97.177] has joined #bitcoin-core-dev
13:54 -!- filchef [~filchef@212.104.97.177] has quit [Client Quit]
14:00 -!- rlaager [~rlaager@37.120.203.188] has quit []
14:16 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
14:17 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
14:21 -!- serAphim [~serAphim@178.162.204.214] has joined #bitcoin-core-dev
14:33 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 265 seconds]
14:36 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:37 -!- Ga1aCt1Cz00__ [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:2143:af3d:c6b2:a825] has left #bitcoin-core-dev []
14:52 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
15:08 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
15:09 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
15:10 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
15:10 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Quit: May the Shwartz be with you]
15:14 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
15:15 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
15:21 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
15:21 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
15:22 -!- gzhao408 [uid453516@gateway/web/irccloud.com/x-eujonyheguhhaxjc] has quit [Quit: Connection closed for inactivity]
15:42 -!- xurzua [~xurzua@181.74.31.104] has quit [Quit: xurzua]
15:54 -!- marcoagner [~user@bl11-17-219.dsl.telepac.pt] has quit [Ping timeout: 258 seconds]
15:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
15:57 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has quit [Ping timeout: 272 seconds]
15:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:58 -!- vasild_ is now known as vasild
16:02 -!- pinheadm_ [~pinheadmz@64.94.215.92] has joined #bitcoin-core-dev
16:05 -!- pinheadmz [~pinheadmz@pool-100-33-69-78.nycmny.fios.verizon.net] has quit [Ping timeout: 264 seconds]
16:08 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
16:08 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
16:08 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has joined #bitcoin-core-dev
16:08 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
16:15 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has joined #bitcoin-core-dev
16:21 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
16:30 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
16:31 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
16:33 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
16:43 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection]
16:44 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
16:44 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
16:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
16:52 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
16:58 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
17:00 -!- serAphim [~serAphim@178.162.204.214] has quit []
17:02 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
17:02 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
17:05 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
17:08 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has quit [Ping timeout: 272 seconds]
17:10 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
17:11 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
17:20 -!- codestr0m [~codestr0m@89.47.234.28] has joined #bitcoin-core-dev
17:32 -!- lnostdal [~lnostdal@cable-84-43-233-231.mnet.bg] has quit [Ping timeout: 240 seconds]
17:33 -!- rabidus [~rabidus@81-175-144-89.bb.dnainternet.fi] has quit [Ping timeout: 240 seconds]
17:34 -!- rabidus [~rabidus@81-175-144-89.bb.dnainternet.fi] has joined #bitcoin-core-dev
17:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
17:44 -!- lnostdal [~lnostdal@cable-84-43-233-231.mnet.bg] has joined #bitcoin-core-dev
17:49 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 256 seconds]
17:50 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #bitcoin-core-dev
18:00 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
18:02 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
18:06 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
18:07 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
18:10 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
18:14 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
18:18 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
18:20 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Quit: yanmaani]
18:20 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 258 seconds]
18:23 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
18:24 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
18:26 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
18:29 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
18:29 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
18:38 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
18:56 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
18:59 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has quit [Ping timeout: 258 seconds]
19:02 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
19:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
19:03 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
19:10 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
19:11 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
19:19 -!- davec [~davec@cpe-24-243-240-159.hot.res.rr.com] has quit [Ping timeout: 240 seconds]
19:21 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has quit [Remote host closed the connection]
19:21 -!- arowser [~arowser1@67.230.166.11.16clouds.com] has joined #bitcoin-core-dev
19:24 -!- davec [~davec@cpe-24-243-240-159.hot.res.rr.com] has joined #bitcoin-core-dev
19:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds]
19:46 -!- proofofkeags [~proofofke@2601:280:c280:e500:89bc:f867:ae83:5ee1] has joined #bitcoin-core-dev
19:47 -!- proofofk_ [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev
19:47 -!- Davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection]
19:47 -!- Davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev
19:50 -!- proofofkeags [~proofofke@2601:280:c280:e500:89bc:f867:ae83:5ee1] has quit [Ping timeout: 244 seconds]
20:00 -!- codestr0m [~codestr0m@89.47.234.28] has quit []
20:01 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
20:02 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
20:16 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
20:17 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
20:22 -!- shoman94 [~shoman94@178.239.168.171] has joined #bitcoin-core-dev
20:50 < kallewoof> Signet PR https://github.com/bitcoin/bitcoin/pull/18267 latest commit now has 1 approach ACK, 1 utACK, 2 test ACKs; more if you count older commits. Feels like more is needed for a merge, but good progress. Please review!
21:09 -!- proofofk_ [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Remote host closed the connection]
21:20 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
21:23 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
21:24 -!- troygiorshev [~troygiors@d67-193-140-136.home3.cgocable.net] has quit [Ping timeout: 240 seconds]
21:26 -!- Davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection]
21:27 -!- Davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev
21:27 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:28 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 240 seconds]
21:28 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
21:28 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev
21:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
22:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
22:09 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
22:10 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
22:18 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
22:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
22:18 < bitcoin-git> [bitcoin] fanquake pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/8d6224fefe01...92735e45badf
22:18 < bitcoin-git> bitcoin/master fa96574 MarcoFalke: test: Move doxygen comment to header
22:18 < bitcoin-git> bitcoin/master fa11ff2 MarcoFalke: test: Pass empty tx pool to block assembler
22:18 < bitcoin-git> bitcoin/master fad84b7 MarcoFalke: test: Activate segwit in TestChain100Setup
22:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
22:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
22:18 < bitcoin-git> [bitcoin] fanquake merged pull request #19775: test: Activate segwit in TestChain100Setup (master...2008-testSegwit) https://github.com/bitcoin/bitcoin/pull/19775
22:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
22:18 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
23:00 -!- shoman94 [~shoman94@178.239.168.171] has quit []
23:07 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
23:08 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
23:22 -!- WhereIsMySpoon [~WhereIsMy@37.120.203.188] has joined #bitcoin-core-dev
23:22 -!- lnostdal [~lnostdal@cable-84-43-233-231.mnet.bg] has quit [Ping timeout: 258 seconds]
23:26 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-ivcziocbzjtetimt] has quit [Quit: Connection closed for inactivity]
23:26 -!- go121212 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #bitcoin-core-dev
23:28 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 265 seconds]
23:28 -!- go11111111111 [~go1111111@104.156.98.86] has quit [Ping timeout: 240 seconds]
23:31 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection]
23:34 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev
--- Log closed Wed Aug 26 00:00:59 2020