--- Day changed Wed Oct 25 2017 00:02 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has quit [Ping timeout: 248 seconds] 00:04 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has joined #bitcoin-core-dev 00:05 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 00:10 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev 00:19 < Varunram> #11555 looks like a troll issue.. 00:19 < gribble> https://github.com/bitcoin/bitcoin/issues/11555 | ПОМОГИТЕ!!!!!!! · Issue #11555 · bitcoin/bitcoin · GitHub 00:21 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 00:25 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:37 -!- wvr- [~wvr@232.red-83-40-193.dynamicip.rima-tde.net] has quit [Ping timeout: 240 seconds] 00:37 -!- wvr- [~wvr@17.red-81-44-205.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 01:04 -!- william [~william@2604:2000:71d5:e500:ef25:5b1c:d633:3daf] has joined #bitcoin-core-dev 01:06 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 246 seconds] 01:17 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #bitcoin-core-dev 01:17 -!- ula [~kvirc@b2b-78-94-9-226.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 01:20 -!- cfields [~quassel@unaffiliated/cfields] has quit [Ping timeout: 246 seconds] 01:21 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev 01:28 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has joined #bitcoin-core-dev 01:29 < meshcollider> Heh the renaming of "Easy to implement" -> "Good first issue" means the 0.16 release schedule is now a "Good first issue" 01:31 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev 01:32 < sipa> it has some nontrivial dependencies, though :) 01:32 -!- william [~william@2604:2000:71d5:e500:ef25:5b1c:d633:3daf] has left #bitcoin-core-dev ["Good Bye"] 01:36 -!- cfields [~quassel@unaffiliated/cfields] has quit [Read error: Connection reset by peer] 01:37 < luke-jr> lol 01:37 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev 01:49 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:52 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 01:53 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 01:56 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-vgkmpwaopnkopjny] has quit [Quit: Connection closed for inactivity] 01:57 < Varunram> though if someone did contribute that, would be great ;) 02:19 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 02:19 -!- shoogz [~shoogz@unaffiliated/shoogz] has joined #bitcoin-core-dev 02:24 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 02:29 -!- promag [~promag@89.214.62.165] has joined #bitcoin-core-dev 02:35 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 02:42 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev 02:45 -!- promag [~promag@89.214.62.165] has quit [Ping timeout: 240 seconds] 02:49 -!- promag [~promag@92.250.73.193] has joined #bitcoin-core-dev 02:51 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 02:53 -!- promag_ [~promag@int.edigma.com] has joined #bitcoin-core-dev 02:54 -!- str4d [~str4d@27.110.123.91] has joined #bitcoin-core-dev 02:55 -!- promag [~promag@92.250.73.193] has quit [Ping timeout: 248 seconds] 03:03 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 03:03 -!- promag_ [~promag@int.edigma.com] has quit [Remote host closed the connection] 03:08 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 03:10 -!- ThomasV [~thomasv@unaffiliated/thomasv] has left #bitcoin-core-dev ["Leaving"] 03:18 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 03:30 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 03:46 < bitcoin-git> [bitcoin] Sjors opened pull request #11557: WIP: Use Sat/WU instead of (μ/m)BTC/kB and show percentage fee (master...fee-sat-per-wu) https://github.com/bitcoin/bitcoin/pull/11557 03:56 -!- adetate [~adetate@145.90.160.88] has joined #bitcoin-core-dev 03:59 -!- promag [~promag@int.edigma.com] has joined #bitcoin-core-dev 04:14 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 04:16 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 255 seconds] 04:19 -!- wxss [~chatzilla@89.238.178.92] has joined #bitcoin-core-dev 04:25 -!- Bitnet [~Bitnet@2604:2000:71d5:e500:ef25:5b1c:d633:3daf] has joined #bitcoin-core-dev 04:27 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Ping timeout: 240 seconds] 04:32 -!- Giszmo [~leo@190.8.79.154] has joined #bitcoin-core-dev 04:37 -!- Giszmo [~leo@190.8.79.154] has quit [Ping timeout: 246 seconds] 04:37 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 04:39 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 04:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:43 -!- pergaminho [~Cleber@201.47.91.172] has joined #bitcoin-core-dev 04:55 -!- Bitnet [~Bitnet@2604:2000:71d5:e500:ef25:5b1c:d633:3daf] has quit [Quit: Leaving] 05:02 -!- adetate [~adetate@145.90.160.88] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 05:05 -!- adetate [~adetate@145.90.160.88] has joined #bitcoin-core-dev 05:12 -!- Giszmo [~leo@ip-52-226-107-190.nextelmovil.cl] has joined #bitcoin-core-dev 05:16 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 05:18 -!- promag [~promag@int.edigma.com] has quit [Remote host closed the connection] 05:21 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:29 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-core-dev 05:40 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 248 seconds] 05:42 -!- pbase [~pbase@unaffiliated/pbase] has quit [Quit: Leaving] 05:46 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 05:48 < bitcoin-git> [bitcoin] sipsorcery opened pull request #11558: Minimal code changes to allow msvc compilation (master...code_msvc) https://github.com/bitcoin/bitcoin/pull/11558 05:50 -!- laurentmt1 [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 05:52 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Ping timeout: 240 seconds] 05:52 -!- laurentmt1 is now known as laurentmt 05:52 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has quit [Ping timeout: 255 seconds] 05:53 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has joined #bitcoin-core-dev 05:55 -!- unholymachine [~quassel@2601:8c:c003:9f16:14df:87d9:3f2d:12b2] has quit [Remote host closed the connection] 05:56 -!- unholymachine [~quassel@2601:8c:c003:9f16:5554:198e:ad6c:2a43] has joined #bitcoin-core-dev 06:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 06:05 < bitcoin-git> [bitcoin] racmnet opened pull request #11559: Create bitcoin.git (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11559 06:06 < bitcoin-git> [bitcoin] fanquake closed pull request #11559: Create bitcoin.git (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11559 06:11 -!- str4d [~str4d@27.110.123.91] has quit [Ping timeout: 246 seconds] 06:21 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 06:37 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-tpuqeigayymjqtkl] has joined #bitcoin-core-dev 06:43 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 06:45 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 07:12 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 07:31 -!- adetate [~adetate@145.90.160.88] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 07:37 -!- twistedline_ [~quassel@unaffiliated/twistedline] has joined #bitcoin-core-dev 07:37 -!- twistedline [~quassel@unaffiliated/twistedline] has quit [Ping timeout: 255 seconds] 07:37 -!- adetate [~adetate@145.90.160.88] has joined #bitcoin-core-dev 07:40 -!- adetate [~adetate@145.90.160.88] has quit [Client Quit] 07:44 -!- twistedline_ [~quassel@unaffiliated/twistedline] has quit [Ping timeout: 252 seconds] 07:56 -!- Grandpa_ [c0285928@gateway/web/freenode/ip.192.40.89.40] has joined #bitcoin-core-dev 07:57 < Grandpa_> Hello, - an old lowtech grandpa on the line here - hoping you guys can help me figure out what to do. I have an old Bitcoin Core wallet with some old BTC coins in it. It haven't spent any or even touched the wallet (other than upgrading to Core 0.15.0.1 a few day ago) since May 2017 - prior to the Segwit implementation and the Bitoin Cash and Gold forks that I have been trying to follow through the media. 07:57 < Grandpa_> Now I would like to transfer some to Bitstamp (the only place where I have an acct) in case I would like to sell a litle bit. But I would of course also like to NOT LOSE the Bitcoin Cash and Gold coins which now (as far as I am able to discern from media coverage) reside inside the belly of each of my old Bitcoins. I've tried to make sense of Bitstamp's official statements but there isn't really any usable information ther 07:57 < Grandpa_> So: Could someone among you PLEASE share some insight as to what to actually do? Since Bitstamp has automatically credited costumer accts with pre-BTCash holdings with one BTCash for each old BTC, do they also automatically do this with BTC that are transferred now? If not, how to go about it from inside Bitcoin Core (with the least possible difficulty and complexity for an aging chap who struggles with the technicalities i 08:00 < gmaxwell> Grandpa_: Bitcoin Cash will not 'replay' your bitcoin transactions. You can send bitcoin without worrying about that. Bitcoin gold doesn't really exist yet, but they claim that when it does it will also not be vulnerable to replay, so again, should be no reason to worry there. 08:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:00 < gmaxwell> When you pay with your bitcoin core wallet, only the bitcoin will move... the Bcash (and presumably bgold) will just stay where they are. 08:01 < Grandpa_> So you are saying that I can safely transfer som BTC to Bitstamp and they will take care of it_ 08:01 < Grandpa_> ? 08:01 < Grandpa_> How can they stay where they are if the BTC are sent away? 08:02 < gmaxwell> No, I am saying you can send btc to bitstamp and other currencies will not be effected. 08:03 < gmaxwell> Grandpa_: because they are entirely seperate systems that diverged from bitcoin in the past, they will not see your transactions. 08:03 -!- timothy [tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 08:03 < gmaxwell> (and, in fact, your bitcoin transactions are not compatible with them). 08:03 < Grandpa_> Should a make a copy of my wallet before sending then? 08:03 < Grandpa_> With the old balance? 08:03 < gmaxwell> That could make it a little easier to later send the bcash/bgold. 08:04 < gmaxwell> Though it is not strictly needed, as you can rescan your wallet on those systems. 08:04 < Grandpa_> How else could I preserve the gold/cash? 08:04 < gmaxwell> it would be preserved even if you didn't back up the wallet because the keys are never removed from the wallet. 08:04 -!- twistedline [~quassel@unaffiliated/twistedline] has joined #bitcoin-core-dev 08:05 < Grandpa_> I mean, if I now send away some coins reducing wallet balance to 0 / could I later extract cash and gold from it_ 08:05 < Grandpa_> ? 08:06 < gmaxwell> Yes, that is what I've been trying to tell you. 08:06 < Grandpa_> Oh, my. 08:06 < Grandpa_> Sound scary though. 08:06 < Grandpa_> Sounds 08:07 < gmaxwell> it isn't really-- these things are just totally seperate cryptocurrencies where they just happened to also pay everyone that owned bitcoin at a certian time on them. 08:07 < gmaxwell> So its like importing the same private key into a litecoin and bitcoin wallet. They're still seperate. 08:09 < Grandpa_> But the recommended path would, however, be to just make a copy of the wallet before sending? And then later on use it for the other two? How exactly would I go about it if I want to get rid of the bcash asap (which I dont like?) 08:09 < sipa> can we move this to #bitcoin ? 08:10 < Grandpa_> how do I do that? 08:10 < Grandpa_> start there anew? 08:11 < sipa> type exactly: 08:11 < sipa> /join #bitcoin 08:29 -!- btcenth [4e81ca1a@gateway/web/freenode/ip.78.129.202.26] has joined #bitcoin-core-dev 08:30 -!- btcenth [4e81ca1a@gateway/web/freenode/ip.78.129.202.26] has quit [Client Quit] 08:32 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:42 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 08:43 -!- twistedline [~quassel@unaffiliated/twistedline] has quit [Ping timeout: 240 seconds] 08:46 -!- twistedline [~quassel@unaffiliated/twistedline] has joined #bitcoin-core-dev 08:49 < Grandpa_> Thank you sincerely for your coaching guys! Might be checking in later. 08:53 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #11487: Check that new headers are not a descendant of an invalid block (master...2017-10-acceptblock-validity-check) https://github.com/bitcoin/bitcoin/pull/11487 08:54 -!- Grandpa_ [c0285928@gateway/web/freenode/ip.192.40.89.40] has quit [Ping timeout: 260 seconds] 08:54 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-mrndwvsklucuhpxw] has quit [Quit: Connection closed for inactivity] 09:03 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 09:04 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 09:06 < cfields> ugh, the whitespace linter is annoying 09:07 < cfields> 09:08 < sipa> good, that means it's working 09:14 -!- d_p_ [~d_p@gateway/tor-sasl/dp/x-51976874] has quit [Ping timeout: 248 seconds] 09:16 -!- Giszmo [~leo@ip-52-226-107-190.nextelmovil.cl] has quit [Ping timeout: 240 seconds] 09:16 -!- d_p_ [~d_p@gateway/tor-sasl/dp/x-51976874] has joined #bitcoin-core-dev 09:19 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Read error: Connection reset by peer] 09:23 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 09:31 -!- mess110 [~kiki@95.77.248.16] has joined #bitcoin-core-dev 09:31 -!- Giszmo [~leo@ip-121-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 09:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 09:33 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ltzxintwmasdlmaa] has joined #bitcoin-core-dev 09:37 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 248 seconds] 09:47 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 10:04 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 10:09 -!- Cogito_Ergo_Sum [~Myself@athedsl-314925.home.otenet.gr] has joined #bitcoin-core-dev 10:09 -!- Cogito_Ergo_Sum [~Myself@athedsl-314925.home.otenet.gr] has quit [Changing host] 10:09 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 10:26 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 10:33 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 255 seconds] 10:44 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 10:44 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 11:12 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 11:16 -!- Giszmo [~leo@ip-121-236-219-201.nextelmovil.cl] has quit [Read error: Connection reset by peer] 11:22 < gmaxwell> Is anyone here permitted on the segwit2x list? it would be nice for someone to ask what the heck this refers to: 11:22 < gmaxwell> 7. I've been paying close attention to the Bitcoin Core 0.15.x rollout. Based on instability and bugs that upstream Bitcoin Core project is seeing 11:22 < gmaxwell> - ie. Core's bugs not ours - segwit2x will stay on Bitcoin Core 0.14.x 11:22 < gmaxwell> through the November fork. This is the most stable path for users, based 11:22 < gmaxwell> on upstream Bitcoin Core instability. 11:33 -!- Giszmo [~leo@ip-228-233.219.201.nextelmovil.cl] has joined #bitcoin-core-dev 11:40 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection] 11:43 -!- paracyst [paracyst@unaffiliated/paracyst] has quit [Quit: bye] 11:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ltzxintwmasdlmaa] has quit [Quit: Connection closed for inactivity] 11:43 -!- paracyst [paracyst@unaffiliated/paracyst] has joined #bitcoin-core-dev 11:43 -!- mess110 [~kiki@95.77.248.16] has quit [Remote host closed the connection] 11:44 < wxss> gmaxwell: the segwit2x-dev branch (based on 0.15) crashes at least 5x during IBD 11:44 < gmaxwell> ?! 11:44 < gmaxwell> wxss: are you sure your hardware isn't just fucked? 11:45 < gmaxwell> gah. must resist urge to ask you about the crashes, I do not intent to help them fix their broken grap. 11:45 < gmaxwell> er crap. 11:46 < wxss> I haven't seen it with the Core client (0.15.x) so I'm pretty sure my hw is ok 11:47 < gmaxwell> well it would be no shock to me if they broke it. 11:48 < wxss> me neither, anyway it was just an observation. 11:51 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 264 seconds] 11:52 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 11:56 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 11:59 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 11:59 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 12:00 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has quit [Quit: Leaving] 12:02 < achow101> I like how he doesn't report the bug upstream and just complains about it instead :/ 12:03 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 12:05 < gmaxwell> we claims that _we're_ seeing instability. 12:05 < gmaxwell> AFAICT this is simply untrue. 12:05 < andytoshi> fwiw adam is on the list and can maybe forward a message 12:06 < gmaxwell> s/we/he/ 12:07 < achow101> are you not able to get on the list? 12:07 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #bitcoin-core-dev 12:08 < gmaxwell> I have no idea now, when they first opened it they were telling people that it was only for supporters and people who agreed they would deploy it, but if adam is on it then perhaps; I don't really have any interest in being on it, and I don't think jeff will reply to me. 12:08 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 252 seconds] 12:12 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 12:15 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 12:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:24 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 252 seconds] 12:26 < aj> gmaxwell: i'd give 80% odds it's talking about the qt bugs fixed in 0.15.0.1... i doubt it's anything unknown or unfixed given the "Bitcoin Core project is seeing" them wording 12:26 < gmaxwell> well the things fixed in 0.15.0.1 wouldn't really make a lot of sense in that context... because ... they're fixed. 12:27 < Chris_Stewart_5> gmaxwell: Don't let your pesky facts get in the way of the narrative 12:29 < aj> gmaxwell: the sensible reason for basing on 0.14 is that rebasing 0.14->0.15 on top of btc1 is too hard; but that's embarassing to admit, and rebasing btc1 on top of 0.15 would also be embarassing 12:36 < MarcoFalke> 0.15.0.1 only fixed the gui oob crash. The "peers.dat" crash will be fixed in 0.15.0.2. 12:36 < MarcoFalke> I am not aware of any other bugs or instabilities. 12:42 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 12:43 < achow101> peers.dat crash? 12:44 < bitcoin-git> [bitcoin] sdaftuar opened pull request #11560: Connect to a new outbound peer if our tip is stale (master...2017-10-stale-tip-new-peer) https://github.com/bitcoin/bitcoin/pull/11560 12:45 < sdaftuar> gmaxwell: cfields: i think i have a working implementation of what we talked about yesterday ^^^ 12:46 < cfields> sdaftuar: great, will take a look 12:46 < sdaftuar> thanks! 12:50 < aj> MarcoFalke: (hm, #11508 was the other one i was thinking of, but i don't think the bug was only introduced in master) 12:50 < gribble> https://github.com/bitcoin/bitcoin/issues/11508 | Fix crash via division by zero assertion by jonasschnelli · Pull Request #11508 · bitcoin/bitcoin · GitHub 12:51 < MarcoFalke> aj: Indeed. achow101: #11252 12:51 < gribble> https://github.com/bitcoin/bitcoin/issues/11252 | [P2P] When clearing addrman clear mapInfo and mapAddr. by instagibbs · Pull Request #11252 · bitcoin/bitcoin · GitHub 12:56 < gmaxwell> MarcoFalke: #11252 exists in 0.14.x and presumably all prior versions back to addrman's introduction. 12:56 < gribble> https://github.com/bitcoin/bitcoin/issues/11252 | [P2P] When clearing addrman clear mapInfo and mapAddr. by instagibbs · Pull Request #11252 · bitcoin/bitcoin · GitHub 12:57 < MarcoFalke> I noticed quite a few issue reports after release of 0.15. Did no one report it previously? 12:57 < gmaxwell> 11508 was fixing an issue added in master just two days before it... so not in 0.15 wither. 12:58 < gmaxwell> MarcoFalke: I wouldn't be surprised if the crashes that 0.15.0.1 fixed caused addrman file corruption. 12:59 -!- geezas [uid253218@gateway/web/irccloud.com/x-heyxzbkgzgalorhk] has quit [Quit: Connection closed for inactivity] 13:00 < achow101> MarcoFalke: ah, ok. I forgot about that 13:00 < gmaxwell> MarcoFalke: yes it was reported prior to 0.15's release: 11079 13:03 < MarcoFalke> Oh right. (I looked at the date of the all responses and assumed it was filed 2 weeks ago as well.) 13:03 < gmaxwell> well at least you established that he could have actually thought there were issues w 0.15 13:13 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 13:19 < gmaxwell> BlueMatt: the ppa is not updated to 0.15 https://www.reddit.com/r/Bitcoin/comments/78ot5o/we_are_now_more_than_2300_nodes_satoshi_01501_o/dovrkeo/ ? 13:20 < gmaxwell> sdaftuar: so remind me a bit about how the scheduler works... when the network hits 30 minutes with no blocks will all peers make their additional connection at exactly the same time? 13:21 < BlueMatt> gmaxwell: wat 13:21 < BlueMatt> no.... 13:21 < BlueMatt> checking 13:23 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 13:29 -!- Giszmo [~leo@ip-228-233.219.201.nextelmovil.cl] has quit [Read error: Connection reset by peer] 13:30 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 240 seconds] 13:31 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 13:37 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 13:37 < sturles> I am on a 3G network, downgraded to GPRS speeds after exceeding daily quota limit. Now my node has been stuck for hours on "Timeout downloading block [...] disconnecting". Is it possible to make it more patient, or will I have to wait until after midnight for more blocks? Does it keep the dowloaded part, or is it discarded before trying to download from the next node? 13:42 < gmaxwell> discarded, unfortunately, though the timeout is 20 minutes, so if you can't transfer a block in that time you're going to fall behind regardless. 13:43 < sturles> Would be nice if it could at least keep valid downloaded transactions in the mempool, to allow for a more compact block download next time. 13:44 < sturles> It seems to download more than one block in parallel, which makes it more likely to time out. 13:45 < Chris_Stewart_5> sturles: Perhaps you could use -blocksonly if you are on mobile? 13:45 < sturles> I need the bandwidht for downloading two or more blocks in 20 minutes. 13:46 -!- jimpo [~jimpo@ec2-52-42-179-84.us-west-2.compute.amazonaws.com] has quit [Ping timeout: 252 seconds] 13:46 -!- lrvick [~weechat_u@ec2-52-27-169-212.us-west-2.compute.amazonaws.com] has quit [Ping timeout: 240 seconds] 13:46 -!- jimpo [~jimpo@ec2-52-42-179-84.us-west-2.compute.amazonaws.com] has joined #bitcoin-core-dev 13:46 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 13:46 -!- merehap_ [~sean@c-73-239-115-62.hsd1.wa.comcast.net] has quit [Ping timeout: 252 seconds] 13:46 < sturles> Chris_Stewart_5: That would not be helpful, I think. I would have to download every block in full, instead of just the unseen parts (ca compact block). 13:47 < Chris_Stewart_5> sturles: I think it would eliminate your mempool problems, but it might not matter since you have to dl the entire block any way 13:48 < sturles> I don't have a mempool problem that I am aware of. 13:49 < sturles> How does sending transactions work with -blocksonly? I guess fee estimation will be off, and privacy will certainly be worse since all unconfirmed transactions I know about are my own. 13:50 -!- merehap_ [~sean@c-73-239-115-62.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 13:51 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 13:51 -!- lrvick [~weechat_u@ec2-52-27-169-212.us-west-2.compute.amazonaws.com] has joined #bitcoin-core-dev 13:57 < Chris_Stewart_5> sturles: That would be a problem AFAIK 13:59 < gmaxwell> sturles: the timeout is increased when there are more blocks in flight. 14:00 < gmaxwell> sturles: it can't get anything from the partially sent block because its sent as a large single message. the bitcoin p2p layer deals with messages as big atomic units. 14:01 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ifdohirtusuqvnnt] has joined #bitcoin-core-dev 14:01 < gmaxwell> It would technically be possible to do something like tear viable transactions out of a partially sent block when disconnecting a peer but it would be a big pile of tricky additional code. 14:01 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 252 seconds] 14:02 < gmaxwell> sturles: its interesting to me that you had block downloads fail on a running node with a mempool. they should have been fetched via compact blocks and been fast to transfer. 14:02 < gmaxwell> I wonder why it didn't. 14:08 < sipa> gmaxwell: he must have been behind already 14:08 < sturles> My node had been offline for several hours, and had downloaded up to the tip about 25 minutes before the speed was downgraded. Perhaps the mempool was not up to date yet when the network speed was limited? 14:08 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has joined #bitcoin-core-dev 14:09 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 14:09 < sturles> I assume progress=1.000000 means it doesn't know about any newer blocks. 14:09 < bitcoin-git> [bitcoin] theuni opened pull request #11562: bench: use std::chrono rather than gettimeofday (master...bench-clock-chrono) https://github.com/bitcoin/bitcoin/pull/11562 14:09 < gmaxwell> no progress is meaningless when its near 1, its just based on timestamps. 14:10 < gmaxwell> sturles: right your mempool only learns about new txn coming in, and most txn getting confirmed now were broadcast quite a while ago (mempool is draining out) 14:10 < gmaxwell> so probably a block came in after you were limited and had very few mempool hits, and you fetched it and couldn't manage it in 20 minutes. 14:10 < sturles> height=491698 was downloaded at 17:48:40 UTC, seconds after my speed was downgraded. 14:11 < sturles> I now have "blocks": 491699, which means one block has been successfully downloaded after that. 14:12 < gmaxwell> you might end up back in sync if you -connect to a single peer. ... other peers sending you txn while you fetch that block might be making the difference. 14:13 < sturles> I think I'll just wait 47 minutes for a new day. :-) 14:14 < gmaxwell> thanks for reporting, I think I know what we need to do to better handle things like this... just so many things to do, and not enough time. 14:19 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 14:19 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 14:20 -!- REm559 [5f1ffc74@gateway/web/freenode/ip.95.31.252.116] has joined #bitcoin-core-dev 14:20 -!- REm559 [5f1ffc74@gateway/web/freenode/ip.95.31.252.116] has quit [Client Quit] 14:29 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 14:30 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 14:31 -!- eck [~eck@fsf/member/eck] has quit [Client Quit] 14:31 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 14:47 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-buzvrvqvkwoqawjc] has joined #bitcoin-core-dev 14:52 -!- wxss_ [~chatzilla@89.238.178.92] has joined #bitcoin-core-dev 14:52 -!- wxss [~chatzilla@89.238.178.92] has quit [Ping timeout: 258 seconds] 14:52 -!- wxss_ is now known as wxss 14:59 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev 15:00 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 15:04 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has quit [Client Quit] 15:04 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 15:05 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 15:07 -!- wraithm [~wraithm@unaffiliated/wraithm] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 15:08 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev 15:09 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #bitcoin-core-dev 15:09 -!- wraithm [~wraithm@unaffiliated/wraithm] has quit [Client Quit] 15:12 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 15:13 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has quit [Quit: afk] 15:15 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 15:17 -!- wvr- [~wvr@17.red-81-44-205.dynamicip.rima-tde.net] has quit [Ping timeout: 264 seconds] 15:19 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev 15:21 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 15:22 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 15:26 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds] 15:27 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 15:28 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 15:44 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 15:59 -!- CubicEarth [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 16:05 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #bitcoin-core-dev 16:06 -!- wraithm [~wraithm@unaffiliated/wraithm] has quit [Client Quit] 16:11 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 16:15 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #bitcoin-core-dev 16:16 -!- wraithm [~wraithm@unaffiliated/wraithm] has quit [Client Quit] 16:17 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has quit [Quit: afk] 16:17 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #bitcoin-core-dev 16:22 -!- CubicEarth [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 16:23 -!- d_p_ [~d_p@gateway/tor-sasl/dp/x-51976874] has quit [Ping timeout: 248 seconds] 16:24 -!- wraithm [~wraithm@unaffiliated/wraithm] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 16:32 -!- d_p_ [~d_p@gateway/tor-sasl/dp/x-51976874] has joined #bitcoin-core-dev 16:37 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev 16:40 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 258 seconds] 16:49 -!- Guest51752 [adefdb11@gateway/web/freenode/ip.173.239.219.17] has quit [Quit: Page closed] 17:00 -!- mxg [~mxg@rrcs-67-251-193-154.nyc.biz.rr.com] has quit [Quit: afk] 17:01 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Read error: Connection reset by peer] 17:22 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 17:43 -!- mxg [~mxg@2604:2000:e8c3:c700:6ced:9db0:3689:b0e3] has joined #bitcoin-core-dev 17:45 -!- mxg [~mxg@2604:2000:e8c3:c700:6ced:9db0:3689:b0e3] has quit [Client Quit] 17:45 -!- mxg [~mxg@2604:2000:e8c3:c700:6ced:9db0:3689:b0e3] has joined #bitcoin-core-dev 17:51 < bitcoin-git> [bitcoin] promag opened pull request #11563: Improve CheckBlockIndex performance (master...2017-10-improve-checkblockindex) https://github.com/bitcoin/bitcoin/pull/11563 18:00 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 18:01 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ifdohirtusuqvnnt] has quit [Quit: Connection closed for inactivity] 18:04 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Remote host closed the connection] 18:05 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 18:05 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Read error: Connection reset by peer] 18:16 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 18:17 -!- Antranik [2f9ae3ca@gateway/web/freenode/ip.47.154.227.202] has joined #bitcoin-core-dev 18:19 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 18:22 -!- axsion [1832635f@gateway/web/freenode/ip.24.50.99.95] has joined #bitcoin-core-dev 18:25 < Antranik> how about them dev forks ey 18:26 -!- axsion [1832635f@gateway/web/freenode/ip.24.50.99.95] has quit [Ping timeout: 260 seconds] 18:39 -!- arowser [~quassel@106.120.101.38] has quit [Ping timeout: 258 seconds] 18:46 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 255 seconds] 19:00 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 19:17 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 19:18 < jb55> #bitcoin-forks 19:26 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 19:26 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 19:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 19:50 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 19:54 -!- Giszmo [~leo@pc-224-130-104-200.cm.vtr.net] has quit [Ping timeout: 260 seconds] 19:54 -!- xinxi [~xinxi@39.109.214.22] has quit [Remote host closed the connection] 19:55 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 19:57 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 20:00 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 246 seconds] 20:08 -!- Giszmo [~leo@ip-140-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 20:20 -!- wxss [~chatzilla@89.238.178.92] has quit [Remote host closed the connection] 20:27 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 20:54 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 260 seconds] 20:54 -!- mxg [~mxg@2604:2000:e8c3:c700:6ced:9db0:3689:b0e3] has quit [Quit: afk] 21:00 < gmaxwell> sdaftuar: do we learn about a peer's tip from GETHEADERS messages they send us... e.g. if they send us a getheaders whos locator starts with our current tip will we update them to that 21:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 21:21 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 21:27 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 260 seconds] 21:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:41 -!- sipa [~pw@unaffiliated/sipa1024] has quit [Ping timeout: 246 seconds] 21:41 -!- sipa [~pw@2001:19f0:ac01:2fb:5400:ff:fe5b:c3ff] has joined #bitcoin-core-dev 21:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 22:01 -!- cheetah2 [~cheetah2@172.242.103.133] has joined #bitcoin-core-dev 22:02 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 22:02 -!- randy-waterhouse [~kiwigb@103.231.90.138] has joined #bitcoin-core-dev 22:03 -!- randy-waterhouse [~kiwigb@103.231.90.138] has quit [Changing host] 22:03 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev 22:04 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Client Quit] 22:06 -!- randy-waterhouse [~kiwigb@103.231.90.138] has joined #bitcoin-core-dev 22:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 22:06 -!- randy-waterhouse [~kiwigb@103.231.90.138] has quit [Changing host] 22:06 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev 22:24 -!- xinxi [~xinxi@39.109.214.22] has joined #bitcoin-core-dev 22:27 -!- Ejy_ [2a6d8f12@gateway/web/freenode/ip.42.109.143.18] has joined #bitcoin-core-dev 22:32 -!- Cryptobit [~Cryptobit@2604:2000:71d5:e500:ef25:5b1c:d633:3daf] has joined #bitcoin-core-dev 22:42 -!- Provoostenator [~textual@210.0.232.132] has joined #bitcoin-core-dev 22:52 -!- jonasschnelli [~jonasschn@bitcoinsrv.jonasschnelli.ch] has quit [Changing host] 22:52 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has joined #bitcoin-core-dev 22:55 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has joined #bitcoin-core-dev 22:58 -!- Cryptobit [~Cryptobit@2604:2000:71d5:e500:ef25:5b1c:d633:3daf] has quit [Quit: Konversation terminated!] 23:00 -!- cheetah2 [~cheetah2@172.242.103.133] has quit [Quit: Mutter: www.mutterirc.com] 23:02 -!- Ejy_ [2a6d8f12@gateway/web/freenode/ip.42.109.143.18] has quit [Ping timeout: 260 seconds] 23:07 -!- Cogito_Ergo_Sum [~Myself@athedsl-314925.home.otenet.gr] has joined #bitcoin-core-dev 23:07 -!- Cogito_Ergo_Sum [~Myself@athedsl-314925.home.otenet.gr] has quit [Changing host] 23:07 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 23:22 -!- xinxi [~xinxi@39.109.214.22] has quit [Ping timeout: 248 seconds] 23:23 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-kmslojrsexfbeeoe] has joined #bitcoin-core-dev 23:37 -!- jdouglas74 [32f6edee@gateway/web/freenode/ip.50.246.237.238] has joined #bitcoin-core-dev 23:37 < bitcoin-git> [bitcoin] fanquake closed pull request #7601: [WIP] HTLC implementation in the wallet (master...zkcp) https://github.com/bitcoin/bitcoin/pull/7601 23:47 -!- jdouglas74 [32f6edee@gateway/web/freenode/ip.50.246.237.238] has quit []