--- Day changed Fri Mar 10 2017 00:11 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:23 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev 00:27 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 00:28 -!- JackH [~laptop@79-73-184-8.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev 00:46 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 00:51 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 240 seconds] 00:58 < wumpus> baahh.. this is the second time I have trouble with the tests due to a stale qa/cache directory 00:58 < wumpus> we should probably nix it when a change in bitcoind is detected 01:00 < wumpus> e.g. write that path and sha256sum of the bitcoind used into the cache directory, and if that changes, delete it 01:02 < sipa> unsure that's worth it... breaks of the cache direction are very infrequent, i think 01:02 < sipa> at least in my experience 01:02 < wumpus> any change to the wallet, at least 01:03 < wumpus> node0 keeps a wallet from mining the initial blocks, which is usually what causes the problems, if the test expects a certain newly introduced property of transactions 01:04 < wumpus> maybe it's infrequent but it is really frustrating and can lead to hours of misdirected search for bugs if it happens 01:04 < wumpus> conceptually it's also not *valid* to use an older cache, there is no guarantee that your tests passing is worth anything 01:05 < wumpus> the new bitcoind may completely mess up the initial steps and it'd still pass because it is cached 01:06 < wumpus> but ok I'll just add a message "Using cached node state in %s" to the test output, maybe that's enough to remind people to delete it if they run into weird issues 01:06 < sipa> no, i think you're right 01:07 < sipa> we shouldn't be using outdated caches 01:08 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Read error: Connection reset by peer] 01:14 -!- Chris_Stewart_5 [~Chris_Ste@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Read error: Connection reset by peer] 01:18 -!- Victor_sueca is now known as Victorsueca 01:19 < jonasschnelli> wumpus: https://github.com/bitcoin/bitcoin/pull/9294#issuecomment-285612826 01:20 < jonasschnelli> This is strange... can it be a caching issue? 01:20 < jonasschnelli> I can't see a reason why the dump is different on your machine than on mine / travis. 01:21 < jonasschnelli> Maybe you have a chance and check the file "wallet.unencrypted.dump" (maybe pastebin it) when running with --nocleanup 01:23 * jonasschnelli starting Ubuntu 16.04 01:28 < jonasschnelli> sipa: maybe you have a chance to review #9965. It seems that you ate most familiar with that code part. It also touches the segwit.py test (where I'm not sure if I did the right thing). 01:29 < wumpus> jonasschnelli: yes it was a caching issue 01:30 < jonasschnelli> Great! *relief* 01:30 < wumpus> jonasschnelli: that why I wrote the posts above ^^ 01:33 < wumpus> I think we should store a hash of the bitcoind executable in the cache directory and delete it when it mismatches 01:37 -!- riemann [~riemann@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 01:39 < jonasschnelli> wumpus: Ah. Thanks. I haven't read the scrollback. Yes. Good idea with the binary-hash mismatch detection. 02:06 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 02:14 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Ping timeout: 260 seconds] 02:26 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev 02:26 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev 02:30 -!- MarcoFalke [~none@198.12.116.246] has joined #bitcoin-core-dev 02:31 < MarcoFalke> 1 02:41 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 02:43 -!- BirneGetreide_ [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has joined #bitcoin-core-dev 03:22 -!- MarcoFalke_ [~none@198.12.116.246] has joined #bitcoin-core-dev 03:22 -!- MarcoFalke [~none@198.12.116.246] has quit [Read error: Connection reset by peer] 03:22 -!- MarcoFalke_ is now known as MarcoFalke 03:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 03:58 -!- jtimon [~quassel@70.30.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 04:10 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 04:11 -!- cryptapus_afk is now known as cryptapus 04:11 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Quit: conversation terminated!] 04:12 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Quit: Leaving] 04:13 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 260 seconds] 04:20 < MarcoFalke> no, the salvagewallet issue is not yet fixed 04:21 < MarcoFalke> At least I am not aware that anyone fixed it and the tests are still disabled 04:22 -!- jtimon [~quassel@70.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 04:22 -!- jannes [~jannes@095-097-246-234.static.chello.nl] has joined #bitcoin-core-dev 04:28 < wumpus> MarcoFalke: from what I remember what causes the test to fail is that salvagewallet can return false when the answer should be true. I don't think any keys are still being lost 04:39 -!- jtimon [~quassel@70.30.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 04:39 < wumpus> at least that was my experience from last time I tried to reproduce the issue 04:40 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 04:42 < MarcoFalke> ok, going to enable the test on the nightly builds and see what happens 04:58 < wumpus> good idea. 04:58 < wumpus> what I also found back then is that if you have a wallet that it fails on, it's fully reproducible with that. So it's something in the specific database that triggers it 04:59 < Victorsueca> be careful, maybe the code becomes self-aware and starts gathering private keys all around the world and then spends all UTXOs to 1Yoink.... :P 05:18 < wumpus> :p 05:27 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving] 05:27 -!- cryptapus is now known as cryptapus_afk 05:31 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:32 -!- Chris_Stewart_5 [~Chris_Ste@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 05:45 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 05:54 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Ping timeout: 246 seconds] 05:56 < morcos> Re: fee estimation and RBF. My plan for Core wallet is as follows: 05:56 < morcos> Fee estimation allowed for targets of: 2, 4, 6, 12, 24, 48, 144, 1008 05:57 < morcos> There will be 2 types of estimate for each target, a conservative estimate (probably not too different from todays estimates, but still a bit less conservative) and an actual estimate 05:58 < morcos> I was imagining some kind of interaction between those and RBF, such that if you don't have RBF enabled then it prompts you to use the conservative estimate or something 05:58 < morcos> Via RPC, you'll be able to get all kinds of more specific information if you choose 06:00 < morcos> Turns out its a bit tricky to do the longer time horizon estimates, b/c if your node hasn't been up for that long, you can't really know.. And if you shut your node down, it doesn't currently record all the txs stuck in your mempool as failing. 06:00 < morcos> Fixing these issues is what's holding me up now... And then I think I may have a performance problem to fix. 06:01 < petertodd> morcos: whatever you do, I'd suggest you plan for far more opt-in usage in the future; with ppl spamming the network to apparently raise fees the next round may make whatever estimating thing we come up with unreliable; tx replacement otoh is much harder to game 06:02 -!- dcousens_ [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 246 seconds] 06:02 < morcos> Yeah I think a separate but related project is to have an auto-replace mode... 06:02 < petertodd> (e.g. something that ignored opt-in txs entirely my fail if the % of them becomes much higher) 06:03 < petertodd> yeah. auto-replace mode is nice - gmaxwell has a neat way to do it where nlocktime is used to ensure replacements can be done prematurely 06:03 < morcos> As far as fee estimates dealing with opt-in txs.. I don't think thats much of a problem.. The only issue with that was to be cautious when they were knew that some miners might nto accept them 06:03 < morcos> prematurely? oh you mean sign in advance? 06:04 < petertodd> morcos: exactly! he suggested signing n contradictory txs, each with a higher nlocktime and higher fee 06:04 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 06:04 < petertodd> morcos: particulkarly relevant for hw wallets like trezor 06:04 < morcos> interesting... and maybe you could have a differential relay too... :) 06:05 < petertodd> morcos: yeah, differential relay would be nice, although at least replacement BW just increases the average; peak BW is our actual bottleneck 06:16 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 06:16 -!- molz_ [~molly@unaffiliated/molly] has quit [Remote host closed the connection] 06:20 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has joined #bitcoin-core-dev 06:35 -!- voyager_ [~voyager@ip68-13-242-116.ok.ok.cox.net] has quit [Read error: Connection reset by peer] 06:44 -!- aalex__ [~aalex@64.187.177.58] has joined #bitcoin-core-dev 06:46 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 06:47 -!- BashCo__ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 06:48 -!- voyager_ [~voyager@ip68-13-242-116.ok.ok.cox.net] has joined #bitcoin-core-dev 06:49 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 268 seconds] 06:51 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 246 seconds] 07:06 -!- Magma [~magma@magma.tokyo] has quit [Ping timeout: 252 seconds] 07:07 -!- Magma [~magma@magma.tokyo] has joined #bitcoin-core-dev 07:07 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 240 seconds] 07:17 -!- roidster [~chatzilla@66-215-230-217.dhcp.rvsd.ca.charter.com] has joined #bitcoin-core-dev 07:17 -!- roidster is now known as Guest65095 07:19 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 07:24 -!- whphhg [whphhg@gateway/vpn/mullvad/x-oilwcxfnpxuuowqg] has quit [Quit: Leaving] 07:37 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 258 seconds] 07:38 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 07:47 -!- whphhg [whphhg@gateway/vpn/mullvad/x-pkuoxctrxathzfvo] has joined #bitcoin-core-dev 07:59 < bsm1175322> I have a need to deliver witness data to SPV clients, which necessitates a one-line change: https://github.com/VidaID/bitcoin/commit/2a3052622596db9b1fe29cd357cfc58a831b050c 07:59 -!- riemann [~riemann@84-10-11-234.static.chello.pl] has quit [Quit: Leaving] 08:00 < bsm1175322> Would we make this an option or something? 08:00 < bsm1175322> *could 08:06 -!- bityogi [~textual@208-104-132-26.brvd.dsl.dyn.comporium.net] has joined #bitcoin-core-dev 08:09 < BlueMatt> bsm1175322: you need to do this over p2p? 08:09 < bsm1175322> yes 08:09 < BlueMatt> bsm1175322: if you can do it over rpc via the gettxoutproof/verifytxoutproof stuff we could probably tweak the format to include proofs of witnesses as well, but p2p....ugh, i think everyone wants to completely remove that code sooner or later, its not good 08:10 < BlueMatt> bsm1175322: (need to replace it with bloom filter commitments in blocks or so) 08:10 < bsm1175322> BlueMatt: agreed on that. 08:10 < bsm1175322> Well giving every random client direct access to RPC is not a good idea for a number of reasons 08:10 < bsm1175322> Stage 2 of this project will be to redesign BIP37. I'm well aware of its flaws. 08:11 < bsm1175322> But, for the moment we're just using it, warts and all. 08:11 < BlueMatt> bsm1175322: well the other thing we can do is extend the rpc to support it and then your patch will be simpler :) 08:11 < BlueMatt> (right now your patch isnt providing any proof of the witnesses, only the tx data, and providing the witness itself just as extra) 08:12 < bsm1175322> Oh I hadn't thought of that...there's a Merkle proof that's possible for the witness data too... 08:12 < bsm1175322> But...who would care about that? The client can verify that the witness signature is correct... 08:13 < BlueMatt> bsm1175322: yea, would have to provide the merkle path to coinbase + merkle path to the witness in question 08:13 < BlueMatt> well assuming they have the transactions being spent, sure 08:14 < bsm1175322> Hmmm since you're here in NYC...we should get together soon and have a brainstorming session about a BIP37 replacement... 08:16 < BlueMatt> sure, iirc there was some ml post not too long ago on it 08:16 < BlueMatt> something about committed bloom filters, I dont recall if they concluded that the filters were too big to be practical or if they were excited though 08:16 < BlueMatt> maybe it was a few months ago..... 08:17 < bsm1175322> Oh that one...and I calculated the size was unreasonable... 08:17 < BlueMatt> awww, damn 08:17 < BlueMatt> well, ok, brainstorming it is 08:17 < bsm1175322> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012674.html 08:17 < BlueMatt> oh wow that was months ago 08:18 < bsm1175322> original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012636.html 08:18 -!- CubicEarth [~cubiceart@190.219.188.141] has joined #bitcoin-core-dev 08:20 < bsm1175322> UTXO set commitment in some form are #1 on my wishlist for improving light client security. 08:20 < gribble> https://github.com/bitcoin/bitcoin/issues/1 | JSON-RPC support for mobile devices ("ultra-lightweight" clients) · Issue #1 · bitcoin/bitcoin · GitHub 08:22 < bitcoin-git> [bitcoin] sdaftuar opened pull request #9970: Improve readability of segwit.py (master...2017-03-segwit-test-improvements) https://github.com/bitcoin/bitcoin/pull/9970 08:23 < BlueMatt> bsm1175322: hmm, yea, 12 GB total isnt trivial, though I dont think its insane...I mean its not like you download that whole dataset unless you dont know when your keys were created 08:23 < BlueMatt> bsm1175322: does have lots of challenges, though :( 08:24 < bsm1175322> There's probably a workable mutation of that idea... 08:24 < BlueMatt> bsm1175322: utxo commitments dont help you sync, though, but, yea, are a huge win 08:24 < BlueMatt> its unclear what the "right" solution is, I mean scanning the chain for your transactions makes less and less sense every day, especially given that folks are moving towards off-chain txn 08:24 < BlueMatt> cant scan for those..... 08:25 < bsm1175322> That's a different problem entirely ;-) SPV-lightning... 08:26 < bsm1175322> Another idea I'm a fan of on this topic is andytoshi's PoW skiplists... 08:29 -!- Alina-malina [~Alina-mal@37.157.223.83] has joined #bitcoin-core-dev 08:29 < BlueMatt> yea, PoW skiplists are cool, though you have to be careful with them depending on your use-case 08:29 < BlueMatt> what use-case do you have for them? I mean 80 bytes * 400k blocks isnt that much, still, today? 08:29 < bsm1175322> Linear algorithms suck. ;-) 08:30 < bsm1175322> Initial sync in SPV mode still takes a non-trivial amount of time on phones. 08:30 < bsm1175322> It's just hashing those 400k blocks... 08:32 < BlueMatt> i mean we can improve that....we need a "give me all headers without the previous block hash in binary form" thing 08:32 < BlueMatt> mabye not p2p, just connect to blockchainheaders.com and get it 08:32 < BlueMatt> its 18MB 08:32 < BlueMatt> and hashing that cant take that long, no? 08:34 < bsm1175322> It does take that long, for whatever reason. Bcoin only verifies headers at a rate of ~20/s on the phone. 08:35 < dgenr8> bsm1175322: did you mean committed bloom filters? 08:35 < bsm1175322> @chjj is there any other reason you can think of besides sha256 speed which might be causing spv sync to be slower on the phone? Obviously it's quite fast in nodejs. 08:35 < bsm1175322> dgenr8: yes that's what we were discussing 08:36 < BlueMatt> bsm1175322: I mean I assume its also p2p latency, which isnt fun 08:36 < dgenr8> BlueMatt: size unreasonable with what fp rate 08:36 < BlueMatt> 20/s seems supperrr slow 08:37 < bsm1175322> dgenr8: see the referenced post with my calculation, I used fp rate= 1/height ~ 10^-6 08:37 < bsm1175322> came out to about 12GB of committed filters. 08:37 < bsm1175322> obviously this can be tuned... 08:37 < bsm1175322> At the cost of holding blocks you don't need. 08:37 < BlueMatt> (though we may want a similar command to remove checkpoints entirely for ibd - much easier to connect to a few peers and ask them for 4MB of headers (~100k blocks) at a time and then get a header chain and ban anyone who tried to spam you 08:38 < BlueMatt> instead of the current getheaders stuff 08:38 < BlueMatt> bsm1175322: to be fair, you probably want something much higher than 10^-6 08:38 < bsm1175322> yes 08:38 < BlueMatt> bsm1175322: you definitely want to download some extra blocks 08:39 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Quit: bye] 08:40 < bsm1175322> The desirable false positive rate is still (constant)/(height) though, or it's still a linear algorithm... 08:41 < BlueMatt> bsm1175322: welcome to the real world, low-cost linear is perfectly ok :P 08:42 < BlueMatt> as long as batteries and lte improve faster than your linear increases, at least for as long as you're not using 2nd layer stuff, you should be fine :) 08:42 < bsm1175322> Only in the bitcoin world...it makes for a horrible user experience. :-P 08:42 < BlueMatt> (well, and data caps...fuck data caps) 08:43 < bsm1175322> I'll keep looking for logarithmic solutions :-P 08:43 < BlueMatt> 10 seconds in a linear scan isnt all that much different from 10 seconds in a magical logarithmic scan, at least for users :P 08:43 < BlueMatt> I see your point, but I'm less worried 08:43 < BlueMatt> superlinear, well...lets not do that 08:44 < bsm1175322> Well...having been doing dev work on testnet for a few months...where it takes 30 minutes for bcoin to do an initial spv sync... 08:45 < BlueMatt> lol, ok, fair point 08:45 < BlueMatt> see previous comment about chunking header requests with new p2p messages 08:45 < BlueMatt> :) 08:45 < BlueMatt> its slow because we've been busy optimizing other things, should be easy to optimize, though 08:47 < bsm1175322> Yeah I'm going to have to look into that on bcoin. For now we're beta testing on regtest so are avoiding the problem. 08:49 -!- abpa [~abpa@96-82-80-25-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:53 -!- aalex__ [~aalex@64.187.177.58] has quit [Ping timeout: 258 seconds] 08:54 -!- riemann [~riemann@ip-222-88.ists.pl] has joined #bitcoin-core-dev 09:00 -!- neha [~narula@tbilisi.csail.mit.edu] has quit [Ping timeout: 268 seconds] 09:01 -!- neha [~narula@tbilisi.csail.mit.edu] has joined #bitcoin-core-dev 09:02 -!- aalex__ [~aalex@64.187.177.58] has joined #bitcoin-core-dev 09:03 -!- Alina-malina [~Alina-mal@37.157.223.83] has quit [Changing host] 09:03 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev 09:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Read error: Connection reset by peer] 09:07 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 09:11 -!- nsh [~lol@wikipedia/nsh] has quit [Read error: Connection reset by peer] 09:11 -!- ensign- [~ensign@2001:41d0:8:d711::1] has quit [Read error: Connection reset by peer] 09:12 -!- musalbas [~musalbas@2001:bc8:30c2:ff00::] has quit [Read error: Connection reset by peer] 09:13 -!- musalbas [~musalbas@2001:bc8:30c2:ff00::] has joined #bitcoin-core-dev 09:14 -!- nsh [~lol@wikipedia/nsh] has joined #bitcoin-core-dev 09:17 -!- ensign_ [~ensign@2001:41d0:8:d711::1] has joined #bitcoin-core-dev 09:21 -!- voyager_ [~voyager@ip68-13-242-116.ok.ok.cox.net] has quit [Read error: Connection reset by peer] 09:22 -!- voyager_ [~voyager@ip68-13-242-116.ok.ok.cox.net] has joined #bitcoin-core-dev 09:29 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 240 seconds] 09:30 -!- Alina-malina [~Alina-mal@37.157.223.83] has joined #bitcoin-core-dev 09:32 -!- Alina-malina [~Alina-mal@37.157.223.83] has quit [Changing host] 09:32 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev 09:40 < bsm1175322> BlueMatt: FYI another idea that's floating in my head for improving SPV is whether we could use some form of https://en.wikipedia.org/wiki/Oblivious_transfer 09:44 < BlueMatt> bsm1175322: hmm, possibly useful to receive blocks after a high-fp-rate filter commitment or something? Maybe too high overhead, though, gmaxwell might have more to say 09:45 < bsm1175322> To be clear, I haven't figured out any algorithm that works and I'm not making a proposal...but I want to find a way... 09:45 < BlueMatt> heh, ok 09:46 -!- CubicEarth [~cubiceart@190.219.188.141] has quit [Remote host closed the connection] 09:46 < BlueMatt> the old "that sounds cool, we should use it somewhere" approach :) 09:46 < bsm1175322> exactly 10:02 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 258 seconds] 10:03 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 10:24 < gmaxwell> .... there have been many concrete proposals before. the performance is bad though. 10:32 < bsm1175322> Yes...in order to be oblivous about which of N bytes are sent, you have to read/process all N bytes, for *each* request... 10:32 < bsm1175322> I'm still hoping there's a way around that observation... 10:35 < BlueMatt> uhh, that would be kinda obvious if you didnt.... 10:35 < BlueMatt> "hey, i dont know what I'm sending you, but its one of A or B, and I never read B from my hdd......" 10:36 < bsm1175322> Insert some preprocessing/Merkle tree magic... 10:38 < BlueMatt> heh 10:42 -!- BirneGetreide_ [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 10:43 < gmaxwell> bsm1175322: https://bitcointalk.org/index.php?topic=1762589.0 10:44 -!- BirneGetreide_ [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has joined #bitcoin-core-dev 10:45 -!- BashCo__ [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 10:46 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 10:46 -!- adiabat [~adiabat@45.63.20.152] has joined #bitcoin-core-dev 10:51 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 260 seconds] 10:52 -!- Guest65095 [~chatzilla@66-215-230-217.dhcp.rvsd.ca.charter.com] has quit [Quit: ChatZilla 0.9.92 [SeaMonkey 2.39/20151103191810]] 11:09 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 11:56 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9971: qa: Initialize log in TestManager (master...Mf1703-logFixup) https://github.com/bitcoin/bitcoin/pull/9971 11:57 -!- jtimon [~quassel@70.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:14 -!- shesek [~shesek@bzq-84-110-53-149.cablep.bezeqint.net] has quit [Ping timeout: 256 seconds] 12:18 -!- BirneGetreide_ [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 12:19 -!- str4d [~str4d@27.110.123.91] has joined #bitcoin-core-dev 12:24 < bitcoin-git> [bitcoin] jnewbery opened pull request #9972: Fix extended rpc tests broken by #9768 (master...test_logging_fixups) https://github.com/bitcoin/bitcoin/pull/9972 12:24 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 268 seconds] 12:27 -!- shesek [~shesek@bzq-84-110-53-149.cablep.bezeqint.net] has joined #bitcoin-core-dev 12:30 -!- Chris_Stewart_5 [~Chris_Ste@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 12:38 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 12:40 < gmaxwell> https://www.reddit.com/r/Bitcoin/comments/5yojyp/on_the_recent_bout_of_malleated_transactions/ 12:40 < midnightmagic> \o/ 12:52 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Quit: No Ping reply in 180 seconds.] 12:54 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 13:04 -!- jtimon [~quassel@70.30.134.37.dynamic.jazztel.es] has quit [Ping timeout: 256 seconds] 13:05 -!- CubicEarth [~cubiceart@190.219.188.141] has joined #bitcoin-core-dev 13:08 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 13:08 -!- roidster [~chatzilla@66-215-230-217.dhcp.rvsd.ca.charter.com] has joined #bitcoin-core-dev 13:08 -!- roidster is now known as Guest95471 13:15 -!- jnewbery [~Thunderbi@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Quit: jnewbery] 13:21 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 13:53 < bitcoin-git> [bitcoin] theuni opened pull request #9973: depends: fix zlib build on osx (master...fix-zlib-osx) https://github.com/bitcoin/bitcoin/pull/9973 13:53 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 240 seconds] 13:55 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 13:57 < bitcoin-git> [bitcoin] ryanofsky opened pull request #9974: Add basic Qt wallet test (master...pr/qt-test) https://github.com/bitcoin/bitcoin/pull/9974 14:00 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 258 seconds] 14:01 -!- str4d [~str4d@27.110.123.91] has quit [Ping timeout: 260 seconds] 14:01 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 14:08 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/8910b4717e5b...21833f9456f6 14:08 < bitcoin-git> bitcoin/master d055bd6 John Newbery: Fix extended rpc tests broken by 8910b4717e5bb946ee6988f7fe9fd461f53a5935 14:08 < bitcoin-git> bitcoin/master 21833f9 MarcoFalke: Merge #9972: Fix extended rpc tests broken by #9768... 14:08 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #9972: Fix extended rpc tests broken by #9768 (master...test_logging_fixups) https://github.com/bitcoin/bitcoin/pull/9972 14:10 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.] 14:28 -!- harrymm1 [~wayne@104.222.140.99] has quit [Ping timeout: 260 seconds] 14:35 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 14:39 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 240 seconds] 14:43 -!- harrymm [~wayne@104.222.140.113] has joined #bitcoin-core-dev 14:49 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 14:52 -!- str4d [~str4d@27.110.123.91] has joined #bitcoin-core-dev 14:54 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 264 seconds] 15:01 -!- CubicEarth [~cubiceart@190.219.188.141] has quit [Remote host closed the connection] 15:04 -!- riemann [~riemann@ip-222-88.ists.pl] has quit [Ping timeout: 240 seconds] 15:09 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 15:23 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #9971: qa: Initialize log in TestManager (master...Mf1703-logFixup) https://github.com/bitcoin/bitcoin/pull/9971 15:27 -!- Guest95471 [~chatzilla@66-215-230-217.dhcp.rvsd.ca.charter.com] has quit [Ping timeout: 240 seconds] 15:30 -!- Telmo [53dfaa1c@gateway/web/freenode/ip.83.223.170.28] has joined #bitcoin-core-dev 15:30 -!- Telmo [53dfaa1c@gateway/web/freenode/ip.83.223.170.28] has quit [Client Quit] 15:32 -!- Telmo [53dfaa1c@gateway/web/freenode/ip.83.223.170.28] has joined #bitcoin-core-dev 15:32 < Telmo> Ola 15:33 -!- Telmo [53dfaa1c@gateway/web/freenode/ip.83.223.170.28] has quit [Client Quit] 15:33 -!- str4d [~str4d@27.110.123.91] has quit [Ping timeout: 240 seconds] 15:45 -!- CubicEarth [~cubiceart@190.219.188.141] has joined #bitcoin-core-dev 15:52 -!- aalex__ [~aalex@64.187.177.58] has quit [Ping timeout: 260 seconds] 16:02 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 16:07 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Read error: Connection reset by peer] 16:08 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 16:22 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 264 seconds] 16:29 -!- vault711 [~vault711@99.197.250.147] has joined #bitcoin-core-dev 16:34 -!- roidster [~chatzilla@66-215-230-217.dhcp.rvsd.ca.charter.com] has joined #bitcoin-core-dev 16:34 < vault711> hey 16:35 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 16:35 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Ping timeout: 246 seconds] 16:44 -!- face [~face@mail.hmel.org] has quit [Read error: Connection reset by peer] 16:45 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:bdab:df8e:3885:5518] has quit [Quit: .] 16:47 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 16:47 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:4d4a:97cf:7cf0:199] has joined #bitcoin-core-dev 16:48 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:4d4a:97cf:7cf0:199] has quit [Remote host closed the connection] 16:49 -!- To7 [~theo@cpe-158-222-192-214.nyc.res.rr.com] has joined #bitcoin-core-dev 16:49 -!- CubicEarth [~cubiceart@190.219.188.141] has quit [] 16:54 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:1d44:ad2f:dd6:1495] has joined #bitcoin-core-dev 17:00 -!- abpa [~abpa@96-82-80-25-static.hfc.comcastbusiness.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:09 -!- vault711 [~vault711@99.197.250.147] has quit [Quit: Leaving] 17:17 -!- cbits [~cbits@2602:306:3b60:af80:49b7:7711:d719:e829] has joined #bitcoin-core-dev 17:25 -!- cbits [~cbits@2602:306:3b60:af80:49b7:7711:d719:e829] has quit [Ping timeout: 246 seconds] 17:39 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Remote host closed the connection] 17:44 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Quit: Konversation terminated!] 17:45 -!- alpalp [~alpalp@2605:6000:f4ea:ff00:7882:f366:ee2c:f85] has joined #bitcoin-core-dev 17:45 -!- alpalp [~alpalp@2605:6000:f4ea:ff00:7882:f366:ee2c:f85] has quit [Changing host] 17:45 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 17:45 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Ping timeout: 240 seconds] 17:46 -!- dcousens_ [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 17:47 -!- jtimon [~quassel@70.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 17:51 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Ping timeout: 246 seconds] 17:57 -!- alpalp [~alpalp@2605:6000:f4ea:ff00:7882:f366:ee2c:f85] has joined #bitcoin-core-dev 17:57 -!- alpalp [~alpalp@2605:6000:f4ea:ff00:7882:f366:ee2c:f85] has quit [Changing host] 17:57 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 17:58 -!- dcousens_ [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 240 seconds] 17:59 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:01 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 18:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 18:03 -!- fanquake [~fanquake@unaffiliated/fanquake] has left #bitcoin-core-dev [] 18:03 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 240 seconds] 18:05 -!- stonecoldpat [62d4926b@gateway/web/freenode/ip.98.212.146.107] has joined #bitcoin-core-dev 18:09 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:11 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Ping timeout: 246 seconds] 18:11 -!- stonecoldpat [62d4926b@gateway/web/freenode/ip.98.212.146.107] has left #bitcoin-core-dev [] 18:12 -!- roidster [~chatzilla@66-215-230-217.dhcp.rvsd.ca.charter.com] has quit [Quit: ChatZilla 0.9.92 [SeaMonkey 2.39/20151103191810]] 18:14 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 256 seconds] 18:15 -!- jannes [~jannes@095-097-246-234.static.chello.nl] has quit [Quit: Leaving] 18:16 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:21 -!- alpalp [~alpalp@2605:6000:f4ea:ff00:7882:f366:ee2c:f85] has joined #bitcoin-core-dev 18:21 -!- alpalp [~alpalp@2605:6000:f4ea:ff00:7882:f366:ee2c:f85] has quit [Changing host] 18:21 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 18:21 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 256 seconds] 18:22 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:27 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 256 seconds] 18:34 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-apbpicssbyrkkboe] has quit [Quit: Connection closed for inactivity] 18:35 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:39 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 240 seconds] 18:40 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:48 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 240 seconds] 18:52 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 19:05 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Remote host closed the connection] 19:05 -!- wudayoda [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev 19:14 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 268 seconds] 19:19 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 19:22 -!- cbits [~cbits@2602:306:3b60:af80:c115:9ba8:ab56:35d7] has joined #bitcoin-core-dev 19:25 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Quit: Leaving] 19:34 -!- dodomojo [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has joined #bitcoin-core-dev 19:35 -!- dodomojo [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has quit [Read error: Connection reset by peer] 19:36 -!- dodomojo [~goksinen@2604:2000:c591:8400:3dd8:2d0a:f61f:bc41] has joined #bitcoin-core-dev 19:37 -!- dodomojo_ [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has joined #bitcoin-core-dev 19:37 -!- dodomojo_ [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has quit [Read error: Connection reset by peer] 19:37 -!- cbits [~cbits@2602:306:3b60:af80:c115:9ba8:ab56:35d7] has quit [Ping timeout: 246 seconds] 19:38 -!- dodomojo_ [~goksinen@2604:2000:c591:8400:d44:28d0:4014:1e71] has joined #bitcoin-core-dev 19:39 -!- dodomoj__ [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has joined #bitcoin-core-dev 19:41 -!- dodomojo [~goksinen@2604:2000:c591:8400:3dd8:2d0a:f61f:bc41] has quit [Ping timeout: 246 seconds] 19:42 -!- dodomojo_ [~goksinen@2604:2000:c591:8400:d44:28d0:4014:1e71] has quit [Ping timeout: 246 seconds] 19:50 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev 20:14 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 20:27 < luke-jr> user confused because bitcoind stops working when he set a rpcpassword 20:27 < luke-jr> turns out he didn't restart bitcoind 20:27 < luke-jr> not sure we can really fix this 20:28 -!- Chris_Stewart_5 [~Chris_Ste@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 20:32 -!- chris2000 [~chris2000@p5DCB445B.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 20:35 -!- chris200_ [~chris2000@p5DCB4DF6.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 20:51 -!- str4d [~str4d@27.110.123.91] has joined #bitcoin-core-dev 21:02 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 21:11 -!- dodomojo [~goksinen@2604:2000:c591:8400:acc2:f2c1:6a27:9f79] has joined #bitcoin-core-dev 21:11 -!- dodomoj__ [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has quit [Read error: Connection reset by peer] 21:18 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 21:21 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 21:33 -!- tunafizz [tunafizz@c-71-207-55-31.hsd1.pa.comcast.net] has joined #bitcoin-core-dev 21:53 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 22:03 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 22:03 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection] 22:04 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 22:04 < gmaxwell> luke-jr: tell users to not set rpcpasswords. 22:05 < gmaxwell> we plan on getting rid of that, so that will solve users following old instructions. 22:05 < luke-jr> gmaxwell: this is beside the point; rpcauth won't do any better 22:06 < gmaxwell> it would be: the utils would still use the cookie auth in that case. so it wouldn't mysteriously stop. 22:06 -!- grubles [~grubles@unaffiliated/grubles] has quit [Client Quit] 22:06 < gmaxwell> And did the user actually need rpcpassword for anything or were they merely following some instructions online? 22:07 < luke-jr> no idea 22:07 -!- grubles [~grubles@96-59-144-27.res.bhn.net] has joined #bitcoin-core-dev 22:08 < luke-jr> cookie auth is typically harder to use, so I imagine he was setting it to use it 22:08 -!- grubles is now known as Guest42163 22:08 -!- Guest42163 [~grubles@96-59-144-27.res.bhn.net] has quit [Remote host closed the connection] 22:08 < luke-jr> gotta read a file in, and know to reload it & retry if it fails to auth later 22:20 < gmaxwell> right but 'set something and the cli tool stop' goes away, e.g. you can use rpcauth for your remote process but the tools can keep using cookie auth. 22:22 < luke-jr> oh, rpcauth doesn't disable cookies? :o 22:22 < luke-jr> don't think I was aware of that 22:34 < gmaxwell> yea, since it has its own username(s) it's pretty sensible that it doesn't. and using both is nice. 22:37 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 22:37 < luke-jr> yeah, makes sense 23:01 -!- vogelito [~Adium@66-90-154-24.dyn.grandenetworks.net] has joined #bitcoin-core-dev 23:02 -!- vogelito [~Adium@66-90-154-24.dyn.grandenetworks.net] has quit [Client Quit] 23:06 -!- dodomojo [~goksinen@2604:2000:c591:8400:acc2:f2c1:6a27:9f79] has quit [Read error: Connection reset by peer] 23:07 -!- dodomojo [~goksinen@2604:2000:c591:8400:acc2:f2c1:6a27:9f79] has joined #bitcoin-core-dev 23:13 -!- dodomojo [~goksinen@2604:2000:c591:8400:acc2:f2c1:6a27:9f79] has quit [Ping timeout: 246 seconds] 23:24 -!- dodomojo [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has joined #bitcoin-core-dev 23:43 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 240 seconds] 23:48 -!- aalex__ [~aalex@64.187.177.58] has joined #bitcoin-core-dev 23:54 -!- aalex__ [~aalex@64.187.177.58] has quit [Ping timeout: 240 seconds]