--- Log opened Wed Sep 09 00:00:13 2020 00:00 -!- Pavlenex [~Thunderbi@185.244.212.67] has joined #bitcoin-core-dev 00:03 -!- promag_ [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 00:04 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 00:07 -!- promag_ [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 00:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 00:09 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/4f229d8904f8...564e1ab0f3dc 00:09 < bitcoin-git> bitcoin/master fa39c62 MarcoFalke: test: inline hashToHex 00:09 < bitcoin-git> bitcoin/master fa188c9 MarcoFalke: test: Use MiniWalet in p2p_feefilter 00:09 < bitcoin-git> bitcoin/master 564e1ab MarcoFalke: Merge #19800: test: Mockwallet 00:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 00:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 00:09 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #19800: test: Mockwallet (master...2008-testMiniWallet) https://github.com/bitcoin/bitcoin/pull/19800 00:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 00:10 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has quit [Remote host closed the connection] 00:11 -!- promag_ [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 00:12 -!- marcoagner [~user@2001:8a0:6a45:1900:2fd7:e0f0:d356:dd70] has joined #bitcoin-core-dev 00:14 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::1e7] has joined #bitcoin-core-dev 00:16 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has joined #bitcoin-core-dev 00:16 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has quit [Remote host closed the connection] 00:16 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has joined #bitcoin-core-dev 00:21 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 240 seconds] 00:21 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 00:25 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 265 seconds] 00:26 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 00:27 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 00:28 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 00:28 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 00:29 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has quit [Remote host closed the connection] 00:29 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has joined #bitcoin-core-dev 00:30 -!- jonatack [~jon@37.171.144.181] has joined #bitcoin-core-dev 00:31 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds] 00:32 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:3963:b450:e139:b2a4] has joined #bitcoin-core-dev 00:33 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:791d:bd7e:eb3c:f699] has quit [Ping timeout: 244 seconds] 00:33 -!- promag [~promag@a89-152-187-241.cpe.netcabo.pt] has joined #bitcoin-core-dev 00:34 -!- jonatack [~jon@37.171.144.181] has quit [Ping timeout: 260 seconds] 00:35 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 00:35 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 00:36 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 00:36 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 00:36 -!- jonatack [~jon@109.232.227.138] has joined #bitcoin-core-dev 00:38 -!- promag [~promag@a89-152-187-241.cpe.netcabo.pt] has quit [Ping timeout: 264 seconds] 00:53 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 00:53 -!- promag_ [~promag@188.251.225.32] has joined #bitcoin-core-dev 00:56 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 00:58 < jonasschnelli> How is the process of merging "back" the state from the GUI repository? Is there a planed timeframe? Will there just be one PR to the main repository that includes all changes (like a backport PR)? Is that process documented already? 00:58 < jonasschnelli> ^ MarcoFalke 01:00 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 01:01 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 01:04 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:3963:b450:e139:b2a4] has quit [Remote host closed the connection] 01:04 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:3963:b450:e139:b2a4] has joined #bitcoin-core-dev 01:06 < promag> jonasschnelli: +1 01:08 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:ad8c:4db0:b1e7:c57] has joined #bitcoin-core-dev 01:08 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:3963:b450:e139:b2a4] has quit [Ping timeout: 244 seconds] 01:10 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 01:14 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 01:23 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 01:23 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 01:27 -!- andreaca_ [~andreacab@2a02:120b:2c22:e0c0:ad8c:4db0:b1e7:c57] has quit [Remote host closed the connection] 01:27 < jnewbery> #proposed meeting topic: stategies for removing recursive locking in the mempool (https://github.com/bitcoin/bitcoin/pull/19872#issuecomment-688852261) 01:27 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:ad8c:4db0:b1e7:c57] has joined #bitcoin-core-dev 01:30 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:ad8c:4db0:b1e7:c57] has quit [Remote host closed the connection] 01:30 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:ad8c:4db0:b1e7:c57] has joined #bitcoin-core-dev 01:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:35 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:ad8c:4db0:b1e7:c57] has quit [Ping timeout: 272 seconds] 01:36 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 01:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:38 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b10e:cc07:fe40:6913] has joined #bitcoin-core-dev 01:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:44 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #19922: test: Run rpc_txoutproof.py even with wallet disabled (master...2009-testMoreMiniWallet) https://github.com/bitcoin/bitcoin/pull/19922 01:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:50 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 01:50 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 01:51 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 01:52 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 01:54 -!- someone235 [uid419897@gateway/web/irccloud.com/x-gfsxyqritboytotn] has joined #bitcoin-core-dev 01:55 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 01:55 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 02:00 -!- whartung1 [~whartung@84.39.117.57] has quit [] 02:00 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 02:00 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 02:04 -!- Pavlenex [~Thunderbi@185.244.212.67] has quit [Quit: Pavlenex] 02:15 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 02:15 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b10e:cc07:fe40:6913] has quit [Remote host closed the connection] 02:16 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b10e:cc07:fe40:6913] has joined #bitcoin-core-dev 02:16 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 02:20 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:b10e:cc07:fe40:6913] has quit [Ping timeout: 244 seconds] 02:21 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 02:22 -!- kaimi1 [~kaimi@s91904426.blix.com] has joined #bitcoin-core-dev 02:24 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 02:25 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 02:26 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds] 02:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 02:31 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:35ce:dc19:96a6:8e93] has joined #bitcoin-core-dev 02:31 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 02:32 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 02:42 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 02:54 -!- provoostenator [~quassel@provoostenator.sprovoost.nl] has quit [Ping timeout: 272 seconds] 02:56 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev 03:02 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 03:04 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 03:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:11 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:35ce:dc19:96a6:8e93] has quit [Remote host closed the connection] 03:11 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:35ce:dc19:96a6:8e93] has joined #bitcoin-core-dev 03:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 03:13 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 240 seconds] 03:15 -!- jonatack [~jon@109.232.227.138] has quit [Ping timeout: 264 seconds] 03:16 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:35ce:dc19:96a6:8e93] has quit [Ping timeout: 260 seconds] 03:18 -!- Emily79Grady [~Emily79Gr@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-dev 03:28 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 03:28 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 03:29 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 03:29 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 03:30 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 03:32 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 03:39 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 03:39 < promag> jnewbery: +1 03:39 -!- promag_ [~promag@188.251.225.32] has quit [Remote host closed the connection] 03:41 -!- brianhoffman [~brianhoff@pool-71-191-34-154.washdc.fios.verizon.net] has quit [Write error: Connection reset by peer] 03:42 -!- brianhoffman [~brianhoff@pool-71-191-34-154.washdc.fios.verizon.net] has joined #bitcoin-core-dev 03:42 -!- Emily79Grady [~Emily79Gr@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 265 seconds] 03:43 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:44 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 03:48 -!- promag [~promag@188.251.225.32] has joined #bitcoin-core-dev 03:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:59 -!- promag_ [~promag@188.251.225.32] has joined #bitcoin-core-dev 04:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 04:07 < elichai2> MarcoFalke: I can't manage to reproduce the error in #19920, instead I'm getting a really weird bug without the full details, any idea why? (I'm getting this: https://pastebin.com/raw/MBzJ0ixB) 04:07 < gribble> https://github.com/bitcoin/bitcoin/issues/19920 | test: Fuzzing siphash against reference implementation [Request for feedback] by elichai 路 Pull Request #19920 路 bitcoin/bitcoin 路 GitHub 04:08 -!- promag [~promag@188.251.225.32] has quit [Remote host closed the connection] 04:08 -!- melande1 is now known as melande 04:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 04:15 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 04:16 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 04:16 < elichai2> found the bug :) you're not allowed to do `&*it` on null 馃槄 04:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds] 04:18 -!- worc3131 [~quassel@2a02:c7f:c026:9500:7d0b:65d0:38a4:4786] has quit [Quit: No Ping reply in 180 seconds.] 04:18 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 04:19 -!- worc3131 [~quassel@2a02:c7f:c026:9500:7d0b:65d0:38a4:4786] has joined #bitcoin-core-dev 04:22 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 04:23 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 04:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 04:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 04:25 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 04:26 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 04:27 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 265 seconds] 04:48 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 04:48 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 04:49 -!- promag_ [~promag@188.251.225.32] has quit [Remote host closed the connection] 04:53 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 240 seconds] 05:00 -!- kaimi1 [~kaimi@s91904426.blix.com] has quit [] 05:02 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 05:03 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 05:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev 05:05 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has quit [Read error: Connection reset by peer] 05:06 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has joined #bitcoin-core-dev 05:20 -!- Eric3 [~exeric3@178.132.3.92] has quit [Ping timeout: 246 seconds] 05:21 -!- Jamalaka1 [~Jamalaka@178.239.168.171] has joined #bitcoin-core-dev 05:21 -!- ExEric3 [~exeric3@178.132.3.92] has joined #bitcoin-core-dev 05:27 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has joined #bitcoin-core-dev 05:29 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 05:33 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 05:34 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 05:38 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 05:43 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 258 seconds] 05:49 -!- twistedline_ [~twisted@2601:14d:8500:26c0:5d9b:82c4:500a:e5f3] has quit [Remote host closed the connection] 05:49 -!- twistedline_ [~twisted@2601:14d:8500:26c0:3d6e:d61c:488e:f082] has joined #bitcoin-core-dev 05:55 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 05:56 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 06:02 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Remote host closed the connection] 06:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 06:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 06:05 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:05 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:06 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:06 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:07 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 06:08 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:08 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:10 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:10 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:11 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:11 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 246 seconds] 06:11 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:12 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:12 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:12 -!- nim87 [2ffeaa16@47.254.170.22] has joined #bitcoin-core-dev 06:13 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:13 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:14 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 06:14 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:14 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:16 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 06:16 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 06:16 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 06:23 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 06:28 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds] 06:39 -!- nim87 [2ffeaa16@47.254.170.22] has quit [Remote host closed the connection] 06:41 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:41 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:42 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Ping timeout: 240 seconds] 06:43 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:43 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 06:44 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 06:44 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 06:45 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 06:46 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 256 seconds] 06:49 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 272 seconds] 06:51 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 06:56 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 06:56 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 07:02 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 07:07 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 07:09 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 07:10 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev 07:13 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 07:17 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 07:19 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 07:19 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 07:25 -!- proofofkeags [~proofofke@174-29-30-112.hlrn.qwest.net] has quit [Ping timeout: 240 seconds] 07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 07:25 < bitcoin-git> [bitcoin] hebasto opened pull request #19926: gui: Add Tor icon (master...200909-tor) https://github.com/bitcoin/bitcoin/pull/19926 07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 07:39 -!- pinheadmz [~pinheadmz@pool-100-33-69-78.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 07:56 -!- mol_ [~mol@unaffiliated/molly] has quit [Remote host closed the connection] 07:57 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-core-dev 08:00 -!- Jamalaka1 [~Jamalaka@178.239.168.171] has quit [] 08:01 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 08:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev 08:05 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Ping timeout: 240 seconds] 08:06 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev 08:11 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev 08:16 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 08:16 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 08:16 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 08:17 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 08:17 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-dev 08:21 -!- ggainey1 [~ggainey@185.163.110.125] has joined #bitcoin-core-dev 08:31 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 08:35 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 246 seconds] 08:45 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 256 seconds] 08:50 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 08:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 09:02 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 09:03 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 09:11 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 09:12 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 09:12 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 09:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 09:15 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 244 seconds] 09:19 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 09:20 -!- melande [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 09:34 -!- gzhao408 [uid453516@gateway/web/irccloud.com/x-kfbemauuxpkroatd] has joined #bitcoin-core-dev 09:57 -!- MrPaz [~paz@24.14.251.223] has joined #bitcoin-core-dev 10:00 -!- b10c [~b10c@fttx-pool-217.61.146.236.bambit.de] has joined #bitcoin-core-dev 10:04 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 10:04 -!- melande [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 10:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 10:08 < bitcoin-git> [bitcoin] dongcarl opened pull request #19927: validation: Reduce direct g_chainman usage (master...2020-09-reduce-g_chainman-usage) https://github.com/bitcoin/bitcoin/pull/19927 10:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 10:10 -!- filchef [~filchef@212.104.97.177] has joined #bitcoin-core-dev 10:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 256 seconds] 10:15 -!- lightlike [~lightlike@p200300c7ef17420094c0841c19b70bd0.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:20 < ariard> jonasschnelli: just replied on bip324, AFAICT real-or-random and I favor MACing the length a la noise, even if as Lloyd is pointing we don't a concrete exploitation of it 10:23 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 256 seconds] 10:27 < achow101> jonasschnelli: IIRC PRs merged to the GUI repo are also pushed to the main repo simultaneously 10:28 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 10:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 10:42 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 10:43 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 11:00 -!- ggainey1 [~ggainey@185.163.110.125] has quit [] 11:02 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 11:03 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 11:04 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 11:04 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 11:05 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 11:20 -!- b10c [~b10c@fttx-pool-217.61.146.236.bambit.de] has quit [Quit: Leaving] 11:20 -!- b10c [~b10c@fttx-pool-217.61.146.236.bambit.de] has joined #bitcoin-core-dev 11:20 -!- ThunderChicken1 [~ThunderCh@195.206.169.184] has joined #bitcoin-core-dev 11:34 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 11:35 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-dev 11:50 -!- b10c [~b10c@fttx-pool-217.61.146.236.bambit.de] has quit [Ping timeout: 256 seconds] 11:57 < luke-jr> wtf :/ https://github.com/bitcoin/bitcoin/issues/19928 12:00 < achow101> luke-jr: O.o 12:00 < achow101> the filenames are hardcoded... 12:00 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer] 12:01 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 12:01 < luke-jr> achow101: isn't this the directory name, actually? 12:02 < achow101> https://twitter.com/2btc10000pizzas/status/1303767335258542085 would indicate it effects the wallet.dat file 12:03 -!- worc3131 [~quassel@2a02:c7f:c026:9500:7d0b:65d0:38a4:4786] has quit [Remote host closed the connection] 12:03 < achow101> although the previous tweet also suggests the directory name 12:03 < luke-jr> ackup.dat doesn't 12:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:03 < bitcoin-git> [bitcoin] vasild opened pull request #19929: sync: use proper TSA attributes (master...use_proper_tsa_attributes) https://github.com/bitcoin/bitcoin/pull/19929 12:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:04 -!- worc3131 [~quassel@2a02:c7f:c026:9500:7d0b:65d0:38a4:4786] has joined #bitcoin-core-dev 12:04 < achow101> right 12:04 < achow101> allet.dat does but maybe he specified wallet.dat and not just "" 12:04 < achow101> so that would mean it's a wallet name handling thing 12:04 < luke-jr> "" is never on disk :p 12:05 < luke-jr> you saw that apparently the actual on-disk filenames are being renamed, right? 12:05 < achow101> yes 12:05 < luke-jr> I'm not 100% sure they know what they're talking about in that regard, but it's weird 12:06 < gwillen> off the top of my head, one way to eat the first character of a path component would be issues with quoting and backslash as a path separator on Windows 12:06 < luke-jr> hmm 12:07 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 12:07 < luke-jr> "It would have been Gentoo Linux with the wallet files on an NTFS partition." lol totally unexpected 12:07 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 12:07 < luke-jr> I doubt the other guy has the same setup tho 12:07 < gwillen> iiiiiinteresting 12:07 < gwillen> could be an issue in the NTFS driver, that thing was always marked 'experimental' 12:07 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 12:08 < luke-jr> what's the chance the other guy had Linux+NTFS tho 12:08 < achow101> luke-jr: yeah, other guy is Win 10 12:08 < achow101> could be a NTFS issue 12:09 < luke-jr> seems unlikely 12:09 < luke-jr> it's not like Windows and Linux share the same NTFS code 12:10 < achow101> if he only see the problem on knots, then we could probably find the problem by looking at the diff? 12:10 < luke-jr> achow101: the second guy had it on Core 12:10 < luke-jr> I think 12:10 < gwillen> any chance the win 10 guy is using WSL or something weird like that? 12:11 < luke-jr> maybe if the Linux guy was using Captive NTFS.. he did say it was a long time ago 12:12 < gwillen> in that case why doesn't every windows user see it, though 12:12 < luke-jr> even the same user couldn't reproduce :/ 12:16 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 12:16 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 12:18 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 12:19 -!- b10c [~b10c@fttx-pool-217.61.146.236.bambit.de] has joined #bitcoin-core-dev 12:24 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 12:25 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev 12:31 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving] 12:34 -!- filchef [~filchef@212.104.97.177] has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/] 12:35 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev 12:58 < phantomcircuit> anybody know how many transaction outputs are in the chain? (not utxo, txo) 13:00 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 13:00 < sipa> years ago it was half a billion iirc 13:00 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 13:06 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 13:07 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Remote host closed the connection] 13:08 -!- Guest82 [c39015c2@gateway/web/cgi-irc/kiwiirc.com/ip.195.144.21.194] has joined #bitcoin-core-dev 13:10 -!- Guest82 [c39015c2@gateway/web/cgi-irc/kiwiirc.com/ip.195.144.21.194] has left #bitcoin-core-dev [] 13:10 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 13:11 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 13:12 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 13:16 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 246 seconds] 13:18 -!- ThunderChicken1 [~ThunderCh@195.206.169.184] has quit [Remote host closed the connection] 13:18 < andytoshi> i have a simple script i used for my mimblewimble presentation, i can get this number in a couple hours 13:18 < andytoshi> it seems to be taking 2-3 seconds per 100 blocks to scan, i don't remember it being so slow 13:23 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 13:28 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Quit: May the Shwartz be with you] 13:30 -!- blardo [~blardo@84.39.116.180] has joined #bitcoin-core-dev 13:32 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 13:33 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 13:36 < phantomcircuit> andytoshi, i've rigged up rescanblockchain to tell me 14:00 -!- blardo [~blardo@84.39.116.180] has quit [] 14:00 < andytoshi> ok cool. i had rigged the `getblock` rpc to dump the number of txouts per block and was using bash from there, but this is pretty brutal ... in the 40 minutes since i last spoke i'm up to block 200k. so it'll finish tonight :P 14:00 < sipa> andytoshi: it may not... there are barely any transactions before 200k i think 14:00 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 14:01 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 14:02 < aj> maybe update the coin stats index from #19521 and use that? 14:02 < andytoshi> hmm, so, i definitely did this in fall 2016 for scaling bitcoin milan and it only took a few hours 14:02 < andytoshi> i guess it's been 4 years :P 14:02 < gribble> https://github.com/bitcoin/bitcoin/issues/19521 | Coinstats Index (without UTXO set hash) by fjahr 路 Pull Request #19521 路 bitcoin/bitcoin 路 GitHub 14:03 < aj> andytoshi: (maybe rusty's bitcoin-iterate is faster?) 14:04 < sipa> 7316308 transactions up to block 200000 14:04 < sipa> out of 566745810 in total 14:05 < sipa> phantomcircuit: given that there have been more transactions now than my claimed earlier historical number for the total txouts, you can safely disregard it 14:05 < yanmaani> luke-jr: Maybe worth adding a check for it? 14:05 < yanmaani> "if wallet.dat doesn't exist and allet.dat does, show a message box" 14:06 < yanmaani> "Hi, a very rare bug has occured. We would be happy if you could email us at asd@asd.com and tell us what filesystem drivers you're using. To fix it, open that folder and rename allet.dat again." 14:06 < yanmaani> bit hacky though 14:07 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 14:08 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 14:11 < phantomcircuit> i think we've regressed on IBD somewhere, i have a server that's comically overpowered and there doesn't seem to be anything that's bottlenecking 14:13 < phantomcircuit> running steady at about 100mbps cpu and disk basically idle on a 1gbps connection 14:14 < sipa> phantomcircuit: do you have good peers to sync from? 14:14 < sipa> the stalling detection logic can kick out the worst peers, but whether you get actually good ones can be hit or miss 14:18 < yanmaani> what's usually the bottleneck for IBD? DB sync? 14:18 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 14:19 < aj> phantomcircuit: i often find i'm stuck on block X from a slow peer, while the other peers are on block X+500 or so 14:19 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 14:20 < sipa> yanmaani: depends... with lots of cache it's either network or (in-memory) utxo datastructure maintenance; with low cache it can be disk I/O 14:20 < phantomcircuit> sipa, it must be the eviction logic cause im sure it would otherwise be network limited 14:21 -!- maurits1 [~maurits@217.146.82.202] has joined #bitcoin-core-dev 14:21 < yanmaani> how much disk I/O do you need? It's just 300gb or so right? 14:22 < aj> yanmaani: disk io is mostly updating the utxo set, which is mitigated by cache 14:22 < yanmaani> Can't you disable disk IO during IBD for utxo set? 14:22 < sipa> yanmaani: yes, by making your cache big enough for the entire utxo set :) 14:22 < sipa> which is 8 GB or so 14:23 < yanmaani> No I mean can't you turn off DB sync and so? 14:23 < yanmaani> Or will it just need to spill to disk regardless? 14:23 < sipa> well the UTXOs need to be stored somewhere! 14:23 < sipa> how will you validate transactions otherwise? 14:23 < yanmaani> yeah, but there's no need to sync the database 14:23 < yanmaani> You can have MongoDB tier safety 14:24 < yanmaani> (during IBD) 14:24 < aj> you have to have a database, it can be in memory or on disk; if it's in memory, it's in cache 14:24 < sipa> if you set the cache big enough to keep the entire utxo set in memory, there will be no database I/O whatsoever during IBD 14:24 < sipa> and it'll be flushed once at the end 14:24 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 14:26 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 14:27 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 14:29 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 272 seconds] 14:31 -!- brianhoffman [~brianhoff@pool-71-191-34-154.washdc.fios.verizon.net] has quit [Ping timeout: 240 seconds] 14:31 -!- b10c [~b10c@fttx-pool-217.61.146.236.bambit.de] has quit [Remote host closed the connection] 14:35 < phantomcircuit> yanmaani, if you set the dbcache high enough you will only write to disk once when you shutdown the node 14:37 < yanmaani> If I set it say 99% of the way, will I notice a sharp slowdown, or is it smart enough to cache as much as possible? 14:39 < sipa> it's a sawtooth function; our cache is kind of a weird mix between a buffer and a cache 14:39 < sipa> once it fills up, it's written entirely to disk, and cleared 14:40 < sipa> (the reason for this is an unusual design that lets us remove entries from the cache if they're created and deleted between flushes, without them ever hitting disk) 14:40 < sipa> and at least years ago, we tried several alternative designs that kept some part in memory when flushing, but this turned out to be always worse 14:40 < yanmaani> And I'm guessing the database is being interacted with by fwrite() rather than mmap 14:41 < sipa> it's leveldb 14:41 < sipa> so whatever leveldb uses, which is a mix (iirc it's all fwrite on 32-bit platforms, and a combination of fwrite and mmap on 64-bit ones) 14:41 < yanmaani> So it's leveldb but with a custom cache? 14:42 < sipa> it's probably better to call it an in-memory database, backed by an on-disk leveldb database 14:42 < sipa> leveldb has its own caching too 14:43 < yanmaani> wouldn't a file-backed mmap be better? 14:43 < yanmaani> it's like malloc but with explicit swap handled by the OS 14:43 < sipa> you're welcome to try, but we're really talking about different layers 14:44 < sipa> the on-disk caching layer is a byte array 14:44 < yanmaani> No, I mean isntead of the RAM blob being used for in-ram caching 14:44 < sipa> there is no RAM blob 14:44 < sipa> there is an in-memory database, with expanded, efficient, data structures 14:44 < sipa> not serialized bytes 14:45 < yanmaani> Isn't the in-memory database in RAM???? 14:45 < sipa> yes, but it's not a blob 14:45 < sipa> no need to yell 14:45 < yanmaani> It's several mallocs? 14:45 < sipa> yes 14:46 < yanmaani> so, wouldn't it make more sense to replace them with backed mmaps that you never flush? Then the OS would have a lot more liberty to optimize 14:46 < yanmaani> than if you force it into RAM 14:46 < sipa> seriouysly, you're welcome to try 14:46 < sipa> i've spent months on optizing that stuff 14:47 < sipa> it's a highly unusual design, but yes, based on the experiments we did back then, it works very well 14:47 < yanmaani> huh 14:48 < sipa> the unusual part is that the UTXOs really have a create-lookuponce-deleteimmediate cycle 14:48 < sipa> which is very strange for databases 14:48 < sipa> usual things aren't designed to take advantage of the degree to which looked up entries are immediately deleted 14:49 < sipa> (and they'll instead create some sort of log that contains the creation and deletion, which still get written to disk at flush time) 14:50 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-dev 14:50 < sipa> by having an allocation per entry, you can just throw it away instantly when spent, and forget about its existence entirely 14:51 < sipa> if you have a few hundred MB or more of cache, it means most UTXOs never hit disk at all 14:52 < yanmaani> Wouldn't mmaps do this nearly as efficiently? Or is the OS too eager to flush changes? 14:52 < sipa> sigh 14:52 < sipa> you're talking about a different layer 14:52 < yanmaani> No, I mean that the malloc is replaced by a mmap 14:53 < yanmaani> And the mmap'd file is then treated like a RAM buffer of 8 GB 14:53 < sipa> then you'd get inconsistent state on disk in case of a crash 14:53 < yanmaani> Yeah, is that a problem? 14:53 < sipa> yes 14:53 < yanmaani> Can't you just remove the UTXO state in case of a crash? 14:53 < yanmaani> at least during IBD 14:53 < sipa> and sync from scratch? :o 14:53 < yanmaani> if you make it fast enough it should be a gain on net 14:53 < yanmaani> and dropping ACID guarantees and giving it the MongoDB treatment seems like it would make things faster 14:53 < sipa> in pruned mode, you'd need to start over redownloading even 14:54 < yanmaani> yeah, that's true. For pruned mode, you'd need to make sure it was synced properly. 14:54 < yanmaani> Although if you're substituting malloc() for mmap() of a temporary file, isn't the persistence as good? "The synced stuff stays, the stuff in RAM doesn't" 14:55 < sipa> there is no guarantee that mmap flushing happens in the same order as writes 14:55 < sipa> is there? 14:57 < yanmaani> no 14:58 < yanmaani> if it crashes, your mmap will be garbage 14:58 < yanmaani> but if you're using it to substitute malloc it should be fine 14:58 < yanmaani> since there's no expectation malloc persists on crash 14:58 < sipa> ah, i see 15:01 < sipa> what advantages would this have? if used with the same cache size as you'd use now, it wouldn't be any faster or have other advantages i think 15:02 < sipa> it'd permit you to make a cache larger than your ram, which may or may not be better 15:02 < sipa> depending on how fast disk is etc 15:02 < yanmaani> If used with the same cache size as you have now, it's roughly identical, but uses less RAM/is more fair 15:02 -!- lightlike [~lightlike@p200300c7ef17420094c0841c19b70bd0.dip0.t-ipconnect.de] has quit [Quit: Leaving] 15:02 < yanmaani> (OS can swap it out as it needs if there's a deficit of RAM) 15:02 < yanmaani> if used with the max cache size* 15:03 < sipa> that assumes the OS can predict better what's useful to have cached 15:03 < yanmaani> it has some caching algorithm on a block level, yes 15:03 < yanmaani> and users who are using zram/zswap will benefit from compression 15:03 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 15:03 < yanmaani> it'll avoid sync disk writes in the cases where cache is too small 15:03 < sipa> sure, but it doesn't know for example that after deleting some UTXO entry it's no longer useful to keep it around 15:04 < yanmaani> after deleting the utxo entry, the ram is filled with something else surely? 15:04 < yanmaani> (or it's never touched again, in which case the OS won't give it a very high priority) 15:04 < sipa> at some point, sure 15:04 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 15:05 < sipa> anyway, you're welcome to try and benchmark :) 15:06 < yanmaani> yeah. Where is the cache? 15:06 < yanmaani> i.e. what file 15:06 < yanmaani> is it src/index/*/ 15:07 < sipa> CCoinsViewCache in src/coins.h 15:09 < yanmaani> right, thanks! 15:13 < luke-jr> mallocs can get swapped out too.. 15:13 < yanmaani> Only if you have swap enabled 15:13 < yanmaani> Otherwise it'll go straight to thrashing 15:14 < yanmaani> With a file-backed mmap, it can flush the pages to disk without consuming your swap 15:14 < sipa> yanmaani: it would add I/O though, because the OS will start writing dirty pages from the mmap to disk, and then you'll read them again and write them again when flushing to the "real" database on disk 15:14 < sipa> though that wouldn't be I/O on the critical latency path 15:15 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-dev 15:15 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Read error: Connection reset by peer] 15:16 < yanmaani> yes, but so does normal thrashing 15:17 < sipa> if the cache is so large that it gets swapped out to disk, you're better off picking a smaller cache 15:17 < luke-jr> yanmaani: did you see my recent PR? 15:17 < yanmaani> there's two options with malloc: either swap (if that's enabled), or thrashing (swap out libc). With mmap, you can also flush it 15:17 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 15:18 < yanmaani> sipa: not necessarily - it might figure out which bits aren't so useful, and swap out those, for a net gain 15:18 < luke-jr> #19873 15:18 < gribble> https://github.com/bitcoin/bitcoin/issues/19873 | [WIP] Flush dbcache early if system is under memory pressure by luke-jr 路 Pull Request #19873 路 bitcoin/bitcoin 路 GitHub 15:19 < yanmaani> That might also work. I don't know which approach is better. 15:19 < sipa> yanmaani: given that every piece of data in the cache is accessed exactly once - when it's spent, i don't see how the OS could predict what is useful and what isn't 15:19 < yanmaani> I suppose I'll have to benchmark it 15:19 < sipa> yeah, it'd be interesting to know 15:19 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 258 seconds] 15:19 < sipa> you'll need some mmap-backed allocator i guess 15:20 < luke-jr> I think a more likely improvement would be to flag cache entries rather than delete them, when writing to db 15:20 < sipa> luke-jr: ? 15:20 < yanmaani> I wonder if it'd make more sense to write everything to DB and have it in some extremely lax sync mode 15:20 < yanmaani> so, take out the cache, and set the DB to MongoDB mode 15:20 < luke-jr> sipa: after flushing changes to db, keep them in memory in case they're read soon 15:20 < yanmaani> write during IBD, then flush when synced 15:20 < sipa> luke-jr: i tried that 15:20 < luke-jr> flag them so you know they don't need to be written anymore 15:21 < luke-jr> sipa: why didn't it work? 15:21 < sipa> luke-jr: at least a few years ago, it will never a win; the reason is that there is less memory available to exploit the "newly created entries that get deleted before ever hitting disk" 15:22 < luke-jr> sipa: you'd delete the flagged entries when you need more space? 15:22 < sipa> luke-jr: yes, i believe i tried something like that 15:22 < luke-jr> I don't see how this can be a lose :/ 15:23 < sipa> where the flushing is done in two tiers; in one, you'd flush everything, but keep the most recently created half around 15:23 < sipa> and in the second tier, when the memory is full, delete all non-dirty entries 15:23 < sipa> luke-jr: because of extra CPU to walk the cache and find things to delete 15:24 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 15:24 < luke-jr> std::move it to a second cache? :x 15:24 < sipa> there are definitely more combinations that could be tried, not claiming it's a certain loss 15:24 < sipa> but after trying half a dozen things, i think it was time to give up :) 15:25 < sipa> it may also depend on relative speeds of RAM/CPU/disk 15:25 < sipa> this was also pre-pertxout that was added in 0.15; that may have changed things 15:25 < luke-jr> hmm 15:25 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 15:26 < sipa> i did have a design a few years ago that i'd like to get back to at some point, which would permit flushing in the background without invalidating on-disk cache 15:26 < phantomcircuit> sipa, nvm for some reason my gateway<->modem was in 100 not 1000 15:26 < phantomcircuit> <.< 15:26 < sipa> eh, on-disk storage 15:26 < phantomcircuit> >.> 15:26 < luke-jr> hmmmm 15:27 < sipa> so you could be continuously writing the oldest entries, outside of the latency critical path 15:27 < sipa> though it'd need extra memory to keep things ordered 15:27 < yanmaani> Is std::unordered_map really the fastest in-memory kv store around? 15:27 < sipa> it's nontrivial to make it work correctly with reorgs etc though, but not impossible, if i remember 15:28 < sipa> yanmaani: it's not 15:29 < yanmaani> But it's advantageous for some other reason? Or is it just being used for some small part? 15:31 < sipa> i think people have tried some variations 15:32 < sipa> the biggest differency would come from using different allocation strategies, i think 15:32 < sipa> this was tried before though: https://github.com/bitcoin/bitcoin/pull/16801 15:32 < sipa> #16801 15:32 < gribble> https://github.com/bitcoin/bitcoin/issues/16801 | faster & less memory for sync: bulk pool allocator for node based containers by martinus 路 Pull Request #16801 路 bitcoin/bitcoin 路 GitHub 15:32 < achow101> how do I make a const unsigned char* into a span? 15:33 < sipa> achow101: do you have its length? 15:33 < achow101> yes 15:33 < sipa> Span(ptr, len) should work 15:33 < achow101> ah, thanks 15:34 < sipa> post c++17 we can add type inference, and you can use Span(ptr, len) 15:34 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 15:34 < luke-jr> doesn't C++17 include std::span anyway? :P 15:34 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-dev 15:34 < sipa> luke-jr: no, that's only in c++20 15:34 < sipa> achow101: if you're passing to a function that takes a Span already, you can use fn({ptr, len}) 15:34 < luke-jr> oh :x 15:35 < achow101> sipa: even better 15:35 < sipa> or {beginptr, endptr} 15:43 -!- sr_gi6 [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 15:44 < jb55> is there something in 0.20.0 -> 0.20.1 that would cause it to redownload the blockchain? trying to figure out why it's doing that after I upgraded my kernel+bitcoin. no configs changed ... 15:44 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has joined #bitcoin-core-dev 15:44 < jb55> maybe this ? https://jb55.com/s/a8e916c5b6f0404b.txt 15:46 < sipa> jb55: there shouldn't be any changes relates to that in minor releases 15:47 < phantomcircuit> sipa, can confirm i am dumb 15:47 < jb55> hmm yeah I figured, maybe weird io issue 15:49 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:50 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 15:50 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-dev 15:52 -!- wullon587 [~wullon@241.243.86.88.rdns.comcable.net] has quit [Ping timeout: 240 seconds] 15:55 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 15:55 -!- gzhao408 [uid453516@gateway/web/irccloud.com/x-kfbemauuxpkroatd] has quit [Quit: Connection closed for inactivity] 15:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds] 16:00 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 265 seconds] 16:09 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Ping timeout: 260 seconds] 16:11 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has joined #bitcoin-core-dev 16:13 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Quit: leaving] 16:16 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 16:19 -!- proofofkeags [~proofofke@c-73-34-43-4.hsd1.co.comcast.net] has quit [Ping timeout: 260 seconds] 16:20 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 16:26 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 16:28 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 16:29 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 16:31 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 272 seconds] 16:31 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 16:41 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 16:42 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 16:57 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 16:57 -!- marcoagner [~user@2001:8a0:6a45:1900:2fd7:e0f0:d356:dd70] has quit [Ping timeout: 244 seconds] 17:00 -!- maurits1 [~maurits@217.146.82.202] has quit [] 17:02 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 17:02 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 17:21 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 17:28 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 17:28 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 17:33 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 17:33 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 17:48 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has quit [Remote host closed the connection] 17:49 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has joined #bitcoin-core-dev 17:55 -!- zepheiryan [~zepheirya@217.146.82.202] has joined #bitcoin-core-dev 18:00 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 18:04 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Ping timeout: 260 seconds] 18:05 -!- troygiorshev [~troygiors@d67-193-140-136.home3.cgocable.net] has joined #bitcoin-core-dev 18:12 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 18:13 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 18:22 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 18:23 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 18:25 -!- troygiorshev [~troygiors@d67-193-140-136.home3.cgocable.net] has quit [Ping timeout: 256 seconds] 18:25 -!- alko89 [~alko89@unaffiliated/alko89] has joined #bitcoin-core-dev 18:38 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] 18:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 18:43 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 18:48 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 260 seconds] 18:49 -!- cato_ [~cato@gateway/tor-sasl/alec] has quit [Ping timeout: 240 seconds] 18:54 -!- cato_ [~cato@gateway/tor-sasl/alec] has joined #bitcoin-core-dev 18:58 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 18:58 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 19:24 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 19:25 -!- melande1 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 19:26 -!- melande1 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 19:26 -!- melande2 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 19:33 -!- proofofkeags [~proofofke@174-29-30-112.hlrn.qwest.net] has joined #bitcoin-core-dev 19:47 -!- arowser [~arowser1@204.124.180.72] has quit [Ping timeout: 240 seconds] 19:49 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 19:54 -!- brianhoffman [~brianhoff@pool-71-191-34-154.washdc.fios.verizon.net] has joined #bitcoin-core-dev 19:58 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has quit [Ping timeout: 256 seconds] 20:00 -!- zepheiryan [~zepheirya@217.146.82.202] has quit [] 20:06 -!- tralfaz [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev 20:07 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 20:19 -!- melande2 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 20:20 -!- melande2 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 20:21 -!- melande2 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 20:21 -!- melande11 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 20:21 -!- shoman94 [~shoman94@195.206.169.184] has joined #bitcoin-core-dev 20:23 -!- wullon587 [~wullon@241.243.86.88.rdns.comcable.net] has joined #bitcoin-core-dev 20:25 -!- proofofkeags [~proofofke@174-29-30-112.hlrn.qwest.net] has quit [Ping timeout: 260 seconds] 20:27 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has joined #bitcoin-core-dev 20:28 -!- melande11 [~melande@gateway/tor-sasl/melande] has quit [Ping timeout: 240 seconds] 20:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds] 20:32 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:d451:ba66:120e:205c] has quit [Ping timeout: 246 seconds] 20:34 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev 20:35 -!- melande11 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 20:57 -!- Highway61 [~Thunderbi@unaffiliated/highway61] has joined #bitcoin-core-dev 21:07 -!- melande11 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 21:08 -!- melande11 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 21:17 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 21:17 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 21:20 -!- melande11 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 21:21 -!- melande11 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 21:28 < kallewoof> Signet review beg -- no more changes planned, probably RFM: https://github.com/bitcoin/bitcoin/pull/18267 21:31 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 21:31 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 21:39 < phantomcircuit> sipa, 563,289,128 21:40 < sipa> phantomcircuit: that's unpossible 21:40 < sipa> txouts? 21:40 < phantomcircuit> wait did i count transactions 21:41 < sipa> i count 566823026 transactions 21:41 < phantomcircuit> damn it 21:42 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 21:42 < phantomcircuit> sipa, yeha i counted short at 99.4% done 21:42 < phantomcircuit> lets try that again 21:42 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 21:51 < phantomcircuit> 2020-09-10T04:49:27Z FlushStateToDisk: write coins cache to disk (72011604 coins, 9823747kB) started 21:51 < phantomcircuit> ok lets try that in 10-20 minutes 21:54 -!- brianhoffman_ [~brianhoff@pool-71-191-34-154.washdc.fios.verizon.net] has joined #bitcoin-core-dev 21:55 -!- brianhoffman [~brianhoff@pool-71-191-34-154.washdc.fios.verizon.net] has quit [Ping timeout: 246 seconds] 21:55 -!- brianhoffman_ is now known as brianhoffman 21:57 < phantomcircuit> only took 411.70s 22:01 < sipa> i hope my numbers are accurated, i have a script that maintains a database with some per-block statistics 22:02 < sipa> so i just added all the numbers in it 22:08 -!- melande11 [~melande@gateway/tor-sasl/melande] has quit [Remote host closed the connection] 22:09 -!- melande11 [~melande@gateway/tor-sasl/melande] has joined #bitcoin-core-dev 22:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 22:16 -!- Mercury_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has quit [Read error: Connection reset by peer] 22:24 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 22:24 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 22:29 < phantomcircuit> sipa, 1,506,642,276 22:32 < sipa> that's more like it 22:34 -!- MrPaz [~paz@24.14.251.223] has quit [Ping timeout: 260 seconds] 22:38 < phantomcircuit> sipa, yeah so this guy has no hope https://github.com/bitcoin/bitcoin/issues/19921 22:39 < sipa> phantomcircuit: it's not O(m*n) 22:40 < sipa> IsMine is O(log n) in the number of keys you have, i think 22:43 < phantomcircuit> sipa, there's a mapWallet.count, IsMine, IsFromMe, all of which will run if the transaction doesn't involve your wallet 22:44 < sipa> phantomcircuit: yes, but they run once per transaction, not per transactions*keycount 22:45 < sipa> only the lookups in the keystore have a time that scales with the number of keys, but it's not linear 22:51 < phantomcircuit> sipa, right so it's O(m log n) for m transactions and n keys 22:52 < phantomcircuit> or something close to that 22:52 < phantomcircuit> transaction outputs not transactions 22:54 < sipa> yes 22:54 < sipa> O(outputs+inputs) 22:54 < sipa> O((outputs+inputs)*log(keys)) 23:00 -!- shoman94 [~shoman94@195.206.169.184] has quit [] 23:09 < achow101> it'll just take a long time 23:10 < achow101> probably a bit faster if mapKeys was unordered map instead of map 23:11 < sipa> yeah 23:12 < sipa> and way faster if it was a map of scriptPubKeys ;) 23:12 < achow101> I suppose he could try #16910 23:12 < gribble> https://github.com/bitcoin/bitcoin/issues/16910 | wallet: reduce loading time by using unordered maps by achow101 路 Pull Request #16910 路 bitcoin/bitcoin 路 GitHub 23:12 < achow101> changes a bunch of things to unordered_map/unordered_set 23:17 -!- mdunnio [~mdunnio@208.59.170.5] has joined #bitcoin-core-dev 23:21 -!- steven1 [~steven@178.162.204.214] has joined #bitcoin-core-dev 23:22 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 258 seconds] 23:26 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 23:36 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 23:37 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 23:38 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 23:43 -!- tralfaz [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 23:43 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev 23:50 -!- arowser [~arowser1@204.124.180.72] has quit [Remote host closed the connection] 23:50 -!- arowser [~arowser1@204.124.180.72] has joined #bitcoin-core-dev 23:51 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 23:59 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Remote host closed the connection] 23:59 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev --- Log closed Thu Sep 10 00:00:06 2020