--- Day changed Mon Oct 02 2017
00:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
00:06 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 258 seconds]     
00:07 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
00:18 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
00:46 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev     
00:54 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev     
00:59 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-umjuqozdsrqxsbkh] has quit [Quit: Connection closed for inactivity]     
01:18 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev     
01:23 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev     
01:24 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
01:29 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 246 seconds]     
01:30 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #bitcoin-core-dev     
01:46 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
01:53 < fanquake> wumpus I have some changes for the Windows builds notes ready, but can't seem to cherry-pick the commit out of 11244. If they push a commit with author info I'll grab that, otherwise will credit them in my commit message. Hopefully we'll have some clarity around the Windows build docs shortly..
02:01 -!- dc0de [~herpdader@p4FEB6609.dip0.t-ipconnect.de] has joined #bitcoin-core-dev     
02:22 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
02:24 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
02:26 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has quit [Ping timeout: 240 seconds]     
02:27 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has joined #bitcoin-core-dev     
02:28 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]     
02:34 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has quit [Ping timeout: 258 seconds]     
02:36 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has joined #bitcoin-core-dev     
02:43 -!- wxxs [~chatzilla@45.248.79.254] has joined #bitcoin-core-dev     
03:10 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
03:11 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]     
03:12 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has quit [Read error: Connection reset by peer]     
03:48 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Excess Flood]     
03:48 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev     
03:49 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fjypfqjqdzsnhbhd] has joined #bitcoin-core-dev     
03:58 < meshcollider> Is there any permission level other than admin which can delete pages
03:58 < meshcollider> "Lead developer" and "Original Client developers" both redirect to a deleted page, so they should be deleted too
03:58 < meshcollider> Oops wrong channel
03:59 < meshcollider> Meant that for the wiki channel lol
04:10 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
04:13 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 258 seconds]     
04:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds]     
04:14 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev     
04:14 -!- Shaun3811 [~shaun@93.109.214.154] has left #bitcoin-core-dev []     
04:14 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev     
04:29 < bitcoin-git> [bitcoin] fanquake opened pull request #11437: [Docs] Update Windows build instructions for using WSL and Ubuntu 17.04 (master...windows-build-1704) https://github.com/bitcoin/bitcoin/pull/11437
04:30 < bitcoin-git> [bitcoin] fanquake closed pull request #11244: Docs: Add extra step to clean $PATH var to strip out windows %PATH% paths. (master...windows_build_fix) https://github.com/bitcoin/bitcoin/pull/11244
04:53 -!- pbase [~pbase@unaffiliated/pbase] has quit [Quit: Leaving]     
05:15 -!- Oda [d5981c54@gateway/web/freenode/ip.213.152.28.84] has joined #bitcoin-core-dev     
05:17 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection]     
05:20 -!- Oda [d5981c54@gateway/web/freenode/ip.213.152.28.84] has quit [Ping timeout: 260 seconds]     
05:26 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds]     
05:28 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
05:28 -!- Oda_Nobunaga [d5981c54@gateway/web/freenode/ip.213.152.28.84] has joined #bitcoin-core-dev     
05:29 -!- Oda_Nobunaga [d5981c54@gateway/web/freenode/ip.213.152.28.84] has left #bitcoin-core-dev []     
05:41 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e542728cde67...c641ccac5bd8
05:41 < bitcoin-git> bitcoin/master bb8376b Matt Corallo: Verify DBWrapper iterators are taking snapshots...
05:41 < bitcoin-git> bitcoin/master c641cca Wladimir J. van der Laan: Merge #11422: qa: Verify DBWrapper iterators are taking snapshots...
05:42 < bitcoin-git> [bitcoin] laanwj closed pull request #11422: qa: Verify DBWrapper iterators are taking snapshots (master...2017-09-leveldb-check-snapshots) https://github.com/bitcoin/bitcoin/pull/11422
05:43 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Ping timeout: 240 seconds]     
05:47 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c641ccac5bd8...10bee0dd4f37
05:47 < bitcoin-git> bitcoin/master d601f16 Anthony Towns: Fix invalid memory access in CScript::operator+=
05:47 < bitcoin-git> bitcoin/master 10bee0d Wladimir J. van der Laan: Merge #11284: Fix invalid memory access in CScript::operator+= (guidovranken, ajtowns)...
05:47 < bitcoin-git> [bitcoin] laanwj closed pull request #11284: Fix invalid memory access in CScript::operator+= (guidovranken, ajtowns) (master...cscript_insert) https://github.com/bitcoin/bitcoin/pull/11284
05:49 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/10bee0dd4f37...557aba6ce7da
05:49 < bitcoin-git> bitcoin/master 49f869f Johnson Lau: Fix bip68-sequence rpc test
05:49 < bitcoin-git> bitcoin/master 557aba6 Wladimir J. van der Laan: Merge #11399: Fix bip68-sequence rpc test...
05:50 < bitcoin-git> [bitcoin] laanwj closed pull request #11399: Fix bip68-sequence rpc test (master...bip68test-1) https://github.com/bitcoin/bitcoin/pull/11399
05:55 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/557aba6ce7da...058c0f996b72
05:55 < bitcoin-git> bitcoin/master 92848e5 João Barbosa: Remove unused fTry from push_lock
05:55 < bitcoin-git> bitcoin/master 058c0f9 Wladimir J. van der Laan: Merge #11432: Remove unused fTry from push_lock...
05:55 < bitcoin-git> [bitcoin] laanwj closed pull request #11432: Remove unused fTry from push_lock (master...2017-08-clean-push-lock) https://github.com/bitcoin/bitcoin/pull/11432
06:00 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev     
06:05 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/058c0f996b72...c5c77bdcc632
06:05 < bitcoin-git> bitcoin/master 3a4401a practicalswift: [Qt] Terminate string *pszExePath after readlink and without using memset
06:05 < bitcoin-git> bitcoin/master c5c77bd Wladimir J. van der Laan: Merge #11193: [Qt] Terminate string *pszExePath after readlink and without using memset...
06:05 < bitcoin-git> [bitcoin] laanwj closed pull request #11193: [Qt] Terminate string *pszExePath after readlink and without using memset (master...null-terminate-after-readlink) https://github.com/bitcoin/bitcoin/pull/11193
06:11 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c5c77bdcc632...339da9ca4143
06:11 < bitcoin-git> bitcoin/master 5ddf560 Jim Posen: script: Change SignatureHash input index check to an assert....
06:11 < bitcoin-git> bitcoin/master 339da9c Wladimir J. van der Laan: Merge #11411: script: Change SignatureHash input index check to an assert....
06:11 < bitcoin-git> [bitcoin] laanwj closed pull request #11411: script: Change SignatureHash input index check to an assert. (master...sighash-bounds-check) https://github.com/bitcoin/bitcoin/pull/11411
06:23 < bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/339da9ca4143...90926db2381d
06:23 < bitcoin-git> bitcoin/master 3336676 Akio Nakamura: Fix getchaintxstats()...
06:23 < bitcoin-git> bitcoin/master 07704c1 Akio Nakamura: Add some tests for getchaintxstats...
06:23 < bitcoin-git> bitcoin/master 90926db Wladimir J. van der Laan: Merge #11021: [rpc] fix getchaintxstats()...
06:23 < bitcoin-git> [bitcoin] laanwj closed pull request #11021: [rpc] fix getchaintxstats() (master...fix_getchaintxstats) https://github.com/bitcoin/bitcoin/pull/11021
06:25 < bitcoin-git> [bitcoin] laanwj closed pull request #10457: Don't use fixed "wallet.bak"-filename during salvagewallet (master...2017/05/rename_bdb) https://github.com/bitcoin/bitcoin/pull/10457
06:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
06:39 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
06:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
06:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
06:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
06:54 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds]     
06:55 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
06:56 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.]     
06:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds]     
06:58 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fjypfqjqdzsnhbhd] has quit [Quit: Connection closed for inactivity]     
07:03 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
07:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
07:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
07:07 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]     
07:15 -!- unholymachine [~quassel@2601:8c:c003:9f16:509c:ff47:326b:6b35] has quit [Remote host closed the connection]     
07:16 -!- unholymachine [~quassel@2601:8c:c003:9f16:387c:55f7:34db:68ee] has joined #bitcoin-core-dev     
07:16 -!- owowo [ovovo@gateway/vpn/mullvad/x-rehsrdmscypapzbh] has joined #bitcoin-core-dev     
07:23 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds]     
07:23 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 248 seconds]     
07:24 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #bitcoin-core-dev     
07:28 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev     
07:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
07:43 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds]     
07:57 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
08:13 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 258 seconds]     
08:38 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-pcgmqgvhytrjwgku] has joined #bitcoin-core-dev     
09:07 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
09:13 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds]     
09:16 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev     
09:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
09:20 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]     
09:22 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
09:27 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
09:29 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev     
09:54 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 246 seconds]     
09:55 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit []     
09:56 -!- timothy [tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!]     
09:59 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 248 seconds]     
10:09 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
10:13 < wxxs> should 0.15 disconnect clients with version string /Satoshi:1.14.4(2X)/ ?
10:15 < andytoshi> there's no point in having an arms race, if btc1 is going to masquerade as core then they'll masquerade as core
10:15 < andytoshi> leaving the situation as-is at least means it's possible to identify them so individuals and businesses can manually patch them out if they cause problems
10:18 < wxxs> so this is btc1 with the signal bit removed?
10:19 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev     
10:22 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
10:29 < BlueMatt> wxxs: yea, btc1 decided to deliberately cause more harm to the network than neccessary, because they felt like trolling, I guess
10:29 < BlueMatt> so if it didnt get disconencted, it was either a pre-version-bit version of btc1, or masquerading
10:29 < BlueMatt> (or core with the version message changed to that)
10:30 < wxxs> ew, I feel violated
10:30 < BlueMatt> trolls gonna troll
10:30 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds]     
10:32 < sipa> i don't think there is any particular problem with them not having the service bit for a while
10:34 < sipa> (up until a bit before the fork, when they'll want preferential peering)
10:35 < BlueMatt> sipa: I dont believe they've implemented any "week before, force service bit on" logic
10:35 < BlueMatt> so that they can maximize network disruption and possible isolate some nodes
10:38 < Murch> Luckily, if the node count stays like this, it'll be likely only disrupt their nodes.
10:42 < BlueMatt> true, but it still seems needlessly stupid...the only reason to have that option is to troll, but, then, that seems to be what 2x is all about
10:43 < Murch> of course it's stupid, but if they're being stupid and only hurting themselves, that's less of an issue than if they were being stupid and hurting others
10:43 < wxxs> wouldn't they rather isolate their own nodes this way? Do the 2X CEOs know what their engineer is doing?
10:44 < BlueMatt> well they're risking it - if some charitable person decides 2x doesnt have enough nodes so spins up some crazy sybil like we've seen with all the previous forks, they could cause issues for both themselves and others
10:48 < gmaxwell> We need bad block interogation.
10:49 < gmaxwell> Whenever we reject a bad block, we should remember it, and try fetching it from every other peer we connect to... and then ban any that serve it to us.
10:49 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
10:49 < gmaxwell> Still won't prevent isolation from s2x nodes entirely but it would make it less bad.
10:49 < BlueMatt> grrr, why didnt they fucking use the hardfork bit
10:51 < gmaxwell> because that would minimize disruption.
10:51 < BlueMatt> trolls gonna troll.....
10:53 < wxxs> provocation?
10:54 < gmaxwell> the whole strategy of s2x is to try to force people to accept their rule change by disrupting everything else.
10:55 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Ping timeout: 258 seconds]     
10:57 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
10:59 < sturles> I suggest to just write a script which periodically scan getpeerinfo for 2x, then limit their bandwidth to a minimum where they will still stay connected.  I used to do that with BU, XT, etc.
11:00 < sturles> They don't seem to thinkt that bandwidth can be a problem to anyone, so it shouldn't bother them.
11:04 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
11:10 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
11:32 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
11:38 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt]     
11:56 -!- jb55 [~jb55@208.98.200.100] has quit [Quit: WeeChat 1.9]     
12:01 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
12:01 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 258 seconds]     
12:09 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 248 seconds]     
12:11 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
12:11 < achow101> gmaxwell: I've been thinking about bad block interrogation. How would you be able to distinguish between they don't have the block, they didn't accept the block, and they're just taking a really long time to respond with the block?
12:12 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev     
12:14 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds]     
12:14 -!- Argo_ [bb704f45@gateway/web/freenode/ip.187.112.79.69] has joined #bitcoin-core-dev     
12:14 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev     
12:15 < andytoshi> probably sufficient to send them a request for it, set a flag somewhere, and then if they ever reply with the block, ban them
12:15 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds]     
12:16 < sipa> it could also be done based on headers
12:16 < sipa> as long as difficulty rule isn't modified, we'll learn about all chains our peers have through the headers
12:19 < gmaxwell> achow101: I don't think we need to.
12:19 < gmaxwell> achow101: we ask for it.  ... and seperately anyone who ever sends it to use gets punted.
12:19 < gmaxwell> we don't even have to track if we asked
12:19 < gmaxwell> though sipa notes doing it through the header is even stronger and simpler.
12:20 < achow101> gmaxwell: well right now we only ban the first person who relays us an invalid block. So I suppose we can just change that to ban anyone who relays us an invalid block regardless of whether we have already seen it
12:20 < achow101> I was already thinking about just using headers. It can all be done in ProcessNewBlockHeaders I think
12:20 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev     
12:21 < gmaxwell> achow101: yes, kind of, but if its burried when they connect they won't send it to us.
12:22 < achow101> gmaxwell: if it's buried, couldn't we imitate IBD?
12:22 < gmaxwell> I don't understand your question.
12:23 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/90926db2381d...f199b8a33d94
12:23 < bitcoin-git> bitcoin/master 634e38c Anditto Heristyo: [Tests] Add Qt GUI tests to Overview and ReceiveCoin Page
12:23 < bitcoin-git> bitcoin/master f199b8a MarcoFalke: Merge #11365: [Tests] Add Qt GUI tests to Overview and ReceiveCoin Page...
12:23 < gmaxwell> I don't think we need to in any case, ejecting any peers that has a header chain with a block we consider invalid is sufficient, and simpler than anything with fetching blocks.
12:23 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11365: [Tests] Add Qt GUI tests to Overview and ReceiveCoin Page (master...Adding-Qt-tests) https://github.com/bitcoin/bitcoin/pull/11365
12:24 < achow101> so we can just ask a peer for the headers starting from block X where block X is invalid to us. If they respond with headers, then ban
12:26 < achow101> by imitating IBD I meant doing the whole fetch 2000 headers thing starting from some block X and seeing if they responded to us with those headers
12:27 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 248 seconds]     
12:28 < gmaxwell> well there are two degress of badness to think about, one is if their best chain contains a block we consider invalid and the other is if they accept a block we consider invalid at all even if its not in their best chain right now.
12:29 < achow101> If a block is not in their best chain, we can't fetch it, no?
12:29 < gmaxwell> we can, if it's not too far outside of it.
12:30 < achow101> but if it is too far outside of the best chain, we can't determine whether they accepted it or not
12:30 < gmaxwell> it avoids a case where it was on their best chain, they offered it to us, we attempted to fetch it... but were too slow.
12:30 < gmaxwell> yes, if it's too far outside we can't, indeed.
12:30 < achow101> unless we give them the block, but that risks getting us banned
12:31 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Ping timeout: 258 seconds]     
12:31 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f199b8a33d94...8ddf60db7ad6
12:31 < bitcoin-git> bitcoin/master 1088b53 Gregory Sanders: add functional test for mempoolreplacement command line arg
12:31 < bitcoin-git> bitcoin/master 8ddf60d MarcoFalke: Merge #11407: [tests] add functional test for mempoolreplacement command line arg...
12:31 < gmaxwell> But I don't think the too far limit is that limiting. 
12:32 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11407: [tests] add functional test for mempoolreplacement command line arg (master...testmempoolreplacearg) https://github.com/bitcoin/bitcoin/pull/11407
12:33 < achow101> the too far limit is one month.
12:37 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev     
12:37 < achow101> I guess we can't cover the case where we are connected to an isolated peer that is following different consensus rules
12:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
12:45 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev     
12:46 -!- r251d [~r251d@65.199.22.139] has joined #bitcoin-core-dev     
12:46 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev     
12:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
12:51 < r251d> If a set of nodes wanted to protect against a 51% attack, they might collectively decide to invalidateblock on an attacking block. The coordination may be difficult, deciding whether a block constitutes an attack, but it may be helpful for the defending nodes to be able to reconsiderblock in some cases. In that scenario, the temporarily invalidated block may not be a bannable offense for nodes who
12:51 < r251d>  relayed it.
12:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
12:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
12:55 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev     
13:01 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev     
13:03 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds]     
13:07 < gmaxwell> r251d: if it isn't your defence won't work well, because you'll invalidate that block but be surrounded by nothing but peers that have it, and so not even hear about the other chain.
13:07 -!- Oda_nobunaga [5a4fd092@gateway/web/freenode/ip.90.79.208.146] has joined #bitcoin-core-dev     
13:07 < gmaxwell> so you're actually giving an argument for the importance of kicking off peers that have a block you consider invalid in their best chain.
13:08 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev     
13:08 < Oda_nobunaga> Yesterday Adam talked about "bunker mode" on slack: that is, if I understood well, a way to build the chain by selecting blocks sort of manually, and invalidating blocks from a suspected 51% attack?
13:09 < r251d> I was hoping that a hypothetical "bunker mode" could keep connections with nodes that have alternative tips until social coordination decided on the best one to follow.
13:10 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds]     
13:10 < Oda_nobunaga> I was also wondering about the reaction to a 51% attack. How long would a PoW change take? Would we be talking hours or weeks?
13:10 < Oda_nobunaga> I'm afraid that Jihan might use the threat of a reorg attack (very implicitly worded of course) as a way to sap confidence in the original chain, and scare people away from investing in it - thus deflating its price and possibly chasing more hash power away. The mere threat of an attack could work almost as well as an actual one.
13:12 < sipa> please keep this channel about software development
13:13 < Oda_nobunaga> Sorry, I was eager to get devs opinions about this. Perhaps this would be more suited for #bitcoin
13:13 < mryandao> i was wondering if it would be possible to remove the libboost dependency for bitcoin-cli so it is possible to compile separately on a lightweight node with minimal libs.
13:15 -!- r251d [~r251d@65.199.22.139] has quit [Quit: Mutter: www.mutterirc.com]     
13:17 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]     
13:17 < achow101> mryandao: what does bitcoin-cli use boost for?
13:17 < mryandao> that's exactly my question a week ago
13:17 < mryandao> if you run `ldd` on it, you will see that bitcoin-cli requires libboost
13:18 < achow101> oh, its for thread management
13:20 -!- Oda_nobunaga [5a4fd092@gateway/web/freenode/ip.90.79.208.146] has quit [Quit: Page closed]     
13:21 < achow101> and some of the things it includes requires boost
13:22 < mryandao> ok, i see.
13:23 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
13:25 -!- Argo_ [bb704f45@gateway/web/freenode/ip.187.112.79.69] has quit [Quit: Page closed]     
13:26 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds]     
13:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
13:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
13:42 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit []     
13:42 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
13:47 < bitcoin-git> [bitcoin] sipsorcery opened pull request #11438: Updated Windows build doc for WSL/Xenial workaround (master...wslbuilddoc) https://github.com/bitcoin/bitcoin/pull/11438
13:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]     
13:51 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
13:52 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev     
13:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
13:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
13:54 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev     
14:03 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-zjtstcuwryikdaxm] has joined #bitcoin-core-dev     
14:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
14:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
14:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
14:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
14:10 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev     
14:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds]     
14:15 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Ping timeout: 240 seconds]     
14:30 < bitcoin-git> [bitcoin] promag opened pull request #11439: [test] Refactor ZMQ test to use one address per notification type (master...2017-10-clean-zmq-test) https://github.com/bitcoin/bitcoin/pull/11439
14:33 < promag> BlueMatt: ^
14:33 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Read error: Connection reset by peer]     
14:34 < BlueMatt> promag: heh, I removed that commit
14:36 < BlueMatt> promag: https://github.com/bitcoin/bitcoin/pull/11439#issuecomment-333672328
14:41 < promag> BlueMatt: replied
14:43 < BlueMatt> promag: does zmq not give you reliable order?
14:45 < promag> AFAIK no, messages can be dropped
14:45 < promag> but that's not the issue
14:45 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit []     
14:46 < promag> the issue is that if we change the publishing order then we break the test (and other clients
14:46 < BlueMatt> yes, thats my point, in common usage it seems to me that a client can vaguely rely on ordering
14:46 < promag> that's why you needed to fix in the old commit
14:46 < BlueMatt> who's to say clients dont rely on ordering today
14:46 < BlueMatt> there are no docs, there is no API, so clients could be doing who-knows-what
14:47 < promag> right
14:47 < BlueMatt> a client would be entirely justified in assuming the ordering was part of the API
14:47 < BlueMatt> so if we want to change that, we need to a) write some docs to begin with, b) document the change, with sufficient notice
14:47 < BlueMatt> and until then, imo, the test should test order
14:48 < BlueMatt> I realized this later based on sdaftuar complaining the lack of API, hence the commit removal
14:48 < promag> So atm the PR is to prevent the test to fail and to be a better example on how to subscribe notifications
14:48 < promag> > a client would be entirely justified in assuming the ordering was part of the API -- why?
14:48 < BlueMatt> why not?
14:48 < BlueMatt> it works, doesnt it?
14:49 < BlueMatt> well my point is the test *should* fail if the interface changes
14:49 < BlueMatt> a client, in the absense of any documentation whatsoever, would be justified in assuming the ordering was part of the api, imo
14:50 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...]     
14:53 -!- wraithm [~wraithm@unaffiliated/wraithm] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]     
14:53 < promag> BlueMatt: it works, doesnt it? -- so? it's not documented as such it shouldn't be used as if it was
14:54 < promag> if the interface changes - you didn't change the interface
14:54 < BlueMatt> well then I'd prefer to rip out the whole thing...it wasnt documented so you shouldnt rely on it being there :p
14:54 < promag> you changed some internals that changed the publishing order, but nothing is said about the order, only about the message contents
14:55 < BlueMatt> nothing is said about the message contents, either
14:55 < BlueMatt> nothing is said about any part of the interface
14:55 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 248 seconds]     
14:55 < BlueMatt> its wholly undocumented
14:55 < promag> doc/zmq.md ?
14:56 < BlueMatt> sorry, it does say that you'll get messages, but it doesnt say why
14:56 < BlueMatt> is hashblock just for new tips?
14:56 < BlueMatt> or all blocks
14:57 < BlueMatt> should you get a hashblock for something that was disconnected? what about something removed from your mempool?
14:57 < promag> tip     
14:57 < BlueMatt> err, sorry, guess it does mention tip, doenst mention mempool, though, and in this case were talking about mempool
14:57 < BlueMatt> those docs are useless
14:58 < BlueMatt> it has 4 types of things, and afaict only mentions what happens in one of them
14:59 < promag> so you suggest to improve the docs?
14:59 < BlueMatt> see, eg, #9371
14:59 < gribble> https://github.com/bitcoin/bitcoin/issues/9371 | Notify on removal by morcos · Pull Request #9371 · bitcoin/bitcoin · GitHub
15:00 < BlueMatt> I'd love to see someone actually document what in the hell the zmq stuff actually does, yes
15:00 < BlueMatt> once we have such a doc, I think it'd be reasonable to deprecate certain behaviors being normative, eg the ordering restrictions
15:00 < promag> later jonasschnelli added sequence which I believe is not documented (sorry if it is)
15:00 < BlueMatt> its mentioned, but only in passing, no what the fuck format it has
15:02 < promag> agree BlueMatt, I'll improve the doc
15:02 < BlueMatt> I dont think we should remove ordering for a release or two, however
15:04 < promag> I can split the PR in 2 - cleanup + remove-ordering
15:04 < promag> create a 3rd improve-doc
15:05 < BlueMatt> I dont think we should remove ordering until 0.17, assuming we have docs noting it is non-normative in 0.16
15:05 < BlueMatt> (also cause there is no rush)
15:05 < BlueMatt> we have no reason to need to remove ordering, and probably will keep the same ordering requirements in validationinterface
15:06 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds]     
15:06 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Quit: May the Shwartz be with you]     
15:08 < promag> From the client perspective, it should not rely on the order not because of bitcoind but because of zmq
15:08 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev     
15:09 < BlueMatt> are you sure zmq doesnt provide consistent ordering?
15:09 < esotericnonsense> zmq is only guaranteed to preserve order over TCP
15:09 < BlueMatt> you may lose messages but I'd assume in practice its ordered
15:09 < BlueMatt> heh, ok, so in common-usage its guaranteed to preserve order :p
15:09 < esotericnonsense> and only in the simple case with no proxies that may cause different paths to be taken by different messages
15:09 < BlueMatt> <BlueMatt> heh, ok, so in common-usage its guaranteed to preserve order :p
15:10 < esotericnonsense> hehe
15:10 < promag> > probably will keep the same ordering requirements in validationinterface - where is this tested (beside in zmq)?
15:11 < BlueMatt> stuff that calls into wallet is required, mostly
15:11 < BlueMatt> depends on which calls zmq uses, I dont recall
15:20 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]     
15:20 < BlueMatt> do we have a standard for adding options to rpc calls now? we have named args, but also lots of stuff in options{} objects....do we prefer one for new things?
15:27 < sipa> i prefer using named arguments over options - easier or equally easy to use
15:27 < sipa> unless it's options that apply to only some arguments (like per-output options in createrawtransactions eg)
15:28 < bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11440: Fix validationinterface build on super old boost/clang (master...2017-10-cblock-validationinterface) https://github.com/bitcoin/bitcoin/pull/11440
15:28 < gmaxwell> results in a terrible commandline expirence either way.
15:30 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
15:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
15:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
15:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
15:37 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
15:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
15:54 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Read error: Connection reset by peer]     
15:58 -!- _flow_ [flow@star.geekplace.eu] has quit [Ping timeout: 246 seconds]     
15:58 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!]     
16:06 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 248 seconds]     
16:13 -!- _flow_ [flow@star.geekplace.eu] has joined #bitcoin-core-dev     
16:17 -!- dc0de [~herpdader@p4FEB6609.dip0.t-ipconnect.de] has quit [Quit: leaving]     
16:18 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
16:24 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit []     
16:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
16:40 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 248 seconds]     
16:46 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev     
16:55 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-pcgmqgvhytrjwgku] has quit [Quit: Connection closed for inactivity]     
17:01 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
17:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
17:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
17:21 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]     
17:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds]     
17:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
17:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
17:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]     
17:37 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
17:51 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev     
17:55 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
17:58 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev     
18:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
18:17 < luke-jr> sipa: then adapt named arguments to work nicer with options? the current way is a kludge, and we shouldn't let named arguments detract from a good non-named interface
18:19 < sipa> luke-jr: care to elaborate?
18:28 < kallewoof> (JSON and *sh don't really go well together as it is. '{"address":"$myaddr"}--- oh wait I need to use " or $ won't resolve. "{'addr... oh wait JSON won't allow apos strings.. gaah... etc.)
18:29 < esotericnonsense> is it possible to explicitly specify named arguments in json queries? I dislike knowing that when writing an API, the commands could change out from under me and I wouldn't know. (yes, modifications to the RPC calls are designed such that it shouldn't happen, but it's still unnerving)
18:29 < sipa> esotericnonsense: yes, JSON RPC supports named arguments
18:29 < sipa> where the arguments are not an array but an object
18:30 < esotericnonsense> for all calls? that's awesome. argh, /me goes off to read the manual.
18:30 < sipa> yes, for all calls
18:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds]     
18:31 < sipa> (since 0.13 or 0.14 it's implemented in bitcoin core, i believe)
18:33 < luke-jr> sipa: tacking on a bunch of optional ordered arguments is unwieldy and a terrible interface; for such cases, an options object makes sense
18:34 < sipa> luke-jr: an options object is also an unwieldy and terrible interface
18:36 < sipa> (see kallewoof's comment above)
18:37 < luke-jr> sipa: that's an issue with sh, not JSON-RPC
18:37 < sipa> luke-jr: programmatic use of JSON-RPC should just upgrade to named arguments, IMHO
18:37 < sipa> safer, clearer, and more flexible in every way
18:40 < sipa> the only downside to named arguments i think is in CLI usage on the command line, where "-named ... name1= ... name2= ..." need to be added
18:41 < luke-jr> some languages don't even support named arguments
18:42 < sipa> then write a wrapper - invoking that will at worst be as hard as constructing the options object you'd otherwise pass
18:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
18:47 < esotericnonsense> hey, so it does. https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs only mentions positional parameters. I'll make a pull request.
18:48 < luke-jr> sipa: this is not an argument to have a crappy interface
18:49 < sipa> luke-jr: indeed it isn't, but i know of no solution to that problem
18:49 < sipa> having many parameters to an RPC will always be annoying to use
18:49 < luke-jr> the options object is the solution we've used so far
18:50 < sipa> and i claim that named arguments are in no way worse than an options object
18:50 < sipa> (in some ways it's equally terribly, though)
18:51 < luke-jr> even if it were true, that's irrelevant, since the topic is the ordered params API
18:51 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
18:51 < sipa> i don't think that's a very interesting topic
18:52 < sipa> when a better alternative exists
18:56 < sipa> in every situation where you'd call an RPC with an options object, have JSON-RPC wrapper that takes a JSON object as argument, and treats its key-value pairs as names and values of named arguments in a call
18:58 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]     
19:03 < esotericnonsense> submitted as #1828 on the bitcoin.org repo. probably just me that's missed it having not been around for the releases but it's nice to have in there.
19:03 < gribble> https://github.com/bitcoin/bitcoin/issues/1828 | Base58 en-/de-coding by roques · Pull Request #1828 · bitcoin/bitcoin · GitHub
19:04 < esotericnonsense> no gribble. (probably the wrong channel anyway).
19:05 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev     
19:20 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
19:33 < bitcoin-git> [bitcoin] luke-jr opened pull request #11441: rpc/server: Support for specifying options as named parameters (master...rpc_namedopts) https://github.com/bitcoin/bitcoin/pull/11441
19:34 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 260 seconds]     
19:34 < bitcoin-git> [bitcoin] fanquake opened pull request #11442: [WIP] [Docs] Update OpenBSD Build Instructions for OpenBSD 6.1 (master...openbsd-doc-update) https://github.com/bitcoin/bitcoin/pull/11442
19:40 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev     
19:44 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.]     
19:44 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Quit: Leaving.]     
20:14 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds]     
20:23 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev     
20:23 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection]     
20:24 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev     
20:34 -!- owowo [ovovo@gateway/vpn/mullvad/x-rehsrdmscypapzbh] has quit [Read error: Connection reset by peer]     
20:40 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev     
20:53 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-zjtstcuwryikdaxm] has quit [Quit: Connection closed for inactivity]     
21:56 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 240 seconds]     
21:57 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev     
22:00 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
22:33 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 248 seconds]     
22:34 -!- Alina-malina [~Alina-mal@37.157.223.81] has joined #bitcoin-core-dev     
22:34 -!- Alina-malina [~Alina-mal@37.157.223.81] has quit [Changing host]     
22:34 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev     
22:42 -!- sanada [sanada@36-2-119-80.chiba.ap.gmo-isp.jp] has quit []     
23:12 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds]     
23:12 < bitcoin-git> [bitcoin] mrwhythat closed pull request #11299: [WIP] Implement pruning to location (master...prune-to-location-option) https://github.com/bitcoin/bitcoin/pull/11299
23:36 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev     
23:53 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-pbmqenecinoaafsr] has joined #bitcoin-core-dev