--- Day changed Thu Jul 20 2017 00:02 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has quit [Read error: No route to host] 00:02 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 00:03 < wumpus> a user on transifex is misbehaving (vandalizing the German translations), anyone have experience with how to handle this? I don't see any ban controls etc in their interface 00:09 < jonasschnelli> hmm...can we revert his changes? 00:09 < wumpus> e.g. nearly all of these are nonsense https://www.transifex.com/bitcoin/bitcoin/translate/#de/$/104570304?user=pehotinec, sometimes he copies slightly similar messages to make it look ok, sometimes he just copies the English message, in any cast this seems deliberate 00:10 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:11 < jonasschnelli> I'll write transiflex support to ban that user 00:11 < wumpus> thank you 00:11 < jonasschnelli> But is there a way to revert all his changes? 00:12 < wumpus> not in one go - there's a revert button on messages, but usually it seems to be disabled; I think that means these messages have no previous translation, it's only noticed now 00:13 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 00:13 < jonasschnelli> Okay. I'll check the german part (and eventually write in the correct transaltion) 00:13 < wumpus> they should be reveted back to untranslated 00:13 < wumpus> yes, or that 00:13 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:14 < Victorsueca> I don't know a way to block a user from a project that doesn't go through making people request to join the translation team 00:15 < jonasschnelli> wumpus: do we also need to take care of <0.15 translations (do these get pulled again?)? 00:15 < wumpus> only 0.14, the others are closed. Those get pulled again when there is a minor release. 00:18 < jonasschnelli> wumpus: although users pehotinec did also correct translations... 00:19 < wumpus> there are a few that seem to be correct, some look very convincing but seem copies of related messages, and others are complete nonsense 00:20 < wumpus> it's quite sneaky which is why it took months to discover, unlike if he just wrote 'poop' everywhere. seone has sent him a message asking about his motivation but I have the feeling he's not going to respond normally to that 00:21 < jonasschnelli> Yes. I guess he filled in english translations into the missing german ones 00:23 < wumpus> he also has some english to english messages in de_DE https://www.transifex.com/bitcoin/bitcoin/translate/#de_DE/$/65093519?user=pehotinec 00:32 -!- cysm [cysm@gateway/shell/elitebnc/x-msqcfqcqxyprprbg] has quit [Ping timeout: 255 seconds] 00:32 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 00:37 -!- btcdrak [uid239175@gateway/web/irccloud.com/x-xurryifwlvdjxlcw] has quit [Quit: Connection closed for inactivity] 00:40 -!- cysm [cysm@gateway/shell/elitebnc/x-ckklhpncnsqgxweo] has joined #bitcoin-core-dev 00:43 -!- btcdrak [uid239175@gateway/web/irccloud.com/x-qaoeimtnhjfsuyek] has joined #bitcoin-core-dev 00:50 -!- Orion3k [~Orion3k@47-51-33-228.static.mtpk.ca.charter.com] has quit [Quit: Leaving] 01:09 -!- ayy1337|2 [~kvirc@110.140.15.24] has quit [Ping timeout: 248 seconds] 01:15 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:19 -!- Lauda_ [~quassel@2a06:8ec0:3::1:b224] has quit [Ping timeout: 240 seconds] 01:21 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 01:22 -!- pescador [~pescador@62-251-9-102.ip.xs4all.nl] has joined #bitcoin-core-dev 01:22 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 255 seconds] 01:36 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/df0793f324e3...bf3b742e2852 01:36 < bitcoin-git> bitcoin/master 2264236 Alex Morcos: Rename -usewallet to -rpcwallet 01:36 < bitcoin-git> bitcoin/master bf3b742 Wladimir J. van der Laan: Merge #10883: Rename -usewallet to -rpcwallet... 01:36 < bitcoin-git> [bitcoin] laanwj closed pull request #10883: Rename -usewallet to -rpcwallet (master...rpcwallet) https://github.com/bitcoin/bitcoin/pull/10883 01:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:55 -!- pescador [~pescador@62-251-9-102.ip.xs4all.nl] has left #bitcoin-core-dev [] 02:18 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 02:19 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has joined #bitcoin-core-dev 02:19 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Client Quit] 02:20 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has joined #bitcoin-core-dev 02:20 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Client Quit] 02:20 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has joined #bitcoin-core-dev 02:21 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Client Quit] 02:21 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has joined #bitcoin-core-dev 02:22 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Client Quit] 02:22 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has joined #bitcoin-core-dev 02:22 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Client Quit] 02:26 -!- promag [~joao@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 02:38 -!- JackH [~laptop@46.231.18.66] has joined #bitcoin-core-dev 02:45 < bitcoin-git> [bitcoin] benma opened pull request #10888: range-based loops and const qualifications in net.cpp (master...netcpp_cosmetics2) https://github.com/bitcoin/bitcoin/pull/10888 02:57 -!- btcdrak [uid239175@gateway/web/irccloud.com/x-qaoeimtnhjfsuyek] has quit [Quit: Connection closed for inactivity] 03:27 -!- promag [~joao@bl6-24-70.dsl.telepac.pt] has quit [Quit: Leaving.] 03:28 -!- Lauda_ [~quassel@2a06:8ec0:3::1:b224] has joined #bitcoin-core-dev 03:29 -!- promag [~joao@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:31 -!- promag [~joao@bl6-24-70.dsl.telepac.pt] has quit [Client Quit] 03:31 -!- promag [~joao@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:33 -!- promag [~joao@bl6-24-70.dsl.telepac.pt] has quit [Read error: Connection reset by peer] 03:46 -!- dev__ [~dev@120.6.105.139] has quit [Read error: Connection reset by peer] 03:54 -!- coredump_ [~quassel@101.165.147.38] has joined #bitcoin-core-dev 04:13 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 04:13 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 260 seconds] 04:15 -!- JackH [~laptop@46.231.18.66] has quit [Read error: Connection reset by peer] 04:42 -!- JackH [~laptop@46.231.18.66] has joined #bitcoin-core-dev 05:00 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 05:08 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 05:12 -!- goatpig [56f75436@gateway/web/freenode/ip.86.247.84.54] has joined #bitcoin-core-dev 05:12 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 05:20 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 240 seconds] 05:23 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 05:38 -!- coredump_ [~quassel@101.165.147.38] has quit [Ping timeout: 246 seconds] 05:46 -!- coredump_ [~quassel@101.165.147.38] has joined #bitcoin-core-dev 06:07 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:11 -!- marcoagner [~user@191.249.242.188] has quit [Ping timeout: 268 seconds] 06:22 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 06:22 -!- marcoagner [~user@177.41.200.241] has joined #bitcoin-core-dev 06:42 -!- wvr [~wvr@121.red-83-45-36.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 06:43 -!- promag [~joao@2001:8a0:fe30:de01:c157:cbe7:ca9e:38e5] has joined #bitcoin-core-dev 07:11 < bitcoin-git> [bitcoin] jnewbery closed pull request #10868: Remove -usewallet (master...remove_use_wallet) https://github.com/bitcoin/bitcoin/pull/10868 07:14 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 246 seconds] 07:27 -!- coredump_ [~quassel@101.165.147.38] has quit [Ping timeout: 246 seconds] 07:29 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 268 seconds] 07:31 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 07:43 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/bf3b742e2852...adf170daf90f 07:43 < bitcoin-git> bitcoin/master 6b4f231 Andrew Chow: Move transaction combining from signrawtransaction to new RPC... 07:43 < bitcoin-git> bitcoin/master adf170d Wladimir J. van der Laan: Merge #10571: [RPC]Move transaction combining from signrawtransaction to new RPC... 07:43 < bitcoin-git> [bitcoin] laanwj closed pull request #10571: [RPC]Move transaction combining from signrawtransaction to new RPC (master...combineraw-rpc) https://github.com/bitcoin/bitcoin/pull/10571 07:47 -!- coredump_ [~quassel@101.165.147.38] has joined #bitcoin-core-dev 07:54 -!- jtimon [~quassel@102.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 07:55 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:57 < bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/adf170daf90f...fd2814ef1182 07:57 < bitcoin-git> bitcoin/master 35aff43 practicalswift: Remove unused variable int64_t nEnd... 07:57 < bitcoin-git> bitcoin/master 5a6671c practicalswift: Fix typo: "conditon" → "condition"... 07:57 < bitcoin-git> bitcoin/master fd2814e Wladimir J. van der Laan: Merge #10862: Remove unused variable int64_t nEnd. Fix typo: "conditon" → "condition".... 07:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 07:58 < bitcoin-git> [bitcoin] laanwj closed pull request #10862: Remove unused variable int64_t nEnd. Fix typo: "conditon" → "condition". (master...nEnd) https://github.com/bitcoin/bitcoin/pull/10862 07:58 -!- coredump_ [~quassel@101.165.147.38] has quit [Ping timeout: 246 seconds] 08:02 < bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/fd2814ef1182...041dad94b047 08:02 < bitcoin-git> bitcoin/master a70d025 Gregory Sanders: fixup some rpc param counting for rpc help 08:02 < bitcoin-git> bitcoin/master 999ef20 Gregory Sanders: importmulti options are optional 08:02 < bitcoin-git> bitcoin/master 4dc1915 Gregory Sanders: check for null values in rpc args and handle appropriately 08:03 < bitcoin-git> [bitcoin] laanwj closed pull request #10783: [RPC] Various rpc argument fixes (master...rpcargfixes) https://github.com/bitcoin/bitcoin/pull/10783 08:05 -!- promag [~joao@2001:8a0:fe30:de01:c157:cbe7:ca9e:38e5] has quit [Quit: Leaving.] 08:07 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 240 seconds] 08:08 -!- promag [~joao@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:10 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 08:11 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:12 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 08:13 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 08:27 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #bitcoin-core-dev 08:28 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 08:31 < jnewbery> sipa gmaxwell: you were asking for #10882 . It should be review-ready now. 08:31 < gribble> https://github.com/bitcoin/bitcoin/issues/10882 | [WIP] Keypool topup by jnewbery · Pull Request #10882 · bitcoin/bitcoin · GitHub 08:32 < sipa> jnewbery: thanks! 08:35 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/041dad94b047...7c2400cb8ab7 08:35 < bitcoin-git> bitcoin/master d9d1bd3 romanornr: nCheckDepth chain height fix 08:35 < bitcoin-git> bitcoin/master 7c2400c Wladimir J. van der Laan: Merge #10775: nCheckDepth chain height fix... 08:36 < bitcoin-git> [bitcoin] laanwj closed pull request #10775: nCheckDepth chain height fix (master...master) https://github.com/bitcoin/bitcoin/pull/10775 08:39 < instagibbs> jnewbery, could you squash? 08:40 < jnewbery> sure - I'll do that now 08:40 < instagibbs> \o/ 08:42 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 08:53 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 08:58 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds] 09:00 -!- nakaluna [~nakaluna@177.141.154.83] has joined #bitcoin-core-dev 09:05 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has joined #bitcoin-core-dev 09:11 -!- jamesob_ [~james@tempo-automation.static.monkeybrains.net] has joined #bitcoin-core-dev 09:16 -!- promag [~joao@bl22-247-244.dsl.telepac.pt] has quit [Quit: Leaving.] 09:17 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 240 seconds] 09:25 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 09:27 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 268 seconds] 09:30 -!- nakaluna [~nakaluna@177.141.154.83] has quit [Ping timeout: 255 seconds] 09:32 -!- nakaluna [~nakaluna@177.141.154.83] has joined #bitcoin-core-dev 09:35 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 248 seconds] 09:36 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 09:36 -!- sipa [~pw@2001:19f0:ac01:2fb:5400:ff:fe5b:c3ff] has quit [Changing host] 09:36 -!- sipa [~pw@unaffiliated/sipa1024] has joined #bitcoin-core-dev 09:37 -!- JackH [~laptop@46.231.18.66] has quit [Remote host closed the connection] 09:51 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 09:54 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Client Quit] 10:26 -!- promag [~joao@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:26 -!- darawk [~textual@2605:e000:1303:91:30ff:485:da03:d796] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 10:27 -!- handlex [~handlex@2804:14c:658f:4ac1:e1e0:d976:f987:eabc] has joined #bitcoin-core-dev 10:28 -!- promag [~joao@bl22-247-244.dsl.telepac.pt] has quit [Client Quit] 10:33 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 10:34 -!- handlex [~handlex@2804:14c:658f:4ac1:e1e0:d976:f987:eabc] has quit [Ping timeout: 240 seconds] 10:44 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 10:58 -!- _flow_ [flow@star.geekplace.eu] has quit [Quit: WeeChat 1.7.1] 10:58 -!- darawk [~textual@76.79.73.19] has joined #bitcoin-core-dev 11:00 < sipa> meeting? 11:00 < instagibbs> in an hour? 11:00 < sipa> oops, in an hour 11:01 < instagibbs> :) thanks for reminder though, completely forgot 11:01 -!- nakaluna [~nakaluna@177.141.154.83] has quit [Ping timeout: 248 seconds] 11:02 < sipa> yes, i didn't actually think it was meeting time, just wanted to give a veiled reminder 11:02 < instagibbs> so humble 11:05 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Plugging out.] 11:08 < gmaxwell> do we have a editable web doc for release notes again? 11:08 < sipa> unsure 11:12 < jonasschnelli> wumpus: https://github.com/bitcoin/bitcoin/pull/10870#discussion_r128546723, .. what do you think about not doing the URL encode 11:12 < jonasschnelli> The allowed wallet characters would not require an urlencode... 11:12 < wumpus> jonasschnelli: well you do an URL decode at the other side, so I think that'd potentially result in problems 11:13 < jonasschnelli> wumpus: look at SAFE_CHARS_FILENAME 11:13 < wumpus> better to keep it symmetrical just in case, even if not strictly needed for what we see now 11:13 < jonasschnelli> I though because its a temp fix and the URI encode/decode (atm) do nothing-. 11:13 < sipa> it may do something later 11:13 < sipa> i don't think it hurts to have it 11:13 < wumpus> I have some terrible experiences with escaping if not very carefully taking care of on both sides 11:14 < jonasschnelli> Yes. Okay. Then lets keep it. 11:14 < jonasschnelli> https://github.com/bitcoin/bitcoin/pull/10870#discussion_r128546723 must be removed (replaced) once 0.15 is fixed. 11:17 < jonasschnelli> whats the long term solution for wallet arguments like -usehd in conjunction with multiwallet? 11:17 < jonasschnelli> A createwallet RPC? 11:18 < sipa> i think so 11:18 < wumpus> yes - dynamically loading/unloading and creating wallets should be possible at some point 11:19 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 11:19 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 11:19 < jonasschnelli> but if you would create a wallet, would it be automatically loaded next start? (== have wallet>s<.dat file somewhere that keeps track of wallets to load)? 11:20 < wumpus> I don't thikn so 11:20 < jonasschnelli> Assume you use Qt and create a wallet. 11:20 < jonasschnelli> You don't want to add a -wallet= to your config file 11:20 < jonasschnelli> But Qt may be different 11:20 < jonasschnelli> (QSettings) 11:20 < wumpus> well, just add a menu option "load wallet" 11:20 < sipa> i guess qt can have modifiable settings that include the wallets to load 11:21 < wumpus> but yes, qt has a dynamic settings mechanism 11:21 < wumpus> it could use that 11:21 < jonasschnelli> Not auto-loading RPC created wallets can be cumbersome if one uses pruning. 11:22 < wumpus> yes, maybe, I think it's something to worry about later 11:23 < wumpus> there's no reason bitcoind couldn't have a dynamic settings mechanism, with some configuration that automatically gets re-loaded on next run, for example the bitcoin-rw.conf idea 11:29 -!- jtimon [~quassel@102.30.134.37.dynamic.jazztel.es] has quit [Ping timeout: 255 seconds] 11:29 < bitcoin-git> [bitcoin] laanwj pushed 6 new commits to master: https://github.com/bitcoin/bitcoin/compare/7c2400cb8ab7...16240f43a550 11:29 < bitcoin-git> bitcoin/master 4d50f38 Pieter Wuille: Support multi-block SHA256 transforms... 11:29 < bitcoin-git> bitcoin/master 2991c91 Pieter Wuille: Add SHA256 dispatcher 11:29 < bitcoin-git> bitcoin/master c1ccb15 Pieter Wuille: Add SSE4 based SHA256 11:29 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 11:29 < bitcoin-git> [bitcoin] laanwj closed pull request #10821: Add SSE4 optimized SHA256 (master...20170713_shasse) https://github.com/bitcoin/bitcoin/pull/10821 11:35 < sipa> \o/ 11:36 < instagibbs> jnewbery, gmaxwell re:unlock of wallet, one issue I see is that we have no way(?) of unlocking the wallet as bitcoind startup argument, so if the user hits the minimum they will be stuck aside from heroically fast fingers 11:36 < gmaxwell> (so bystanders aren't confused, thats defaulted to off, enabled with a configure flag, in master) 11:36 < gmaxwell> instagibbs: yea, it's ugly. 11:36 < sipa> instagibbs: it's annoying... we effectively have no means of recovery 11:36 < instagibbs> at a minimum, should the wallet.dat get copied and backed up temporarily? 11:37 < instagibbs> upon any rescan 11:37 < sipa> but i do think that it's better than the alternative (which is making the state even harder to recover from, with also no means of recovery) 11:37 < instagibbs> at least allow the user to take the older wallet.dat to some other software 11:37 < instagibbs> sipa, im sorry what's the worse idea of the two? 11:37 < instagibbs> not scanning forward and missing funds? 11:37 < gmaxwell> sipa: if it just won't start syncing with the wallet emptied and locked.. then you could unlock at your leasure. 11:38 < sipa> instagibbs: well if you don't stop, it means your wallet will go further out of sync with the chain, which may force you to do a full reindex later (if you're pruning) 11:38 < sipa> gmaxwell: yes, if we had support for stopping sync without shutdown, absolutely 11:38 < instagibbs> oh, stop syncing wallet but not chain, didn't know what you were talking about 11:38 < instagibbs> agreed 11:38 < gmaxwell> sipa: I mean it could shut down still but on restart just not start again. 11:39 < gmaxwell> It's easier to not start than it is to stop it, I think. 11:39 < sipa> gmaxwell: i see, that may be the case yes 11:39 < sipa> instagibbs: no, i mean that's what we're currently doing 11:39 < sipa> instagibbs: the keypool would go out of sync, and you'd keep syncing, making the wallet go out of sync (while not even being aware of it) 11:39 < sipa> so i think stopping when running out is a strict improvement 11:40 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 248 seconds] 11:40 < sipa> but it's far from a complete solution 11:40 < instagibbs> wait it's already doing that? 11:40 < instagibbs> :( 11:40 < instagibbs> ok then 11:40 < BlueMatt> sipa: do you know offhand what the performance difference between the sse4 sha256 and the avx1 sha256 impls are? 11:40 < sipa> BlueMatt: small 11:40 < sipa> instagibbs: that's the problem we're trying to solve, no? 11:40 < instagibbs> sipa, I thought it was adding a "min" level 11:40 < gmaxwell> BlueMatt: AVX1 is a performance disaster on AMD and hardly faster on intel. 11:40 < instagibbs> which is separate from the "total" 11:41 < sipa> instagibbs: i'm confused 11:41 < BlueMatt> gmaxwell: hmm, ok, i was just trying to figure if i should remove the avx1 patch i have in fibre or leave it 11:41 < instagibbs> < 500 of 1000, topup vs 1000 of 1000 topup 11:41 < wumpus> BlueMatt: https://github.com/laanwj/bitcoin/tree/2016_05_sha256_accel readme.md has some benchmarks 11:41 < instagibbs> sipa, I'm probably just horribly confused about how the wallet currently operates 11:41 < wumpus> but yes, on most cpus there's hardly or no difference 11:42 < wumpus> and when there is a big difference it's SLOW 11:42 < BlueMatt> wumpus: ok, so, unless i get some rorx CPUs, just use sse4 and wait till there's shani 11:42 < sipa> shani is awesome 11:42 < instagibbs> sipa, right now the PR makes it shut down when you are below a new argument, default of 500 11:42 < sipa> it's 5.5x faster than sse4 here 11:42 < BlueMatt> lol, nice 11:42 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 11:42 < sipa> sorry, 4.5x 11:42 < wumpus> the rorx implementations are a little bit faster 11:42 < BlueMatt> so, fibre servers will use that in....5 years? 11:43 < wumpus> but yes, -ni is definitely what to go for 11:43 < BlueMatt> yea, I'm just limited by what random cheap hosting providers have available 11:43 < gmaxwell> BlueMatt: broadwell-ep 11:43 < gmaxwell> +Impl | avg | speed% 11:43 < gmaxwell> +------------ | ---------- | -------- 11:43 < gmaxwell> +basic |0.00599851 | 100 11:43 < gmaxwell> +sse4 |0.00396052 | 151 11:43 < gmaxwell> +avx |0.00397483 | 151 11:43 < gmaxwell> +rorx |0.00334802 | 179 11:43 < sipa> BlueMatt: shani makes my reindex to 450k time go from 4900s to 4200s 11:43 < gmaxwell> +rorx_x8ms | 0.00328667 | 183 11:43 -!- name [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev 11:44 < gmaxwell> sipa: do you have a table like that for your system with shani on it? 11:44 < sipa> i had, somewhere 11:44 < sipa> it's probably in your PM history with me 11:45 < sipa> SHA256_32b_avx,4,0.464040040969849,0.464066028594971,0.464053034782410,1670543604,1670636664,1670590134 11:45 < sipa> SHA256_32b_basic,4,0.298919439315796,0.298947453498840,0.298933446407318,1076109714,1076210442,1076160078 11:45 < sipa> SHA256_32b_rorx,6,0.215215563774109,0.216080069541931,0.215623021125793,774776664,777886704,776242368 11:46 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 260 seconds] 11:46 < sipa> SHA256_32b_rorx8,4,0.460553050041199,0.460564017295837,0.460558533668518,1657989792,1658029986,1658009889 11:46 < sipa> SHA256_32b_shani,16,0.064792513847351,0.065104484558105,0.064978063106537,233253936,234375822,233920892 11:46 < sipa> SHA256_32b_sse4,6,0.230213999748230,0.230278015136719,0.230246663093567,828768096,829000080,828886758 11:47 < gmaxwell> Thanks. 11:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 11:48 < gmaxwell> BlueMatt: I assume we'll add rorx and sha-ni right after branching... 11:48 < BlueMatt> gmaxwell: yea, would be cool to not carry patches for that on fibre 11:48 < sipa> that's already with a patch to make the rorx cases use larger CSHA256 buffers, because they process multiple blocks at once faster 11:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:49 < sipa> that patch doesn't affect the performance of others (in fact, it seems to slightly improve it...) 11:49 -!- nakaluna [~nakaluna@2804:14c:104:8078::28] has joined #bitcoin-core-dev 11:49 < gmaxwell> BlueMatt: ISTM you'd be better off with what we have in master than what you have now. (IIRC you're using just the AVX not the rorx one) 11:50 < BlueMatt> gmaxwell: that is correct, yes 11:51 -!- lichtamberg_ [~Adium@80-110-90-15.cgn.dynamic.surfer.at] has joined #bitcoin-core-dev 11:51 -!- lichtamberg_ is now known as Guest19525 11:51 < sipa> i'm afraid we'll need to startup benchmark to determine what sha256 implementation to use :( 11:51 < gmaxwell> I don't see why. 11:52 < sipa> because rorx8 is presumably faster than sse4 on intel, but slower on amd 11:52 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 11:52 < gmaxwell> sipa: well we need to try with the multiblock changes, it wasn't a big change before, but good point. 11:52 < gmaxwell> sipa: though we could simply check for intel and only use it on intel. 11:53 < wumpus> doing a sha256 benchmark at every start seems excessive to me 11:53 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 11:54 < gmaxwell> I doubt we'll have reason to do so. even if rorx8 is faster only on intel, and enough faster to include, fine.. we'll just check the vendor string. 11:54 < sipa> fair 12:00 < achow101> meeting? 12:00 < gmaxwell> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier 12:00 < jonasschnelli> hi 12:00 < instagibbs> hi 12:00 < wumpus> #startmeeting 12:00 < lightningbot> Meeting started Thu Jul 20 19:00:49 2017 UTC. The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 12:00 < cfields> hi 12:01 < achow101> hi 12:01 < wumpus> #topic high priority for review 12:02 < sipa> #10882 needs 0.15 tag? 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/10882 | Keypool topup by jnewbery · Pull Request #10882 · bitcoin/bitcoin · GitHub 12:02 < wumpus> https://github.com/bitcoin/bitcoin/projects/8 has pretty much been cleaned out (only #10652 left), anything new? 12:02 < sipa> otherwise, the things with current 0.15 tag? 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/10652 | Small step towards demangling cs_main from CNodeState by TheBlueMatt · Pull Request #10652 · bitcoin/bitcoin · GitHub 12:02 < gmaxwell> ACK for 10882 0.15 tag 12:02 < wumpus> https://github.com/bitcoin/bitcoin/pulls?q=is%3Aopen+is%3Apr+milestone%3A0.15.0 12:02 < BlueMatt> 10652 can lose its 15 tag 12:03 < BlueMatt> #10758 really wants review sooner rather than later 12:03 < gribble> https://github.com/bitcoin/bitcoin/issues/10758 | Fix some chainstate-init-order bugs. by TheBlueMatt · Pull Request #10758 · bitcoin/bitcoin · GitHub 12:03 < cfields> i'd say #10821 needs high prio review if it's going in for 0.15, though it's got a bunch of ACKs already 12:03 < gribble> https://github.com/bitcoin/bitcoin/issues/10821 | Add SSE4 optimized SHA256 by sipa · Pull Request #10821 · bitcoin/bitcoin · GitHub 12:03 < instagibbs> cfields, it got merged.. 12:03 < jonasschnelli> cfields: it's merged 12:03 < wumpus> 10821 is merged 12:04 < cfields> hah 12:04 < wumpus> there's virtually no regression risk as it's disabled by default 12:04 < kanzure> hi. 12:04 * cfields refreshes 12:05 -!- ovovo is now known as owowo 12:05 < wumpus> ok, added #10758 to project 8, and #10882 to 0.15 12:05 < gribble> https://github.com/bitcoin/bitcoin/issues/10758 | Fix some chainstate-init-order bugs. by TheBlueMatt · Pull Request #10758 · bitcoin/bitcoin · GitHub 12:05 < gribble> https://github.com/bitcoin/bitcoin/issues/10882 | Keypool topup by jnewbery · Pull Request #10882 · bitcoin/bitcoin · GitHub 12:06 < wumpus> #10652 was already untagged for 0.15 2 days ago 12:06 < gribble> https://github.com/bitcoin/bitcoin/issues/10652 | Small step towards demangling cs_main from CNodeState by TheBlueMatt · Pull Request #10652 · bitcoin/bitcoin · GitHub 12:06 < BlueMatt> good :) 12:07 < wumpus> other topics? 12:07 -!- btcdrak [uid239175@gateway/web/irccloud.com/x-yyririgsygqypfzw] has joined #bitcoin-core-dev 12:08 < BlueMatt> Make 0.15 Great Again! 12:08 < achow101> forks! forks! forks! 12:08 < instagibbs> 10882 halting condition 12:08 < gmaxwell> 10882 halting problem. 12:08 < instagibbs> so, there's gotta be something better than "load your wallet in an older bitcoin instance" 12:08 < sipa> i'd like to bring up #10526 12:08 < gribble> https://github.com/bitcoin/bitcoin/issues/10526 | Force on-the-fly compaction during pertxout upgrade by sipa · Pull Request #10526 · bitcoin/bitcoin · GitHub 12:08 < btcdrak> hi 12:08 < instagibbs> oh sorry il lwait for topic 12:09 < wumpus> about 2.5 weeks to go before projected 0.15 split-off 12:09 < wumpus> #topic Force on-the-fly compaction during pertxout upgrade 12:09 < gmaxwell> master is too reliable. 12:09 < sipa> so, the 0.15 per-txout database needs conversion on first startup 12:09 < sipa> this has the risk of leveldb leaving the old tables around 12:10 -!- rhavar [uid237883@gateway/web/irccloud.com/x-sbptlufktlhgtaly] has joined #bitcoin-core-dev 12:10 < sipa> leaving you with a 4.something GB chainstate rather than 2.something 12:10 < wumpus> did anyone see any difference with that merged? 12:10 < sipa> i did - i don't know if anyone else tried 12:10 < sipa> but it's pretty worrying if it doesn't work deterministically 12:11 < wumpus> did it make a difference for you? any idea what happened in my case? 12:11 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 12:11 < sipa> wumpus: no... 12:11 < sipa> it did make a difference for me, yes, as far as i remember 12:12 < sipa> i'll investigate again and rebase 12:12 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:12 < sipa> probably not much else to say 12:12 < wumpus> can anyone else try, please? I think it makes a lot of sense to have it in 0.15, *if* it works :) 12:12 < sipa> agree. 12:12 < sipa> will rebase 12:12 < wumpus> will tag it 12:13 < wumpus> #action test #10526 12:13 < gribble> https://github.com/bitcoin/bitcoin/issues/10526 | Force on-the-fly compaction during pertxout upgrade by sipa · Pull Request #10526 · bitcoin/bitcoin · GitHub 12:13 < gmaxwell> wumpus: I thought there might have been something weird about your test; hardlinked database directories or something 12:13 < wumpus> gmaxwell: not hard-linked directories, just individual files 12:14 -!- jtimon [~quassel@102.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:15 < wumpus> e.g. I use https://gist.github.com/laanwj/3c4614a23e072cbb3d39090da1834a68 to make copies - but not sure how it could cause the problem 12:15 < sipa> i don't see that either 12:15 < wumpus> but sure I could copy the ldb files instead and retry 12:16 < gmaxwell> Unrelated, does anyone have a point of contact with '1Hash' (or whomever was the author of block 476670) 12:16 < gmaxwell> ? 12:16 < wumpus> no, no idea 12:17 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 12:17 < btcdrak> gmaxwell: I do 12:17 -!- name [~name@unaffiliated/aqquadro] has quit [Ping timeout: 248 seconds] 12:18 < gmaxwell> btcdrak: thanks. 12:18 < wumpus> #topic 10882 halting condition 12:19 < jnewbery> instagibbs ? 12:19 < instagibbs> I think users need some sane way of recovering from their wallet hitting topup 12:20 < instagibbs> and their node shutting down, since the user cannot recover using the current software 12:20 < instagibbs> sorry, don't have great solutions, just bringing it up because I'd like it merged 12:21 < instagibbs> (for encrypted wallets, obviously) 12:21 < gmaxwell> My suggestion is the although stoping the sync was hard, preventing it from starting may be easy. 12:22 < gmaxwell> so if you start with a locked tip-behind wallet, that doesn't have enough keys, it could just not start the sync until unlocked. 12:22 < gmaxwell> but I haven't investigated. 12:22 < wumpus> sounds good to me 12:22 < gmaxwell> instagibbs: Sipa's point was that an unrecoverable always shuts down state is STILL better than what we do now. 12:23 < gmaxwell> because you at least won't end up with a silently screwed up wallet. 12:23 < jnewbery> There are a couple of solutions that I hope we could get into v0.15.1 : dynamic loading of wallets with the option to unlock on load (#10740) and a standalone wallet tool with option to topup (#8745) 12:23 < gribble> https://github.com/bitcoin/bitcoin/issues/10740 | [WIP] [wallet] dynamic loading/unloading of wallets by jnewbery · Pull Request #10740 · bitcoin/bitcoin · GitHub 12:23 < gribble> https://github.com/bitcoin/bitcoin/issues/8745 | [PoC] Add wallet inspection and modification tool "bitcoin-wallet-tool" by jonasschnelli · Pull Request #8745 · bitcoin/bitcoin · GitHub 12:23 < instagibbs> gmaxwell, mmm sure, conveying actionable info is still a requirement, though this may be off topic for meeting 12:23 < wumpus> dynamic loading is a feature, that won't make it into 0.15.1 12:24 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 12:25 < wumpus> (but will to 0.16, ofc) 12:25 < instagibbs> jnewbery, oh optional unlock on load, nice, will look 12:26 < jnewbery> it's not in 10740 yet, but hopefully not too difficult to add 12:26 < instagibbs> ok, well if it's not super pressing to anyone else, whatever. I don't run crypted anyways :) 12:27 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:27 < wumpus> suddeny crashing on startup w/ the wallet effectively being unusable is unacceptable at least 12:27 < gmaxwell> I think it's preferable to current behavior where the wallet is effectively silently corrupted. 12:28 < BlueMatt> well its fixable with rescan 12:28 < sipa> BlueMatt: no 12:28 < sipa> it'll fail to load 12:28 < instagibbs> sipa, ? 12:28 < BlueMatt> i was responding to greg's "silently corrupted" comment 12:28 < sipa> oh, ok 12:28 < wumpus> forcing a rescan would be somewhat better 12:28 < wumpus> but just crashing will lead people to do things like salvagewallet and worse 12:28 < instagibbs> nvm 12:29 < gmaxwell> BlueMatt: fixable somehow doesn't mean not silently corrupted though. since it's silent you won't know to rescan. 12:29 < gmaxwell> wumpus good point. 12:29 < gmaxwell> in any case, lets see what we can do with the PR. 12:29 < BlueMatt> fair 12:29 -!- tiagotrs [~tiago@pD9FD6682.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:29 < gmaxwell> (there were people running salvage wallet in response to the 50/100 warning... :( :( ) 12:29 < BlueMatt> holy what the fuck 12:29 < gmaxwell> Humans. 12:30 < wumpus> yes, at least if it crashes it should tell something actionable to do, not just leave the user to dry 12:30 < jnewbery> Yes, the current error message is "Error: Keypool is too small. Shutting down" 12:30 < jnewbery> which isn't helpful enough 12:30 < instagibbs> startingly vague 12:30 < wumpus> not helpful at all 12:30 < instagibbs> salvagewallet may seem reasonable in response 12:30 < wumpus> they'll try providing a larger -keypool 12:30 < wumpus> which doesn't help 12:30 < instagibbs> "my keys disappeared!" 12:30 < gmaxwell> Any time we create a warning or an error condition that a user can't suppress a few people will do increasingly insane things to try to get it to go away. 12:31 < jnewbery> suggested action for user could be: set "-keypoolmin to 0 and then rescan"? 12:31 < wumpus> yes, 'core nuked my wallet!' 12:31 < sipa> jnewbery: and unlock beforehand 12:31 < gmaxwell> jnewbery: no, that'll just corrupt their wallet. (they'll end up scanning past the end) 12:31 < gmaxwell> they need to unlock before. 12:31 < wumpus> ideally this would just be automated 12:31 < wumpus> if there is a course of recovery 12:32 < jnewbery> ok: "set -keypoolmin to 0, unlock wallet, rescan" 12:32 < jtimon> my keypool is too small? isn't this just a warning because I resuse addresses and they want me to create more new ones? 12:32 < gmaxwell> I guess you can keypoolmin, restart, unlock, and restart with rescan. 12:32 < jtimon> sorry, bad joke 12:32 < gmaxwell> or we find out if we can just suppress the scanstart until unlock, then it just needs to nag you to unlock. 12:33 < wumpus> would be nice 12:33 < instagibbs> if error messages are more helpful, and there is a manual method of recovery, I'm fine with it for now 12:33 < wumpus> sure 12:33 -!- ayy1337|2 [~kvirc@110.140.15.24] has joined #bitcoin-core-dev 12:33 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 12:33 < wumpus> if this is a rare condition, and explaining what to do is easier than automating it, that would be acceptable for 0.15 12:34 < jnewbery> ok, I'll improve the error message. PR could still do with lots of review 12:34 < instagibbs> Great! 12:34 < sipa> note that all of this can only ever occur when restoring a wallet backup in the first place 12:34 < wumpus> #action review #10882 12:34 < gribble> https://github.com/bitcoin/bitcoin/issues/10882 | Keypool topup by jnewbery · Pull Request #10882 · bitcoin/bitcoin · GitHub 12:35 < wumpus> the more important not to scare people with unrecoverable errors 12:35 -!- unholymachine [~quassel@2601:8c:c003:9f16:e18d:5bfe:3c1:754f] has quit [Remote host closed the connection] 12:36 < gmaxwell> if people can't tell what to do in order to get rid of the error, they'll do something dangerous eventually, after trying a few safe but unsuccessful things. 12:36 < gmaxwell> I wonder how many people have died due to blinking 12 on VCRs. 12:36 < wumpus> they'll escalate to worse and worse things 12:36 < wumpus> heh 12:36 -!- unholymachine [~quassel@2601:8c:c003:9f16:5524:e1a:7af4:87f0] has joined #bitcoin-core-dev 12:38 < sipa> well improving the error message at least would be a start 12:38 < wumpus> yes, that would be good 12:39 < sipa> but i agree more is needed 12:39 < jnewbery> It's a shame all the wallet initialization stuff is so coupled to node initialization. Hopefully we can make some good progress with that in 0.16. That'd make issues like this a lot easier to deal with. 12:39 < sipa> jnewbery: yeah 12:39 < wumpus> it is a shame indeed 12:40 < wumpus> although it's better than it used to be 12:40 < wumpus> but both multiwallet and this are good reasons to make further progress with it in 0.16 12:41 < wumpus> any other topics? 12:43 < wumpus> ... I guess not, we can end the meeting early 12:44 < wumpus> #endmeeting 12:44 < lightningbot> Meeting ended Thu Jul 20 19:44:01 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 12:44 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-07-20-19.00.html 12:44 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-07-20-19.00.txt 12:44 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-07-20-19.00.log.html 12:44 < instagibbs> "activate segwit" maybe not so much of a joke this time :) 12:44 < sipa> may be the fork be with you 12:44 < sipa> always 12:45 < wumpus> it was never a joke :) 12:45 < cfields> instagibbs: whew, good thing we don't have to talk about a UASF to activate BIP91 :p 12:46 < instagibbs> we still have time! 12:46 < kanzure> should there be a reorgs warning about bip91 and possible partial activation 12:46 < kanzure> ? 12:46 < instagibbs> bitcoincore.org could have something like bitcoin.org's warning 12:46 < instagibbs> btcdrak, ? 12:47 < Chris_Stewart_5> kanzure: that is what I was wondering too 12:47 < kanzure> the bitcoin.org warning was about aug1? 12:47 < instagibbs> oh right 12:47 < kanzure> well i don't know. 12:47 < gmaxwell> premature. 12:47 < gmaxwell> we should look again a day after 91 lockin. 12:47 < kanzure> is there signalling during the lock in period? 12:47 < gmaxwell> it may be at that point ~100% hashrate is setting bit 1 and there will be little reason to warn more. 12:47 < sipa> bip9 specifies that there should 12:48 < kanzure> well okay then. 12:48 < jtimon> sipa: but it is not required, is it? 12:48 < gmaxwell> if its still 50% hashrate setting bit1 at that point, there will need to be a warning. 12:48 < sipa> jtimon: it is not consensus enforced 12:49 < btcdrak> instagibbs: sorry battery died 12:49 -!- Murch [~murch@96.82.80.28] has joined #bitcoin-core-dev 12:50 < jtimon> I don't see why specify that then, it doesn't make any difference, does it? not even the warnings need it, do they? 12:51 < sipa> jtimon: it's helpful to be able to observe how the adoption goes 12:51 < jtimon> oh, I see 12:55 -!- tiagotrs [~tiago@pD9FD6682.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 12:56 < instagibbs> how do I trigger a rescan inside -cli?(outside of importing a key/addr...) 12:57 < instagibbs> sorry for #bitcoin level q, testing 12:57 -!- name [~name@93-44-136-150.ip97.fastwebnet.it] has joined #bitcoin-core-dev 12:57 -!- name [~name@93-44-136-150.ip97.fastwebnet.it] has quit [Changing host] 12:57 -!- name [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev 12:58 < jonasschnelli> instagibbs: impossibke 12:58 < sipa> isn't there a rescanchain RPC? 12:58 < sipa> or was that in an unmerged PR? 12:58 < instagibbs> so... I have to import a junk key to recover? oh boi 12:58 < jonasschnelli> https://github.com/bitcoin/bitcoin/pull/7061 12:58 < jonasschnelli> But unmerged 12:58 -!- aqquadro [~name@93-44-136-150.ip97.fastwebnet.it] has joined #bitcoin-core-dev 12:59 < sipa> oh 12:59 -!- aqquadro [~name@93-44-136-150.ip97.fastwebnet.it] has quit [Remote host closed the connection] 12:59 < jonasschnelli> I think RPC makes much more sense then -argument 12:59 < jonasschnelli> Will rebase soon 12:59 -!- name [~name@unaffiliated/aqquadro] has quit [Client Quit] 13:00 -!- aqquadro [~name@93-44-136-150.ip97.fastwebnet.it] has joined #bitcoin-core-dev 13:00 -!- aqquadro [~name@93-44-136-150.ip97.fastwebnet.it] has quit [Changing host] 13:00 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev 13:02 < instagibbs> ah! walletpassphrase calls topup, and rescan works. Ok. 13:05 -!- ulrich [b18763a7@gateway/web/freenode/ip.177.135.99.167] has joined #bitcoin-core-dev 13:09 -!- ulrich [b18763a7@gateway/web/freenode/ip.177.135.99.167] has quit [Client Quit] 13:12 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 246 seconds] 13:19 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 13:22 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 255 seconds] 13:27 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 13:27 < Guest19525> shouldnt there be a better warning for "“unknown block versions being mine” 13:27 < Guest19525> ? 13:30 -!- JackH [~laptop@188.204.181.234] has joined #bitcoin-core-dev 13:32 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Quit: Leaving] 13:33 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 255 seconds] 13:46 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 268 seconds] 13:46 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 13:48 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 14:08 < jnewbery> wumpus: Any chance of #10604 being tagged 0.15? 14:08 < gribble> https://github.com/bitcoin/bitcoin/issues/10604 | [wallet] [tests] Add listwallets RPC, include wallet name in `getwalletinfo` and add multiwallet test by jnewbery · Pull Request #10604 · bitcoin/bitcoin · GitHub 14:12 < wumpus> jnewbery: tagged 14:12 -!- RoyceX [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 14:14 < wumpus> (don't know if it's going to be controversial because it adds RPC stuff after the feature freeze, but it seems pretty simple straightforward) 14:15 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 14:15 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds] 14:16 < wumpus> ...and doesn't add translation messages 14:16 < jnewbery> thanks. It had plenty of ACKs while we were settling on the multiwallet API. Trivial rebase 14:17 < sipa> can i haz review on https://github.com/bitcoin-core/leveldb/pull/5 and https://github.com/bitcoin-core/leveldb/pull/10 ? 14:17 -!- RoyceX [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 240 seconds] 14:17 < jnewbery> speaking of translations, #10882 has some translations strings. Is that going to be an issue? 14:17 < gribble> https://github.com/bitcoin/bitcoin/issues/10882 | Keypool topup by jnewbery · Pull Request #10882 · bitcoin/bitcoin · GitHub 14:20 < wumpus> jnewbery: it's increasingly unlikely that they're going to be translated before the 0.15 release 14:24 < jnewbery> ok, but that doesn't block the PR from going in? 14:26 < wumpus> blah according to the release schedule it should, it's too late to change messages, but anyhow having the functionality untranslated is better than not having it at all in this case I guess? 14:29 < wumpus> that's the consideration that needs to be made, the message freeze is there to give the translators time, and thus increase the quality of the translations, but that might not matter for last-minute fixes 14:29 < wumpus> would be stupid to leave the walllet in a broken state just because we can't add a translation emssage 14:30 < jnewbery> ok good. 10882 is now mostly waiting on review. So far I have comments from instagibbs and ryanofsky 14:35 -!- QBcrusher [~QBcrusher@cpe-71-72-246-231.insight.res.rr.com] has joined #bitcoin-core-dev 14:36 -!- QBcrusher [~QBcrusher@cpe-71-72-246-231.insight.res.rr.com] has quit [Client Quit] 14:37 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 255 seconds] 14:39 < bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/6adc3a37324caa07015368bfe8529e1964366eef 14:39 < bitcoin-git> bitcoin/master 6adc3a3 Wladimir J. van der Laan: qt: Periodic translations update... 14:49 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 14:50 -!- CubicEarth [~cubiceart@206.54.118.113] has joined #bitcoin-core-dev 14:55 -!- coredump_ [~quassel@101.165.147.38] has joined #bitcoin-core-dev 15:10 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 246 seconds] 15:20 -!- aqquadro [~name@95.233.20.247] has joined #bitcoin-core-dev 15:20 -!- aqquadro [~name@95.233.20.247] has quit [Changing host] 15:20 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev 15:28 -!- coredump_ [~quassel@101.165.147.38] has quit [Ping timeout: 246 seconds] 15:28 -!- Guest19525 [~Adium@80-110-90-15.cgn.dynamic.surfer.at] has quit [Quit: Leaving.] 15:30 -!- CubicEarth [~cubiceart@206.54.118.113] has quit [Remote host closed the connection] 15:33 -!- corebob [~corebob@2a02:fe0:c150:1a00:8958:6277:6ca3:b2cf] has joined #bitcoin-core-dev 15:37 -!- vicenteH [~user@13.232.15.37.dynamic.jazztel.es] has quit [Ping timeout: 268 seconds] 15:37 -!- CubicEarth [~cubiceart@206.54.118.113] has joined #bitcoin-core-dev 15:46 -!- MeshCollider [~androirc@130.123.29.162] has joined #bitcoin-core-dev 15:48 -!- MeshCollider [~androirc@130.123.29.162] has quit [Client Quit] 15:48 -!- MeshCollider [~MeshColli@130.123.29.162] has joined #bitcoin-core-dev 15:49 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Remote host closed the connection] 15:52 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 255 seconds] 15:53 -!- nakaluna [~nakaluna@2804:14c:104:8078::28] has quit [Ping timeout: 255 seconds] 15:53 -!- lichtamberg_ [~Adium@80-110-90-15.cgn.dynamic.surfer.at] has joined #bitcoin-core-dev 15:53 -!- MeshCollider [~MeshColli@130.123.29.162] has quit [Read error: Connection reset by peer] 15:53 -!- Mesh [~MeshColli@130.123.29.162] has joined #bitcoin-core-dev 15:53 -!- lichtamberg_ is now known as Guest98786 15:53 -!- promag [~joao@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 15:57 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 15:57 -!- btcdrak [uid239175@gateway/web/irccloud.com/x-yyririgsygqypfzw] has quit [Quit: Connection closed for inactivity] 15:58 -!- Mesh [~MeshColli@130.123.29.162] has quit [Ping timeout: 248 seconds] 15:58 -!- Mesh [~MeshColli@130.123.29.5] has joined #bitcoin-core-dev 16:00 -!- MeshCollider [~MeshColli@203-114-132-147.dyn.inspire.net.nz] has joined #bitcoin-core-dev 16:00 -!- MeshCollider [~MeshColli@203-114-132-147.dyn.inspire.net.nz] has quit [Client Quit] 16:02 -!- Mesh [~MeshColli@130.123.29.5] has quit [Read error: Connection reset by peer] 16:11 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 16:12 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 16:14 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 255 seconds] 16:17 -!- coredump_ [~quassel@vpn-qld171.vpnsolutions.com.au] has joined #bitcoin-core-dev 16:24 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 16:32 -!- tucenaber [~tucenaber@unaffiliated/tucenaber] has quit [Quit: Konversation terminated!] 16:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 16:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 16:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 16:49 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 276 seconds] 16:53 -!- CubicEarth [~cubiceart@206.54.118.113] has quit [Remote host closed the connection] 16:53 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 16:53 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 16:58 -!- CubicEarth [~cubiceart@206.54.118.113] has joined #bitcoin-core-dev 17:04 -!- aqquadro [~name@95.233.20.247] has joined #bitcoin-core-dev 17:04 -!- aqquadro [~name@95.233.20.247] has quit [Changing host] 17:04 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev 17:07 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 17:11 < gmaxwell> BIP-91 lock in is now guarenteed (short of a reorg...) 17:18 -!- Guest98786 [~Adium@80-110-90-15.cgn.dynamic.surfer.at] has quit [Quit: Leaving.] 17:23 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 255 seconds] 17:24 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 17:26 -!- ivan [~ivan@unaffiliated/ivan/x-000001] has quit [Quit: lp0 on fire] 17:26 -!- jamesob_ [~james@tempo-automation.static.monkeybrains.net] has quit [Ping timeout: 260 seconds] 17:34 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 260 seconds] 17:45 -!- lichtamberg_ [~Adium@80-110-90-15.cgn.dynamic.surfer.at] has joined #bitcoin-core-dev 17:45 -!- lichtamberg_ is now known as Guest33464 17:46 -!- Murch [~murch@96.82.80.28] has quit [Quit: Snoozing.] 17:47 -!- Guest33464 [~Adium@80-110-90-15.cgn.dynamic.surfer.at] has quit [Client Quit] 17:49 -!- MeshCollider [~MeshColli@130.123.29.138] has joined #bitcoin-core-dev 17:54 -!- CubicEarth [~cubiceart@206.54.118.113] has quit [Remote host closed the connection] 17:59 -!- MeshCollider [~MeshColli@130.123.29.138] has quit [Ping timeout: 255 seconds] 18:01 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 18:04 -!- CubicEarth [~cubiceart@206.54.118.113] has joined #bitcoin-core-dev 18:08 -!- CubicEarth [~cubiceart@206.54.118.113] has quit [Ping timeout: 260 seconds] 18:22 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 268 seconds] 18:46 -!- promag [~joao@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 255 seconds] 19:01 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 260 seconds] 19:02 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 19:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 19:08 < gmaxwell> So with BIP-91 lock in I am of the belief that BIP-148 (esp if modified to start enforcing at the same height coordinated by 91) is a pure marginal mitigation in risk for the network now. 19:10 < bitcoin-git> [bitcoin] brianmcmichael opened pull request #10889: Docs: Run windows build in a clean path (master...docswin) https://github.com/bitcoin/bitcoin/pull/10889 19:16 < luke-jr> would anyone object to an emergency 0.14.3 with BIP148 modified to activate at the same height as BIP91? the downside is that there's only 1-2 days for people to upgrade to it, so we'd need to forego RCs (although most of the code has been tested in the UASF repo) and probably release today or tomorrow.. 19:17 < luke-jr> BlueMatt: morcos ^ 19:17 < luke-jr> (note this would also help avoid the propagation/partitioning risk BIP91 currently has) 19:22 < gmaxwell> I'd like to do something there, at a minimum we could put up a minimal patch. 19:23 < gmaxwell> I believe that if turns out that there was significant false bit-4 signaling the harm minimizing outcome will still be to enforce bit1 signaling; also doing so will protect you from seeing the reorgs this enforcement will create; so it's protective in both ways. 19:26 -!- darawk [~textual@76.79.73.19] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 19:26 -!- darawk [~textual@76.79.73.19] has joined #bitcoin-core-dev 19:27 -!- darawk [~textual@76.79.73.19] has quit [Client Quit] 19:28 -!- KevinPan [~kevinpan@static-ip-25-116-90-219.rev.dyxnet.com] has joined #bitcoin-core-dev 19:32 -!- btcdrak [uid239175@gateway/web/irccloud.com/x-dmrgsqbbpuohvqbb] has joined #bitcoin-core-dev 19:32 -!- goatpig [56f75436@gateway/web/freenode/ip.86.247.84.54] has quit [Quit: Page closed] 19:40 -!- CubicEarth [~cubiceart@host-69-144-45-132.static.bresnan.net] has joined #bitcoin-core-dev 19:41 < BlueMatt> its two days 19:41 < BlueMatt> I'd rather make sure the network has consistent(ish) network rules 19:41 < luke-jr> why observe when we can make sure it does? 19:42 < BlueMatt> it somewhat frightens me that the network doesnt due to 148 nodes, though I'm skeptical there are many of those behind businesses, more users who can/will pause their actions based on activation, and are at least aware enough to have decided to run 148 19:42 < BlueMatt> uhh...we cant? you arent getting every business and user who uses their wallet to upgrade in 2.5 days 19:43 < sipa> BlueMatt: it only needs them to update by end of august 19:43 < BlueMatt> miners decided to take the risk, let them take it, and dont pull everyone into it 19:43 < BlueMatt> sipa: i belive the suggestion was to enable it on the now-locked bip91 activation block 19:43 < luke-jr> BlueMatt: we can drastically improve the situation 19:44 < BlueMatt> im not convinced thats an improvement 19:44 < sipa> that's just way too fast 19:46 < gmaxwell> BlueMatt: consistent rules are out the window already, guarenteed. 19:47 < luke-jr> back in ~45 min 19:47 < BlueMatt> gmaxwell: im more ok with miners having inconsistent rules and users having marginally consistent rules than users being split. ofc I'm hoping 148 users either dont use their wallet in the coming weeks or switch to another node 19:48 < gmaxwell> BlueMatt: so by enforcing you can shield yourself from instability and potentially increase consistency. 19:48 -!- niall_ [~niall@lithium.mailguard.com.au] has joined #bitcoin-core-dev 19:48 < gmaxwell> BlueMatt: going offline isn't an option for everyone. 19:48 -!- niall_ is now known as niallyoung 19:49 < BlueMatt> gmaxwell: i believe that will decrease consistency, not increase 19:49 < BlueMatt> assuming miners are all enforcing 91, its true you will shield yourself from some instability 19:51 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev 19:52 -!- d_t [~d_t@73.189.35.88] has joined #bitcoin-core-dev 19:52 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nwxrfyssmvxpgriw] has quit [Quit: Connection closed for inactivity] 20:04 < gmaxwell> BlueMatt: there are two main protective effects, assuming you can't go offline it protects you from seeing the network forking... the other is that it would damp enforcement instability. 20:04 < gmaxwell> BlueMatt: imagine that there was a lot of false signaling, and at enforcement time half the hashrate doesn't enforce.... 20:05 < gmaxwell> You could imagine (say) slush going "oh crap! network is forked, we're getting orphaned, we're going to stop enforcing 91!" while at the same time antpool goes "oh crap, we're getting orphaned we need to start enforcing 91!!" 20:05 -!- d_t [~d_t@73.189.35.88] has quit [Ping timeout: 255 seconds] 20:05 < gmaxwell> this might take a frightningly large time to converge, and even if it converges fast it means that all users will see a very large reorg. 20:05 < BlueMatt> gmaxwell: I agree with the first part, but given heavily inconsistent enforcement I'm far from convinced it wont just be that china is sleeping and europe is awake and 91 gets turned off :p 20:06 < gmaxwell> Now if you have some major parties and users running this, the outcome is immediately stabilized: the enforcing parties won't stop. 20:06 < gmaxwell> Even better only _some_ users see a big reorg. 20:06 < BlueMatt> that assumes an outcome 20:06 < gmaxwell> It creates it, and in doing so retroactively erases instability. 20:07 < BlueMatt> and given lack of 100% clarity given the timelines involved, I dont think we should assume an outcome, especially given that we cant get upgrades in time for this to be "useful" 20:07 < BlueMatt> i dont believe it does 20:07 < BlueMatt> simply because of the timelines involved 20:07 < BlueMatt> fuck, getting gitian builders dont will take 6 hours and there's a huge chunk of your time already 20:07 < gmaxwell> it wouldn't if not for the fact that that outcome is already in play. 20:08 < gmaxwell> who said anything about gitian even... just putting up an 'officially supported' patch would be protective, allow parties to shield themselves, and contribute to symmetry breaking. 20:09 * gmaxwell dinner 20:10 < BlueMatt> ugh, i need sleep sorry...I'm very much not convinced...I'm skeptical a few 148-but-sooner-activation nodes will meaningfully contribute to symmetry breaking, and even if they did, I'm skeptical that it outweighs the convergance risks as it introduces yet another set of consensus rules into play 20:13 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 20:13 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 20:14 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 20:15 -!- KevinPan [~kevinpan@static-ip-25-116-90-219.rev.dyxnet.com] has quit [Ping timeout: 240 seconds] 20:53 -!- CubicEarth [~cubiceart@host-69-144-45-132.static.bresnan.net] has quit [Remote host closed the connection] 21:02 -!- CubicEarth [~cubiceart@host-69-144-45-132.static.bresnan.net] has joined #bitcoin-core-dev 21:07 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 21:08 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 258 seconds] 21:17 -!- drapetomano [c872f22d@gateway/web/freenode/ip.200.114.242.45] has joined #bitcoin-core-dev 21:20 -!- CubicEarth [~cubiceart@host-69-144-45-132.static.bresnan.net] has quit [] 21:36 < bitcoin-git> [bitcoin] rohythakur opened pull request #10890: added version (master...master) https://github.com/bitcoin/bitcoin/pull/10890 21:39 -!- djbooth007 [6eafbeec@gateway/web/freenode/ip.110.175.190.236] has joined #bitcoin-core-dev 21:47 -!- drapetomano [c872f22d@gateway/web/freenode/ip.200.114.242.45] has quit [Quit: Page closed] 21:52 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 22:03 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:04 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:04 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:04 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:05 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:05 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:06 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has quit [Ping timeout: 248 seconds] 22:06 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:06 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:07 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:07 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:07 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:08 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:08 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:08 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:09 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:09 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:10 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:10 -!- Dyaheon [~Dya@a91-156-192-39.elisa-laajakaista.fi] has joined #bitcoin-core-dev 22:11 -!- jamesob [~jamesob@73.241.180.136] has joined #bitcoin-core-dev 22:11 -!- jamesob [~jamesob@73.241.180.136] has quit [Remote host closed the connection] 22:12 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:12 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:12 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:13 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:13 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:14 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:14 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:15 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:15 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:15 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 22:16 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:20 -!- jamesob [~jamesob@c-73-241-180-136.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 22:36 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 22:49 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 268 seconds] 22:56 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 23:12 -!- alan_baker [~alan_bake@220.250.50.60] has joined #bitcoin-core-dev 23:16 -!- alan_baker [~alan_bake@220.250.50.60] has quit [Ping timeout: 240 seconds] 23:21 -!- alan_baker [~alan_bake@220.250.50.60] has joined #bitcoin-core-dev 23:27 -!- niallyoung [~niall@lithium.mailguard.com.au] has quit [] 23:27 -!- niall_ [~niall@lithium.mailguard.com.au] has joined #bitcoin-core-dev 23:27 -!- niall_ [~niall@lithium.mailguard.com.au] has quit [Client Quit] 23:38 -!- rhavar [uid237883@gateway/web/irccloud.com/x-sbptlufktlhgtaly] has quit [Quit: Connection closed for inactivity] 23:46 -!- JackH [~laptop@188.204.181.234] has quit [Ping timeout: 255 seconds] 23:50 -!- alan_baker [~alan_bake@220.250.50.60] has quit [Ping timeout: 240 seconds]