--- Day changed Sun Feb 19 2017 00:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 00:14 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev 00:18 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds] 00:22 -!- whphhg [whphhg@gateway/vpn/mullvad/x-kvdknxbekxbjviqq] has joined #bitcoin-core-dev 00:23 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has joined #bitcoin-core-dev 00:44 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-unttxiyuxfoeqxpm] has joined #bitcoin-core-dev 00:57 -!- murchandamus [~murchghos@ghostdub.de] has quit [Remote host closed the connection] 01:00 -!- murchandamus [~murchghos@ghostdub.de] has joined #bitcoin-core-dev 01:04 -!- murchandamus [~murchghos@ghostdub.de] has quit [Remote host closed the connection] 01:06 -!- pavel_ [~paveljani@79.98.72.176] has joined #bitcoin-core-dev 01:06 -!- pavel_ [~paveljani@79.98.72.176] has quit [Remote host closed the connection] 01:07 -!- murchandamus [~murchghos@ghostdub.de] has joined #bitcoin-core-dev 01:08 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev 01:09 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 240 seconds] 01:12 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds] 01:13 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 240 seconds] 02:01 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev 02:05 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds] 02:11 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev 02:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 02:18 -!- BitBully [~Mutter@197.210.25.221] has joined #bitcoin-core-dev 02:21 -!- BitBully [~Mutter@197.210.25.221] has quit [Client Quit] 02:26 -!- ChatSharp [~ChatSharp@stc.66.70.188.95.dsl.krasnet.ru] has joined #bitcoin-core-dev 02:29 -!- ChatSharp [~ChatSharp@stc.66.70.188.95.dsl.krasnet.ru] has left #bitcoin-core-dev [] 03:00 -!- chris200_ [~chris2000@p5082A630.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:02 -!- chris2000 [~chris2000@p5082A630.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 03:10 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has quit [Quit: Bye] 03:10 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 03:21 -!- juscamarena [~justin@47.148.176.74] has quit [Remote host closed the connection] 03:22 -!- juscamarena [~justin@47.148.176.74] has joined #bitcoin-core-dev 03:22 -!- juscamarena [~justin@47.148.176.74] has quit [Client Quit] 04:05 < wumpus> luke-jr: well I managed to screw up my base image, wouldn't be the first time, I do some optimizations to speed up the "upgrading operating system" step, I don't think there's any reason to dig deeper 04:05 < luke-jr> ah 04:05 < luke-jr> I just worry that the "rebuild base" solution is prone to malware getting in 04:06 < luke-jr> otoh, so is the updating step 04:06 < wumpus> if you feel like digging deeper I may be able to dig up my old base image and send it to you but I relaly don't have the time 04:06 < luke-jr> nah, probably not worth it all things considered 04:06 < luke-jr> if we weren't autoupdating, maybe, but we are 04:07 < wumpus> there's just no way to do this properly as long as we're not using a deterministically built OS for building 04:07 < luke-jr> right 04:09 < wumpus> I think it's more curious that making a new base image solved achow101 osx non-determinism - we have no reliance on the OS's build tools in that 04:09 < wumpus> at least I had three versions of gcc installed :) 04:09 < luke-jr> indeed 04:12 < wumpus> please just leave the "About Qt" link where it is, that's a common fixturefor all Qt programs and it's useful to be able to see what version of Qt is used for troubleshooting problems 04:12 < wumpus> there's no reason at all to remove it, it's not like we lack space in that menu and absolutely need to change something 04:14 < Arvidt> ) is expired 04:14 < luke-jr> wumpus: the original reason I brought it up, was translators confusing it for "About Bitcoin-Qt". but that has since been resolved in other ways, so 04:14 < Arvidt> Wladimir J. van der Laan (Bitcoin Core binary release signing key) 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964 is expired 04:14 < wumpus> no, it's been updated and bumped forward 2 years 04:15 < wumpus> try gpg --refresh-keys 04:15 * luke-jr wonders if this should be added to release announcements 04:16 < wumpus> that makes little sense, you could add arbitrary steps to release announcements to make the signature check out as ok 04:16 < wumpus> you can't trust any steps in it before you've verified the signature 04:16 < luke-jr> yes, but this one makes sense 04:17 < wumpus> it's not our job to explain people how to use gpg 04:18 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 04:19 < wumpus> at least not in the release notes 04:20 < fanquake> I've still got the same issues even after re-building the base image. So I'm guessing I've somehow done that incorrectly.. 04:20 < wumpus> I'm very surprised that the base image solved it for achow101 04:20 < wumpus> osx build hardly uses anything from the base image 04:21 < wumpus> we should check what the differences are 04:22 < fanquake> Looking at his new PR, it looks like the previous build was using the old version of Qt? 04:22 < fanquake> Actually, no. 04:23 < wumpus> I don't think so 04:25 < wumpus> normally would suggest "remove the gitian cache directories" but due to that switch, 0.14 uses new ones anyway 04:25 < wumpus> so it can't be using anything stale 04:26 < wumpus> your gitian-builder is up to date? 04:26 < fanquake> I might be missunderstanding, but why do the hashes for the same file change in his new PR? 04:26 < fanquake> Yes gitian-builder up to date. 04:26 < fanquake> Talking about something like native_mac_alias-1.1.0-f064d7cfd4c.tar.gz 04:27 < wumpus> curious. yes. 04:28 < fanquake> Same for cctools andbiplist. 04:28 < wumpus> not sure where those files come from. cfields? 04:28 < fanquake> That hasn't changed in depends recently as far as I remember. And those hashes don't even match the ones we have in depends anyways. 04:28 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7ff4a538a868...1f9e904f4556 04:28 < bitcoin-git> bitcoin/master 5c8fd50 Pieter Wuille: Avoid VLA in hash.h 04:28 < bitcoin-git> bitcoin/master 1f9e904 Wladimir J. van der Laan: Merge #9791: Avoid VLA in hash.h... 04:29 < bitcoin-git> [bitcoin] laanwj closed pull request #9791: Avoid VLA in hash.h (master...novla) https://github.com/bitcoin/bitcoin/pull/9791 04:29 < wumpus> maybe the gitian "tarballs are not deterministic" issue 04:29 < wumpus> eh GITHUB not gitian 04:29 < fanquake> except biplist comes from bitcucket 04:30 < fanquake> actually, from pypi.python.org 04:30 < wumpus> oh right, maybe bitbucket has that issue too, or has it now that github no longer has it, I don't know \ 04:30 < wumpus> good catch though, that could very well be the reason 04:31 < wumpus> we'd need to find the old and new versions of those files and compare 04:31 < fanquake> They should still be in the /inputs folder 04:32 < wumpus> df26cbb976befd59ba20b73ee33676f22b6ed7aa1329e373307e0a21055f5a5a ./cache/bitcoin-osx-0.13/x86_64-apple-darwin11/native_biplist/native_biplist-0.9-d766a97a608.tar.gz 04:32 < wumpus> ed6c2d2b2839164e592859f5eff62df7fedde9657c9e7a853720d0a768b8b756 ./cache/bitcoin-osx-0.14/x86_64-apple-darwin11/native_biplist/native_biplist-0.9-d766a97a608.tar.gz 04:32 < wumpus> those are mine. Both have different hash from achow101's new and old one 04:33 < wumpus> maybe they regenerate that file on every download?! 04:33 < fanquake> Surely we would have noticed if that we happening before now ? 04:33 < wumpus> for all the other downloaded dependencies we check the hash 04:34 < wumpus> apparently not for this one 04:34 < fanquake> https://github.com/bitcoin/bitcoin/blob/master/depends/packages/native_biplist.mk#L5 04:36 < fanquake> My cached biplist files don't even match yours or his.. 04:36 -!- str4d [~str4d@host-78-145-20-180.as13285.net] has joined #bitcoin-core-dev 04:37 < fanquake> Well, I even have a different file cached for 0.13 compared to you. 04:37 < fanquake> 490e9049e68ec8c7010be3cd19a6237e463d5115839c4cbccbb1dff1196129b4 native_biplist-0.9-1c39c8871c7.tar.gz 04:40 < wumpus> so my hypothesis of it changing every time isn't far off the mark, probably 04:40 < fanquake> Looking at my two asserts, my biplist files haven't changed between the two. 04:41 < fanquake> My other theory is something zlib related. Given it's new to our build. 04:42 < fanquake> It also doesn't compile using the depends system on OS X. 04:43 < wumpus> we should probably start by comparing the resulting files, it maybe some silly metadata thing too 04:43 < fanquake> Yes hopefully. 04:44 < fanquake> Something like #8373 04:44 < gribble> https://github.com/bitcoin/bitcoin/issues/8373 | Fix OSX non-deterministic dmg by theuni · Pull Request #8373 · bitcoin/bitcoin · GitHub 04:48 < wumpus> yes, like that one 04:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 04:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:57 -!- Aaronvan_ [~AaronvanW@110.red-88-20-218.staticip.rima-tde.net] has joined #bitcoin-core-dev 04:59 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 05:05 < wumpus> fanquake: could you upload your bitcoin-0.14.0-osx64.tar.gz somewhere? 05:06 < wumpus> I can't guarantee anything, I don't have the tooling to compare or analyze osx executables, but maybe I can find something obvious 05:14 < fanquake> wumpus probably. Sketchy internet at the moment. Will find a site. 05:16 < bitcoin-git> [bitcoin] kirit93 opened pull request #9798: Fix Issue #9775 (master...issue) https://github.com/bitcoin/bitcoin/pull/9798 05:19 < gmaxwell> uh. hey, so the release notes don't mention bumpfee. 05:20 < gmaxwell> thats like, a major feature, no? :P 05:21 < wumpus> yes 05:37 < gmaxwell> Relase notes make it sound like getinfo is hard-cut disabled in this version. 05:39 < gmaxwell> (I'm answering questions about the RC on reddit) 05:41 -!- Aaronvan_ [~AaronvanW@110.red-88-20-218.staticip.rima-tde.net] has quit [Remote host closed the connection] 05:47 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has joined #bitcoin-core-dev 05:56 -!- Arvidt [~Arvidt@p5B2AB21C.dip0.t-ipconnect.de] has left #bitcoin-core-dev [] 05:58 -!- moli_ [~molly@unaffiliated/molly] has quit [Remote host closed the connection] 06:11 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Remote host closed the connection] 06:11 < wumpus> well, it mentions that getinfo was deprecated, not that it was removed. But yeah I guess it could be clearer 06:11 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev 06:13 < wumpus> I implemented getinfo client-side at some point (https://github.com/bitcoin/bitcoin/pull/8843) so that anyone using bitcoin-cli would hardly notice the command being removed from the server 06:14 < wumpus> but that only resulted in a big argument, so I gave up on it 06:16 < luke-jr> not the first time someone confused deprecated to mean removed 06:17 < wumpus> on the dev side getinfo was already deprecated for years, iti's just that this was never communicated on the RPC interface 06:18 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.] 06:23 < achow101> wumpus: fanquake: I did delete gitian-builder and redownload it before making the base vm, so maybe that could be part of why the build was fixed, although I don't see why it should 06:24 < wumpus> achow101: yes, it's no longer possible to isolate what the cause of the problem was 06:24 < wumpus> although the same is not working for fan 06:24 < wumpus> fanquake 06:31 -!- cdecker [~cdecker@mail.snyke.net] has quit [Ping timeout: 276 seconds] 06:31 < gmaxwell> I wonder if the next step there shouldn't be to disable getinfo but allow a config option to reenable it. Another half measure would be to make the error field there always preface with a warning. 06:31 -!- cdecker [~cdecker@mail.snyke.net] has joined #bitcoin-core-dev 06:51 < wumpus> I think the next major release we should just get rid of it 06:51 < wumpus> we've delayed that enough 06:51 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 06:52 < wumpus> announcing it in the release notes in strong language was a good start 06:52 < wumpus> and we provide *exactly* a table of how to get the information 06:54 < wumpus> no need to draw this out like the account deprectation, where it's not 100% clear what the replacement for some use cases 07:01 < da2ce7> if you decide now to remove it in the next version, state. "in version 0.15, getinfo will be removed from bitcoin-core". :) 07:02 < wumpus> yes, would make sense to add that 07:02 < wumpus> also clears up that it is not removed yet 07:04 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1f9e904f4556...390a39bb5cf4 07:04 < bitcoin-git> bitcoin/master eb49101 Wladimir J. van der Laan: doc: Update manpages for master... 07:04 < bitcoin-git> bitcoin/master 390a39b Wladimir J. van der Laan: Merge #9795: doc: Update manpages for master (laanwj)... 07:04 < bitcoin-git> [bitcoin] laanwj closed pull request #9795: doc: Update manpages for master (laanwj) (master...Mf1602-docManMaster) https://github.com/bitcoin/bitcoin/pull/9795 07:05 -!- AaronvanW [~AaronvanW@110.red-88-20-218.staticip.rima-tde.net] has joined #bitcoin-core-dev 07:05 -!- AaronvanW [~AaronvanW@110.red-88-20-218.staticip.rima-tde.net] has quit [Changing host] 07:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:22 < gmaxwell> wumpus: the problem with hard cuts like that is predictable people will just not upgrade their nodes when their software is incompatible, and in doing so harm the network. 07:22 < gmaxwell> especially since its super easy to just have never noticed a release note. 07:23 < gmaxwell> (not really trying to argue it out with you now, just defending why I'd even suggest such a thing) 07:45 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds] 07:48 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Remote host closed the connection] 07:49 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev 08:11 < achow101> wumpus: it's still non-deterministic :( I just ran gitian again and got my original results 08:38 -!- harrymm [~wayne@104.207.83.19] has quit [Ping timeout: 268 seconds] 08:39 -!- chjj [~chjj@unaffiliated/chjj] has quit [Quit: WeeChat 1.7] 08:39 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 08:50 -!- chjj [~chjj@unaffiliated/chjj] has quit [Quit: WeeChat 1.7] 08:51 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 08:54 -!- harrymm [~wayne@104.207.83.25] has joined #bitcoin-core-dev 08:58 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:00 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has quit [Quit: ZNC 1.6.4 - http://znc.in] 09:01 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:01 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 09:02 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:04 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has quit [Client Quit] 09:05 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:05 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has quit [Client Quit] 09:05 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:06 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 09:06 -!- afk11_ [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 09:07 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 09:08 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 09:11 -!- afk11_ is now known as afk11 09:21 < gmaxwell> instagibbs: you're double counted in the contributor list 09:31 < bitcoin-git> [bitcoin] gubatron opened pull request #9801: Removed redundant parameter from mempool.PrioritiseTransaction (master...refactor-mempool-prioritisetx) https://github.com/bitcoin/bitcoin/pull/9801 09:34 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Read error: Connection reset by peer] 09:49 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 09:58 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 09:59 -!- jtimon [~quassel@245.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 10:04 < bitcoin-git> [bitcoin] dooglus opened pull request #9803: Fix typo in release notes. (0.14...patch-5) https://github.com/bitcoin/bitcoin/pull/9803 10:08 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Ping timeout: 240 seconds] 10:21 -!- moli_ [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 10:23 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 10:25 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 240 seconds] 10:28 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 11:13 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev 11:27 -!- isle2983 [~isle2983@46.166.190.181] has joined #bitcoin-core-dev 11:46 < bitcoin-git> [bitcoin] JeremyRubin opened pull request #9804: Fixes subscript 0 (&var[0]) where should use (var.data()) instead. (master...fix-subscript-0) https://github.com/bitcoin/bitcoin/pull/9804 11:48 -!- bsm117532 [~mcelrath@135.84.167.210] has quit [Ping timeout: 260 seconds] 11:53 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 11:55 < achow101> cfields: I now have what appears to be a consistently inconsistent gitian build for osx. Each time I build it, it alternates between the hashes that everyone else has, and the hashes that fanquake and I have 11:56 < sipa> "consistently inconsistent" 11:57 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 260 seconds] 12:11 < achow101> cfields: I put the two different assert files in different branches: https://github.com/achow101/gitian.sigs/tree/0.14.0rc1-match and https://github.com/achow101/gitian.sigs/tree/0.14.0rc1-mismatch the only difference between the two are the output files. everything else matches according to diff 12:36 -!- harrymm [~wayne@104.207.83.25] has quit [Ping timeout: 255 seconds] 12:37 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Quit: ZNC 1.6.4 - http://znc.in] 12:38 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 12:40 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 12:42 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 12:56 -!- harrymm [~wayne@104.207.83.33] has joined #bitcoin-core-dev 13:13 < bitcoin-git> [bitcoin] petertodd opened pull request #9805: Add seed.btc.petertodd.org to mainnet DNS seeds (master...2017-02-add-pt-mainnet-seed) https://github.com/bitcoin/bitcoin/pull/9805 13:29 -!- tunafizz [tunafizz@c-71-207-55-31.hsd1.pa.comcast.net] has quit [Ping timeout: 260 seconds] 13:32 -!- boab [7cb98629@gateway/web/freenode/ip.124.185.134.41] has joined #bitcoin-core-dev 13:33 < boab> Looking for readme on upgrade of core from 0.8.x to 0.10.x Help? 13:34 < gmaxwell> uh? why run such an old version as 0.10? I assume everyone has long forgotten about it, it's old and insecure. 13:35 < boab> Yep, good ppoint. My main mission is to get off of 0.8.x ... and how-to's please? 13:37 < gmaxwell> the blockchain files and wallets are all compatible. shut down, backup your wallet (for good measure), install 0.13.2. start it. 13:37 < boab> Fantastic...that's all the assurance I needed. Just did not want to trash something in the process. 13:39 < sipa> make a backup of your wallet after shutting down 0.8 if you want to be sure 13:39 < sipa> (which you should have anyway) 13:42 < boab> Thanks mate. I used the [backup wallet] option from within 0.8 and have stored off site. 13:42 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 240 seconds] 13:43 < luke-jr> need to backup the wallet before shutting down.. 13:43 < boab> ?? I think that's right: I was running 0.8, used the GUI option to create a backup, and then have shut 0.8 down. 13:44 < luke-jr> sounds good 13:44 < sipa> sounds good 13:44 < boab> fingers crossed...about to fire up new core now... 13:46 < boab> Rock n roll! v013.2 seems to have read the wallet and blockchain and is happily syncing right now. Thanks for your hand-holding...much appreciated. 13:47 < gmaxwell> Great! congrats on joining the modern era! 13:47 < boab> heheh...respkt ur elders? 13:50 < sipa> boab: also, 0.14.0 will be released in a few weeks likely 13:53 -!- boab [7cb98629@gateway/web/freenode/ip.124.185.134.41] has quit [] 14:03 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has joined #bitcoin-core-dev 14:04 -!- str4d [~str4d@host-78-145-20-180.as13285.net] has quit [Quit: Leaving] 14:16 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 14:30 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 15:03 -!- cdecker [~cdecker@mail.snyke.net] has quit [Ping timeout: 255 seconds] 15:06 -!- cdecker [~cdecker@mail.snyke.net] has joined #bitcoin-core-dev 15:21 -!- isle2983 [~isle2983@46.166.190.181] has quit [K-Lined] 15:33 -!- isle2983 [~isle2983@162.216.46.162] has joined #bitcoin-core-dev 15:48 -!- waxwing [~waxwing@185.65.132.137] has quit [Ping timeout: 256 seconds] 16:01 -!- waxwing [~waxwing@185.65.135.88] has joined #bitcoin-core-dev 16:09 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 240 seconds] 16:10 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 16:38 < instagibbs> gmaxwell, commits so nice they're credited twice 16:41 -!- chris200_ [~chris2000@p5082A630.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 16:44 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 16:46 -!- goksinen_ [~goksinen@2604:2000:c591:8400:3420:31fb:5538:73fd] has joined #bitcoin-core-dev 16:47 -!- moli_ [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 16:55 -!- chris2000 [~chris2000@p5082A5BF.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 16:55 -!- IRCFrEAK [~gk.1wm.su@2a03:4a80:3:43d:43d:23b:2e38:2839] has joined #bitcoin-core-dev 16:55 -!- IRCFrEAK [~gk.1wm.su@2a03:4a80:3:43d:43d:23b:2e38:2839] has left #bitcoin-core-dev [] 17:01 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 17:24 -!- city22 [~textual@211.94.117.2] has joined #bitcoin-core-dev 17:38 < bitcoin-git> [bitcoin] droark opened pull request #9806: txoutsbyaddress index (take 3) (master...gettxoutsbyaddress) https://github.com/bitcoin/bitcoin/pull/9806 17:47 < bitcoin-git> [bitcoin] fanquake opened pull request #9807: RPC doc fix-ups. (master...rpc-test-trivial-fixups) https://github.com/bitcoin/bitcoin/pull/9807 17:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 18:06 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has quit [Quit: Leaving.] 18:14 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-unttxiyuxfoeqxpm] has quit [Quit: Connection closed for inactivity] 18:18 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 18:21 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 18:28 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds] 18:28 -!- chjj_ [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 18:28 -!- chjj_ [~chjj@unaffiliated/chjj] has quit [Client Quit] 18:28 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 18:59 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 260 seconds] 19:16 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Read error: Connection reset by peer] 19:16 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 19:34 -!- jtimon [~quassel@245.30.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection] 19:42 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 19:44 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 19:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds] 19:48 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 260 seconds] 19:50 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 19:58 -!- goksinen_ [~goksinen@2604:2000:c591:8400:3420:31fb:5538:73fd] has quit [Remote host closed the connection] 20:00 -!- dermoth [~thomas@dsl-216-221-55-141.mtl.contact.net] has quit [Read error: Connection reset by peer] 20:00 -!- dermoth [~thomas@dsl-216-221-55-141.mtl.contact.net] has joined #bitcoin-core-dev 20:01 -!- madgoat [~gk.1wm.su@2a03:4a80:5:41e:41e:efdd:c10d:1c12] has joined #bitcoin-core-dev 20:01 -!- madgoat [~gk.1wm.su@2a03:4a80:5:41e:41e:efdd:c10d:1c12] has left #bitcoin-core-dev [] 20:19 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Quit: bye] 20:19 < gmaxwell> https://www.reddit.com/r/Bitcoin/comments/5uy4h6/bitcoin_core_0140_release_candidate_1_available/ddyj3sx/ report that the transparent overlay isn't transparent. (thinking about it I have no idea if it was transparent for me...) 20:19 < achow101> I'm doing a fix for unifying the boolean verbose arguments with the RPCs. should the default be a boolean, or a verbosity number? 20:19 < achow101> gmaxwell: it's supposed to be transparent? 20:23 < sipa> it's modal, not transparent? 20:24 < sipa> oh, release notes say semi-transparent 20:25 < achow101> the pr for it, #8371 says its supposed to be semi-transparent. but that screenshot does not look very semi-transparent 20:25 < gribble> https://github.com/bitcoin/bitcoin/issues/8371 | [Qt] Add out-of-sync modal info layer by jonasschnelli · Pull Request #8371 · bitcoin/bitcoin · GitHub 20:26 < sipa> maybe the transparent part is the background, where you can see the actual tab? 20:27 < achow101> it looks like you have to look really close. then you can see the background 20:27 < achow101> zoom in. a lot 20:29 < gmaxwell> I'm just a messager! 20:50 -!- Guest80933 [~GeekEndz@112.198.72.253] has joined #bitcoin-core-dev 20:51 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:54 -!- chris200_ [~chris2000@p5DCB50F5.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 < Guest80933> Sirs How can I start with signature campaign. I am just a newbie in bitcointalk.org 20:56 -!- Guest80933 [~GeekEndz@112.198.72.253] has quit [Excess Flood] 20:57 -!- chris2000 [~chris2000@p5082A5BF.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 21:01 -!- chjj [~chjj@unaffiliated/chjj] has quit [Quit: WeeChat 1.7] 21:01 -!- city22 [~textual@211.94.117.2] has quit [Quit: Textual IRC Client: www.textualapp.com] 21:01 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 21:04 < bitcoin-git> [bitcoin] GCarneiroA opened pull request #9808: Master (master...master) https://github.com/bitcoin/bitcoin/pull/9808 21:14 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds] 21:19 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 264 seconds] 21:24 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 21:36 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Ping timeout: 264 seconds] 21:46 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 21:46 -!- cannon-c [ccc23f04@gateway/web/freenode/ip.204.194.63.4] has joined #bitcoin-core-dev 22:07 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.] 22:07 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 22:14 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev 22:17 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: This computer has gone to sleep] 22:22 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 22:22 -!- justan0theruser is now known as OfficialLeibniz 22:23 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 22:35 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has quit [Quit: Whatever] 22:41 -!- chjj [~chjj@unaffiliated/chjj] has quit [Quit: WeeChat 1.7] 22:41 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 23:09 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev 23:25 < wumpus> gmaxwell: I like the idea of always adding a warning to getinfo's warning field though. We could introduce that in a minor 0.14 release 23:29 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-mhokbajobrvljjxd] has joined #bitcoin-core-dev 23:35 < jonasschnelli> Has there been talk to default enable -walletrbf=1 in 0.15? Or should the direction be that one can set the rbf flag per send*? 23:40 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 23:52 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 268 seconds] 23:53 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 23:54 < wumpus> jonasschnelli: not sure about that. We'd have be sure there are no significant wallets or companies that have problems accepting RBF transactions before making it default