--- Day changed Sun Nov 12 2017 00:06 -!- cheetah2 [~cheetah2@172.242.103.133] has quit [Quit: Mutter: www.mutterirc.com] 00:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 00:09 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 00:09 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds] 00:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 00:20 -!- cheetah2 [~cheetah2@172.242.103.133] has joined #bitcoin-core-dev 00:20 -!- cheetah2 [~cheetah2@172.242.103.133] has quit [Client Quit] 00:25 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fcqmzedpwcnbzsyy] has joined #bitcoin-core-dev 00:37 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 00:41 -!- halform [~halform@173.199.80.131] has joined #bitcoin-core-dev 00:47 -!- klow [sid213056@gateway/web/irccloud.com/x-qcqzzsblmsixtpfx] has joined #bitcoin-core-dev 00:47 < ossifrage> I tried to rbf a transaction with 2 outputs, one in my wallet and one external, but it didn't mark the one from my wallet as a change address. Is this a bug? 00:47 < ossifrage> [I didn't use the change address field, just manually added it as an output] 00:49 -!- juscamarena_ [~justin@47.148.173.164] has joined #bitcoin-core-dev 00:54 -!- ibbl564rk75eu [~ibbl564rk@93.123.73.114] has joined #bitcoin-core-dev 01:06 < BGL> why can't bitcoin core start where it left off on re-indexing blocks, i seriously just had to restart twice in the last day and i'm back to zero again 01:06 -!- lalaland [32234c93@gateway/web/freenode/ip.50.35.76.147] has quit [Ping timeout: 260 seconds] 01:06 < BGL> probly not even going to finish by tomorrow 01:07 < BGL> not even sure why i bothered manually transferring the block files 01:08 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 01:08 < gmaxwell> BGL: it does continue where it left off, though if you've set your dbcache large then most of its work won't have been written to disk yet. 01:09 < BGL> it's default 01:10 < BGL> 450mb, and now i'm 7 years behind again 01:11 < BGL> for the 3rd time 01:11 < BGL> this is on a brand new ssd so .. i don't get that either 01:12 -!- nandal [~nandal@49.32.67.56] has joined #bitcoin-core-dev 01:19 -!- juscamarena_ [~justin@47.148.173.164] has left #bitcoin-core-dev ["Leaving"] 01:22 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 01:25 -!- eck [~eck@fsf/member/eck] has quit [Ping timeout: 240 seconds] 01:29 -!- nandal [~nandal@49.32.67.56] has quit [Remote host closed the connection] 01:39 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 01:51 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit [] 01:58 < luke-jr> BGL: why did you have to restart? ie, how did your computer stop doing it? 01:58 < luke-jr> might be best to take this to #bitcoin .. 01:58 < BGL> windows update 01:59 < BGL> this last time 01:59 < BGL> and the first time was because i forgot the program closes instead of minimizing to the tray by default 02:00 < BGL> i've blown a whole day, literally now 02:00 < luke-jr> hmm, I would expect a clean shutdown to work properly at least regardless of dbcache state 02:00 -!- ibbl564rk75eu [~ibbl564rk@93.123.73.114] has quit [Quit: Leaving] 02:00 < BGL> i don't know if i'd consider windows update a clean shutdown 02:01 < BGL> according to it anyways 02:02 < meshcollider> I guess the first should have been a clean shutdown though, if you just hit close? 02:03 < BGL> well i guess that's a good point i'm not sure 02:03 < BGL> i copied the blockchain, chainstate and some otehr stuff from another machine 02:03 < BGL> i'd hoped this wouldn't be so involved by doing that 02:05 -!- moroogle [d94c19c1@gateway/web/freenode/ip.217.76.25.193] has joined #bitcoin-core-dev 02:05 < BGL> but maybe i incorrectly copied some file into this new machine that's causing a problem? 02:05 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev 02:05 < luke-jr> when you start it, does it mention corruption or anything? 02:05 < BGL> no 02:07 < BGL> if i manage to get fully through and it decides to start all over then i'll just clean install and download the chain again directly 02:08 < BGL> but i sure wish this wasn't ungodly slow and gave some explanation or something 02:09 < luke-jr> it's just going to get slower and slower until the block size is reduced :< 02:10 < BGL> i was wondering if that blocks dir can be compressed for transfer? or does it not compress well at all 02:10 < BGL> by the time i thought of it i was halfway through anyways 02:23 -!- halform [~halform@173.199.80.131] has quit [Remote host closed the connection] 02:24 -!- halform [~halform@173.199.80.131] has joined #bitcoin-core-dev 02:25 < luke-jr> BGL: it probably can be compressed, but not exceptionally well with standard tools 02:26 < luke-jr> in terms of syncing, compression may be more harm than good since ideal compression could break parallelism 02:29 -!- halform [~halform@173.199.80.131] has quit [Ping timeout: 268 seconds] 02:29 -!- moroogle is now known as moakeri 02:29 -!- moakeri [d94c19c1@gateway/web/freenode/ip.217.76.25.193] has quit [Quit: Page closed] 02:30 -!- mareikaa [d94c19c1@gateway/web/freenode/ip.217.76.25.193] has joined #bitcoin-core-dev 02:39 -!- matt42 [~matthieu@alf94-3-82-66-250-214.fbx.proxad.net] has joined #bitcoin-core-dev 02:54 -!- Herptiderpty [53532b5b@gateway/web/freenode/ip.83.83.43.91] has joined #bitcoin-core-dev 02:58 -!- wxss [~chatzilla@82.221.112.213] has joined #bitcoin-core-dev 03:02 -!- ekrok_ [~ekrok@10.249.16.62.customer.cdi.no] has joined #bitcoin-core-dev 03:07 -!- JackH [~laptop@85.219.170.195] has quit [Ping timeout: 260 seconds] 03:07 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 03:16 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Read error: Connection reset by peer] 03:20 -!- JackH [~laptop@85.219.170.195] has joined #bitcoin-core-dev 03:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 03:41 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:42 < gmaxwell> [OT] TD-Linux was able to disable ME on my new T470p using me_cleaner, it was zero difficulty (releatively speaking: requires clamping a flash programmer into the board) 03:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 03:46 -!- BogatMohogat [~BogadMoho@p20030006431B01209D717D6A20143A1E.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:48 < luke-jr> gmaxwell: any effect on battery life? 03:48 < gmaxwell> luke-jr: dunno yet, not expecting so, but will test tomorrow. 03:56 < matt42> quit 03:56 -!- matt42 [~matthieu@alf94-3-82-66-250-214.fbx.proxad.net] has left #bitcoin-core-dev ["WeeChat 1.9.1"] 04:08 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 04:18 -!- tuannguyen [0137c7eb@gateway/web/freenode/ip.1.55.199.235] has joined #bitcoin-core-dev 04:19 -!- tuannguyen [0137c7eb@gateway/web/freenode/ip.1.55.199.235] has quit [Client Quit] 04:22 -!- BogatMohogat [~BogadMoho@p20030006431B01209D717D6A20143A1E.dip0.t-ipconnect.de] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:24 -!- sher48 [d5187ede@gateway/web/freenode/ip.213.24.126.222] has joined #bitcoin-core-dev 04:29 < sher48> what about big hashrate fluctuations? -28.68% _in 24 hours) is not good 04:29 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 04:35 < sher48> it's time to switch miners mostly to commission income... 04:36 -!- nandal [~nandal@49.32.79.238] has joined #bitcoin-core-dev 04:42 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 04:47 -!- JackH [~laptop@85.219.170.195] has quit [Ping timeout: 248 seconds] 05:05 -!- visitor23623 [52a418df@gateway/web/freenode/ip.82.164.24.223] has joined #bitcoin-core-dev 05:09 -!- visitor23623 [52a418df@gateway/web/freenode/ip.82.164.24.223] has quit [Ping timeout: 260 seconds] 05:32 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-uhkkrfwoweorfnic] has quit [Quit: Connection closed for inactivity] 05:32 -!- LeMiner2 is now known as Leminer 05:32 -!- Leminer [LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has quit [Changing host] 05:32 -!- Leminer [LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 05:36 -!- mareikaa [d94c19c1@gateway/web/freenode/ip.217.76.25.193] has quit [Quit: Page closed] 05:45 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 05:50 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 05:53 -!- Copperfield [5038fc84@gateway/web/freenode/ip.80.56.252.132] has joined #bitcoin-core-dev 05:54 -!- Copperfield [5038fc84@gateway/web/freenode/ip.80.56.252.132] has quit [Client Quit] 05:55 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 06:04 < bitcoin-git> [bitcoin] jBarz opened pull request #11669: Trivial: use unsigned type for delta (master...fix) https://github.com/bitcoin/bitcoin/pull/11669 06:05 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 06:07 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:07 < bitcoin-git> [bitcoin] fanquake closed pull request #11669: Trivial: use unsigned type for delta (master...fix) https://github.com/bitcoin/bitcoin/pull/11669 06:19 -!- halform [~halform@96.30.101.192] has joined #bitcoin-core-dev 06:31 -!- Fff [6a434982@gateway/web/freenode/ip.106.67.73.130] has joined #bitcoin-core-dev 06:31 -!- Fff is now known as Guest59587 06:36 -!- Guest59587 [6a434982@gateway/web/freenode/ip.106.67.73.130] has quit [Ping timeout: 260 seconds] 07:07 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:10 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 07:10 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Quit: Leaving] 07:11 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 07:17 -!- halform [~halform@96.30.101.192] has quit [Read error: Connection reset by peer] 07:18 -!- halform [~halform@182.232.113.151] has joined #bitcoin-core-dev 07:18 -!- nandal [~nandal@49.32.79.238] has quit [Remote host closed the connection] 07:40 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 268 seconds] 07:57 -!- blockchain [~linux@95.211.172.35.adsl.inet-telecom.org] has joined #bitcoin-core-dev 08:05 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 08:10 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 08:21 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 08:24 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 08:29 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 08:43 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 08:48 -!- Deacydal [~Deacyde@unaffiliated/deacyde] has quit [Read error: Connection reset by peer] 08:51 -!- halform [~halform@182.232.113.151] has quit [Remote host closed the connection] 08:52 -!- nandal [~nandal@49.32.79.238] has joined #bitcoin-core-dev 08:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 08:53 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 248 seconds] 09:08 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds] 09:09 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 248 seconds] 09:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 09:15 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 09:17 < ossifrage> Should dumprivkey work for a segwit address? validateaddress lists the address, but dumpprivkey returns 'Address does not refer to a key (code -3)' 09:27 < sher48> quit 09:27 < sher48> exit 09:28 -!- sher48 [d5187ede@gateway/web/freenode/ip.213.24.126.222] has quit [Quit: Page closed] 09:38 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 09:39 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 09:41 < sipa> ossifrage: not yet 09:43 < ossifrage> sipa, thanks... eventually I was able to backtrack to the original address I used for the 'addwitnessaddress' and the privkey for that address... 09:56 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:15 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:30 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds] 10:51 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 10:52 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:58 -!- jb55 [~jb55@d154-5-59-193.bchsia.telus.net] has joined #bitcoin-core-dev 11:05 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection] 11:09 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 11:17 < luke-jr> ossifrage: note that ordinarily people should not use dumpprivkey at all - it's for wallet debugging, nothing more 11:18 -!- owowo [ovovo@gateway/vpn/mullvad/x-rtypldbfwjhlfbls] has quit [Ping timeout: 250 seconds] 11:18 < ossifrage> luke-jr, yeah I just did that as a sanity check when the dumprivkey key was confusing me 11:18 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 11:19 < ossifrage> When I saw that none of the segwit addresses where in the dump I realized it wasn't specific to the key I was looking for 11:23 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 11:26 -!- s31415 [544a18c4@gateway/web/freenode/ip.84.74.24.196] has joined #bitcoin-core-dev 11:28 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev 11:32 < bitcoin-git> [bitcoin] mikedennis closed pull request #11670: [Docs] Update with instructions for WSL for Win 10 fall 2017 creator update (master...master) https://github.com/bitcoin/bitcoin/pull/11670 11:34 -!- nandal [~nandal@49.32.79.238] has quit [Read error: Connection reset by peer] 11:34 -!- s31415 [544a18c4@gateway/web/freenode/ip.84.74.24.196] has quit [Quit: Page closed] 11:34 < blockchain> @luke-jr why not ? I used dumprivkey to dump all my privat keys and save them seperatly 11:35 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection] 11:37 < luke-jr> blockchain: 1) you'll miss metadata for sure, 2) novices will miss change, 3) newer wallets are HD, which don't have individual per-address private keys 11:57 < blockchain> so what do you recommend. I don´t want all my bitcoins in one wallet 11:58 < blockchain> individual per-address privat keys? I have about 100 privat keys with my bitcoins in it spreaded 11:59 -!- Am3543 [6da68a9d@gateway/web/freenode/ip.109.166.138.157] has joined #bitcoin-core-dev 12:00 -!- Am3543 [6da68a9d@gateway/web/freenode/ip.109.166.138.157] has quit [Client Quit] 12:00 -!- Am6272 [6da68a9d@gateway/web/freenode/ip.109.166.138.157] has joined #bitcoin-core-dev 12:01 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev 12:02 < sipa> blockchain: bitcoin core now supports multiple wallets 12:02 < sipa> since 0.15 12:04 -!- tyrick [~tyrick@ip70-190-209-166.ph.ph.cox.net] has quit [Read error: Connection reset by peer] 12:04 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 12:06 < blockchain> i like the idea being able to redeem by privat keys on other wallets as well. So i can use my privat keys to redeem on blockchain.info for example. Its precarious ? 12:07 < sipa> you can, but you're on your own 12:07 < sipa> it's not what bitcoin core was designed for 12:08 -!- Am6272 [6da68a9d@gateway/web/freenode/ip.109.166.138.157] has quit [Quit: Page closed] 12:11 < blockchain> So actually I have saved one wallet.dat with all my bitcoins stored some years ago. Then when I want to use some bitcoin I just load one privat key into my new wallet.dat. I am somehow concerned loading my whole wallet with all my bitcoins stored evertime I want to move some bitcoins 12:12 < blockchain> Although my computer is crypted, someone might catch up while I am outside or some police raid or forced robbery. 12:12 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 12:12 < eck> I was told that there's a proposal from someone (I forget who!) to do multi-process bitcoin core, where some of the processes could be sandboxed (similar to firefox/chrome); does anyone know where I could learn more about this? 12:14 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 12:16 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 12:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 12:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 12:25 -!- wunpunch [~Alli@176.27.129.249] has joined #bitcoin-core-dev 12:28 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 12:30 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 12:31 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds] 12:35 -!- lukedashjr is now known as luke-jr 12:39 -!- jb55 [~jb55@d154-5-59-193.bchsia.telus.net] has quit [Read error: Connection reset by peer] 12:39 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 12:40 -!- jb55 [~jb55@d154-5-59-193.bchsia.telus.net] has joined #bitcoin-core-dev 12:41 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 12:41 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 12:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 12:50 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer] 12:51 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 12:55 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Quit: Snoozing.] 13:00 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tfyywcbphawbbgfj] has joined #bitcoin-core-dev 13:15 -!- jb55 [~jb55@d154-5-59-193.bchsia.telus.net] has quit [Ping timeout: 260 seconds] 13:21 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has quit [Ping timeout: 268 seconds] 13:38 -!- kbokka [4229378b@gateway/web/freenode/ip.66.41.55.139] has joined #bitcoin-core-dev 13:38 -!- kbokka [4229378b@gateway/web/freenode/ip.66.41.55.139] has quit [Client Quit] 13:40 -!- v_ [32ea47e2@gateway/web/freenode/ip.50.234.71.226] has joined #bitcoin-core-dev 13:43 -!- ZSky [~ZSky@AOrleans-654-1-115-249.w86-220.abo.wanadoo.fr] has joined #bitcoin-core-dev 13:49 -!- v_ [32ea47e2@gateway/web/freenode/ip.50.234.71.226] has quit [Quit: Page closed] 13:51 -!- Herptiderpty [53532b5b@gateway/web/freenode/ip.83.83.43.91] has quit [Quit: Page closed] 13:53 -!- doflamingo [3ae7ed1c@gateway/web/freenode/ip.58.231.237.28] has joined #bitcoin-core-dev 13:55 -!- doflamingo [3ae7ed1c@gateway/web/freenode/ip.58.231.237.28] has quit [Client Quit] 14:02 -!- ZSky [~ZSky@AOrleans-654-1-115-249.w86-220.abo.wanadoo.fr] has quit [] 14:02 -!- JackH [~laptop@alvira.static.korbank.pl] has joined #bitcoin-core-dev 14:02 -!- PaulCape_ [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 14:04 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 14:17 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 14:17 < puff> Good evening. 14:17 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 14:29 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 14:36 -!- jb55 [~jb55@184.68.16.70] has joined #bitcoin-core-dev 14:41 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 14:42 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 14:49 -!- jb55 [~jb55@184.68.16.70] has quit [Ping timeout: 248 seconds] 14:51 < luke-jr> v0.15.1.knots20171111 tagged on https://github.com/bitcoinknots/bitcoin if anyone wants to help do gitian builds 14:54 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 14:54 -!- timothy [~tredaelli@redhat/timothy] has quit [Client Quit] 14:57 -!- jb55 [~jb55@184.68.16.70] has joined #bitcoin-core-dev 14:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer] 14:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 15:14 < BGL> i think this core client really is downloading all the dat again despite it saying its reindexing blocks on disks 15:16 < sipa> why do you think so? 15:16 < BGL> it's been like 15 hours and it's at 8% 15:16 -!- oerauakk [d94c19c1@gateway/web/freenode/ip.217.76.25.193] has joined #bitcoin-core-dev 15:17 < oerauakk> "But in reality that's bullshit, full nodes are useless in the Bitcoin beyond providing connection points, what matter is the ring of inter connected mining nodes that guarantee your new transactions to reach 99% of hash power within 3 seconds." 15:17 < oerauakk> How much truth is there to this statement? 15:17 < sipa> oerauakk: full nodes are there to keep miners in check 15:18 < sipa> if all miners are honest, full nodes are useless 15:18 < sipa> but in that case, why do we have mining in the first place? 15:18 < sipa> the whole point is to design a system where we don't rely on assuming miners - or anyone - is honest 15:20 < oerauakk> sipa: but is there a limit to how many extra full nodes still benefit the network? Less nodes means more centralisation, but does more nodes mean a healthier network, or is there some threshold where there is not really any point in adding more nodes? 15:20 < oerauakk> Can more nodes actually hinder the network? 15:20 < sipa> oerauakk: *using* a full node matters 15:21 < sipa> as in: basing your economic activity on one 15:21 < sipa> not accepting transactions unless *your own* full node accepts ot 15:21 < sipa> that is how you reduce trust 15:22 < oerauakk> I see 15:22 < oerauakk> Thanks, I understand it a little better now 15:22 < sipa> you shouldn't care about others full nodes, except as an indication for how hard it is 15:23 < oerauakk> But is there any merit to the argument that adding more nodes doesn't necessarily mean a healthier network? 15:23 < oerauakk> how hard? 15:24 < sipa> adding random nodes that nobody looks at doesn't matter at all 15:24 < sipa> the network doesn't have a need for more nodes 15:25 < sipa> but the ecosystem needs much more players that *use* their own nodes 15:25 < sipa> also, this discussion probably belongs on #bitcoin 15:25 < oerauakk> Sorry, I wasn't sure where to go 15:25 < oerauakk> But thanks for your answers 15:27 < luke-jr> BGL: quite often, the bottleneck is your CPU/disk, not bandwidth 15:27 < luke-jr> BGL: it's not just loading data; it's verifying and processing it into a database 15:28 < BGL> it's on a brand new ssd and not putting more than a ~25% load on the cpu 15:28 < BGL> i've benchmarked both and they are acting as expected 15:29 < sipa> BGL: increase your dbcache 15:29 < BGL> for some reason i thought i'd save time by copying the blocks folder to this machine 15:29 < sipa> also, validation early on in the chain is limited to 1 core 15:29 < BGL> increasing that on the fly while re-indexing will make a diff? 15:30 < luke-jr> BGL: you need to restart the node to change it (although it *should* resume where it left off) 15:30 -!- oerauakk [d94c19c1@gateway/web/freenode/ip.217.76.25.193] has quit [Ping timeout: 260 seconds] 15:30 < BGL> it didn't restart where it left off when i accidentally closed the window the first time, or when windows update re-booted the machine unexpextedly 15:31 < luke-jr> I remember, hence the "should" 15:32 -!- oerauakk [3e8c840e@gateway/web/freenode/ip.62.140.132.14] has joined #bitcoin-core-dev 15:32 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 15:32 < oerauakk> sipa: can I just ask though, if adding more nodes does not necessarily benefit the network, then why is it important to have more players use their own node? 15:33 < sturles> Can I make bitcoin use segwit addresses for change now, on master, or is that still a subject for discussion on how to do it properly? 15:34 < BGL> sipa when does validation start using more than 1 core? 15:34 < luke-jr> oerauakk: I answered that already in #Bitcoin fyi 15:34 < BGL> you can't change the dbcache without a client restart 15:35 < luke-jr> sturles: pretty sure you can't right now at least 15:35 < sturles> Will it do it automatically, or optionally as an agrument to sendmany etc? 15:35 < oerauakk> luke-jr: I seem to have missed it (disconnected) 15:35 < oerauakk> could you copy? 15:36 < oerauakk> I'll switch to #bitcoin 15:36 < luke-jr> oerauakk: reposted there 15:48 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 15:50 -!- oerauakk [3e8c840e@gateway/web/freenode/ip.62.140.132.14] has quit [Quit: Page closed] 15:51 -!- PaulCapestany [~PaulCapes@ip68-100-207-53.dc.dc.cox.net] has joined #bitcoin-core-dev 15:52 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 16:00 -!- wxss [~chatzilla@82.221.112.213] has quit [Remote host closed the connection] 16:01 -!- wxss [~chatzilla@82.221.112.213] has joined #bitcoin-core-dev 16:16 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 16:20 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Quit: Mutter: http://www.mutterirc.com] 16:25 -!- ZSky [~ZSky@AOrleans-654-1-115-249.w86-220.abo.wanadoo.fr] has joined #bitcoin-core-dev 16:26 < ZSky> Hi 16:27 < ZSky> How popular is the idea of moving from hashcash to another one (not requiring ASICs) in Bitcoin core (not a fork but the real one)? 16:28 -!- Guest67384 [~chatzilla@71-92-221-248.static.mtpk.ca.charter.com] has joined #bitcoin-core-dev 16:28 -!- LumberCartel [~randolf@209.205.87.205.core.cipherkey.net] has joined #bitcoin-core-dev 16:30 -!- Guest67384 is now known as roidster 16:32 -!- JackH [~laptop@alvira.static.korbank.pl] has quit [Read error: Connection reset by peer] 16:33 -!- LumberCartel [~randolf@209.205.87.205.core.cipherkey.net] has quit [Ping timeout: 240 seconds] 16:33 -!- JackH [~laptop@alvira.static.korbank.pl] has joined #bitcoin-core-dev 16:48 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer] 16:49 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 16:52 -!- azerty [6fdd3644@gateway/web/freenode/ip.111.221.54.68] has joined #bitcoin-core-dev 16:53 -!- azerty [6fdd3644@gateway/web/freenode/ip.111.221.54.68] has quit [Client Quit] 16:54 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 16:54 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 16:56 -!- ZSky [~ZSky@AOrleans-654-1-115-249.w86-220.abo.wanadoo.fr] has quit [] 16:58 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Client Quit] 17:03 -!- wunpunch [~Alli@176.27.129.249] has quit [Read error: Connection reset by peer] 17:08 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 17:20 -!- jb55 [~jb55@184.68.16.70] has quit [Ping timeout: 268 seconds] 17:24 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Quit: Mutter: http://www.mutterirc.com] 17:24 < achow101> what's the reason for shutting down after encrypting the wallet? 17:24 < achow101> Is it not sufficient to just close and reopen the wallet? 17:26 < sipa> closing and flushing and snapshotting would be enough 17:26 < sipa> but at the tike encryption was added, there was no multiwallet 17:26 < sipa> so the only way to close the wallet was to shut down 17:27 < achow101> ah, ok. I was thinking that it should be enough to just all StopWallets, CloseWallets, and then OpenWallets after encrypting a wallet 17:27 < achow101> AFAICT that should close, flush everything, remove keys from memory, and then open again 17:28 -!- taj [6a331047@gateway/web/freenode/ip.106.51.16.71] has joined #bitcoin-core-dev 17:28 < sipa> probably 17:28 -!- taj [6a331047@gateway/web/freenode/ip.106.51.16.71] has left #bitcoin-core-dev [] 17:31 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has joined #bitcoin-core-dev 17:32 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fcqmzedpwcnbzsyy] has quit [Quit: Connection closed for inactivity] 17:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 17:41 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 17:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Client Quit] 17:44 -!- scratch_1 [~Mutter@122-237-dsl.kielnet.net] has quit [Quit: Mutter: http://www.mutterirc.com] 17:47 -!- blockchain [~linux@95.211.172.35.adsl.inet-telecom.org] has quit [Quit: Verlassend] 17:48 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Remote host closed the connection] 17:48 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has joined #bitcoin-core-dev 17:53 -!- mesh_ [Elite20673@gateway/shell/elitebnc/x-hncgbhziyjzjazic] has joined #bitcoin-core-dev 17:53 -!- CubicEarth [~cubiceart@xdsl-31-164-62-119.adslplus.ch] has quit [Ping timeout: 248 seconds] 18:16 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 18:16 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 18:43 -!- roconnor [~roconnor@host-45-58-192-10.dyn.295.ca] has joined #bitcoin-core-dev 18:44 < roconnor> Hi, are there gitian build logs of the build tty output somewhere that I can puruse? 18:48 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 18:48 < fanquake> rconnor gitian-builder/var/ 18:48 < fanquake> should be build.log and install.log 18:55 < roconnor> fanquake: is it available online somewhere? 19:13 -!- ChristianXK [23b6fefc@gateway/web/freenode/ip.35.182.254.252] has joined #bitcoin-core-dev 19:15 -!- longvnit [abe26ce6@gateway/web/freenode/ip.171.226.108.230] has joined #bitcoin-core-dev 19:15 -!- longvnit [abe26ce6@gateway/web/freenode/ip.171.226.108.230] has quit [Client Quit] 19:17 < fanquake> rconnor logs for your own build? I'd hope nope, gitian building is contained to the vm you've setup to build with. Or do you mean gitian build logs for an official release? 19:18 < fanquake> *roconnor 19:19 < fanquake> roconnor The signatures used to create the final release are available from https://github.com/bitcoin-core/gitian.sigs . There is no way to get the various build.logs from each of the individual builders. 19:20 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 19:50 < roconnor> ok ty 19:50 < achow101> besides deadlock, is there any reason that a lock is not able to be acquired? 19:51 < roconnor> I suppose I just wanted to double check if ccache is being used in the gitian builds. It seems it is, but I'm presuming to no advantage. 19:53 < achow101> roconnor: why would there be no advantage? 19:53 < roconnor> Maybe I don't understand what ccache does. I thought it avoid recompiling object files that have been compiled before. 19:55 < achow101> roconnor: yes, it does 19:55 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit [Ping timeout: 240 seconds] 19:55 < achow101> gitian builds multiple binaries for each OS target 19:55 < achow101> well, just the linux one actually 19:56 < roconnor> different OS targets? can you give an example? 19:57 < achow101> the linux build does 4 different builds, one for each list: HOSTS="i686-pc-linux-gnu x86_64-linux-gnu arm-linux-gnueabihf aarch64-linux-gnu" 19:58 < achow101> Windows does the same: HOSTS="i686-w64-mingw32 x86_64-w64-mingw32" 19:58 < achow101> osx technically does the same, but only has one host 19:58 < roconnor> how can it do x86 and arm and yet share object files? 20:00 < achow101> oh right, hmmm 20:01 < roconnor> If the ccache offers no advantage, perhaps it should be removed from the gitian builds. 20:05 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev 20:29 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 20:33 < sipa> achow101: if something elwe holds the lock already, that does not necessarily imply a deadlock 20:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1] 20:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 21:02 -!- quanlou [734f8ce8@gateway/web/freenode/ip.115.79.140.232] has joined #bitcoin-core-dev 21:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:07 -!- roidster [~chatzilla@71-92-221-248.static.mtpk.ca.charter.com] has quit [Quit: ChatZilla 0.9.92 [SeaMonkey 2.40/20160120202951]] 21:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1] 21:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 21:11 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has quit [Remote host closed the connection] 21:12 -!- quanlou [734f8ce8@gateway/web/freenode/ip.115.79.140.232] has quit [Quit: Page closed] 21:16 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00::1] has joined #bitcoin-core-dev 21:25 -!- LumberCartel is now known as Randolf 21:26 -!- Randolf is now known as LumberCartel 21:48 -!- qwerty [~wqetyy@212.133.241.10] has joined #bitcoin-core-dev 21:48 -!- qwerty is now known as Guest50579 22:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tfyywcbphawbbgfj] has quit [Quit: Connection closed for inactivity] 22:18 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00::1] has quit [Ping timeout: 240 seconds] 22:22 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-rfxpalwyzkkbouqw] has joined #bitcoin-core-dev 22:26 -!- Guest50579 [~wqetyy@212.133.241.10] has quit [Remote host closed the connection] 22:30 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev 22:31 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 240 seconds] 22:32 -!- go1111111 [~elliot@199.231.240.157] has joined #bitcoin-core-dev 22:35 < wumpus> roconnor: ccache is not used in the gitian builds at all, just for travis 22:36 -!- bitstr3am [~Mutter@50-47-107-125.evrt.wa.frontiernet.net] has joined #bitcoin-core-dev 22:36 < wumpus> together with travis' caching it makes PRs and new commits compile faster 22:38 < wumpus> it just happens that ccache is part of the depends system so it gets built automatically, it builds quickly enough that adding a NO_CCACHE option to depends likely isn't worth the extra complexity 22:46 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-emgpqgjuvncgwahu] has joined #bitcoin-core-dev 22:47 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 22:50 -!- bitstr3am [~Mutter@50-47-107-125.evrt.wa.frontiernet.net] has quit [Ping timeout: 248 seconds] 22:55 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 22:57 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 22:57 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit [] 22:59 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 23:09 -!- ChristianXK [23b6fefc@gateway/web/freenode/ip.35.182.254.252] has quit [Ping timeout: 260 seconds] 23:13 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 23:14 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 23:30 < wumpus> intermittent error in sendheaders.py test_null_locators, assert_equal(test_node.check_last_announcement(headers=[tip_hash]), True) 23:31 -!- go1111111 [~elliot@199.231.240.157] has quit [Ping timeout: 240 seconds] 23:34 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 240 seconds] 23:42 < meshcollider> wumpus: yep I've seen that one before 23:42 < meshcollider> Locally 23:43 < wumpus> indeed, this was locally too 23:43 < wumpus> will create an issue 23:43 < meshcollider> Encountered it yesterday while working on 11667 23:44 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has joined #bitcoin-core-dev 23:46 < wumpus> https://github.com/bitcoin/bitcoin/issues/11673 23:46 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 23:47 < wumpus> I've seen it on 11651, but makes no sense that it would be caused by that change 23:50 -!- qwerty [~wqetyy@212.133.241.10] has joined #bitcoin-core-dev 23:51 -!- qwerty is now known as Guest55818 23:52 -!- JackH [~laptop@alvira.static.korbank.pl] has quit [Ping timeout: 268 seconds] 23:59 < Lauda> Does 0.15.0 have any bugs that makes the software crash? 23:59 < Lauda> Any known*.