--- Day changed Wed Dec 27 2017 00:01 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 00:03 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has quit [] 00:07 -!- Danilo_ [~quassel@179.97.232.153] has quit [Read error: Connection reset by peer] 00:09 -!- Danilo_ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 00:09 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 00:10 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 00:26 -!- motoxk [43a46082@gateway/web/freenode/ip.67.164.96.130] has joined #bitcoin-core-dev 00:45 -!- motoxk [43a46082@gateway/web/freenode/ip.67.164.96.130] has quit [Ping timeout: 260 seconds] 00:48 -!- rabidus [~rabidus@91.145.115.22] has quit [Read error: Connection reset by peer] 00:48 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:49 -!- rabidus [~rabidus@91-145-115-22.bb.dnainternet.fi] has joined #bitcoin-core-dev 00:55 -!- rabidus [~rabidus@91-145-115-22.bb.dnainternet.fi] has quit [Ping timeout: 240 seconds] 00:56 -!- rabidus [~rabidus@91-145-115-22.bb.dnainternet.fi] has joined #bitcoin-core-dev 01:04 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has quit [Ping timeout: 272 seconds] 01:19 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 01:20 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 01:27 -!- Gordon__ [3d87148e@gateway/web/freenode/ip.61.135.20.142] has joined #bitcoin-core-dev 01:29 -!- Gordon__ [3d87148e@gateway/web/freenode/ip.61.135.20.142] has quit [Client Quit] 01:30 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 01:31 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 01:31 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-tnjfsyxwhgdlmhhs] has joined #bitcoin-core-dev 01:39 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 01:40 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 01:47 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 01:49 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 01:49 < meshcollider> would it make more sense to have the rpc cookie file stored in the "files" argument section or the "rpc" argument section 03:04 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 03:04 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 03:19 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 03:23 -!- xiedeacc_ [~xiedeacc@122.226.183.88] has joined #bitcoin-core-dev 03:25 -!- karanlearns [67d8d48d@gateway/web/freenode/ip.103.216.212.141] has joined #bitcoin-core-dev 03:25 -!- xiedeacc [~xiedeacc@122.226.185.78] has quit [Ping timeout: 240 seconds] 03:26 < karanlearns> hi , i cloned from github and installed on my online computer. i also added few commits to create segwit address 03:26 < karanlearns> i then copied the bitcoin-qt file from bin folder to my other offline computer. 03:27 < karanlearns> i get this error when i try to run latest source bitcoin-qt from offline computer 03:27 < karanlearns> error while loading shared libraries: libboost_system.so.1.63.0: cannot open shared object file: No such file or directory 03:31 < rafalcpp> karanlearns: move this question to #bitcoin imo. How ever the problem seems to be that you do not have lib boost system installed (system wide) on the target offline computer 03:32 < karanlearns> rafalcpp: this was working fine when i copied the 0.15.1 release bin file to offline computer 03:34 < karanlearns> earlier - i had copied bitcoin-qt from bin/ of the release 0.15.1 on my offline computer and it worked fine. 03:35 < karanlearns> now when i cloned from github,added one commit , make, install and then copied bitcoin-qt file from bin on offline computer - i got error 03:36 < karanlearns> "error while loading shared libraries: libboost_system.so.1.63.0: cannot open shared object file: No such file or directory" 03:36 < rafalcpp> karanlearns: you mean the officially released binaries worked? 03:37 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 03:37 < karanlearns> rafalcpp: yes 03:37 < karanlearns> then i needed one commit not present in released binary. so i cloned, added the commit, make, install 03:38 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 03:38 < karanlearns> and then copied the bitcoin-qt file from src folder first, then tried with bitcoin-qt under bin folder 03:39 < karanlearns> copied to offline computer and bitcoin-qt gives error 03:39 < karanlearns> i created a question here as well - https://bitcoin.stackexchange.com/questions/66695/error-while-loading-shared-libraries-libboost-system-so-1-63-0-cannot-open-sha 03:39 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 03:41 < rafalcpp> karanlearns: official binaries are from Gitian. It could be building it differently then normal Make, e.g. static linking some libraries like boost system. While your normal ./configure + make does not 03:42 < arubi> use this https://github.com/bitcoin/bitcoin/blob/master/depends/README.md 03:45 < karanlearns> arubi: for tails 64 bit - what should i do , i cannot easily figure from the docs. 03:45 < karanlearns> shall i do this make HOST = aarch64-linux-gnu 03:46 < arubi> no that's for arm 64 03:47 < arubi> karanlearns, run `gcc -v` I guess and look at the "Target: " , for me it's "Target: x86_64-linux-gnu" 03:47 < karanlearns> i need the one for 64 bit linux present here - https://bitcoin.org/en/download 03:47 < rafalcpp> karanlearns: target computer is 64 bit PC right? 03:47 < karanlearns> ok 03:47 < karanlearns> yes 03:47 < karanlearns> tails os = linux 64 bit 03:48 < rafalcpp> karanlearns: and you build on what, also 64 bi PC, 64 bit linux? 03:48 < rafalcpp> karanlearns: and you build on what, also 64 bit PC, 64 bit linux? 03:48 < karanlearns> so i just need to do make host = 03:48 < karanlearns> instead of make 03:48 < karanlearns> yes 03:48 < karanlearns> rafalcpp: yes 03:48 < arubi> it's more than that 03:49 < arubi> you have to build the stuff in depends too 03:49 < rafalcpp> if you build and run on same architecture (64 bit intel/amd, 64 bit linux os) then the host=... option is not needed, skip it. Continue to the paragraph below about installing dependencies 03:54 < rafalcpp> arubi: I'm not sure if that README alone address his issue. Doesn't he need to either 1) install lib boost on target OS, or 2) use options to make the build be a [partially] static one? 03:55 < karanlearns> everything works great on my online computer already from cloned,modified source 03:55 < rafalcpp> karanlearns: easiest would be imo to install libboost package (not -dev, just the regular one) on the target offline machine 03:55 < arubi> iirc, it's cd into the depends dir, run make (with host set or not), go back to the root dir, run configure with the prefix flag set to the depends build dir, run make 03:55 < karanlearns> now i need to build this for my target system so that target system doesnt look for libboost_system.so 03:56 < arubi> it's not that the target is wrong, the binary you built is link dynamically 03:57 < arubi> you'll want to use the depends system to build statically with the proper versions of the libs 03:57 < arubi> s/link/linked/ 03:58 < rafalcpp> karanlearns: yeap try that method with cd and make in deps first as above; let me know if it worked :) 04:02 < karanlearns> arubi: thanks - i am trying this out. 04:03 < karanlearns> rafalcp: thanks, i shall report back. 04:03 < karanlearns> rafalcpp: thanks, i shall report back. 04:09 -!- Danilo__ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 04:10 -!- Danilo_ [~quassel@179.97.232.153] has quit [Ping timeout: 252 seconds] 04:22 < sipa> karanlearns: you can do a depends build if you want release-like binaries without the overhead of gitian's determistic build system 04:22 < arubi> already linked ^ 04:23 < sipa> ok, cool, i didn't read backlog 04:24 -!- Danilo_ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 04:26 -!- Danilo__ [~quassel@179.97.232.153] has quit [Ping timeout: 252 seconds] 04:26 -!- karanlearns [67d8d48d@gateway/web/freenode/ip.103.216.212.141] has quit [Ping timeout: 260 seconds] 04:30 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 04:48 -!- Danilo__ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 04:50 -!- Danilo_ [~quassel@179.97.232.153] has quit [Ping timeout: 255 seconds] 04:53 -!- dbit [4b5314c8@gateway/web/freenode/ip.75.83.20.200] has quit [Ping timeout: 260 seconds] 05:00 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:21 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 05:29 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-tnjfsyxwhgdlmhhs] has quit [Quit: Connection closed for inactivity] 05:31 -!- xiedeacc [~xiedeacc@183.236.3.13] has joined #bitcoin-core-dev 05:52 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 05:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 05:55 -!- rsb [1f1f3739@gateway/web/freenode/ip.31.31.55.57] has joined #bitcoin-core-dev 06:00 -!- Danilo__ [~quassel@179.97.232.153] has quit [Read error: Connection reset by peer] 06:01 -!- Danilo_ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 06:03 -!- Kozuch [~Kozuch@81.0.198.168] has joined #bitcoin-core-dev 06:03 -!- banavara [7aac9433@gateway/web/freenode/ip.122.172.148.51] has joined #bitcoin-core-dev 06:06 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 272 seconds] 06:06 -!- rsb [1f1f3739@gateway/web/freenode/ip.31.31.55.57] has quit [Ping timeout: 260 seconds] 06:08 < rafalcpp> why Bitcoin chooses to link libc dynamically? any pros/cons? 06:10 < contrapumpkin> on macOS, it's effectively required to link it dynamically, to be well behaved. Not that everyone respects that... 06:11 < contrapumpkin> are you concerned about something in particular? 06:14 < rafalcpp> contrapumpkin: I'm generally learning how Bitcoin chooses to use static vs dynamic linking and why so 06:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 06:14 < contrapumpkin> do you understand the pros and cons in other contexts? 06:16 < contrapumpkin> I don't think it's all that different for bitcoin, unless you're concerned about someone injecting malicious code by swapping out a dynamically linked dependency. But if they're futzing with executable code on your computer, you're probably screwed anyway (they could do LD_PRELOAD, poke around in memory, and various other shenanigans to mess with your running node) 06:16 < sipa> rafalcpp: release binaries have it statically, no? 06:17 < sipa> or, as BlueMatt tells me irl "because otherwise resolv.conf doesn't work properly" 06:18 < contrapumpkin> because some glibcs interpret nsswitch.conf differently? 06:24 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.] 06:33 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 06:34 -!- Cogito_Ergo_Sum [~Myself@80.107.151.135] has joined #bitcoin-core-dev 06:34 -!- Cogito_Ergo_Sum [~Myself@80.107.151.135] has quit [Changing host] 06:34 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 06:50 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 06:51 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 06:54 < rafalcpp> sipa: no, released (Gitian) binary dynamically links libc, also librt, libgcc, libpthread, (and ld), and libm in bitcoind but not in -cli. (ldd bitcoin-cli shows) 06:55 < contrapumpkin> those are all pretty basic runtime libs 06:56 < rafalcpp> indeed. Though some could be moved to static too, so I wondered about this reasoning 06:57 < contrapumpkin> I take it you're only asking about the linux situation? 06:57 -!- banavara [7aac9433@gateway/web/freenode/ip.122.172.148.51] has quit [Ping timeout: 260 seconds] 06:59 < rafalcpp> contrapumpkin: nope, for all platforms too 07:00 < contrapumpkin> on macOS, those libraries are all lumped into one called libSystem (minus libgcc/librt which are replaced with their LLVM counterparts), and you're expected to dynamically link against it, because Apple doesn't commit to a syscall ABI from the kernel 07:00 < contrapumpkin> the big exception here is Go, who ignored the advice and wrote their own syscall wrappers, so go binaries compiled before 1.7 will break on recent macOS 07:00 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 240 seconds] 07:03 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 07:03 -!- Guyver2_ [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 07:04 -!- Guyver2_ [AdiIRC@guyver2.xs4all.nl] has quit [Read error: Connection reset by peer] 07:05 -!- photonclock_ [~photonclo@47.37.153.193] has quit [Quit: photonclock_] 07:07 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 07:07 -!- xiedeacc [~xiedeacc@183.236.3.13] has quit [Quit: Leaving] 07:09 -!- xiedeacc_ [~xiedeacc@122.226.183.88] has quit [Remote host closed the connection] 07:12 -!- vasp [~antony@modemcable139.60-131-66.mc.videotron.ca] has quit [Ping timeout: 268 seconds] 07:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 07:15 -!- LordCow [~lordcow@lordcow.org] has left #bitcoin-core-dev [] 07:16 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qxbtcwlnapqovmia] has quit [Quit: Connection closed for inactivity] 07:17 -!- promag_ [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 07:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Read error: Connection reset by peer] 07:18 -!- promag_ [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 07:21 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 07:22 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:24 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 07:25 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 07:26 -!- luis__ [c9a26cc8@gateway/web/freenode/ip.201.162.108.200] has joined #bitcoin-core-dev 07:27 -!- Giszmo [~leo@ip-26-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 07:33 < tyrick> where is the new segwit UI code? I checkout out sipa201709_segwitwallet2 07:33 < tyrick> But not seeing new UI there 07:35 -!- luis__ [c9a26cc8@gateway/web/freenode/ip.201.162.108.200] has quit [Ping timeout: 260 seconds] 07:40 < sipa> tyrick: it'll give you segwit addresses by default everywhere 07:41 -!- Giszmo [~leo@ip-26-236-219-201.nextelmovil.cl] has quit [Ping timeout: 240 seconds] 07:41 < contrapumpkin> oh, is it using bech32 now? 07:41 < sipa> you can control the type of addresses with the -addresstype command line / config option 07:41 < sipa> contrapumpkin: p2sh-p2wpkh by default 07:41 < sipa> bech32 if you ask for it 07:43 < contrapumpkin> nice 07:43 < tyrick> nice job! 07:43 < contrapumpkin> this is to shut up all the people asking for segwit by default? 07:43 < contrapumpkin> erm, I mean, to improve adoption 07:44 < sipa> contrapumpkin: the interesting thing is that about 90% of the complication in that PR is dealing with backward compatibility 07:44 < sipa> (downgrading software, restoring backups, ...) 07:44 < sipa> otherwise having segwit in the wallet would likely have happened much faster 07:44 < contrapumpkin> yeah, makes sense 07:45 < tyrick> Is this being released as 0.16? 07:45 < sipa> tyrick: likely 07:45 < sipa> (it's not even merged yet into master, much less included in a releasr) 07:47 < contrapumpkin> the schnorr stuff only helps space efficiency with multiple inputs to a txn, not outputs, right? 07:48 -!- Kozuch [~Kozuch@81.0.198.168] has quit [Ping timeout: 250 seconds] 07:52 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:53 < sipa> contrapumpkin: indeed 07:54 -!- finkan [~finkan@c80-216-92-154.bredband.comhem.se] has joined #bitcoin-core-dev 07:55 -!- Giszmo [~leo@ip-20-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 07:59 -!- finkan [~finkan@c80-216-92-154.bredband.comhem.se] has quit [Remote host closed the connection] 08:01 -!- mangoknight [~mangoknig@209.148.63.66] has joined #bitcoin-core-dev 08:06 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 08:09 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 08:09 < bitcoin-git> [bitcoin] jb55 opened pull request #12035: [qt] change µBTC to bits (master...qt-bits) https://github.com/bitcoin/bitcoin/pull/12035 08:11 -!- Giszmo [~leo@ip-20-236-219-201.nextelmovil.cl] has quit [Quit: Leaving.] 08:13 < jb55> is anyone working on schnorr stuff? 08:13 -!- Giszmo [~leo@ip-20-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 08:16 < contrapumpkin> jb55: from a similar question I asked yesterday, 08:16 < contrapumpkin> [13:31:53] to the extent that they're talking about anything specific, i believe they're talking about the aggregate signature proposal that gmaxwell sipa and myself are working on 08:16 < jb55> nice 08:22 -!- mangoknight [~mangoknig@209.148.63.66] has quit [Quit: mangoknight] 08:25 -!- mangoknight [~mangoknig@209.148.63.66] has joined #bitcoin-core-dev 08:31 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 08:32 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 08:35 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 08:38 -!- vasp [~antony@modemcable139.60-131-66.mc.videotron.ca] has joined #bitcoin-core-dev 08:39 -!- helpplx [4f100b5e@gateway/web/freenode/ip.79.16.11.94] has joined #bitcoin-core-dev 08:40 < rafalcpp> so cool, so there could be then services to recover dust of various people, and pay then out of bound, e.g. by fiat, or charging their LN? 08:40 < helpplx> hi, i tried to send a tx from bitcoin core with too low fee it seems, it shows as 0/not broadcasted yet. trying to use pushtx services shows the fee is too low. it deducted the balance from the bitcoin-core wallet.. what should i do? restart the wallet? if so will the funds return there? thatnks, sorry 08:40 < helpplx> its 25 btc 08:40 < helpplx> :( 08:41 < helpplx> " Error sending transaction: insufficient priority and fee for relay. " blockcypher push tx shows, and blockchain pushtx shows Validation Error: Insufficient fee. Please try again with a higher fee... bitcoin console showsTX decode failed (code -22) when broadcasting with sendrawtx 08:44 -!- alf1 [57a8acd2@gateway/web/freenode/ip.87.168.172.210] has joined #bitcoin-core-dev 08:44 < alf1> hi! 08:45 < alf1> anyone dev here? 08:45 < alf1> or support guy? 08:45 < contrapumpkin> alf1: ask your question and if someone can answer, they will (or will tell you where to ask instead) 08:46 < contrapumpkin> this is not a support channel though 08:48 < helpplx> im sorry too for asking a support question but its a 25 btc transaction. sendrawtransaction fails, i dont understand if the btc are still in my wallet if i restart the bitcoin core wallet..only this..thanks guys 08:48 -!- Guest4EF9DB [~snufff@176.79.165.64] has joined #bitcoin-core-dev 08:53 -!- mangoknight [~mangoknig@209.148.63.66] has quit [Quit: mangoknight] 08:56 < helpplx> ..+ 08:56 -!- Giszmo [~leo@ip-20-236-219-201.nextelmovil.cl] has quit [Quit: Leaving.] 08:56 -!- Giszmo [~leo@ip-20-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 08:57 < jb55> helpplx alf1: try asking on bitcoin.stackexchange.com 08:59 < helpplx> thanks but its really a "yes" or "no" question, the devs here know this..i used bitcoin-core wallet, set the fee to low (24 hours) and this mess happend. balance is deducted but tx not broadcated. do i need to restart btc core to get those 25 btc (390k $) back into the sender wallet? thanks for the work. 09:01 < provoostenator> contrapumpkin: I made PR #11991 to add a bech32 checkbox in the GUI, which is on top of sipa's changes. 09:01 < gribble> https://github.com/bitcoin/bitcoin/issues/11991 | [qt] Receive: checkbox for bech32 address by Sjors · Pull Request #11991 · bitcoin/bitcoin · GitHub 09:02 < alf1> okay, i try: i have transfer btcs from bitpanda.com to my bitcoin core wallet (0.15.1). (transaction ID 41354056bfe77f201d1aa098b2a2b34505aa9d4812935c44cf66a417abcde3ed). but i cant working with btc, because its still pending. i still waiting for "availible". i try -rescan, but it isnt working. can anybody help? 09:02 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 09:04 < helpplx> is this hard to get a yes or no from the official irc channel of the software i just used to send 390k$ and got issues? sorry but holy shit im stressed out 09:06 < rabidus> calm down. official channel is #bitcoin 09:12 < contrapumpkin> helpplx: short answer is that the core client never gets rid of your private keys unless you delete them yourself, so if the txn really wasn't broadcast, the money is still yours. If it was broadcast and the client is just being weird and not showing you that, then the money is going where you wanted it to. I don't see many chances for bad outcomes 09:13 < rafalcpp> helpplx: this channel is only about C++/etc developers who code bitcoin core client. Ask in #bitcoin. And as others say, you can NOT lose your money by sending it with too low fee. 09:15 < helpplx> thanks, tx shows as "Status: 0/offline, has not been successfully broadcast yet" on my wallet (sender).. so i can safely restart it? and funds will be returned.. 09:18 < helpplx> after restarting it shows the same..balance deducted..shit.. 09:18 -!- snufff [~snufff@83.223.234.232] has joined #bitcoin-core-dev 09:22 -!- Guest4EF9DB [~snufff@176.79.165.64] has quit [Ping timeout: 268 seconds] 09:23 -!- snufff [~snufff@83.223.234.232] has quit [Read error: Connection reset by peer] 09:24 -!- Guest4EF9DB [~snufff@dsl-165-64.bl27.telepac.pt] has joined #bitcoin-core-dev 09:32 < provoostenator> I might be witnessing #10646 live. Trying to gather some useful info. What aspect of catching up on the latest blocks uses gigabytes of disk I/O but <5% CPU and 350 MB memory, while hardly decreasing the number of blocks left for > 10 minutes? 09:32 < gribble> https://github.com/bitcoin/bitcoin/issues/10646 | Windows Gui becomes non responsive after "Done loading" · Issue #10646 · bitcoin/bitcoin · GitHub 09:32 -!- pkx2 [~pkx@unaffiliated/pkx] has quit [Remote host closed the connection] 09:32 < provoostenator> (on OSX though) 09:32 < sipa> provoostenator: low dbcache? 09:32 < provoostenator> 5 GB 09:33 < sipa> pruning on? 09:33 < provoostenator> Not pruned. I'm running a bitcoind instance in the background, but not on the same network. Also running btcd in the background. So there's probably a lot of disk I/O getting in the way from these competing things. 09:33 < provoostenator> But the machine is very responsive otherwise. 09:34 < provoostenator> Mmm, it also only has 2 peers, that's odd 09:36 < provoostenator> It only received data from one of those peers, and just 5 MB 09:38 < provoostenator> getmemoryinfo -> {"locked": {"used": 32704, "free": 491584, "total": 524288, "locked": 524288,"chunks_used": 1022, "chunks_free": 899}} 09:38 < helpplx> im importing a full datadir from another client (same linux, diff laptop), and keeping only the original wallet.dat. will this return my 25 btc to the wallet? thanks 09:39 < sipa> helpplx: this channel is not for support, take this elsewhere 09:40 -!- Guest4EF9DB [~snufff@dsl-165-64.bl27.telepac.pt] has quit [Ping timeout: 256 seconds] 09:41 < provoostenator> getblockchaininfo takes 64 seconds to respond, but UI remains responsive. 09:41 < helpplx> its a issue of the wallet, it didint warn me. i selected "low fee, 24 hours", it created a transaction that the network doesnt accept. is not my fault, at least add a warning. where to ask? #bitcoin is sandboxed nobody replies its a joke 09:42 < sipa> helpplx: try https://bitcoin.stackexchange.com 09:42 < provoostenator> Oh and as I said in the Github ticket, this is the SegWit wallet branch, though slightly outdated. I'll make sure to update it so I can get more useful info if it happens again. 09:43 < sipa> provoostenator: is the I/O due to bitcoin core, or from other processes? 09:43 < provoostenator> BitcoinQT 09:44 < provoostenator> Bitcoin Core wrote 3.2 GB so far and read 4 GB, not sure how much bitcoind and btcd read/wrote in the same time period. 09:44 < sipa> is it writing the whole time, or only reading, or writing in batches? 09:45 < sipa> bitcoind == Bitcoin Core? 09:45 < provoostenator> No, I meant "Bitcoin Core" when I said "BitcoinQT" (the name of the GUI process) 09:46 < provoostenator> It seems to be reading and writing at the same time, 158 reads/sec, 61 writes/sec. Not sure how aggregated that is. 09:46 < provoostenator> I can run top with your favorite arguments... 09:46 < sipa> the expected behaviour is that it's reading pretty much the whole time, and only writing when flushing 09:47 < sipa> you can see the flushing by seeing the size of the dbcache (in the uodatetip log line) go down 09:47 -!- koltenb [48bf62c9@gateway/web/freenode/ip.72.191.98.201] has joined #bitcoin-core-dev 09:48 -!- koltenb [48bf62c9@gateway/web/freenode/ip.72.191.98.201] has quit [Client Quit] 09:49 < provoostenator> And I assume you'd see memory use drop during a flush? I don't see that. It's climing slowly, maybe a couple of MB per minute, at about 400 MB now. Total system memory usage is only 9 GB out of 16. 09:50 < helpplx> it still shows the deducted balance wtf 09:50 < sipa> it should go up until it hits the limit, and then drop back to zero 09:50 < helpplx> what can i do seriously? this is bad 09:51 < sipa> helpplx: i'm sure this is a serious problem for you, but this is not the place to ask. people here are at work and have their own priorities. on stackexchange or other fora there are far more people who can help you 09:52 < provoostenator> Right, that's not happening; and it really shouldn't hit the limit of 5 GB anytime soon Do you mean debug.log or another file? I don't see any "tip" entries for this session. 09:53 < sipa> debug.log should always contain those entries 09:53 < sipa> UpdateTip 09:54 < provoostenator> Oh wait: UpdateTip: new best=0000000000000000008adf168e59c00d74f5a0077993e0c3848eefd82e4daa9c height=500856 version=0x20000000 log2_work=87.723434 tx=285685879 date='2017-12-24 16:07:09' progress=0.997127 cache=22.2MiB(169291txo) 09:55 < sipa> yes 09:55 < sipa> the cache= field 09:55 < helpplx> you understand thousands of people could suffer the same "bug" where the wallet creates invalid tx? if 25 btc its not important i dont know what is lol. i just asked what to do, like "that tx will return to you in X hours, chill" or "do this or that, fine" is ok. 09:59 < provoostenator> sipa: the cache just increased every block during this session: https://gist.github.com/Sjors/a9a383175a6c00e126e090df61dd39e8 09:59 < sipa> helpplx: if you suspect there is a bug, you can also file an issue on https://github.com/bitcoin/bitcoin/issues 09:59 < sipa> helpplx: i don't have time to look into all details of your situation, but i suspect it will just eventually either confirm, or cancellable using abandontransaction 10:00 -!- Danilo__ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 10:01 < provoostenator> Note the block index 369541ms on line 44 , which I assume is there the UI was handing 10:01 < sipa> that's 6 minutes 10:01 < sipa> that may just be the flush 10:02 -!- Danilo_ [~quassel@179.97.232.153] has quit [Ping timeout: 240 seconds] 10:04 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 10:04 < provoostenator> Meanwhile disk I/O is now at 3.9 / 5.22 GB (from 3.2 / 4 GB 20 minutes ago) 10:05 < provoostenator> (normally I would just kill everthing in the background and things generally get better, but I'll leave those on now) 10:06 < helpplx> Transaction not eligible for abandonment (code -5) 10:06 -!- Guest4EF9DB [~snufff@dsl-165-64.bl27.telepac.pt] has joined #bitcoin-core-dev 10:07 < sipa> helpplx: that means the transaction is in the mempool and will confirm when a miner picks it up 10:08 -!- Guest4EF9DB is now known as snufff 10:08 -!- hirishaway is now known as hirish 10:08 < sipa> helpplx: in any case, either the transaction goes through or it does not; you don't lose money 10:08 < sipa> helpplx: now, please, go to the proper forums 10:15 < sipa> provoostenator: i'm confused, what is the unexpected behaviour you're observing? 10:15 < sipa> is it during a flush? 10:15 < sipa> you'd expect it do several GB of writes during a flush 10:18 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Ping timeout: 240 seconds] 10:18 -!- Guest4EF9DB [~snufff@dsl-165-64.bl27.telepac.pt] has joined #bitcoin-core-dev 10:22 -!- snufff [~snufff@dsl-165-64.bl27.telepac.pt] has quit [Ping timeout: 268 seconds] 10:23 < provoostenator> Ok, so you're saying it's been flushing for the past 30 minutes? Flushing what exactly? Is there any way to know for sure? 10:23 < sipa> are there new lines being produced in the log? 10:24 < sipa> flushing the utxo changes 10:24 < provoostenator> yes, every time it receives a block 10:24 < sipa> flushing is blocking 10:24 < sipa> so no 10:24 < sipa> you wouldn't see anything during a flush 10:25 < provoostenator> Right, so there's some other reason why it's slowly reading and writing gigabytes of data... 10:26 < sipa> there shouldn't really been any writes at all 10:26 -!- snufff [~snufff@83.223.234.232] has joined #bitcoin-core-dev 10:26 -!- snufff [~snufff@83.223.234.232] has quit [Client Quit] 10:26 < sipa> apart from writing the new block to disk 10:26 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #bitcoin-core-dev 10:26 < sipa> oh, with txindex enabled you'd see much more writes 10:26 < sipa> if that turned on? 10:26 < provoostenator> Oh yes, I probably should have mentioned that. 10:26 < sipa> yes, that will kill performamce 10:27 < provoostenator> That's an understatement. 10:27 < sipa> i don't believe actual progress is that much slowed down by it 10:28 < sipa> but it's not optimized in any way, really 10:29 < provoostenator> txindex is useful if you want to run Lightning against your own full node. So presumably more people will run into this, if performance really is a problem. Although I should compare against a scenario of not having other processes with disk i/o in the background. 10:29 -!- Guest4EF9DB [~snufff@dsl-165-64.bl27.telepac.pt] has quit [Ping timeout: 248 seconds] 10:29 < provoostenator> Does it have to rewrite the index every time a tx comes in? 10:31 < sipa> provoostenator: what? 10:31 < sipa> does loghtning require txindex?! 10:31 < jb55> no 10:32 < sipa> that's pretty terrible 10:32 < provoostenator> eclair does: https://github.com/ACINQ/eclair 10:32 < jb55> clightning does not 10:32 < provoostenator> Obviously lightning doesn't intrisically. 10:32 < provoostenator> So does lnd I believe, although they currently don't support bitcoin core yet. 10:33 < provoostenator> btcd is taking two weeks to just do an IBD, because it doesn't have any of Core's recent performance enhancement stuff. But I've never tried that without txindex=1 10:34 < sipa> well it's ridiculous to assume end users can run with txindex imho 10:34 < provoostenator> I guess now I have an excuse to try https://github.com/ElementsProject/lightning (at least the README doesn't specify that such an index is needed) 10:34 < jb55> it's a bit buggy but it works sometimes 10:35 < sipa> it's for debugging or running a rudinentary explorer like thing 10:35 < provoostenator> sipa: is it inherently resource intensive? 10:37 < jb55> I want to write a standalone indexing daemon but I wonder how much internal state I would need... 10:37 < provoostenator> lnd will let you connect to somebody else's node fairly easily, but that uses the still experimental neutrino protocol. 10:38 < provoostenator> eclair needs RPC and ZMQ and sends and receive directly using the Core wallet, so hard to avoid the problem there. 10:39 < provoostenator> I don't know what they need the index for, I'd have to dig a bit more and maybe file some Github tickets there to make them rethink that. 10:39 < molz> lnd requires txindex in bitcoind too 10:40 < provoostenator> molz: yes, but in *somebody elses* bitcoind :-) 10:40 < sipa> provoostenator: just the idea that you'd need the entire history of the currency for any end user application is already ridiculous - it being fully indexed even more so 10:45 < provoostenator> I asked: https://github.com/lightningnetwork/lnd/issues/527 10:48 < provoostenator> I'll ask the Eclair folks as well once I know a bit more why lnd needs this. Anyway, I'll let it run for a few more hours here... will let you know if anything interesting happens. 10:51 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 10:52 -!- alpha_red [~jampajeen@223.205.235.201] has joined #bitcoin-core-dev 10:54 < alpha_red> disconnect 10:54 -!- alpha_red [~jampajeen@223.205.235.201] has quit [Client Quit] 10:57 < gmaxwell> if something needs txindex that means that it is incompatible with pruning, which means that it is at least eventally incompatible with decenteralized operation. 10:59 -!- Cache_Money [~Cache_Mon@c-24-22-208-82.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 11:00 < provoostenator> gmaxwell: it could at least use a txindex that starts at the block height of the oldest open channel I assume. 11:01 < provoostenator> But as I said, I have no idea why they need it at all. Hopefully there's a better approach possible. 11:02 -!- alpha_red [~jampajeen@223.205.235.201] has joined #bitcoin-core-dev 11:02 -!- Giszmo [~leo@ip-20-236-219-201.nextelmovil.cl] has quit [Ping timeout: 240 seconds] 11:02 < provoostenator> My guess would be that they're not tracking any state and just tell the node "hey, have you seen this specific tx id yet?". And if so, tell the user the channel just got closed / they got cheated. 11:08 < cluelessperson> why use berkeleydb for wallet.dat ? 11:10 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 11:10 < luke-jr> cluelessperson: only because nobody has done the work of replacing it, basically 11:12 < zelest> lets migrate it to mysql! *trollface* 11:12 * Randolf votes for PostgreSQL 11:12 -!- pindarhk_ [sid105966@gateway/web/irccloud.com/x-ehxgcujcfarhtxgh] has quit [Ping timeout: 252 seconds] 11:12 -!- robby938 [sid238281@gateway/web/irccloud.com/x-vswrocdweertpaai] has quit [Ping timeout: 252 seconds] 11:12 -!- wbnns [sid105317@21/bitcoin/binns] has quit [Ping timeout: 252 seconds] 11:12 < cluelessperson> luke-jr: Ah. Well my intention isn't to disrespect. I just don't know why it would have been chosen. Perhaps there was some discussion about effeciency or large scaling for vendors, I dunno. I'm a HUGE fan of json, sqlite, postgres myself. 11:12 < zelest> any relation database sounds a bit overkill tbh 11:13 -!- ThisAsYou [sid214210@gateway/web/irccloud.com/x-zsjwiiwaqzsylvtm] has quit [Ping timeout: 252 seconds] 11:13 -!- NicolasDorier [sid129442@gateway/web/irccloud.com/x-uubyigqtqlzdjgpe] has quit [Ping timeout: 252 seconds] 11:13 < cluelessperson> zelest: not for exchanges. 11:13 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-ieceermpktuwxjbq] has quit [Ping timeout: 240 seconds] 11:13 < zelest> true 11:13 -!- CodeShark [sid126576@gateway/web/irccloud.com/x-jbubhekbfqypyqtl] has quit [Ping timeout: 252 seconds] 11:13 < zelest> but for a single users' wallet.dat 11:13 -!- exit70 [sid231392@gateway/web/irccloud.com/x-gzycamqwloaqzxew] has quit [Ping timeout: 255 seconds] 11:13 -!- nOgAnOo [sid146237@gateway/web/irccloud.com/x-suybxbscomlkkpbo] has quit [Ping timeout: 264 seconds] 11:13 -!- trotski2000 [sid206086@gateway/web/irccloud.com/x-kdzmleqpjfdmimhr] has quit [Ping timeout: 264 seconds] 11:13 -!- rubensayshi [sid201751@gateway/web/irccloud.com/x-pobdpflbfjjdcayp] has quit [Read error: Connection reset by peer] 11:13 -!- Varunram [sid210151@gateway/web/irccloud.com/x-ncdsyoxqflvkkcvm] has quit [Read error: Connection reset by peer] 11:13 -!- ibrightly [sid113387@gateway/web/irccloud.com/x-pplqfyntkefbzyso] has quit [Ping timeout: 250 seconds] 11:13 -!- aspect_ [sid151486@gateway/web/irccloud.com/x-gkmuwnjivgxyujyd] has quit [Read error: Connection reset by peer] 11:13 -!- derbumi [sid186430@gateway/web/irccloud.com/x-wdeeldhonzocmizb] has quit [Read error: Connection reset by peer] 11:13 < cluelessperson> zelest: I've had cases where people used tens of thousands of addresses. 11:13 -!- Bosma [sid103570@gateway/web/irccloud.com/x-yqiftmilteomxipn] has quit [Write error: Connection reset by peer] 11:13 < cluelessperson> has to scale 11:13 -!- mappum [sid43795@gateway/web/irccloud.com/x-gppzkjqwqmxmwufe] has quit [Ping timeout: 255 seconds] 11:13 -!- eragmus [sid136308@gateway/web/irccloud.com/x-fypjtyvwcufqgyoe] has quit [Ping timeout: 252 seconds] 11:14 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-awcpjtqkdsybdhat] has quit [Ping timeout: 250 seconds] 11:14 -!- mariorz [sid490@gateway/web/irccloud.com/x-fhtgxosxcnlrxeap] has quit [Ping timeout: 255 seconds] 11:14 -!- lejitz [sid205154@gateway/web/irccloud.com/x-bigshmoihzgpptyb] has quit [Ping timeout: 264 seconds] 11:14 -!- brg444 [sid207215@gateway/web/irccloud.com/x-rggvmajaktsnkjdq] has quit [Ping timeout: 264 seconds] 11:14 -!- Muis [sid26074@gateway/web/irccloud.com/x-orvtmzdnchuvtnmv] has quit [Ping timeout: 272 seconds] 11:14 -!- wallet42 [sid154231@gateway/web/irccloud.com/x-tgwwwwyjopcikrhp] has quit [Ping timeout: 272 seconds] 11:14 -!- sugarpuff [sid92283@gateway/web/irccloud.com/x-gqxzmxdhrrzqhony] has quit [Ping timeout: 255 seconds] 11:14 -!- nejon [uid38993@gateway/web/irccloud.com/x-lhbbvqvwjrtmfcth] has quit [Ping timeout: 240 seconds] 11:14 < cluelessperson> luke-jr: Can you help me understand the skills I need to help? I'm planning on taking classes, but that's going to take me months-year to even start working in c++ 11:14 < eck> berkeleydb can handle tens of thousands of database entries too 11:14 -!- epic [sid37137@gateway/web/irccloud.com/x-popvyvbxolbewxlz] has quit [Ping timeout: 255 seconds] 11:14 -!- michagogo [uid14316@wikia/Michagogo] has quit [Ping timeout: 240 seconds] 11:14 -!- mturquette [sid66043@gateway/web/irccloud.com/x-tgedrohzntedshwt] has quit [Ping timeout: 250 seconds] 11:14 -!- klow [sid213056@gateway/web/irccloud.com/x-hmqznljfujgqzmvq] has quit [Ping timeout: 272 seconds] 11:15 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-hrqmjnqngzxcldyq] has quit [Ping timeout: 276 seconds] 11:15 < cluelessperson> eck: it's just impossible for laymen to use/troubleshoot in this state. 11:15 < zelest> i dunno, i might lack the understanding of the bitcoin protocol, but having a whole database because a few single corner cases has to scale feels a bit bloated tbh :o 11:15 < cluelessperson> outside of through bitcoin core itself 11:15 < cluelessperson> Hell, I'm doing this in python 11:15 < Randolf> For a Wallet application written in Java, I'd lean heavily to using the H2 database engine for a high-performance pure-Java SQL option (it has a built-in AES encryption option that encrypts the entire database file): http://www.h2database.com/ 11:15 < cluelessperson> w = db.DB() 11:15 < cluelessperson> w.open("wallet.dat", "main", db.DB_BTREE, db.DB_RDONLY) 11:16 < cluelessperson> for i in w.items(): print(i) and it's 1000 lines of human unreadable info. :/ 11:16 -!- Giszmo [~leo@181-163-46-243.baf.movistar.cl] has joined #bitcoin-core-dev 11:17 < zelest> this just reminds me of when people setup mail servers.. they demand a fully configured database server and yet they setup a single domain with 3 mail accounts.. that's it.. :P 11:18 < zelest> but yeah, mayhaps have the option to use different database backends, if needed.. might be a bit much to support though? 11:20 < Randolf> zelest: That's where you start getting into setting up a "driver" layer so that others can contribute support for their favourite databases in a modular fashion. 11:21 * zelest nods 11:22 -!- hirish is now known as hirishaway 11:23 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 11:24 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 11:26 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-anxgjctdpjadalor] has joined #bitcoin-core-dev 11:26 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 11:26 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Ping timeout: 240 seconds] 11:27 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Read error: Connection timed out] 11:33 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 11:33 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 11:34 -!- sugarpuff [sid92283@gateway/web/irccloud.com/x-soqldylegbicorcj] has joined #bitcoin-core-dev 11:35 < luke-jr> cluelessperson: BDB isn't a relational database; Satoshi chose it, so nobody will have a certain answer why 11:39 -!- alpha_red [~jampajeen@223.205.235.201] has quit [Quit: Lost terminal] 11:42 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 265 seconds] 11:42 -!- michagogo [uid14316@wikia/Michagogo] has joined #bitcoin-core-dev 11:42 -!- lejitz [sid205154@gateway/web/irccloud.com/x-usmblvoqfiqivkgt] has joined #bitcoin-core-dev 11:43 -!- mappum [sid43795@gateway/web/irccloud.com/x-zjpsiozdrqgsznkg] has joined #bitcoin-core-dev 11:43 -!- rubensayshi [sid201751@gateway/web/irccloud.com/x-insbbmbpzaqjdkmd] has joined #bitcoin-core-dev 11:43 -!- pindarhk_ [sid105966@gateway/web/irccloud.com/x-kufizyqxnaiehpep] has joined #bitcoin-core-dev 11:44 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-llfrfguazbcygoyn] has joined #bitcoin-core-dev 11:44 < sipa> cluelessperson: the wallet loads all data in RAM anyway, the file format is pretty much irrelevant, it could be a text file 11:44 -!- exit70 [sid231392@gateway/web/irccloud.com/x-pklzjzigdlxxtrja] has joined #bitcoin-core-dev 11:45 -!- wallet42 [sid154231@gateway/web/irccloud.com/x-jpvvydibghscttdo] has joined #bitcoin-core-dev 11:45 -!- ThisAsYou [sid214210@gateway/web/irccloud.com/x-pfwmbmkothqyzjdy] has joined #bitcoin-core-dev 11:45 -!- brg444 [sid207215@gateway/web/irccloud.com/x-eqzedhvskjmxlxzg] has joined #bitcoin-core-dev 11:45 -!- klow [sid213056@gateway/web/irccloud.com/x-kptiqhzecebgdcep] has joined #bitcoin-core-dev 11:45 -!- nOgAnOo [sid146237@gateway/web/irccloud.com/x-fisthmcuuurrjhst] has joined #bitcoin-core-dev 11:45 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 11:46 -!- NicolasDorier [sid129442@gateway/web/irccloud.com/x-dihdicihreyibhsj] has joined #bitcoin-core-dev 11:46 -!- robby938 [sid238281@gateway/web/irccloud.com/x-mcperenxczgdgrcx] has joined #bitcoin-core-dev 11:47 -!- trotski2000 [sid206086@gateway/web/irccloud.com/x-kvhpfjmzwcljtlci] has joined #bitcoin-core-dev 11:47 -!- Bosma [sid103570@gateway/web/irccloud.com/x-nzstlbbckkmwsnue] has joined #bitcoin-core-dev 11:48 -!- CodeShark [sid126576@gateway/web/irccloud.com/x-dmsxjppardkwgvpf] has joined #bitcoin-core-dev 11:49 -!- wbnns [sid105317@21/bitcoin/binns] has joined #bitcoin-core-dev 11:49 -!- ibrightly [sid113387@gateway/web/irccloud.com/x-qhsjmrgijmlucefy] has joined #bitcoin-core-dev 11:51 -!- Varunram [sid210151@gateway/web/irccloud.com/x-togftzvbyjcvsieu] has joined #bitcoin-core-dev 11:53 -!- mturquette [sid66043@gateway/web/irccloud.com/x-rlumbfctefvmfasl] has joined #bitcoin-core-dev 11:53 -!- eragmus [sid136308@gateway/web/irccloud.com/x-gttwybxuopfxcetn] has joined #bitcoin-core-dev 11:53 -!- Muis [sid26074@gateway/web/irccloud.com/x-cjqjjujsbgchknzm] has joined #bitcoin-core-dev 11:56 -!- derbumi [sid186430@gateway/web/irccloud.com/x-cwfbbnbjnpvibpbf] has joined #bitcoin-core-dev 11:57 -!- aspect_ [sid151486@gateway/web/irccloud.com/x-pcwteqbaakyxvdnz] has joined #bitcoin-core-dev 11:59 -!- mariorz [sid490@gateway/web/irccloud.com/x-qwxxtbsnshxuccus] has joined #bitcoin-core-dev 12:03 -!- quantbot_ [~quantbot@74.73.145.69] has joined #bitcoin-core-dev 12:05 -!- finkan [~finkan@c80-216-92-154.bredband.comhem.se] has joined #bitcoin-core-dev 12:06 -!- quantbot [~quantbot@cpe-74-73-145-69.nyc.res.rr.com] has quit [Ping timeout: 248 seconds] 12:07 -!- quantbot_ [~quantbot@74.73.145.69] has quit [Ping timeout: 256 seconds] 12:08 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 12:09 -!- jb55 [~jb55@184.70.144.230] has joined #bitcoin-core-dev 12:11 -!- Cache_Money [~Cache_Mon@c-24-22-208-82.hsd1.wa.comcast.net] has quit [Quit: Cache_Money] 12:13 < cluelessperson> Thoughts on this structure? https://hastebin.com/raw/wenabegati 12:27 < sipa> cluelessperson: please read the gist i linked to in the segwit pr 12:28 < gmaxwell> cluelessperson: redesigning things you do not understand is a bad reflex. 12:30 -!- finkan [~finkan@c80-216-92-154.bredband.comhem.se] has quit [] 12:30 < cluelessperson> gmaxwell: I feel that's incredibly insulting and unhelpful. It's a wallet file that stores keys, what do I not understand about it? 12:30 < cluelessperson> what's hard to understand about it? 12:30 < sipa> cluelessperson: that hardly the only thing it stores 12:32 < cluelessperson> sipa: what do you feel I'm missing? transaction cache, block height last seen?, hash of the wallet file so if it's modified, it knows to rescan the blockchain ? 12:32 < cluelessperson> or utxo 12:33 < sipa> all of those and more 12:34 < sipa> redeemscripts, public keys 12:34 < sipa> pre generated keys / keypool 12:34 < sipa> labels 12:34 < sipa> tinestamps, key birthdates 12:36 < phantomcircuit> not to mention most of the data is binary and storing it in json is a huge blowup 12:37 < sipa> cluelessperson: and no offense, but if you need to ask "what's so hard about it", you clearly haven't really done much effort to understand what it is doing now 12:38 < sipa> cluelessperson: that may be fine if you'd want to design something from scratch, but we're stuck with pretty demanding compatibility requirements (you can still load a 0.2.10 wallet.dat file and it will work) 12:38 < cluelessperson> sipa: I'm suggesting a framework to make life easier for users using bitcoin. Extracting and dealing with keys at this point is inevitable and currently painful. All those things you mentioned fit into this framework. 12:38 < sipa> cluelessperson: that still doesn't give a helpful upgrade scenario 12:39 < sipa> the difficulty is not in designing a storage scheme, but in how it fits into all current use cases 12:39 < cluelessperson> This is more of an example of how I want to make life easier for users, by no means would it be exactly this if I seriously suggest a change. :/ 12:39 < sipa> well, please go read the gist i linked to in the segwit pr 12:39 -!- jb55 [~jb55@184.70.144.230] has quit [Ping timeout: 260 seconds] 12:39 < cluelessperson> sipa: sorry, I don't see a link from you 12:40 < sipa> it talks how things work now, and how they can move towards something that's more like what you're describing 12:40 < sipa> i'm on my phone in a train; it's linked in the segwit wallet pr 12:40 < cluelessperson> ah, I'll find it then 12:41 < sipa> also, no we're not seriously going to store wallets in JSON 12:41 -!- jb55 [~jb55@184.70.144.230] has joined #bitcoin-core-dev 12:41 < sipa> though something like what you're describing may be useful as a dump/import format 12:44 -!- pkx2 [~pkx@unaffiliated/pkx] has quit [Read error: Connection reset by peer] 12:44 < gmaxwell> cluelessperson: sorry man, but when you batter your head against something, then don't understand it, and respond by offering a redesign, _THAT_ is insulting and disrespectful. It's sending a message that everyone else is such idiots that they couldn't manage to do it the simple way that you just tossed out. That is seldom the case, usually when someone doesn't understand something thats beca 12:44 < gmaxwell> use they haven't fully internalized the requirements, so they have no idea what its doing... and that is why attempting to redesign when you don't understand things is a bad reflex. 12:45 < cluelessperson> gmaxwell: You're right, I'm sorry. It's not really my intention to throw out your expertise. I just deal with users day in and day out that have difficulty accessing their keys, which I feel is inevitable. 12:46 < sipa> yes, there is no doubt that things can be improved a lot 12:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:46 < sipa> but changing things in this context is also very hard 12:46 < cluelessperson> agreed. 12:47 < gmaxwell> "difficulty accessing their keys"-- 12:47 < gmaxwell> I have no freeking idea what that means. 12:48 < sipa> letting users access their keys was never a design goal 12:48 < sipa> letting them manage them at a high level however perhaps should be 12:48 < cluelessperson> gmaxwell: Currently, the only method that seems reliable for exporting private keys, is to get the bitcoin core binary, start it, and use the console to dumpwallet. 12:48 < gmaxwell> (1) there is a wallet dump which exports keys directly. (2) for HD wallet there probably should eventually be no private keys in the wallet except for master keys. (3) It is extraordinarly dangerous for users to work with keys directly, and has resulted losses of thousands of bitcoins, manually handling keys is not something we should encourage. 12:49 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 12:49 < cluelessperson> which often leads to misunderstanding like, "should I let it sync before I can export?" and things like that, there's a phenomenal amount of ignorance ;) 12:49 < gmaxwell> cluelessperson: yes, and that is how it has to be ultimately; because they keys don't even need to be stored in the wallet files. 12:49 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:49 < gmaxwell> some of that misunderstanding is due to the overly agressive initial sync screen, which could be clarified some. 12:50 < cluelessperson> gmaxwell: the problem is that the multiple softwares/wallets all have different methods of using/storying/importing keys. that's what's forcing users to use them directly. 12:51 < gmaxwell> They shouldn't be doing that, they should transfer funds. manually mucking with keys is supremely dangerous and for unsophicated users will reliably result in funds loss. 12:51 < gmaxwell> not to mention that keys from one program may not even be compatible with anything else. 12:52 < cluelessperson> Maybe I should write some procedure paper based on this topic. 12:53 < cluelessperson> gmaxwell: Another reason is that users sometimes go through a lot of effort to memorize seeds. They don't want to send to another wallet, they want to keep it. 12:53 < cluelessperson> that's what causes moving keys between softwares. 12:54 < gmaxwell> you cannot use different 'seeds' in different wallets. They aren't compatible and cannot reasonably be because the functionality is different. 12:54 < Bosma> Private keys have use now because they're used to claim fork funds. 12:54 < cluelessperson> Bosma: paper wallets 12:55 < sipa> Bosma: yeah &$#@! 12:55 < gmaxwell> cluelessperson: which no one should ever be using. 12:56 < gmaxwell> cluelessperson: and which are unrelated to bitcoin core in any case. (they cause a desire for _import_ which we support, not export) 12:57 < cluelessperson> gmaxwell: Another idea comes to mind. Suppose I should focus on writing up a list of reasons *why* I felt I'd want to change the wallet.dat structure. Part of it was to make it portable, modifiable, and allow users to just insert new keys at whim, from Electrum, BIP39, xpriv, xpub, WIF, mini, etc. 12:57 < gmaxwell> that cant work. 12:57 -!- gmaxwell [gmaxwell@wikimedia/KatWalsh/x-0001] has left #bitcoin-core-dev [] 12:57 < cluelessperson> Honestly, it's not the wallet.dat that's the problem, it's that I'm asking for more features, and they're not being presented what the requested features are. 12:59 < cluelessperson> I'm confused how that can't work. Electrum does that to an extent. 13:02 < jb55> one of the first things I did was get my keys out of core, never felt comfortable having them in some arbitrary binary blob. I never recommend core wallet new people for that reason, I've seen so many lose their hd/etc. I force them to all get trezors now :P 13:02 < sipa> i agree there 13:03 < sipa> i don't think compatibility with other wallet software, or allowing inserting keys at a wh 13:03 < sipa> but there are benefits to a clearly understandable structure, which we currently really don't have 13:04 < cluelessperson> sipa: The only reason I mention electrum is because they did derivation first, so I consider them a standard. 13:04 < sipa> cluelessperson: and there's no reason to assume we'll want to be compatible - or if we do, that we can remain so 13:04 -!- Giszmo [~leo@181-163-46-243.baf.movistar.cl] has quit [Quit: Leaving.] 13:05 < jb55> hopefully we can crunch out a clean wallet upgrade path for hd hww's <> core soon. It's so hairy though gahh 13:05 < sipa> compatibility is nice when possible, but generally different wallets have such different ideas about what even constitutes a wallet that i don't think it's a worthwhile goal on its own 13:05 < sipa> jb55: yes! 13:06 < cluelessperson> Here's the thing 13:07 < cluelessperson> Pretty much everything uses BIP32/44 | xpriv,xpub right? 13:07 < sipa> no 13:07 < sipa> bip32 yes 13:07 < jb55> sipa no like 44 13:07 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Read error: Connection reset by peer] 13:07 < cluelessperson> so, we could just store that and allow importing functions in general 13:07 < sipa> but electrum does not follow bip44 afaik 13:07 < sipa> cluelessperson: have you read my gist? 13:08 < sipa> (it suggests that) 13:10 < zelest> I have a /usr/local/lib/db4 (4.6.21) and I try to compile with --with-incompatible-bdb, yet ./configure fails with "libdb_cxx headers missing". By looking at the config.log, it tries to include bdb4.8/db_cxx.h, how can I specify what directory to look in? 13:10 < zelest> compile/configure* 13:10 < sipa> cluelessperson: but my gist also explains why doing so right now is very hard 13:11 < jb55> zelest: try 4.8? 13:11 < sipa> zelest: it needs at least 4.7 or 4.8 13:11 < sipa> (i forgot which of the two is the minimum) 13:13 < zelest> Ah, fair enough :) 13:14 < zelest> then I give up completely on the ports version of bdb :) 13:18 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Ping timeout: 260 seconds] 13:18 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:22 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:25 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-meiqojleyvdnhefq] has joined #bitcoin-core-dev 13:29 -!- epic [sid37137@gateway/web/irccloud.com/x-nvnsmpkzbgyaiwul] has joined #bitcoin-core-dev 13:32 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-umcdadvrswufzprf] has joined #bitcoin-core-dev 13:32 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-rcgcavgpmfcwnrgt] has joined #bitcoin-core-dev 13:38 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 13:43 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has joined #bitcoin-core-dev 13:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:54 -!- qube_ [25bc9519@gateway/web/freenode/ip.37.188.149.25] has joined #bitcoin-core-dev 13:54 -!- jb55 [~jb55@184.70.144.230] has quit [Ping timeout: 248 seconds] 13:58 < zelest> wumpus, around? 13:58 -!- qube_ [25bc9519@gateway/web/freenode/ip.37.188.149.25] has quit [Ping timeout: 260 seconds] 14:01 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:13 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 14:16 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 14:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 14:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Read error: Connection reset by peer] 14:26 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:27 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 14:32 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has quit [] 14:37 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 14:40 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:57 -!- bahat [c5d2181f@gateway/web/freenode/ip.197.210.24.31] has joined #bitcoin-core-dev 15:04 -!- bahat [c5d2181f@gateway/web/freenode/ip.197.210.24.31] has quit [Quit: Page closed] 15:05 -!- pkx2 [~pkx@unaffiliated/pkx] has quit [Remote host closed the connection] 15:06 -!- Giszmo [~leo@ip-65-233.219.201.nextelmovil.cl] has joined #bitcoin-core-dev 15:06 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 15:24 -!- detire [~detire@unaffiliated/detire] has joined #bitcoin-core-dev 15:27 -!- Giszmo [~leo@ip-65-233.219.201.nextelmovil.cl] has quit [Ping timeout: 272 seconds] 15:27 -!- ryanofsky [~russ@jumpy.yanofsky.org] has quit [Quit: ZNC 1.6.5 - http://znc.in] 15:30 < zelest> If I have a file I wish to change (quite a lot) and someone has already made a pull request with the same file. How should I approach it? wumpus told me to "please base it on" the pull request. Anyone care to explain what that means or how I do that? Thanks 15:31 -!- ryanofsky [~russ@jumpy.yanofsky.org] has joined #bitcoin-core-dev 15:33 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has joined #bitcoin-core-dev 15:37 < goatpig> zelest: pull the PR locally 15:37 < goatpig> rebase your commits on top of it 15:40 < zelest> Ah, and create a PR of that? 15:40 < goatpig> im guessing you'd be submitting that way yes 15:40 < zelest> Thanks 15:42 -!- mangoknight [~mangoknig@ool-18ba9f85.dyn.optonline.net] has joined #bitcoin-core-dev 15:45 -!- vasp [~antony@modemcable139.60-131-66.mc.videotron.ca] has quit [Read error: Connection reset by peer] 15:48 -!- vasp [~antony@modemcable139.60-131-66.mc.videotron.ca] has joined #bitcoin-core-dev 15:50 -!- Giszmo [~leo@ip-187-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 15:57 -!- nejon [uid38993@gateway/web/irccloud.com/x-vicdawrpjalmxtvy] has joined #bitcoin-core-dev 15:58 -!- helpplx [4f100b5e@gateway/web/freenode/ip.79.16.11.94] has quit [Ping timeout: 260 seconds] 16:33 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has quit [Ping timeout: 265 seconds] 16:39 -!- Giszmo [~leo@ip-187-236-219-201.nextelmovil.cl] has quit [Quit: Leaving.] 16:43 -!- jb55 [~jb55@184.70.147.2] has joined #bitcoin-core-dev 16:50 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Read error: Connection reset by peer] 16:50 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 16:53 -!- digitalway [~digitalwa@mtrlpq2853w-lp140-03-69-159-160-174.dsl.bell.ca] has joined #bitcoin-core-dev 16:54 -!- motoxkx [43a46082@gateway/web/freenode/ip.67.164.96.130] has joined #bitcoin-core-dev 16:55 -!- motoxkx [43a46082@gateway/web/freenode/ip.67.164.96.130] has quit [Client Quit] 16:55 -!- motoxkx [43a46082@gateway/web/freenode/ip.67.164.96.130] has joined #bitcoin-core-dev 16:56 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 17:05 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-llfrfguazbcygoyn] has quit [Quit: Connection closed for inactivity] 17:09 -!- profall [sid29922@gateway/web/irccloud.com/x-peljetslnyukatrg] has joined #bitcoin-core-dev 17:10 -!- motoxkx [43a46082@gateway/web/freenode/ip.67.164.96.130] has quit [Quit: Page closed] 17:11 -!- motoxkx [43a46082@gateway/web/freenode/ip.67.164.96.130] has joined #bitcoin-core-dev 17:25 < achow101> are we having a meeting tomorrow? 17:45 -!- moctos [~moctos@cpe-107-9-138-59.neo.res.rr.com] has joined #bitcoin-core-dev 17:49 -!- moctos [~moctos@cpe-107-9-138-59.neo.res.rr.com] has quit [Ping timeout: 248 seconds] 17:49 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 17:59 -!- Cache_Money [~Cache_Mon@c-24-18-214-173.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 18:04 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 18:06 -!- Cache_Money [~Cache_Mon@c-24-18-214-173.hsd1.wa.comcast.net] has quit [Quit: Cache_Money] 18:07 -!- Cache_Money [~Cache_Mon@c-24-18-214-173.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 18:07 -!- Cache_Money [~Cache_Mon@c-24-18-214-173.hsd1.wa.comcast.net] has quit [Client Quit] 18:10 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 256 seconds] 18:13 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Remote host closed the connection] 18:16 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 18:22 -!- adiabat [~adiabat@45.63.20.152] has quit [Ping timeout: 248 seconds] 18:23 -!- adiabat [~adiabat@45.63.20.152] has joined #bitcoin-core-dev 18:42 -!- alpha_red [~jampajeen@223.205.235.201] has joined #bitcoin-core-dev 18:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-anxgjctdpjadalor] has quit [Quit: Connection closed for inactivity] 18:45 -!- CubicEarths [~cubiceart@73.61.11.64] has joined #bitcoin-core-dev 18:49 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has quit [Ping timeout: 248 seconds] 18:49 < echeveria> 2017-12-28 02:49:21.589437 Reindexing block file blk00854.dat... 18:49 < echeveria> 2017-12-28 02:49:23.455371 LoadExternalBlockFile: Deserialize or I/O error - Read attempted past buffer limit: unspecified iostream_category error 18:49 < echeveria> eh? 18:51 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has joined #bitcoin-core-dev 18:52 -!- jb55 [~jb55@184.70.147.2] has quit [Ping timeout: 252 seconds] 18:56 < phantomcircuit> echeveria, disk failure i believe 18:57 < echeveria> looking at the block binaries there's a bunch which fell short of being full. maybe that happens during an unclean shutdown? 18:57 < phantomcircuit> shouldn't 18:57 < phantomcircuit> but i guess a very unclean shutdown could do that 18:58 < phantomcircuit> the blockindex won't point to those but the block file itself would have the partial write 18:59 < echeveria> I'll chalk that up to random corruption. 19:05 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has quit [Ping timeout: 248 seconds] 19:06 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has joined #bitcoin-core-dev 19:06 -!- motoxkx [43a46082@gateway/web/freenode/ip.67.164.96.130] has quit [Ping timeout: 260 seconds] 19:10 -!- alpha_red [~jampajeen@223.205.235.201] has quit [Ping timeout: 265 seconds] 19:12 -!- moctos [~moctos@cpe-107-9-138-59.neo.res.rr.com] has joined #bitcoin-core-dev 19:17 -!- moctos [~moctos@cpe-107-9-138-59.neo.res.rr.com] has quit [Ping timeout: 248 seconds] 19:19 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 19:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 19:21 -!- alpha_red [~jampajeen@223.205.235.201] has joined #bitcoin-core-dev 19:25 -!- alpha_red [~jampajeen@223.205.235.201] has quit [Ping timeout: 248 seconds] 19:28 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 19:33 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 19:34 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 19:52 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 19:55 -!- eenoch is now known as eenoch_ 20:00 -!- eenoch_ is now known as eenoch 20:00 -!- eenoch is now known as eenoch_ 20:01 -!- eenoch_ [~eenoch@unaffiliated/eenoch] has quit [Quit: leaving] 20:01 -!- eenoch [~eenoch@unaffiliated/eenoch] has joined #bitcoin-core-dev 20:11 -!- Varunram [sid210151@gateway/web/irccloud.com/x-togftzvbyjcvsieu] has quit [Changing host] 20:11 -!- Varunram [sid210151@unaffiliated/varunram] has joined #bitcoin-core-dev 20:11 -!- Varunram [sid210151@unaffiliated/varunram] has quit [Changing host] 20:11 -!- Varunram [sid210151@gateway/web/irccloud.com/x-togftzvbyjcvsieu] has joined #bitcoin-core-dev 20:15 -!- nicktesla [cc1c7e8a@gateway/web/freenode/ip.204.28.126.138] has joined #bitcoin-core-dev 20:16 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Ping timeout: 260 seconds] 20:17 -!- mangoknight [~mangoknig@ool-18ba9f85.dyn.optonline.net] has quit [Quit: mangoknight] 20:32 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 20:38 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has joined #bitcoin-core-dev 20:52 -!- MrPaz [~PazPazPaz@2600:1700:f0c1:9f0:90b7:91f7:1898:e5cc] has joined #bitcoin-core-dev 21:16 -!- daniel1 [4572481f@gateway/web/freenode/ip.69.114.72.31] has joined #bitcoin-core-dev 21:20 -!- daniel1 [4572481f@gateway/web/freenode/ip.69.114.72.31] has quit [Client Quit] 21:24 -!- CubicEarths [~cubiceart@73.61.11.64] has quit [] 21:27 -!- go1111111 [~go1111111@gateway/vpn/privateinternetaccess/go1111111] has quit [Ping timeout: 264 seconds] 21:34 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has quit [Quit: mangoknight] 21:37 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has joined #bitcoin-core-dev 21:40 -!- MrPaz [~PazPazPaz@2600:1700:f0c1:9f0:90b7:91f7:1898:e5cc] has quit [Ping timeout: 265 seconds] 21:42 -!- go1111111 [~go1111111@199.231.240.191] has joined #bitcoin-core-dev 21:46 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has quit [Quit: mangoknight] 21:47 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Quit: Snoozing.] 21:51 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 21:55 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Ping timeout: 248 seconds] 21:56 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has joined #bitcoin-core-dev 22:01 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 248 seconds] 22:02 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 22:07 -!- aj [aj@cerulean.erisian.com.au] has quit [Remote host closed the connection] 22:08 -!- aj [aj@cerulean.erisian.com.au] has joined #bitcoin-core-dev 22:16 -!- obzen [49d26ff9@gateway/web/freenode/ip.73.210.111.249] has joined #bitcoin-core-dev 22:17 -!- obzen [49d26ff9@gateway/web/freenode/ip.73.210.111.249] has quit [Client Quit] 22:22 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 22:25 -!- AegisAttack [~colin@2605:6000:cdc9:3b00:70ba:5c6:f755:88a8] has joined #bitcoin-core-dev 22:26 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds] 22:28 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 22:39 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has quit [Quit: mangoknight] 22:44 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 22:49 -!- CubicEarths [~cubiceart@73.61.11.64] has joined #bitcoin-core-dev 22:49 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has joined #bitcoin-core-dev 22:52 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has quit [Read error: Connection reset by peer] 22:53 -!- mangoknight [~mangoknig@ool-457ad9bd.dyn.optonline.net] has quit [Client Quit] 23:07 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:20 -!- mangoknight [~mangoknig@ool-18ba9f85.dyn.optonline.net] has joined #bitcoin-core-dev 23:28 -!- degenorate [~degenorat@unaffiliated/degenorate] has joined #bitcoin-core-dev 23:31 -!- AegisAttack [~colin@2605:6000:cdc9:3b00:70ba:5c6:f755:88a8] has quit [Quit: Leaving] 23:32 -!- smilpent [~smilpent@unaffiliated/smilpent] has joined #bitcoin-core-dev 23:36 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 23:39 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 23:43 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Ping timeout: 248 seconds]