--- Day changed Thu Oct 26 2017 00:19 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 00:20 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Quit: Leaving.] 00:23 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 240 seconds] 00:26 -!- Provoostenator [~textual@210.0.232.132] has quit [Quit: Textual IRC Client: www.textualapp.com] 00:41 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 00:48 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:58 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 01:01 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 01:04 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #bitcoin-core-dev 01:05 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 248 seconds] 01:06 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 01:13 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 01:21 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 01:23 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 260 seconds] 01:23 -!- decho [5fbee8df@gateway/web/freenode/ip.95.190.232.223] has joined #bitcoin-core-dev 01:27 -!- decho [5fbee8df@gateway/web/freenode/ip.95.190.232.223] has quit [Ping timeout: 260 seconds] 01:33 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 01:33 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Remote host closed the connection] 01:33 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 01:38 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Ping timeout: 258 seconds] 01:39 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 01:43 -!- marko_ [~marko@82.117.202.34] has joined #bitcoin-core-dev 01:44 -!- marko_ [~marko@82.117.202.34] has quit [Client Quit] 01:51 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-kmslojrsexfbeeoe] has quit [Quit: Connection closed for inactivity] 01:56 -!- wumpus [~quassel@pdpc/supporter/professional/wumpus] has quit [Ping timeout: 248 seconds] 01:58 -!- wumpus [~quassel@pdpc/supporter/professional/wumpus] has joined #bitcoin-core-dev 01:59 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 02:02 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 02:06 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 02:07 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 260 seconds] 02:08 -!- Giszmo [~leo@ip-140-236-219-201.nextelmovil.cl] has quit [Ping timeout: 260 seconds] 02:09 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 02:12 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 02:12 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 02:16 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 02:18 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 02:23 -!- CubicEar_ [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 02:24 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Read error: Connection reset by peer] 02:24 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 02:28 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 02:28 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 02:29 < sdaftuar> gmaxwell: my understanding of the scheduler is that it'll start scheduling callbacks at some point after startup, so i wouldn't expect the network to be completely synced 02:29 < sdaftuar> gmaxwell: also there's random drift, since the scheduler schedules the next callback N milliseconds after the prior one finishes 02:29 < sdaftuar> but worth discussing whether the interval is short enough that there still might be too much concentration of everyone trying to find a new peer 02:30 < sdaftuar> gmaxwell: regarding getheaders/locator -- no we don't update pindexBestKnownBlock from a peer's locator 02:30 < sdaftuar> we use pindexBestKnownBlock to figure out what blocks we can download from our peer 02:30 < sdaftuar> and the peer will update its locator based on headers it knows (not blocks!) during initial headers sync 02:31 < sdaftuar> in order to sync the whole headers chain (and given the MAX_HEADERS_RESULTS constraint on headers messages) 02:38 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 02:41 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 02:45 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 02:47 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 02:48 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 02:55 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 02:57 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 248 seconds] 02:58 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 03:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 03:06 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 03:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:14 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 03:15 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 03:17 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 03:20 < bitcoin-git> [bitcoin] Sjors closed pull request #11557: WIP: Use Sat/WU instead of (μ/m)BTC/kB (master...fee-sat-per-wu) https://github.com/bitcoin/bitcoin/pull/11557 03:26 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 03:43 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 03:51 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 03:56 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 240 seconds] 04:13 < bitcoin-git> [bitcoin] ryanofsky opened pull request #11565: Make listsinceblock refuse unknown block hash (master...pr/since) https://github.com/bitcoin/bitcoin/pull/11565 04:23 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 04:31 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 04:32 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev 04:34 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 04:47 -!- wxss [~chatzilla@5.254.89.171] has joined #bitcoin-core-dev 04:48 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 04:50 -!- Antranik [2f9ae3ca@gateway/web/freenode/ip.47.154.227.202] has quit [Quit: Page closed] 04:51 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 05:05 -!- d_p_ [~d_p@gateway/tor-sasl/dp/x-51976874] has quit [Remote host closed the connection] 05:05 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Write error: Connection reset by peer] 05:05 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 05:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 05:05 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Write error: Connection reset by peer] 05:05 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 05:06 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 05:07 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 05:11 -!- d_p [~d_p@gateway/tor-sasl/dp/x-51976874] has joined #bitcoin-core-dev 05:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 05:41 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 05:41 -!- CubicEar_ [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [] 05:51 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 05:59 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 240 seconds] 06:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 06:09 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [] 06:09 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 06:16 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 06:17 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 06:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds] 06:20 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 255 seconds] 06:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 06:39 -!- Giszmo [~leo@ip-152-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 06:41 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 06:44 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:45 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 06:53 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 06:53 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer] 06:54 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 06:57 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #bitcoin-core-dev 06:58 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 06:59 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Remote host closed the connection] 06:59 -!- Guest21 [~textual@qr148.plus.com] has joined #bitcoin-core-dev 06:59 -!- Giszmo [~leo@ip-152-236-219-201.nextelmovil.cl] has quit [Ping timeout: 260 seconds] 07:04 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 07:14 -!- nony [ab07f773@gateway/web/freenode/ip.171.7.247.115] has joined #bitcoin-core-dev 07:16 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 07:16 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 07:18 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 07:27 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 246 seconds] 07:33 -!- nony [ab07f773@gateway/web/freenode/ip.171.7.247.115] has quit [Quit: Page closed] 07:35 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 248 seconds] 07:41 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 248 seconds] 07:42 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 07:48 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:48 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 07:48 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 07:49 -!- Emcy [~MC@94.197.121.115.threembb.co.uk] has joined #bitcoin-core-dev 07:49 -!- Emcy [~MC@94.197.121.115.threembb.co.uk] has quit [Changing host] 07:49 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 07:55 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 07:58 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 08:01 -!- gaf_ [~fag@12.smos-linux.org] has quit [Quit: SMOS - http://smos-linux.org] 08:08 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 264 seconds] 08:11 -!- Giszmo [~leo@ip-198-233.219.201.nextelmovil.cl] has joined #bitcoin-core-dev 08:16 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 264 seconds] 08:26 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:27 < bitcoin-git> [bitcoin] pkaksha opened pull request #11566: 0.9 (master...0.9) https://github.com/bitcoin/bitcoin/pull/11566 08:28 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/57ee73990f1c...cf8c4a7633b1 08:28 < bitcoin-git> bitcoin/master fa81534 MarcoFalke: Add share/rpcuser to dist. source code archive 08:28 < bitcoin-git> bitcoin/master cf8c4a7 Wladimir J. van der Laan: Merge #11530: Add share/rpcuser to dist. source code archive... 08:28 < bitcoin-git> [bitcoin] laanwj closed pull request #11530: Add share/rpcuser to dist. source code archive (master...Mf1710-distShare) https://github.com/bitcoin/bitcoin/pull/11530 08:29 < bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/265bb214ecf616a7a55fc979a227d5f215046d84 08:29 < bitcoin-git> bitcoin/0.15 265bb21 MarcoFalke: Add share/rpcuser to dist. source code archive... 08:34 -!- Giszmo [~leo@ip-198-233.219.201.nextelmovil.cl] has quit [Read error: Connection reset by peer] 08:34 -!- Giszmo [~leo@ip-198-233.219.201.nextelmovil.cl] has joined #bitcoin-core-dev 08:36 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:38 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 252 seconds] 08:42 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 08:47 < bitcoin-git> [bitcoin] sipa closed pull request #11566: 0.9 (master...0.9) https://github.com/bitcoin/bitcoin/pull/11566 08:49 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 08:50 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 08:52 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 08:53 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 08:57 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-buzvrvqvkwoqawjc] has quit [Quit: Connection closed for inactivity] 09:16 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 248 seconds] 09:17 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 09:25 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 09:26 -!- Giszmo [~leo@ip-198-233.219.201.nextelmovil.cl] has quit [Ping timeout: 240 seconds] 09:27 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 09:28 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 09:36 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 09:50 -!- quantbot [~quantbot@38.101.106.141] has quit [Remote host closed the connection] 09:50 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 09:52 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Quit: Leaving] 09:56 < bitcoin-git> [bitcoin] sdaftuar closed pull request #11534: Evict outbound peers if tip is stale (master...2017-10-stale-tip-eviction) https://github.com/bitcoin/bitcoin/pull/11534 10:08 -!- pergaminho [~Cleber@201.47.91.172] has quit [Quit: Saindo] 10:12 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has quit [Read error: Connection reset by peer] 10:12 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 10:15 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 10:20 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 10:28 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 10:29 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 10:31 -!- quantbot [~quantbot@38.101.106.141] has quit [Ping timeout: 240 seconds] 10:43 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 10:44 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 10:55 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 10:56 -!- Testing [257f3c27@gateway/web/freenode/ip.37.127.60.39] has joined #bitcoin-core-dev 10:57 -!- Testing is now known as Guest9936 10:58 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 10:59 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 11:01 -!- quantbot [~quantbot@38.101.106.141] has quit [Remote host closed the connection] 11:02 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 11:06 -!- quantbot [~quantbot@38.101.106.141] has quit [Ping timeout: 240 seconds] 11:12 -!- ula [~kvirc@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev 11:21 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 11:35 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 11:52 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:55 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-hawfcpvtbhlnllli] has joined #bitcoin-core-dev 11:55 -!- maaku [~mark@173.234.25.100] has joined #bitcoin-core-dev 11:55 -!- clarkmoody [~clarkmood@47-218-248-206.bcstcmta04.res.dyn.suddenlink.net] has joined #bitcoin-core-dev 11:59 -!- Guest9936 [257f3c27@gateway/web/freenode/ip.37.127.60.39] has quit [Ping timeout: 260 seconds] 12:00 < achow101> meeting? 12:00 < sdaftuar> meeting 12:00 < promag> +1 12:00 -!- StopAndDecrypt|p [~StopAndDe@142.75.255.199] has joined #bitcoin-core-dev 12:00 < wumpus> #startmeeting 12:00 < lightningbot> Meeting started Thu Oct 26 19:00:53 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:01 < wumpus> #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 jl2012 achow101 12:01 < achow101> hi 12:01 < meshcollider> Hi 12:01 < kanzure> hi. 12:02 < wumpus> #topic 0.15.0.2 12:02 < cfields> hi 12:02 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 12:02 < wumpus> anything ready for merge there? 12:02 < maaku> present 12:02 < sdaftuar> i think #11490 is ready? maybe needs another ACK? 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/11490 | Disconnect from outbound peers with bad headers chains by sdaftuar · Pull Request #11490 · bitcoin/bitcoin · GitHub 12:03 < jtimon> hi 12:03 < wumpus> ok, good to know 12:03 < wumpus> #action merge 11490 12:03 < gmaxwell> Hi. 12:04 < cfields> 11490 looked good last i looked, will take a quick look at the last changes and re-ack 12:04 < gmaxwell> sdaftuar: I already ACKed it. I think it's pretty great. 12:04 < sdaftuar> thanks! 12:04 < achow101> gmaxwell: found a peer that his node with 11490 kicked. we're not sure whether it was kicked for being brain dead or spynode 12:04 < achow101> or ibd 12:04 < gmaxwell> but is should have been kicked regardless. 12:05 < wumpus> yes was about to say that 12:05 < wumpus> seems an improvement in any case to kick it :) 12:05 < jtimon> I was going to say if there was anything stopping 8994, but it needs rebase... 12:05 < achow101> ok, I just wasn't sure that it would effect nodes in inbd 12:05 < gmaxwell> Yes, I've had a node running the patch for a few days and after the first day I started cycling out all my outbounds every few hours with the hopes of hitting some broken peers. 12:05 < gmaxwell> achow101: yes, it should-- they're useless to us as outbound targets. 12:06 < achow101> oh right, duh. outbound.. 12:06 < gmaxwell> .yes, this is outbound only 12:06 < gmaxwell> and it avoids acting on 4 peers. so even if it goes nuts and kicks things it shouldn't the damage is limited. 12:08 < bitcoin-git> [bitcoin] sdaftuar opened pull request #11568: Disconnect outbound peers on invalid chains (master...2017-10-disconnect-outbound-peers-on-invalid-chains) https://github.com/bitcoin/bitcoin/pull/11568 12:08 < sdaftuar> also i think i have a fix to #11446 that should satisfy concerns raised in that PR ^^^ 12:08 < gribble> https://github.com/bitcoin/bitcoin/issues/11446 | Disconnect Peers for Duplicate Invalid blocks. by achow101 · Pull Request #11446 · bitcoin/bitcoin · GitHub 12:08 < achow101> sdaftuar: yay 12:08 < cfields> tangentially, does it not make sense to take their blockheight in version into consideration? sure it can be spoofed higher, but if it's low and we're in IBD (and presumably they are too), is it worth it to hang around? 12:08 < gmaxwell> to reiterite why this specific patch is important; beyond general braindead peer elimination, it addresses the case where you have peers on incompatible consensus rules which you aren't discovering because their chain has less work, so you aren't fetching their invalid blocks. 12:08 < sdaftuar> it's a refactor unfortunately, so not sure it is a good candidate for backport to 0.15. but it was simple to do 12:08 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:09 < gmaxwell> cfields: well someone could have a lower height but more work chain 12:09 < wumpus> yes, so for 0.15.0.2 we have open at the moment, apart from the one just discussed: #11560 #11446 #10593 12:09 < gribble> https://github.com/bitcoin/bitcoin/issues/11560 | Connect to a new outbound peer if our tip is stale by sdaftuar · Pull Request #11560 · bitcoin/bitcoin · GitHub 12:09 < gribble> https://github.com/bitcoin/bitcoin/issues/11446 | Disconnect Peers for Duplicate Invalid blocks. by achow101 · Pull Request #11446 · bitcoin/bitcoin · GitHub 12:09 < gribble> https://github.com/bitcoin/bitcoin/issues/10593 | Relax punishment for peers relaying invalid blocks and headers by luke-jr · Pull Request #10593 · bitcoin/bitcoin · GitHub 12:09 < sdaftuar> #11560 as well 12:09 < gribble> https://github.com/bitcoin/bitcoin/issues/11560 | Connect to a new outbound peer if our tip is stale by sdaftuar · Pull Request #11560 · bitcoin/bitcoin · GitHub 12:10 < sdaftuar> oh nvm you had that 12:10 < wumpus> #11446 has some doubts from BlueMatt 12:10 < gribble> https://github.com/bitcoin/bitcoin/issues/11446 | Disconnect Peers for Duplicate Invalid blocks. by achow101 · Pull Request #11446 · bitcoin/bitcoin · GitHub 12:10 < meshcollider> Is #11531 also aimed for 0.15.0.2? 12:10 < gribble> https://github.com/bitcoin/bitcoin/issues/11531 | Check that new headers are not a descendant of an invalid block (more effeciently) by TheBlueMatt · Pull Request #11531 · bitcoin/bitcoin · GitHub 12:10 < jnewbery> #10593 seems to be reverting unrelated code with no rationale, so I think that can be untagged 12:11 < gribble> https://github.com/bitcoin/bitcoin/issues/10593 | Relax punishment for peers relaying invalid blocks and headers by luke-jr · Pull Request #10593 · bitcoin/bitcoin · GitHub 12:11 < achow101> I guess 11446 has some edge cases that could be problematic 12:11 < gmaxwell> for some reason I thought what we were doing in 11446 was outbound only. I agree that our agressiveness increases here should be outbound only. 12:11 < luke-jr> jnewbery: reverting what? it removes tests that check for the behaviour that is being removed 12:11 < wumpus> ok added 11531 12:11 < gmaxwell> it's important that we don't fully partition old nodes during a softfork. 12:12 < achow101> it would be better if we could get more granular errors from processnewblockheaders 12:12 < wumpus> how much time do we have left? 12:12 < sdaftuar> 11568 is the same as 11446, except it avoids disconnecting hb compact block peers, and only applies to outbound peers 12:12 < wumpus> sdaftuar: ok we should remove one, then :) 12:12 < sdaftuar> agreed :) 12:12 < wumpus> eh wait 11568 isn't tagged 0.15.0.2 at all 12:13 < cfields> heh, it's getting hard to keep up with these 12:13 < achow101> wumpus: it was just made 12:13 < sdaftuar> i was trying to open it before the meeting started, doh 12:13 < wumpus> cfields: very hard, yes 12:13 < achow101> if 11568 is 11446 but only for outbound peers, I'm fine with that 12:13 < jnewbery> luke-jr: I haven't fully dug into it, but it regresses #8305, no? 12:13 < gribble> https://github.com/bitcoin/bitcoin/issues/8305 | Improve handling of unconnecting headers by sdaftuar · Pull Request #8305 · bitcoin/bitcoin · GitHub 12:13 < wumpus> ok, replacing 11446 then 12:13 < BlueMatt> I mean if we want a 0.15.0.2 we literally need to rc tomorrow or this weekend, imo 12:14 < gmaxwell> 11568 looks good on first run through. 12:15 < cfields> disclosure there: I'll be away after tomorrow night until tuesday morning 12:15 < wumpus> BlueMatt: what can we realistically merge before that time? 12:15 < luke-jr> jnewbery: I don't think so - 8305 disconnects under certain conditions, but 10593 disconnects a superset of those conditions 12:15 < cfields> i can make plans to be available for building if really necessary 12:15 < BlueMatt> wumpus: I dont think a sufficient set to make 0.15.0.2 worth it 12:16 < gmaxwell> I think probably if you try you can merge one PR per minute... we could empty out github by then, no problem.. just lots of button pushing! 12:16 < meshcollider> lol 12:16 < wumpus> well we have some fixes on the 0.15 branch already that are nice 12:16 < BlueMatt> heh 12:16 < wumpus> but I agree it kind of misses the point 12:16 < BlueMatt> wumpus: anything worth an 0.15.0.2? 12:17 < wumpus> BlueMatt: well it's a minor-minor release, that's not a high bar, but yes 12:17 < BlueMatt> I mean things like #11531, which may be important as far as our b2x-shitshow fixes go, are smack-dab in the middle of consensus code and have not review yet? 12:17 < gribble> https://github.com/bitcoin/bitcoin/issues/11531 | Check that new headers are not a descendant of an invalid block (more effeciently) by TheBlueMatt · Pull Request #11531 · bitcoin/bitcoin · GitHub 12:17 < wumpus> BlueMatt: nothing that warrants hurring it though 12:17 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 12:17 < BlueMatt> I suppose it may be worth it to get an 0.15.0.2 out like day-before b2x-shitshow 12:17 < gmaxwell> even a small portion of the network running it is protective. 12:18 < BlueMatt> then at least if some asshat spins up a billion stupid sybil nodes there is a response 12:18 < morcos> BlueMatt: +1 12:18 < BlueMatt> but we need to be clear what our target is here 12:18 < gmaxwell> at least if we cover the major possible cases: Fork has low to no hashpower, fork has higher hashpower for the case where we're completely partitioned by surrounded by forknodes or where we're partially surrounded. 12:18 < BlueMatt> and really focus on it 12:18 < BlueMatt> there hasnt been much progress the last 3 weeks 12:18 < BlueMatt> (I'm to blame there, too, I've been mostly mia) 12:18 < gmaxwell> I think there has been a lot of progress. 12:18 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 255 seconds] 12:18 < gmaxwell> sdaftuar has been right on top of making changes. 12:19 < BlueMatt> sorry, lots of progress on making new prs, rewriting prs, talking about issues, lack of *merge* progress 12:19 < wumpus> yes there absolutely has been a lot of progress, PR after PR 12:19 < BlueMatt> or finalizing review for things to get merged 12:19 < wumpus> but very little merging, yeah 12:19 < morcos> have we finalized the list 12:19 < morcos> lets focus on that 12:19 < morcos> and then everyone commit to reviewing 2 of them over the next 24 hours 12:19 < BlueMatt> well one thing on it was opened today cause it was decided to also be important/replace other things 12:19 < morcos> and we'll see where we stand 12:20 < wumpus> no, it seems to change every week 12:20 < morcos> wumpus: exactly 12:20 < BlueMatt> but, yea, I think if we want to see hhis happen, we can get it out day-or-two-before-ish, but we need review *today* 12:20 < cfields> agree with gmaxwell about focusing on those things that may actually be of significance in the next month 12:20 < wumpus> as cfieds said it's hard to keep track of 12:20 < BlueMatt> I think they're all tagged now, no? 12:20 < gmaxwell> To get the full coverage of those sets of cases, we need 11490, 11560, and 11568-or-11446 12:20 < morcos> focus... BlueMatt, sipa, gmaxwell, sdaftuar you guys have been thinking abou tthis the most... look at the list right now and be confident it is right and if not fix it 12:20 < BlueMatt> except #10593, ignore that 12:20 < gribble> https://github.com/bitcoin/bitcoin/issues/10593 | Relax punishment for peers relaying invalid blocks and headers by luke-jr · Pull Request #10593 · bitcoin/bitcoin · GitHub 12:20 < achow101> I think we can remove 10593 12:21 < morcos> stop arguing with Belshe on the web 12:21 < sdaftuar> :) 12:21 < wumpus> ok removed 10593 12:21 < BlueMatt> yea, 10593 got nack'ed (correctly, imo) a while ago 12:21 < gmaxwell> 11490 covers the case where fork has lower hashpower and doesn't completely surround you, 11560 covers where it has higher hashpower, 11568-or-11446 covers where it has lower and may completely surround you. 12:21 < luke-jr> does something else cover the cases 10593 does? 12:21 < rafalcpp> sorry if stupid question, but re `semOutbound = new CSemaphore(std::min((nMaxOutbound + nMaxFeeler + nMaxExtraOutbound), nMaxConnections));` if we're at nMaxOutbound == nMaxConnections doesn't it mean node in such conditin will not try to resolve being stalled? dunno if that's any issue 12:22 < morcos> luke-jr: explicit case you're worried about not being covered (soft forks? , we can worry abou tthose later) 12:22 < BlueMatt> luke-jr: tbh, I dont actually have any fucking clue what that pr is *supposed* to do in the context on b2x-shitshow 12:22 < achow101> rafalcpp: not now 12:22 < sdaftuar> rafalcpp: let's discuss after (thanks for taking a look!) 12:22 < BlueMatt> rafalcpp: sorry, mid-meeting atm 12:22 < morcos> rafalcpp: hi 12:23 < gmaxwell> achow101: that was related to the PR that adds an extra connection 12:23 < luke-jr> morcos: Bitcoin is almost a softfork relative to 2X 12:23 < luke-jr> BlueMatt: it is necessary for people to switch from 2X to Bitcoin, or run them both 12:23 -!- IniGit [~Gernot@62-178-56-62.cable.dynamic.surfer.at] has joined #bitcoin-core-dev 12:23 < IniGit> hello 12:23 < BlueMatt> luke-jr: you cannot switch back and forth, your blockindex will be corrupt (yay shitty fork developers) 12:24 < IniGit> I read the whitepaper of ethereum and I have a question (it is the same for bitcoin): 12:24 < IniGit> APPLY(S,TX) -> S' 12:24 < IniGit> My question is since S is defined as a set of UTXO, but the blockchain does not store each balance in a block, is this set of UTXO only preset in RAM and not on the blockchain. Is it calculated by the node by going thhrough each block since the genesis block and only present in RAM? 12:24 < luke-jr> BlueMatt: different datadirs.. 12:24 < luke-jr> or even different machines 12:24 < wumpus> IniGit: not here, not now 12:24 < morcos> luke-jr has a bit of a point there 12:24 < gmaxwell> luke-jr: it's unclear of specifically what you're turned about, don't get into an argument in the weeds, state what the overall concern is. 12:24 < IniGit> where can I ask this question and get more knowledge? 12:24 < gmaxwell> IniGit: #bitcoin 12:24 < sdaftuar> are we talking about relaxing bans to be disconnects instead? i generally agree with that 12:24 < BlueMatt> luke-jr: tbh, so what? our banning is deliberately slow, if you get banned from some small percentage of the network, slowly, over time, for running 2x, sucks for you 12:24 < morcos> gmaxwell: if someone on your IP runs a 2X node, your IP gets banned, and you cna't then run or simulataneiously run a core node 12:25 < luke-jr> gmaxwell: right now, we can peers that send invalid blocks, which means their Bitcoin nodes will get rejected from the p2p network too 12:25 < BlueMatt> (like one peer per block kinda slow) 12:25 < achow101> gmaxwell: I think the concern is if someone runs 2x and gets themselves banned, if they switch back to bitcoin they can't connect to the network anymore 12:25 < luke-jr> ban* 12:25 < gmaxwell> morcos: nothign we can do about that now regardless; as it's a property of the widely deployed network. 12:25 < wumpus> achow101: only if *everyone* banned them, which is unlikely as hell! 12:25 < wumpus> achow101: if a few nodes they were connected to banned them they will certainly find others 12:26 < luke-jr> wumpus: when 2X gets banned from Peer A, it will move on to Peer B, etc 12:26 < morcos> gmaxwell: hmm.. ok fair, and it'll take a lot of blocks to get banned by most of the network... 12:26 < gmaxwell> luke-jr: yes, but this takes longer than a day to cycle through all reachable nodes that way. 12:26 < luke-jr> gmaxwell: so long as not all peers ban, they will eventually find ones with the newer code.. 12:26 < morcos> luke-jr's pull should be maybe considered for soon release, in case there is extended period of two chains 12:26 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 12:26 < karelb> sorry for breaking in, the plan is that you cannot simultaneously run 2x and btc on the same IP? that is unfortunate 12:26 < morcos> but maybe 0.15.1 espeically if its not ready yet 12:26 < wumpus> gmaxwell: and by that time the first ones will have unbanned them again 12:26 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 12:26 < luke-jr> gmaxwell: even with the peers banning them? 12:27 < morcos> karelb: that's not the plan, thats an unfortunate side effect of the existing software 12:27 < gmaxwell> luke-jr: yes, because the banning goes slowly. 12:27 < gmaxwell> karelb: 2x foolishly connects to non-2x nodes and will relay them invalid blocks, so it will get itself banned. 12:27 < achow101> banning also requires blocks to be found, so ... 12:28 < achow101> that means 144 peers to switch through per day, on average 12:28 < luke-jr> gmaxwell: just because it hits 20% DoS penalty each header? 12:28 < wumpus> karelb: it could have been resolved with e.g. service bits if 2x was willing, but they're insisting on making this a mess, so we have to do the least harmful thing for the existing bitcoin network 12:28 < karelb> oh OK. That happens with the current core node 12:28 < BlueMatt> karelb: if you run 2x nodes without their broken -pretendimnot2x then no, you cannot, if you dont use that option, you should be fine 12:28 < gmaxwell> karelb: yes. 12:29 < wumpus> BlueMatt: exactly 12:29 < karelb> BlueMatt 👍 great 12:29 < BlueMatt> (which is another point against 10593) 12:29 < gmaxwell> luke-jr: also as matt points out, if you don't undermine service flag disconnects you won't get banned by bitcoin 0.15+ peers, so I think that answers your concern/. 12:29 < luke-jr> ok 12:30 < BlueMatt> if you run with -imstupidandignorereason, you should get banned, thats your problem, not mine 12:30 < karelb> what would be the reason of running that option? what is the incentive for the 2x node to connect to core nodes? 12:30 < gmaxwell> in the long run I want to move away from banning more or less entirely but that isn't a thing to worry about for now. 12:30 < BlueMatt> karelb: please not mid-meeting 12:30 < karelb> ok 12:30 < morcos> ok yes, thats a good point that we should publish, unfortunately lots of companies will need to run both 12:30 < karelb> sorry 12:30 < BlueMatt> gmaxwell: lots to be fixed in our dos/ban/disconnect logic, indeed 12:31 < morcos> ok back to question... list is good, please ack if you know what you're talking about. alex was here. 12:31 < sdaftuar> getting back to 0.15.0.2 -- i think the currently tagged PRs cover all the cases i think we would ideally cover pre-b2x 12:31 < achow101> list looks good to me 12:31 < wumpus> sdaftuar: great! 12:31 < gmaxwell> What sdaftuar said 12:31 < wumpus> let's focus on getting these reviewed and merged as soon as possible then 12:31 < achow101> +1 12:31 < wumpus> and lot's not add any new ones unless absolutely necessary 12:32 < gmaxwell> unless some interesting bug crops up I don't see why we would. 12:32 < meshcollider> Sounds good 12:32 < BlueMatt> ok, so #action 24-hour review sprint? 12:32 < gmaxwell> like maybe B2X's developer tells us about this mysterious instability in 0.15. :) 12:32 < morcos> i can't wait to tell them about my embargoed accidental hard fork 12:33 < BlueMatt> gmaxwell: lol, uh huhhhhh 12:33 < luke-jr> FTR, the problematic option is -advertise2x=0 or -noadvertise2x 12:34 < BlueMatt> aka -shootmeinthefacekthx 12:34 < cfields> BlueMatt: i'll commit to a 24hr sprint, at least ack/nack/cfields was here on all of those PRs. 12:34 < wumpus> I'll try 12:34 < gmaxwell> I'll test and review all that I haven't yet, of course. 12:35 < BlueMatt> ok, just gotta finish caching debug.log writing on fibre nodes then I'll do it 12:35 < BlueMatt> 30+ms pauses fron debug.log prints, ftr........... 12:35 < gmaxwell> BlueMatt: we could also release note this point-- that running -shootmeinthefacekthx will cause your IP to get banned by bitcoin nodes when the fork happens and make it harder to switch back or run both. 12:35 < gmaxwell> so uh. I hate to do this. 12:35 < gmaxwell> but 12:35 < achow101> oh no 12:36 < gmaxwell> ... I believe a one liner is possible to detect if our chainstate DB has been corrupted by running b2x post fork... would it be worthwhile to have that? 12:36 < gmaxwell> e.g. check out block at the fork height and see if its too big. 12:36 < kanzure> detect and warn? 12:36 < wumpus> yes, that would be worth it 12:36 < gmaxwell> and then shut down with a polite fuck you instead of just sitting stuck. 12:37 < kanzure> detect and exit? 12:37 < wumpus> yes 12:37 < BlueMatt> yea, I think so :'( 12:37 < cfields> gmaxwell: that sounds like exactly the kind of thing we should be aiming for in 0.15.0.2 :( 12:37 < gmaxwell> all we can do is exit and tell you to reindex. 12:37 < achow101> I guess.. 12:37 < morcos> in my opinion it'll be more than 24 hours until we agree if a 1-liner makes sense. i think we should just tell people you must reindex chainstate if you switch back... 12:37 < jnewbery> polite fuck you == "please use invalidateblock RPC" ? 12:37 < BlueMatt> i guess at least thats easy to review 12:37 < luke-jr> gmaxwell: why shut down? we can already rewind.. 12:37 < gmaxwell> oaky I'm sorry for the scope creep. It should be a near oneliner. 12:37 < luke-jr> jnewbery: need to automatic it, because RPC won't work if we shutdown 12:37 < BlueMatt> jnewbery: no, I think probably easier to just printf("please reindex") exit(); 12:37 -!- pavle [~pavle@cable-178-149-89-101.dynamic.sbb.rs] has joined #bitcoin-core-dev 12:37 < wumpus> that's more work 12:37 < gmaxwell> it's not easy to test unfortunately. 12:38 < luke-jr> BlueMatt: we already have code to rewind for segwit rechecking 12:38 < wumpus> for master it probably makes sense to make it automatic 12:38 < wumpus> but that's not realistic for 0.15.0.2 12:38 < BlueMatt> yea, i dont want to test any of this, or think about complicated interactions 12:38 < BlueMatt> just printf and exit 12:38 < wumpus> as gmaxwell says, warn+exit is better than mystieriously getting stuck 12:38 < wumpus> that's the aim here 12:38 < achow101> I support the thing that requires less work to review 12:38 < sdaftuar> i don't know that i think it's worth it, but i don't object i guess if other people want to add this "feature" 12:39 < gmaxwell> okay, I'll do the simplest possible first we could also consider others for master/later/etc... 12:39 < BlueMatt> morcos: points out this does not work on a pruned node, i forgot about that.... 12:39 < wumpus> sdaftuar: less mysterious bug reports... 12:39 < wumpus> sdaftuar: that's always a plus 12:39 < morcos> can we agree that this extra PR is lower priority than the others, lets not risk getting 0 of them out 12:39 < gmaxwell> SURE 12:39 < wumpus> morcos: I agree with that too 12:39 < gmaxwell> I don't even 'want' it so much as I realized it was a problem people will encounter which we could address. 12:39 < wumpus> I think it's worth doing in general, don't care if it doesn't get into 0.15.0.2 12:39 < morcos> tag it "Extra Credit" 12:40 < sdaftuar> haha sounds good to me 12:40 < wumpus> fine for 0.15.1 too 12:40 < wumpus> heh 12:40 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #bitcoin-core-dev 12:40 < gmaxwell> well I'll try something. decide if you want to review it or not. 12:40 < kanzure> might make sense for flip floppers later 12:41 < gmaxwell> after the fork it can just hardcode the hash. :) 12:41 < wumpus> yep 12:41 < gmaxwell> e.g. like doing an invalidateblock at startup. 12:42 < gmaxwell> I agree it's certantly less important in part because we can address with announcements/release notes-- don't do this. 12:42 * sipa here for a minute 12:43 < BlueMatt> sipa: we're doing 24 hour code review spring for 0.15.0.2, you owe us review on 4 prs today! :p 12:43 < sipa> BlueMatt: i'll try! 12:44 -!- fengling_ [~fengling@2400:8901::f03c:91ff:fe61:b65c] has quit [Quit: WeeChat 1.6] 12:44 < achow101> not just 4 PRs, the 4 PRs tagged for 0.15.0.2 12:45 < luke-jr> we could make a BLOCK_OPT_WITNESS-like thing and require it for the 2X height block only.. but that'll break normal upgrades too 12:45 < luke-jr> not sure it's worth it 12:46 < spudowiar> Which PRs are those? https://github.com/bitcoin/bitcoin/projects/8 shows one PR under "Review priority for 0.15.0.2" 12:46 < achow101> spudowiar: https://github.com/bitcoin/bitcoin/milestone/32 12:46 < wumpus> spudowiar: just use the milestone https://github.com/bitcoin/bitcoin/milestone/32 12:46 < spudowiar> Thanks, sorry 12:46 < wumpus> yeah no problem, I'll update review priority too 12:47 < achow101> other topics? 12:49 < wumpus> apparently not 12:49 < achow101> In other news, I got someone to write meeting notes for the website. we'll try to get through all of the meetings missed too 12:49 < wumpus> achow101: that's great news! 12:49 < meshcollider> \o/ 12:50 -!- jb55 [~jb55@184.68.162.218] has joined #bitcoin-core-dev 12:50 < gmaxwell> bad news is that the someone is roger ver. 12:50 < gmaxwell> :P 12:50 < achow101> lol. no 12:50 < wumpus> hahahaha 12:50 < luke-jr> XD 12:51 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 12:51 < luke-jr> achow101: you've checked? 12:51 < meshcollider> Comic relief would be the whole meeting notes 12:51 < achow101> luke-jr: unless I am blind, I am pretty sure the person writing the notes next to me is roger ver 12:51 < achow101> *is not 12:51 < gmaxwell> uh oh. 12:51 < luke-jr> achow101: maybe on his payroll :P 12:52 * gmaxwell imagines the delayed correction coming after a sharp poke to the ribs 12:52 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 12:52 < achow101> now we got our comic relief :p 12:52 < wumpus> #endmeeting 12:52 < lightningbot> Meeting ended Thu Oct 26 19:52:51 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 12:52 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-10-26-19.00.html 12:52 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-10-26-19.00.txt 12:52 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-10-26-19.00.log.html 12:53 < sdaftuar> ico time? 12:53 < BlueMatt> sdaftuar: wait, we cant both ICO, I'm ICOing first! 12:53 < gmaxwell> ICO time. 12:53 < gmaxwell> pretty sure everyone can ICO, theres is like an app for it or something. 12:54 < clarkmoody> When your One More Thing (TM) comes from gmaxwell ... 12:54 < sdaftuar> rafalcpp: if you had questions about #11560 i'd be happy to discuss 12:54 < gribble> https://github.com/bitcoin/bitcoin/issues/11560 | Connect to a new outbound peer if our tip is stale by sdaftuar · Pull Request #11560 · bitcoin/bitcoin · GitHub 12:54 < gmaxwell> I heard about it in an email with the subject lime "Make Money Fast". 12:54 < bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/cf8c4a7633b1...d93fa261f079 12:54 < bitcoin-git> bitcoin/master c60fd71 Suhas Daftuar: Disconnecting from bad outbound peers in IBD... 12:54 < bitcoin-git> bitcoin/master 5a6d00c Suhas Daftuar: Permit disconnection of outbound peers on bad/slow chains... 12:54 < bitcoin-git> bitcoin/master e065249 Suhas Daftuar: Add unit test for outbound peer eviction 12:54 < achow101> mmm. subject limes 12:54 < cfields> gmaxwell: it matters who's first though. If only we had some way to trustlessly timestamp things... 12:54 < luke-jr> ICO is just scamcoins 2.0; BlueMatt once had a generator.. 12:54 < sdaftuar> wumpus: thanks! 12:54 < esotericnonsense> gmaxwell: well the title isn't wrong. 12:54 < sdaftuar> rebase time... 12:54 < rafalcpp> sdaftuar: right, it's the question that was posted above 12:54 * esotericnonsense wanders off to 'make some money' on regtest 12:55 < gmaxwell> cfields: it could be a device that ticks at a regular interval 12:55 < bitcoin-git> [bitcoin] laanwj closed pull request #11490: Disconnect from outbound peers with bad headers chains (master...2017-10-outbound-peers-good-chain) https://github.com/bitcoin/bitcoin/pull/11490 12:55 < maaku> esotericnonsense: don't you go monetizing regtest coins! 12:55 -!- jb55 [~jb55@184.68.162.218] has quit [Ping timeout: 258 seconds] 12:55 < sdaftuar> nMaxConnections is generally much larger than nMaxOutbound, but yes if someone set nMaxConnections very low, then i think that could cause issues. but that's no different eg than running with -connect= or something, i think? 12:56 < sdaftuar> rafalcpp: ie if you run with non-standard p2p config, then i think you could run into issues... maybe worth release noting? 12:56 < cfields> gmaxwell: 15 seconds? :p 12:57 < luke-jr> btw, the advertise2x warning seems more appropriate for a blog post than release notes, since it has nothing to do with our release 12:57 < meshcollider> Only 3 PRs left to review now :) 12:57 < rafalcpp> sdaftuar: dunno, maybe? :) I didn't yet developed on bitcoin. Wouldn't it be possible to increase both sides of min? 12:58 < gmaxwell> luke-jr: well I dunno the release note is "if you plan on using this program with that program on the same computer" 12:58 < rafalcpp> though then we're skipping check for system limit of connections so maybe not. sdaftuar 12:59 < sdaftuar> rafalcpp: i think it makes more sense for the user to continue to have a toggle for the overall number of connections, and just explain what the consequence is 12:59 < luke-jr> gmaxwell: it's also true for older releases of ours though 12:59 < gmaxwell> if we have a zillion inbound connections we probably don't need the anti-partition rotation anyways. 12:59 < wumpus> meshcollider: review is still welcome after something is merged :) 12:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:02 -!- notmike [uid209547@gateway/web/irccloud.com/x-ifsaouugdscatapg] has joined #bitcoin-core-dev 13:02 < notmike> Its time. I'm ready. 13:04 < rafalcpp> sdaftuar: to me a release note sounds good. unless also logging a warning when it happens, if that code isn't frozen 13:07 -!- jb55 [~jb55@72.143.220.170] has joined #bitcoin-core-dev 13:07 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:17 -!- jb55 [~jb55@72.143.220.170] has quit [Ping timeout: 260 seconds] 13:20 -!- jb55 [~jb55@72.143.220.170] has joined #bitcoin-core-dev 13:25 -!- jb55 [~jb55@72.143.220.170] has quit [Ping timeout: 248 seconds] 13:26 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 13:29 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 13:31 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:31 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 13:32 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 13:33 -!- RoyceX [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 13:35 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 240 seconds] 13:36 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds] 13:39 -!- Stephanzf [46304998@gateway/web/freenode/ip.70.48.73.152] has joined #bitcoin-core-dev 13:39 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 13:48 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 13:50 -!- Stephanzf [46304998@gateway/web/freenode/ip.70.48.73.152] has quit [Ping timeout: 260 seconds] 13:51 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:54 -!- IniGit1 [~Gernot@62.178.56.62] has joined #bitcoin-core-dev 13:55 -!- IniGit [~Gernot@62-178-56-62.cable.dynamic.surfer.at] has quit [Ping timeout: 248 seconds] 13:57 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 255 seconds] 14:02 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 14:05 -!- clarkmoody [~clarkmood@47-218-248-206.bcstcmta04.res.dyn.suddenlink.net] has quit [Quit: Leaving] 14:06 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 14:06 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 14:06 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:07 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 14:11 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 255 seconds] 14:14 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 14:14 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 14:16 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 14:16 -!- wxss [~chatzilla@5.254.89.171] has quit [Ping timeout: 264 seconds] 14:16 -!- maaku [~mark@173.234.25.100] has left #bitcoin-core-dev [] 14:22 -!- otium [~otium@2a01:e35:2eeb:c00:5858:357c:75de:9e05] has joined #bitcoin-core-dev 14:22 -!- otium [~otium@2a01:e35:2eeb:c00:5858:357c:75de:9e05] has quit [Client Quit] 14:25 -!- notmike [uid209547@gateway/web/irccloud.com/x-ifsaouugdscatapg] has left #bitcoin-core-dev [] 14:35 -!- IniGit1 [~Gernot@62.178.56.62] has quit [] 14:40 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 14:49 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 258 seconds] 14:50 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 14:51 -!- wxss [~chatzilla@5.254.89.171] has joined #bitcoin-core-dev 14:55 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 15:01 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 15:04 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Ping timeout: 240 seconds] 15:05 -!- Squidicc is now known as squidicuz 15:06 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 1.9.1] 15:09 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 15:17 < bitcoin-git> [bitcoin] jnewbery reopened pull request #10160: [WIP] updatepeer RPC (master...updatepeer) https://github.com/bitcoin/bitcoin/pull/10160 15:21 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 15:22 -!- pavle [~pavle@cable-178-149-89-101.dynamic.sbb.rs] has quit [Remote host closed the connection] 15:31 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds] 15:33 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 15:51 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has quit [Ping timeout: 264 seconds] 15:52 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has joined #bitcoin-core-dev 16:05 -!- mxg [~mxg@2604:2000:e8c3:c700:6ced:9db0:3689:b0e3] has joined #bitcoin-core-dev 16:06 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has quit [Ping timeout: 252 seconds] 16:07 -!- mxg [~mxg@2604:2000:e8c3:c700:6ced:9db0:3689:b0e3] has quit [Client Quit] 16:10 -!- Giszmo [~leo@190.8.79.154] has joined #bitcoin-core-dev 16:15 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 16:17 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds] 16:22 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has joined #bitcoin-core-dev 16:25 -!- RoyceX [~Cheeseo@unaffiliated/cheeseo] has quit [Read error: Connection reset by peer] 16:27 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 258 seconds] 16:29 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit [Ping timeout: 240 seconds] 16:34 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has quit [Ping timeout: 248 seconds] 16:39 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 16:42 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has joined #bitcoin-core-dev 16:46 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 16:47 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 264 seconds] 16:54 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 260 seconds] 16:57 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 17:01 -!- jb55 [~jb55@72.143.220.187] has joined #bitcoin-core-dev 17:04 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 17:09 -!- jb55 [~jb55@72.143.220.187] has quit [Ping timeout: 240 seconds] 17:16 -!- jdouglas74 [32f6edee@gateway/web/freenode/ip.50.246.237.238] has joined #bitcoin-core-dev 17:20 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has quit [Ping timeout: 248 seconds] 17:21 -!- wxss [~chatzilla@5.254.89.171] has quit [Remote host closed the connection] 17:35 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has joined #bitcoin-core-dev 17:37 -!- jdouglas74 [32f6edee@gateway/web/freenode/ip.50.246.237.238] has quit [] 17:48 -!- Giszmo [~leo@190.8.79.154] has quit [Ping timeout: 248 seconds] 17:59 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 18:01 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has quit [Ping timeout: 240 seconds] 18:12 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Read error: Connection reset by peer] 18:12 -!- dabura667_ [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 18:15 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-hawfcpvtbhlnllli] has quit [Quit: Connection closed for inactivity] 18:16 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wsypnkjnwqcqbvcm] has joined #bitcoin-core-dev 18:21 -!- wordsToLiveBy [~wordsToLi@gateway/vpn/privateinternetaccess/wordstoliveby] has joined #bitcoin-core-dev 18:22 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 18:47 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 18:56 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 19:36 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has quit [Ping timeout: 255 seconds] 19:38 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has joined #bitcoin-core-dev 19:50 -!- terror_ [dd0c0ada@gateway/web/freenode/ip.221.12.10.218] has joined #bitcoin-core-dev 19:50 -!- terror_ [dd0c0ada@gateway/web/freenode/ip.221.12.10.218] has quit [Client Quit] 19:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds] 20:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 20:12 -!- JackH [~laptop@host-80-47-85-226.as13285.net] has joined #bitcoin-core-dev 20:53 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit [] 20:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1] 20:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 20:55 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 20:57 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Quit: Leaving] 21:12 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 21:13 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 21:15 -!- LeMiner [~LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 21:17 -!- LeMiner2 [~LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has quit [Ping timeout: 248 seconds] 21:17 -!- LeMiner is now known as LeMiner2 21:31 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection] 21:45 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Quit: Lost terminal] 22:13 -!- mlz [~IRCIdent@unaffiliated/molly] has joined #bitcoin-core-dev 22:22 -!- molz [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 22:46 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev 22:51 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Remote host closed the connection] 22:55 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev