--- Log opened Mon Feb 17 00:00:41 2020 00:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 00:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 00:09 -!- Kiminuo [~mix@141.98.103.124] has joined #bitcoin-core-dev 00:13 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 00:15 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 00:16 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 00:25 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection] 00:28 -!- marcoagner [~user@bl11-16-246.dsl.telepac.pt] has joined #bitcoin-core-dev 00:30 -!- ivycheeuf [~ivycheeuf@2a00:23c7:b08b:6500:ec29:734f:9445:4f0e] has quit [Ping timeout: 246 seconds] 00:34 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit] 00:34 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 00:35 -!- sipsorcery [~sipsorcer@37.228.255.208] has joined #bitcoin-core-dev 00:52 -!- wumpus2 is now known as wumpus 00:57 -!- TheHoliestRoger [~TheHolies@unaffiliated/theholiestroger] has quit [Quit: Find me in #TheHolyRoger or https://theholyroger.com] 00:57 -!- TheHoliestRoger [~TheHolies@unaffiliated/theholiestroger] has joined #bitcoin-core-dev 01:00 -!- gholms1 [~gholms@176.113.74.179] has quit [] 01:06 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:07 -!- yozaam [88e801ae@136.232.1.174] has joined #bitcoin-core-dev 01:07 -!- yozaam [88e801ae@136.232.1.174] has quit [Remote host closed the connection] 01:12 -!- jkk [570a3539@host57-53-dynamic.10-87-r.retail.telecomitalia.it] has joined #bitcoin-core-dev 01:13 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit] 01:14 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 01:14 -!- jkk [570a3539@host57-53-dynamic.10-87-r.retail.telecomitalia.it] has quit [Remote host closed the connection] 01:18 -!- dfreedm [~dfreedm@195.206.169.238] has joined #bitcoin-core-dev 01:18 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 01:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:33 < jonasschnelli> Oh. I can macOS notarize the 0.19.1rc2 binary 01:33 < jonasschnelli> "message": "The executable does not have the hardened runtime enabled.", 01:34 < fanquake> jonasschnelli: likely need some additions to a .plist somewhere 01:34 < jonasschnelli> Probably... strange it worked with rc1?! 01:34 < fanquake> Interesting 01:35 < jonasschnelli> maybe they (Apple) just started to enforce it? dunno 01:35 < fanquake> I think that might be the case, was just trying to find the dates 01:36 < fanquake> It would have been January when you signed rc1 right? https://developer.apple.com/news/?id=09032019a 01:36 < fanquake> I assume now that it's Feb something has changed 01:38 < jonasschnelli> I notarized rc1 5 days ago and Sjors did confirm it worked: https://github.com/bitcoin/bitcoin/issues/15774#issuecomment-585324648 01:38 < jonasschnelli> Interesting: 01:38 < jonasschnelli> https://osxapps-ssl.itunes.apple.com/itunes-assets/Enigma124/v4/70/50/9d/70509d8c-c1b2-5e0c-47fc-b0c5df5de7f0/developer_log.json?accessKey=1582126708_7042408886895258564_pAgS0zq76QE9xKf6bLXiRcUifSnsajT%2BOMaGiI2hapSXmKhFdNM%2BgQdCZPgc2Oq5bL7IjkoP1gQQVStu7TIxONtJdQm6jpMTLP%2FsLi2NUGmcycExtzhgKIFBnxbP2Xy1YwM12BR2jhOkh%2BpT3pyzcU1kKGTUBZNv3DdEfdnDWNE%3D 01:39 < jonasschnelli> Apple had just a warning for the rc1 for the hardening entitlements 01:40 < fanquake> hmm. I can PR the .plist requirements if you're not already working on it 01:45 < jonasschnelli> fanquake: Yes. Please do if you know how... 01:45 < jonasschnelli> There is eventually a flag we need to change during code signing... 01:45 < jonasschnelli> (just looking into it) 01:45 < jonasschnelli> OTHER_CODE_SIGN_FLAGS 01:46 < jonasschnelli> https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/resolving_common_notarization_issues 01:47 < jonasschnelli> I can't see a difference in the Info.plist when enabling hardening in a sample XCode project.. 01:48 < jonasschnelli> I guess its more on the code signing level? 01:48 -!- asukan [~jan@183.128.110.62] has quit [Ping timeout: 268 seconds] 01:49 < fanquake> I think the changes might actually be in a separate .xml file 01:49 < fanquake> Which you pass to the codesigning tool 01:49 < jonasschnelli> https://devblogs.microsoft.com/xamarin/macos-hardened-runtime-notary/ 01:50 < jonasschnelli> fanquake: I think so. Yes. 01:50 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 01:50 < fanquake> Although we can add that to our tree with the other macdeploy files 01:50 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 260 seconds] 01:53 < jonasschnelli> fanquake: I guess we need `--options runtime` during codesign 01:53 < jonasschnelli> (detached-sig-create) 01:54 < jonasschnelli> fanquake: would be nice if you can investigate further and PR. We can make a testbuild for rc2 and make sure we land in rc3 or final 01:54 < fanquake> Sure. I can take a look at some changes. 01:54 -!- achow101 [~achow101@unaffiliated/achow101] has joined #bitcoin-core-dev 01:56 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:58 < wumpus> FWIW I'm not going to be at bitcoin 2020 / coredev next month, sorry, even less eager than normal to go on a long flight like that with the coronavirus and quarantaine scare 02:00 < jonasschnelli> I won't be there as well... 02:00 < wumpus> I don't have a good feeling about this tbh 02:01 < promag> wumpus: keep calm and enjoy merging #13339 02:01 < gribble> https://github.com/bitcoin/bitcoin/issues/13339 | wallet: Replace %w by wallet name in -walletnotify script by promag . Pull Request #13339 . bitcoin/bitcoin . GitHub 02:05 < wumpus> yes these are the times i'm quite happy to work remotely 02:07 < wumpus> jonasschnelli: glad to see the notarization worked 02:10 < fanquake> wumpus: If you want to get even more remote, feel free to come hang out on the farm. hah. 02:13 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 02:15 -!- jcoe [seru@gateway/vpn/protonvpn/joncoe] has joined #bitcoin-core-dev 02:20 < wumpus> fanquake: thinking about it :) 02:32 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 02:34 -!- pingwindyktator [~pingwindy@pingwindyktator.me] has joined #bitcoin-core-dev 02:45 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 03:00 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:00 < bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/263f53e2d07a...051439813e2c 03:00 < bitcoin-git> bitcoin/master 9a5b5ee Joao Barbosa: wallet: Replace %w by wallet name in -walletnotify script 03:00 < bitcoin-git> bitcoin/master 4e9efac Joao Barbosa: test: Check wallet name in -walletnotify script 03:00 < bitcoin-git> bitcoin/master 0514398 Wladimir J. van der Laan: Merge #13339: wallet: Replace %w by wallet name in -walletnotify script 03:00 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:00 < promag> \o/ 03:01 < promag> wumpus: I was kidding... that PR is really bad 03:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:01 < bitcoin-git> [bitcoin] laanwj merged pull request #13339: wallet: Replace %w by wallet name in -walletnotify script (master...2018-05-walletnotify) https://github.com/bitcoin/bitcoin/pull/13339 03:02 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:02 < wumpus> worst PR ever 03:02 < promag> sorry heh 03:03 < wumpus> happy we got it over with though, that was one shedpainting party 03:03 < promag> curious about who is going to pick win support 03:03 < promag> not me! 03:03 -!- Lambert82Morar [~Lambert82@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 03:04 < promag> #18160 03:04 < gribble> https://github.com/bitcoin/bitcoin/issues/18160 | gui: Avoid Wallet::GetBalance in WalletModel::pollBalanceChanged by promag . Pull Request #18160 . bitcoin/bitcoin . GitHub 03:04 < promag> this one might fix high cpu of bitcoin-qt 03:04 < wumpus> me neither, linux and BSD only here 03:05 < promag> so if you have a big wallet test let me know 03:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:06 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/051439813e2c...179504ccb6f4 03:06 < bitcoin-git> bitcoin/master 530d02a fanquake: build: pass -fno-ident in Windows gitian descriptor 03:06 < bitcoin-git> bitcoin/master 179504c Wladimir J. van der Laan: Merge #17948: build: pass -fno-ident in Windows gitian descriptor 03:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:06 < bitcoin-git> [bitcoin] laanwj merged pull request #17948: build: pass -fno-ident in Windows gitian descriptor (master...pass_fno_ident) https://github.com/bitcoin/bitcoin/pull/17948 03:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:06 < promag> I wasn't aware of MODEL_UPDATE_DELAY = 250ms 03:07 < promag> so we are calling GetBalances 4 times a second 03:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:07 < promag> *always* 03:13 < wumpus> at least there should be a try_lock there so that lock contention won't hang the whole UI, but yea 03:19 < promag> don't get fooled with that try_lock 03:20 < promag> not waiting for locks is nice obviously 03:21 < wumpus> right it helps a bit but doesn't change that it's still bad to do that polling in the GUI thread 03:21 < promag> problem is after, if GetBalances takes some time, and also it's called for no good reason 03:22 < promag> right 03:23 < promag> also we are caching the last block height but we aren't checking for that as early as possible 03:24 < wumpus> mind that the balance can change without the block height changing 03:24 < wumpus> (e.g. if you send, or unconfirmed balance for unconfirmed incoming transactions) 03:25 < wumpus> then again that's always after a transaction 03:25 < promag> yeah, there's the force flag for that 03:25 < wumpus> I guess the polling is only needed if blocks changed 03:26 < wumpus> (e.g. coinbases becoming mature, transactions confirming) 03:26 < promag> and if locks couldn't be acquired 03:27 < promag> I'm planning to move the timer from walletmodel(s) to wallet controller, and move the calls to the background thread 03:27 < wumpus> makes sense 03:28 < promag> but that's a bigger change and I think 18160 improves a lot cpu usage and is an easy backport 03:28 < promag> let's see what jonasschnelli and ryanofsky say 03:55 -!- masterdonx2 [~masterdon@185.108.128.160] has quit [Ping timeout: 272 seconds] 03:55 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 03:58 -!- MasterdonX [~masterdon@42.0.30.151] has joined #bitcoin-core-dev 04:00 -!- dfreedm [~dfreedm@195.206.169.238] has quit [] 04:09 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 04:09 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 04:12 -!- promag_ [~promag@a89-152-187-241.cpe.netcabo.pt] has joined #bitcoin-core-dev 04:13 -!- promag_ [~promag@a89-152-187-241.cpe.netcabo.pt] has quit [Remote host closed the connection] 04:13 -!- promag_ [~promag@a89-152-187-241.cpe.netcabo.pt] has joined #bitcoin-core-dev 04:15 -!- mhzesent [~pi@078088207100.walbrzych.vectranet.pl] has joined #bitcoin-core-dev 04:17 -!- IOMonster1 [~IOMonster@176.113.74.179] has joined #bitcoin-core-dev 04:20 -!- Lambert82Morar [~Lambert82@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 272 seconds] 04:52 -!- promag_ [~promag@a89-152-187-241.cpe.netcabo.pt] has quit [Remote host closed the connection] 04:59 -!- laurentmt [~Thunderbi@92.223.89.145] has joined #bitcoin-core-dev 05:07 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 05:09 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 05:10 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 05:17 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 05:22 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 05:28 -!- laurentmt [~Thunderbi@92.223.89.145] has quit [Quit: laurentmt] 05:31 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 05:35 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 268 seconds] 05:35 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:39 -!- mhzesent [~pi@078088207100.walbrzych.vectranet.pl] has quit [Quit: leaving] 05:47 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 05:51 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 05:59 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 06:09 -!- Highway61 [~Thunderbi@ip184-186-2-14.no.no.cox.net] has joined #bitcoin-core-dev 06:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev 06:21 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 06:27 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 06:38 -!- fox2p [~fox2p@cpe-66-108-32-173.nyc.res.rr.com] has quit [Ping timeout: 240 seconds] 06:39 -!- fox2p [~fox2p@cpe-66-108-32-173.nyc.res.rr.com] has joined #bitcoin-core-dev 06:46 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 06:50 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 06:53 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 06:55 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 06:56 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 07:00 -!- IOMonster1 [~IOMonster@176.113.74.179] has quit [] 07:00 -!- promag [~promag@188.250.106.244] has quit [Ping timeout: 240 seconds] 07:02 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 07:10 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit] 07:11 -!- qubenix [~qubenix@66.172.11.228] has joined #bitcoin-core-dev 07:17 -!- promag [~promag@188.250.106.244] has quit [Remote host closed the connection] 07:18 -!- kerbyu [~kerbyu@141.98.101.133] has joined #bitcoin-core-dev 07:18 -!- promag [~promag@188.250.106.244] has joined #bitcoin-core-dev 07:19 -!- promag_ [~promag@188.250.106.244] has joined #bitcoin-core-dev 07:19 -!- promag [~promag@188.250.106.244] has quit [Client Quit] 07:23 < luke-jr> wumpus: does RISC-V need #17569 backported? (why not?) 07:23 < gribble> https://github.com/bitcoin/bitcoin/issues/17569 | build: Allow export of environ symbols and work around rv64 toolchain issue by laanwj . Pull Request #17569 . bitcoin/bitcoin . GitHub 07:29 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit] 07:30 -!- qubenix [~qubenix@66.172.11.228] has joined #bitcoin-core-dev 07:31 < wumpus> luke-jr: couldn't hurt at least 07:37 -!- Kiminuo [~mix@141.98.103.124] has quit [Ping timeout: 260 seconds] 07:39 -!- SiAnDoG [~514nDoG@gateway/tor-sasl/siandog] has joined #bitcoin-core-dev 07:49 -!- emilengler [~emilengle@stratum0/entity/emilengler] has joined #bitcoin-core-dev 08:05 -!- promag_ [~promag@188.250.106.244] has quit [Remote host closed the connection] 08:33 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 08:37 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 268 seconds] 08:55 -!- roconnor [~roconnor@host-104-157-187-25.dyn.295.ca] has quit [Quit: Konversation terminated!] 09:02 < luke-jr> wumpus: well, it means a rc3... :/ 09:03 < luke-jr> wumpus: if the rc2 binaries work on RISC-V as-is, then we don't need it in 0.19.1 at least 09:03 < luke-jr> (IIRC you have a RISC-V system to test on, right?) 09:06 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-dev 09:06 < luke-jr> (to be clear, it's the noexecstack commit that I'm unsure about - obviously gitian builds complete ;P) 09:06 < hebasto> promag: mind looking into #17966 ? 09:06 < gribble> https://github.com/bitcoin/bitcoin/issues/17966 | qt, refactor: Optimize signal-slot connections logic by hebasto . Pull Request #17966 . bitcoin/bitcoin . GitHub 09:11 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Remote host closed the connection] 09:11 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-dev 09:15 -!- Kiminuo [~mix@141.98.103.124] has joined #bitcoin-core-dev 09:17 -!- bsm1175321 [~mcelrath@2601:196:4902:25b0:3067:a90a:9a06:babf] has joined #bitcoin-core-dev 09:17 -!- bsm1175321 [~mcelrath@2601:196:4902:25b0:3067:a90a:9a06:babf] has quit [Client Quit] 09:21 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 09:21 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:21 -!- jcoe1 [~seru@195.206.169.231] has joined #bitcoin-core-dev 09:21 -!- jcoe [seru@gateway/vpn/protonvpn/joncoe] has quit [Ping timeout: 272 seconds] 09:37 -!- Highway61 [~Thunderbi@ip184-186-2-14.no.no.cox.net] has quit [Ping timeout: 240 seconds] 09:53 -!- sipsorcery [~sipsorcer@37.228.255.208] has quit [Ping timeout: 260 seconds] 09:55 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 09:55 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds] 09:58 -!- sipsorcery [~sipsorcer@37.228.255.208] has joined #bitcoin-core-dev 09:58 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 09:58 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 10:00 -!- kerbyu [~kerbyu@141.98.101.133] has quit [] 10:02 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Ping timeout: 265 seconds] 10:02 -!- Kiminuo [~mix@141.98.103.124] has quit [Read error: Connection reset by peer] 10:03 -!- Kiminuo [~mix@141.98.103.124] has joined #bitcoin-core-dev 10:03 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 10:04 -!- Highway61 [~Thunderbi@ip24-252-87-140.no.no.cox.net] has joined #bitcoin-core-dev 10:04 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 265 seconds] 10:05 -!- braydonf_ [~braydon@gateway/tor-sasl/braydonf] has quit [Ping timeout: 240 seconds] 10:05 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 10:05 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qihsiglcjcbokopg] has quit [Ping timeout: 246 seconds] 10:07 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-getudbsqdkdesixh] has quit [Ping timeout: 245 seconds] 10:07 -!- mrostecki [mrosteckim@gateway/shell/matrix.org/x-kvemstlzaxnsgdfs] has quit [Ping timeout: 245 seconds] 10:07 -!- mael-rolland[m] [mael-rolla@gateway/shell/matrix.org/x-bbqnyvsmlyrqmjpy] has quit [Ping timeout: 240 seconds] 10:09 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 10:13 -!- braydonf_ [~braydon@gateway/tor-sasl/braydonf] has joined #bitcoin-core-dev 10:14 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 10:14 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...] 10:16 -!- selenamarie [~selenamar@139.28.218.198] has joined #bitcoin-core-dev 10:18 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection timed out] 10:21 -!- mael-rolland[m] [mael-rolla@gateway/shell/matrix.org/x-woxnzviitnhwovvx] has joined #bitcoin-core-dev 10:21 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 10:22 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 10:24 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qdaiuvjbvcvohzfc] has joined #bitcoin-core-dev 10:24 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 10:30 -!- spinza [~spin@102.132.245.16] has joined #bitcoin-core-dev 10:43 < dongcarl> What's the current thinking on running Bitcoin Core on non-ECC devices? Are there enough safe guards in place so that at least casual users can use non-ECC devices? 10:43 < sipa> what is a non-ECC device? 10:43 < sipa> elliptic curve crypto? 10:44 < sipa> error correcting code? 10:44 < dongcarl> devices without ECC RAM haha 10:45 < luke-jr> I suspect most people do 10:46 < luke-jr> IIRC Intel doesn't even allow you to use ECC with their normal CPUs 10:46 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 260 seconds] 10:46 < rafalcpp> dongcarl: almost all users sadly sit on non-ECC RAM. and you have no idea what will bitflip, it could be disk driver that will erase wallet or whatever. probably rather pointless to defend in software 10:46 < sipa> is there *any* consumer oriented CPU that supports ECC? 10:46 -!- mrostecki [mrosteckim@gateway/shell/matrix.org/x-kzltththfrnoteew] has joined #bitcoin-core-dev 10:47 < rafalcpp> sipa: pretty sure AMD Bulldozer supports, for example 10:47 < luke-jr> rafalcpp: there are places we *should* definitely defend.. your backups won't help you if you bitflip a change address 10:47 < luke-jr> sipa: POWER9 10:47 < luke-jr> (not typical, but the 4-core variants are consumer-oriented) 10:48 < dongcarl> This one too: https://www.96boards.org/product/developerbox/ 10:48 < dongcarl> I guess I'm just trying to understand the specific risks here... 10:49 < dongcarl> If I want to buy hardware to be my dedicated Bitcoin Core node... Should ECC RAM be a main concern? Or is it outweighed by other concerns 10:49 < luke-jr> dongcarl: I would put supervisor-free over ECC 10:50 < dongcarl> luke-jr: supervisor = BMC? 10:51 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 10:52 < luke-jr> dongcarl: nah, backdoors like Intel ME and AMD PSP 10:52 < sipa> dongcarl: if an ECC system is more expensive than a non-ECC system that can run two instances of bitcoind in parallel, pick the latter :) 10:52 < luke-jr> and the Microsoft ThreadX in Raspberry Pi 10:52 < rafalcpp> this purity in choosing realiable and not backdoored hardware is highly inspiring at least for me 10:53 < dongcarl> sipa: That's very true! 10:54 < dongcarl> luke-jr: Is that normally reported on wikichip? e.g., how do I tell if https://en.wikichip.org/wiki/socionext/sc2a11 has a supervisor? 10:54 * dongcarl googles Microsoft ThreadX 10:54 < rafalcpp> 2-of-2 multisign on other, cheap, device would solve it basically, although much less comfortable to use, dongcarl. an idea for future when it becomes non-trivial amount 10:54 < luke-jr> dongcarl: I don't know :/ 10:56 < dongcarl> rafalcpp: Right, I think the fact that usable SBCs are getting cheaper and cheaper is great. However, setting up clusters is quite a pain still 10:58 < dongcarl> Another question: When testing out lower-power SBCs, what's a good metric for "runs Bitcoin Core well"? Is "being able to keep up with tip" good enough? 10:58 < luke-jr> dongcarl: IBD in an hour? :P (haha) 11:00 < yevaud> dongcarl: even on the upper end SOCs IBD takes days. 11:01 < yevaud> dongcarl: the cheapest "sbc" with ECC is almost certainly the APU2/APU4, it's still slow and fanless, like any other SBC. 11:01 < dongcarl> Disregarding IBD I mean... In a steady state, is there anything else that would hinder correct operation and security other than keeping up with tip? 11:01 -!- Highway61 [~Thunderbi@ip24-252-87-140.no.no.cox.net] has quit [Ping timeout: 272 seconds] 11:03 < dongcarl> yevaud: right, from my understanding the apu2 might be affected by PSP, but I'm not sure that the NICs will cooperate if someone wants to attack 11:03 < yevaud> not really. on most SBCs you're going to see rather high rates of data loss due to MicroSD cards, but they run acceptably in the sync state. 11:06 < dongcarl> luke-jr: Did you get to look at the apu2 architecture and evaluate the risks closely? 11:06 < rafalcpp> dongcarl: a cluster? just run two separate instances. If anything is needed, I suppose bitcoind/gui could support 2-2 multisign more easily (if it doesn't yet) 11:07 < yevaud> dongcarl: yes, it has a PSP core. 11:07 < luke-jr> dongcarl: no 11:08 < luke-jr> dongcarl: I saw AMD and closed it 11:08 < dongcarl> yevaud: Right, but what's the exact attack though? From my understanding you'd need the NICs to cooperate, and PSP isn't in the coreboot payload that PC Engine builds... 11:09 < dongcarl> rafalcpp: That's true, you could probably do some deduplication at the FS level to save some space too 11:09 < rafalcpp> dongcarl: well this isn't separate computer then. but just fully prune one (or both) then it is around 6 GB 11:09 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 11:10 < yevaud> dongcarl: I don't know without asking PcEngines (do, they're helpful), but I don't think it's a realistic concern in the real world. 11:10 < luke-jr> I'm not sure PcEngines would know either? 11:10 < dongcarl> yevaud: That's a good point. Will email. 11:11 < dongcarl> luke-jr: They have quite a deep understanding of their hardware: https://github.com/pcengines/apu2-documentation 11:11 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 11:12 < luke-jr> dongcarl: but afaik the PSP is inivislbe outside the CPU? 11:13 < yevaud> luke-jr: on the Intel one it's stored on an external flash chip. 11:14 < luke-jr> but at least on Intel, if you deprive it, it won't work 11:15 < yevaud> stands to reason the manufacturer would have to understand that, if it were the case on AMD. 11:15 * dongcarl has some reading to do 11:16 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit] 11:16 < luke-jr> yevaud: they might not understand the ramifications of not providing it, even if that is the case 11:16 < luke-jr> eg, on Intel the IME is used to workaround silicon bugs, so with me_cleaner and such, you're vulnerable to undisclosed vulnerabilities 11:17 < yevaud> uh, really? the microcode is a separate thing to the ME core. 11:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 11:18 < bitcoin-git> [bitcoin] practicalswift opened pull request #18166: ci: Run fuzz testing test cases under valgrind (master...fuzz-test-cases-under-valgrind) https://github.com/bitcoin/bitcoin/pull/18166 11:19 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 11:19 < luke-jr> yevaud: someone disclosed or leaked that a while ago. it's not just microcode that patches silicon issues. 11:20 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 11:20 < luke-jr> I don't know that any of the specific details of the silicon bug were disclosed, so we can only speculate on why Intel might have done ti that way 11:20 < luke-jr> (maybe it's a silicon issue with the ME core, and not patching it means external attackers can compromise the ME core?) 11:21 < dongcarl> (if this is off-topic, someone should let me know) 11:22 < dongcarl> luke-jr: I think the PSP firmware has to be in the BIOS to be loaded 11:22 < yevaud> luke-jr: I was under the impression that ME operations against the main cores were effectively a NMI, so having it do any sort of continuous operation would demolish performance. 11:22 < dongcarl> And in the apu2 case, they did not include it in the coreboot payload: https://coreboot.coreboot.narkive.com/7e2UHc2x/pc-engines-apu2-platform-psp-support 11:23 < yevaud> luke-jr: but obviously I don't have specific knowledge here, so I'll leave it at that. 11:25 < luke-jr> yevaud: I'm not sure why that would matter. Injecting a bit of code wouldn't need to be continuous, and most things can be done by reading/changing RAM directly 11:25 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 11:27 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit] 11:37 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 11:38 -!- jcoe1 [~seru@195.206.169.231] has quit [Ping timeout: 268 seconds] 11:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 11:46 -!- mrostecki [mrosteckim@gateway/shell/matrix.org/x-kzltththfrnoteew] has quit [Quit: killed] 11:46 -!- mael-rolland[m] [mael-rolla@gateway/shell/matrix.org/x-woxnzviitnhwovvx] has quit [Quit: killed] 11:47 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qdaiuvjbvcvohzfc] has quit [Quit: killed] 11:49 -!- sanket1729 [~sanket172@72.36.89.11] has quit [Ping timeout: 250 seconds] 11:50 -!- Kiminuo [~mix@141.98.103.124] has quit [Ping timeout: 268 seconds] 11:50 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 11:51 -!- sanket1729 [~sanket172@72.36.89.11] has joined #bitcoin-core-dev 11:55 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has joined #bitcoin-core-dev 11:55 -!- jimmysong_ [~jimmysong@65-36-83-142.static.grandenetworks.net] has joined #bitcoin-core-dev 11:57 -!- jimmysong_ [~jimmysong@65-36-83-142.static.grandenetworks.net] has quit [Client Quit] 12:00 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has quit [Quit: Leaving] 12:02 -!- rafalcpp [~racalcppp@ip-178-211.ists.pl] has quit [Ping timeout: 265 seconds] 12:07 < wumpus> luke-jr: they work fine without the patch, #17569 does work around a noexecstack issue (so the stack is executable), I don't think it's worth doing a new rc for but if there is one anyway we could include it 12:07 < gribble> https://github.com/bitcoin/bitcoin/issues/17569 | build: Allow export of environ symbols and work around rv64 toolchain issue by laanwj . Pull Request #17569 . bitcoin/bitcoin . GitHub 12:11 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has joined #bitcoin-core-dev 12:12 < dongcarl> Does anyone know how to setup gribble for another channel? I'm thinking #bitcoin-builds 12:14 -!- Kiminuo [~mix@141.98.103.124] has joined #bitcoin-core-dev 12:14 -!- Highway61 [~Thunderbi@ip184-186-2-14.no.no.cox.net] has joined #bitcoin-core-dev 12:15 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:15 < bitcoin-git> [bitcoin] TheQuantumPhysicist opened pull request #18167: Fix a violation of C++ standard rules where unions are used for type-punning (master...master) https://github.com/bitcoin/bitcoin/pull/18167 12:15 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:16 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-pvuhrdptiepzivku] has joined #bitcoin-core-dev 12:21 -!- Guyver2__ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 12:22 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qgdvtvrbxrlnzoxg] has joined #bitcoin-core-dev 12:22 -!- mrostecki [mrosteckim@gateway/shell/matrix.org/x-hqsvcdzswjhmkjbd] has joined #bitcoin-core-dev 12:22 -!- mael-rolland[m] [mael-rolla@gateway/shell/matrix.org/x-hybbornnfndepota] has joined #bitcoin-core-dev 12:23 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 268 seconds] 12:29 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Ping timeout: 268 seconds] 12:30 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 12:32 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit] 12:33 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 12:33 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit] 12:35 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev 12:36 -!- emilengler [~emilengle@stratum0/entity/emilengler] has quit [Quit: Leaving] 12:42 -!- dr-orlovsky [~dr-orlovs@ip216.ip-54-36-238.eu] has quit [Ping timeout: 240 seconds] 12:45 -!- dr-orlovsky [~dr-orlovs@ip216.ip-54-36-238.eu] has joined #bitcoin-core-dev 13:00 -!- selenamarie [~selenamar@139.28.218.198] has quit [] 13:07 -!- Kiminuo [~mix@141.98.103.124] has quit [Ping timeout: 260 seconds] 13:08 -!- proshanta [25c9e0f0@aftr-37-201-224-240.unity-media.net] has joined #bitcoin-core-dev 13:14 -!- proshanta [25c9e0f0@aftr-37-201-224-240.unity-media.net] has quit [Remote host closed the connection] 13:18 -!- unknown1 [~unknown@104.254.90.235] has joined #bitcoin-core-dev 13:19 -!- Highway61 [~Thunderbi@ip184-186-2-14.no.no.cox.net] has quit [Remote host closed the connection] 13:25 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 13:29 -!- Guyver2__ [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 13:36 < achow101> dongcarl: talk to nanotube 13:40 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 13:45 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds] 14:03 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection] 14:25 -!- IGHOR [~quassel@93.178.216.72] has quit [Ping timeout: 272 seconds] 14:31 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 14:42 -!- cavemansalem [~oitdmser@c-71-237-150-172.hsd1.or.comcast.net] has joined #bitcoin-core-dev 14:48 -!- cavemansalem [~oitdmser@c-71-237-150-172.hsd1.or.comcast.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 14:49 -!- cavemansalem [~irc@c-71-237-150-172.hsd1.or.comcast.net] has joined #bitcoin-core-dev 14:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 14:55 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 14:58 -!- manantial [~tecnecio_@unaffiliated/manantial] has quit [Remote host closed the connection] 15:00 -!- Highway61 [~Thunderbi@ip184-186-2-14.no.no.cox.net] has joined #bitcoin-core-dev 15:39 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 15:46 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 15:58 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 260 seconds] 16:00 -!- unknown1 [~unknown@104.254.90.235] has quit [] 16:06 -!- marcoagner [~user@bl11-16-246.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 16:08 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 16:09 -!- jarthur_ [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 16:12 -!- jarthur [~jarthur@207.114.244.5] has quit [Ping timeout: 240 seconds] 16:13 -!- jarthur_ [~jarthur@207.114.244.5] has quit [Ping timeout: 272 seconds] 16:18 -!- robwerks1 [~robwerks@139.28.218.198] has joined #bitcoin-core-dev 16:36 -!- jrawsthorne_ [jrawsthorn@gateway/vpn/privateinternetaccess/jrawsthorne] has joined #bitcoin-core-dev 16:40 -!- jrawsthorne [jrawsthorn@gateway/vpn/privateinternetaccess/jrawsthorne] has quit [Ping timeout: 268 seconds] 17:05 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 17:05 < bitcoin-git> [bitcoin] MarcoFalke pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/179504ccb6f4...36f42e1bf43f 17:05 < bitcoin-git> bitcoin/master a6f6359 Amiti Uttarwar: [util] allow scheduler to be mocked 17:05 < bitcoin-git> bitcoin/master 1cd43e8 Amiti Uttarwar: [test] unit test for new MockForward scheduler method 17:05 < bitcoin-git> bitcoin/master 930d837 Amiti Uttarwar: [test] add chainparams property to indicate chain allows time mocking 17:05 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 17:05 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 17:05 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #18037: Util: Allow scheduler to be mocked (master...2020-01-mock-scheduler) https://github.com/bitcoin/bitcoin/pull/18037 17:05 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 17:07 -!- jrawsthorne [jrawsthorn@gateway/vpn/privateinternetaccess/jrawsthorne] has joined #bitcoin-core-dev 17:10 -!- jrawsthorne_ [jrawsthorn@gateway/vpn/privateinternetaccess/jrawsthorne] has quit [Ping timeout: 260 seconds] 17:11 -!- cavemansalem [~irc@c-71-237-150-172.hsd1.or.comcast.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 17:14 -!- asukan [~jan@183.128.110.62] has joined #bitcoin-core-dev 17:22 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Remote host closed the connection] 17:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 272 seconds] 17:48 -!- uncleray95 [183dc268@c-24-61-194-104.hsd1.ma.comcast.net] has joined #bitcoin-core-dev 18:00 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 18:02 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 18:03 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 265 seconds] 18:04 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 18:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 18:09 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 18:11 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Remote host closed the connection] 18:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 18:12 < bitcoin-git> [bitcoin] toxeus opened pull request #18168: httpserver: use own HTTP status codes (master...500) https://github.com/bitcoin/bitcoin/pull/18168 18:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 18:13 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 18:17 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev 18:50 < mryandao> hi, i'm trying to cross-compile for aarch64. I followed the instructions in depends/README.md, but when i try to run `./configure --prefix=$PWD/depends/aarch64-linux-gnu --disable-wallet --with-gui=no --with-tests=no`, i'm getting `checking for exit in -lboost_system-mt-a64... no`. 18:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 18:50 < bitcoin-git> [bitcoin] travinkeith opened pull request #18169: Update CONTRIBUTING.md (master...patch-1) https://github.com/bitcoin/bitcoin/pull/18169 18:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 18:51 < mryandao> looking at the logs, configure did pick up where boostlib is. 18:52 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 18:52 < bitcoin-git> [bitcoin] fanquake closed pull request #18169: Update CONTRIBUTING.md (master...patch-1) https://github.com/bitcoin/bitcoin/pull/18169 18:53 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 18:57 -!- SiAnDoG [~514nDoG@gateway/tor-sasl/siandog] has quit [Remote host closed the connection] 18:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 18:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 19:00 -!- robwerks1 [~robwerks@139.28.218.198] has quit [] 19:01 -!- abrissbirne [~abrissbir@unaffiliated/abrissbirne] has joined #bitcoin-core-dev 19:03 < mryandao> oh nvm, used the wrong toolchain 19:03 < mryandao> false alarm 19:05 -!- abrissbi1ne [~abrissbir@unaffiliated/abrissbirne] has quit [Ping timeout: 256 seconds] 19:08 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 19:18 -!- SynOps [~SynOps@185.189.112.11] has joined #bitcoin-core-dev 19:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 19:33 < bitcoin-git> [bitcoin] travinkeith opened pull request #18170: doc: Minor grammatical changes and flow improvements (master...patch-2) https://github.com/bitcoin/bitcoin/pull/18170 19:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 19:42 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 19:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 19:49 -!- felixfoertsch23 [~felixfoer@i6DFA6AAA.versanet.de] has joined #bitcoin-core-dev 19:51 -!- felixfoertsch [~felixfoer@2001:16b8:50bf:a300:e546:4651:fe6b:4481] has quit [Ping timeout: 272 seconds] 20:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 20:30 -!- Highway61 [~Thunderbi@ip184-186-2-14.no.no.cox.net] has quit [Ping timeout: 265 seconds] 20:41 < midnight> sipa: Helios4 was built with ECC (and no other option) for one example. It was very inexpensive.. 20:43 < midnight> The kobol types were making noises that they were amenable to a future helios iteration which was user-Efuse'able too which is pretty cool 20:44 < midnight> So they exist and they occasionally cycle through inexpensive machines. 21:08 -!- asukan_ [~quassel@ec2-35-180-180-58.eu-west-3.compute.amazonaws.com] has joined #bitcoin-core-dev 21:09 -!- asukan [~jan@183.128.110.62] has quit [Quit: Konversation terminated!] 21:09 -!- asukan_ is now known as asukan 21:22 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 21:22 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 21:28 -!- Madars [~null@unaffiliated/madars] has quit [Ping timeout: 260 seconds] 21:38 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has quit [Read error: Connection reset by peer] 21:38 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has joined #bitcoin-core-dev 21:46 -!- braydonf_ [~braydon@gateway/tor-sasl/braydonf] has quit [Remote host closed the connection] 21:47 -!- braydonf_ [~braydon@gateway/tor-sasl/braydonf] has joined #bitcoin-core-dev 21:48 -!- Madars [~null@unaffiliated/madars] has joined #bitcoin-core-dev 22:00 -!- SynOps [~SynOps@185.189.112.11] has quit [] 22:09 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 22:11 -!- mryandao_ [~mryandao@gateway/tor-sasl/mryandao] has joined #bitcoin-core-dev 22:11 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection] 22:13 -!- Madars [~null@unaffiliated/madars] has quit [Ping timeout: 268 seconds] 22:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 22:14 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 272 seconds] 22:18 -!- hellekin1 [~hellekin@141.98.101.133] has joined #bitcoin-core-dev 22:20 -!- mryandao_ is now known as mryandao 22:23 -!- hellekin1 [~hellekin@141.98.101.133] has quit [Remote host closed the connection] 22:45 -!- Madars [~null@unaffiliated/madars] has joined #bitcoin-core-dev 22:47 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 272 seconds] 22:58 -!- Kiminuo [~mix@141.98.103.124] has joined #bitcoin-core-dev 22:58 -!- manantial [~tecnecio_@unaffiliated/manantial] has joined #bitcoin-core-dev 23:05 -!- Madars [~null@unaffiliated/madars] has quit [Ping timeout: 240 seconds] 23:16 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 23:22 -!- esandeen [~esandeen@185.189.112.19] has joined #bitcoin-core-dev 23:25 -!- Madars [~null@unaffiliated/madars] has joined #bitcoin-core-dev 23:33 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 23:46 -!- Madars [~null@unaffiliated/madars] has quit [Ping timeout: 265 seconds] 23:50 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev --- Log closed Tue Feb 18 00:00:44 2020