--- Day changed Sun Nov 08 2015
00:33 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-iqfqhukhcsjcvxaw] has joined #bitcoin-core-dev
00:45 -!- fanquake [~Adium@unaffiliated/fanquake] has joined #bitcoin-core-dev
01:17 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
01:20 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 250 seconds]
01:40 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
02:51 -!- fanquake [~Adium@unaffiliated/fanquake] has quit [Quit: Leaving.]
03:12 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
04:09 -!- jonasschnelli [~jonasschn@2a01:4f8:200:7025::2] has quit [Changing host]
04:09 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has joined #bitcoin-core-dev
04:19 -!- vineet [59655721@gateway/web/freenode/ip.89.101.87.33] has joined #bitcoin-core-dev
04:23 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
04:53 -!- guest234234 [~guest2342@171.4.113.178] has joined #bitcoin-core-dev
04:54 -!- Guest23423 [~guest2342@171.4.237.14] has quit [Ping timeout: 255 seconds]
05:01 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
05:07 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds]
05:30 -!- Guest23423 [~guest2342@171.4.235.52] has joined #bitcoin-core-dev
05:32 -!- guest234234 [~guest2342@171.4.113.178] has quit [Ping timeout: 240 seconds]
05:41 -!- guest234234 [~guest2342@223.207.207.17] has joined #bitcoin-core-dev
05:42 -!- Guest23423 [~guest2342@171.4.235.52] has quit [Ping timeout: 272 seconds]
05:59 -!- Guest23423 [~guest2342@171.4.237.159] has joined #bitcoin-core-dev
06:02 -!- guest234234 [~guest2342@223.207.207.17] has quit [Ping timeout: 260 seconds]
06:08 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
06:26 -!- vineet [59655721@gateway/web/freenode/ip.89.101.87.33] has quit [Ping timeout: 246 seconds]
06:27 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]
06:28 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev
06:35 -!- ParadoxSpiral_ [~ParadoxSp@p508B8F19.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
06:38 -!- ParadoxSpiral [~ParadoxSp@p508B9A5E.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
07:41 < harding> I see people gitian building 0.11.2RC1, but the release notes seem to be for 0.11.1.  Is there somewhere else I should be looking for the notes?  https://github.com/bitcoin/bitcoin/blob/v0.11.2rc1/doc/release-notes.md
07:56 < PRab> harding: Not quite release notes, but https://github.com/bitcoin/bitcoin/compare/v0.11.1...v0.11.2rc1 gives you the idea.
08:07 < harding> PRab: oh, I was looking for what to put on the release notes section of the Bitcoin.org website when 0.11.2 gets released.  (We usually put up a draft PR when the RCs start getting built.)
08:09 < harding> If there are no notes yet, maybe I'll try drafting them now (sounds kinda fun) and wumpus can give them a review when he gets a chance.
08:23 < jgarzik> tagged univalue 1.0.1
08:30 -!- wangchun [~wangchun@li414-193.members.linode.com] has quit [Quit: leaving]
08:30 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-core-dev
08:44 -!- Guest23423 [~guest2342@171.4.237.159] has quit [Ping timeout: 250 seconds]
08:46 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
09:25 < michagogo> harding: I'd imagine it couldn't hurt
09:25 < michagogo> Worst case, they don't get used :-)
09:26 < michagogo> And yeah, I think there aren't release notes (at least not published ones) yet: 1:51:56 <wumpus> I don't think there's anything to be done there either (well apart from version bump and release notes)
09:26 < michagogo> 1:52:20 <wumpus> (and release notes don't necessarily have to wait before the tag)
09:32 < harding> michagogo: that's what I figured too, worst case they don't get used.  :-)  I think I'm almost done; I'm just trying to figure out good wording for the BIP65 stuff.
09:36 < harding> Luke-Jr, anyone else: for the release notes, should I include a paragraph like this one (updated to BIP65): https://bitcoin.org/en/release/v0.10.0#mining-and-relay-policy-enhancements
09:37 < harding> (And is there a block v4 libblkmaker?)
09:51 < Luke-Jr> harding: ugh, probably need that yes
09:52 < Luke-Jr> hopefully this will be the last ISM hack
09:58 < btcdrak> We probably want to mention something about the mempool median-past-locktime policy too so miners are aware of it.
10:01 < harding> btcdrak: yes, I'm doing that now; it's harder to write than I thought. :-)
10:01 < harding> (At least, keeping it concise is harder than I thought.)
10:02 < btcdrak> well it's probably just better to point them to  BIP113
10:03 < harding> I'm doing that too, of course. :-)
10:09 -!- trippysalmon [rob@2001:984:6466:0:51d:b5ab:ab61:bed8] has joined #bitcoin-core-dev
10:48 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
10:51 < GitHub174> [bitcoin] harding opened pull request #6968: [Docs] First-draft release notes for 0.11.2RC1 (0.11...release-notes-0.11.2) https://github.com/bitcoin/bitcoin/pull/6968
11:05 < gmaxwell> Has someone actually compared MTP to blocktime over the history of the bitcoin network to figure out what the median correction is precisely?
12:03 -!- BashCo [BashCo@gateway/vpn/mullvad/x-hjcgqioyaqmubkbf] has quit [Read error: Connection reset by peer]
12:07 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
12:43 -!- CodeShark [~androirc@40.135.239.174] has joined #bitcoin-core-dev
12:52 -!- fkhan [weechat@gateway/vpn/mullvad/x-ghdxmcfiadssqrnd] has quit [Read error: Connection reset by peer]
12:52 -!- CodeShark [~androirc@40.135.239.174] has quit [Ping timeout: 250 seconds]
12:54 -!- CodeShark [~androirc@40.135.239.174] has joined #bitcoin-core-dev
12:55 -!- CodeShark [~androirc@40.135.239.174] has quit [Client Quit]
12:56 -!- CodeShark [~androirc@40.135.239.174] has joined #bitcoin-core-dev
12:57 -!- fkhan [weechat@gateway/vpn/mullvad/x-urggymssigpspxaw] has joined #bitcoin-core-dev
13:08 -!- CodeShark [~androirc@40.135.239.174] has quit [Ping timeout: 250 seconds]
13:13 -!- trippysalmon [rob@2001:984:6466:0:51d:b5ab:ab61:bed8] has quit [Ping timeout: 250 seconds]
13:14 -!- CodeShark [~androirc@4.35.70.123] has joined #bitcoin-core-dev
13:20 -!- ParadoxSpiral_ [~ParadoxSp@p508B8F19.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
13:29 -!- CodeShark [~androirc@4.35.70.123] has quit [Ping timeout: 240 seconds]
13:56 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
14:15 -!- belcher [~user@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
14:15 -!- CodeShark_ [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has quit [Read error: Connection reset by peer]
14:17 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
15:32 -!- PRab_ [~chatzilla@2601:40a:8000:8f9b:c49b:a2dc:3cab:6419] has joined #bitcoin-core-dev
15:34 -!- PRab [~chatzilla@2601:40a:8000:8f9b:d59b:22a1:99bf:deb1] has quit [Ping timeout: 240 seconds]
15:34 -!- PRab_ is now known as PRab
15:40 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
15:44 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .]
15:46 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
16:21 -!- Yoghur114 [~jorn@g227014.upc-g.chello.nl] has joined #bitcoin-core-dev
16:34 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
16:50 -!- CodeShark [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has joined #bitcoin-core-dev
16:51 -!- CodeShark [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has quit [Client Quit]
16:51 -!- CodeShark [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has joined #bitcoin-core-dev
17:12 -!- CodeShark [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
17:12 -!- CodeShark [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has joined #bitcoin-core-dev
17:13 -!- CodeShark_ [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has joined #bitcoin-core-dev
17:14 -!- CodeShark is now known as Guest88917
17:14 -!- CodeShark_ [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has quit [Client Quit]
17:14 -!- Guest88917 [~CodeShark@2600:380:477f:a98c:ef40:2e55:154b:4d21] has quit [Client Quit]
17:30 -!- Yoghur114 [~jorn@g227014.upc-g.chello.nl] has quit [Remote host closed the connection]
17:44 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-iqfqhukhcsjcvxaw] has quit [Quit: Connection closed for inactivity]
18:12 -!- Guest23423 [~guest2342@171.5.156.154] has joined #bitcoin-core-dev
18:14 -!- Guest23423 [~guest2342@171.5.156.154] has quit [Read error: Connection reset by peer]
18:14 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
18:15 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
18:38 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
18:38 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
19:34 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev
19:36 < dcousens> Is there any difference to minReasonableRelayFee and minRelayTxFee ?
19:39 < dcousens> I'm not sure why there is two, but it seems the minReasonableRelayFee is not kept in sync with minRelayTxFee, any one know why?
20:02 -!- JackH [~Jack@host-80-43-141-3.as13285.net] has quit [Ping timeout: 265 seconds]
20:09 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: Leaving]
20:12 < dcousens> aye, the `-minrelaytxfee` seems to have no effect at all on `estimatefee` or the mempool in general
20:12 < dcousens> Is that intended?
20:13 < dcousens> (Or am I missing something)
20:31 < dcousens> Also, is there a reason estimatefee returns `-1` if `nblocks` is > 25?
21:00 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection]
21:12 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
21:16 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
21:30 < GitHub157> [bitcoin] laanwj opened pull request #6969: doc: there is no libboost-base-dev, add missing sudo in release notes (master...2015_11_docfix) https://github.com/bitcoin/bitcoin/pull/6969
21:46 -!- CodeShark [~androirc@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
22:09 < wumpus> fingers itch to merge #6954
22:10 < Luke-Jr> wumpus: Is it possible to generate/use a cookie file in addition to the rpcuser/pass?
22:10 < wumpus> no, only one authentication method at a time is supported
22:10 < Luke-Jr> k
22:10 < Luke-Jr> I guess -rpcpassword= does it for debugging purposes
22:15 < Luke-Jr> hrm, any way to access strDataDir QSettings without Qt? :/
22:16 < Luke-Jr> thoughts on a bitcoin-cli -printdatadir option or something?
22:16 < Luke-Jr> although it's unlikely to be in PATH on Windows.. so maybe that won't work
22:17 < Luke-Jr> wait, is that a bug for Core? that bitcoin-cli won't find -qt's cookie file?
22:17 < dcousens> Luke-Jr: the datadir will be in the same line you're executing?
22:17 < Luke-Jr> dcousens: bitcoin-qt supports overriding the data dir from a QSettings value
22:17 < wumpus> qt has its own settings, bitcoind/bitcoin-cli are not able to access those
22:17 < dcousens> ah
22:17 < wumpus> that's not a bug
22:17 < Luke-Jr> wumpus: what's the point of the cookie then?
22:18 < wumpus> to let bitcoind and bitcoin-cli communicate given just the datadir
22:18 < Luke-Jr> …
22:19 < Luke-Jr> awful lot considering bitcoin-cli is just a testing tool, and bitcoind users should be capable of configuring bitcoin.conf anyway :x
22:19 < wumpus> pass the right datadir to bitcoin-cli and it should work
22:19 < wumpus> well other software could use it too, but sure it needs to find out what the datadir is, or let the user point them at it
22:20 < Luke-Jr> I thought the whole point of the cookie file was so Bitcoin-Qt users didn't need to configure RPC explicitly
22:20 < wumpus> yes, it is
22:21 < Luke-Jr> but there's no reasonable way to get to it
22:21 < wumpus> any software that knows the bitcoin data dir can communicate with bitcoin{d,qt} if server=1
22:21 < wumpus> if it doesn't it needs to be pointed at it
22:23 < Luke-Jr> would it be terrible to have Bitcoin-Qt get strDataDir from a special QSettings that explicitly uses <default datadir>/datadir.ini or something?
22:23 < Luke-Jr> or better yet, ignore strDataDir for cookie purposes?
22:24 < wumpus> sure, another option would be to ignore the datadir completely
22:24 < wumpus> e.g. tor drops the cookie file in /var/... by default
22:24 < wumpus> then again, how to handle multiple instances in that case
22:24 < wumpus> I think putting it in the datadir makes sense
22:24 < wumpus> you can override the cookie path to be something else
22:24 < Luke-Jr> multiple Qt instances can't use the QSettings for datadir anyway
22:25 < Luke-Jr> if the user has to override anything, it defeats the purpose of being zero-configuration <.<
22:25 < wumpus> -rpccookiefile=/var/run/bitcoindcookie
22:25 < wumpus> just look in the registry, find the data dir, and use that
22:26 < Luke-Jr> that's a lot of code, considering Mac and Linux do it differently
22:26 < wumpus> normally you can assume that the cookie is in the data directory along with the other files, that's a feature not a  bug
22:26 < dcousens> Any ideas on the question I had before RE minReasonableRelayFee being out of sync with minRelayTxFee, is that intentional? In terms of the estimator policy.  All good if it is, but, it'd be nice to maybe just add a comment there to reassure its not just a missing reference
22:26 < wumpus> you can also use QSettings if your application is qt-based
22:26 < Luke-Jr> it's not even C++
22:27 < wumpus> yes it's some code, maybe we can make a libfindbitcoindatadir ...
22:27 < Luke-Jr> ugh
22:28 < gmaxwell> wait why isn't bitcoin-qt and bitcoin-cli finding the same datadir?!
22:28 < wumpus> although I think it's a  bad idea, as it wouldn't handle multiple instances, you need a way to choose a data directory anyway
22:28 < wumpus> bitcoin-qt allows choosing a data directory on first start in the GUI, this is stored inthe qt settings
22:28 < wumpus> bitcoin-cli and bitcoind don't care about that
22:28 < Luke-Jr> gmaxwell: bitcoin-qt gets datadir from Windows registry, Mac registry-equivalent, or an INI file on Linux; based on user input at first run
22:29 < Luke-Jr> wumpus: multiple instances can't mix with QSettings datadir period, unless I am missing something?
22:29 < wumpus> Luke-Jr: that's true. The datadir from QSettings is seen as a default, it's still possible to override it from the command line
22:30 < Luke-Jr> wumpus: so what if cookie file uses the same logic as bitcoin-cli for datadir? this seems to work in all cases..?
22:30 < Luke-Jr> if it's overridden via bitcoin.conf or cmdline, it uses that; otherwise the platform default
22:30 -!- ParadoxSpiral [~ParadoxSp@p508B8F19.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
22:32 < wumpus> dcousens: -1 for estimatefee means 'unknown'
22:32 < dcousens> wumpus: why not just give back an error
22:32 < wumpus> dcousens: don't know about minReasonableRelayFee/minRelayTxFee
22:33 < wumpus> dcousens: because
22:33 < Luke-Jr> …
22:33 < dcousens> (because ...?)
22:34 < wumpus> dcousens: yes I don't know, the interface was written in this way not that way
22:34 < wumpus> it's just a choice that was made at some point that made sense
22:34 < wumpus> or something
22:34 < dcousens> ok
22:35 < wumpus> if you go change it around now then people will complain about that
22:35 < wumpus> the values it can return are documented in the RPC help
22:35 < dcousens> that wasn't my main question, just something I noticed that was odd why playing with -minrelaytxfee and noticing it had no effect on the estimation algorithm
22:35 < wumpus> that's everything of an interface definition that we have, asking why it doesn't behave otherwise is quite pointless
22:37 < Luke-Jr> wumpus: if I made cookies ignore QSettings, will you accept it?
22:37 < wumpus> Luke-Jr: I think it's strange to make something ignore qsettings
22:38 < wumpus> Luke-Jr: it's a valid concern and maybe reason to re-think where the cookie file gets placed, but 'let's ignore qsettings' sounds like a terrible hack
22:38 < wumpus> then it will make *two* data directories
22:39 < gmaxwell> using something QT specific for handling finding the datadir on windows was probably what should have been avoided, since bitcoind and bitcoin-cli also need to find the data directory.
22:39 < Luke-Jr> it's tempting to change this to write to bitcoin.conf instead of QSettings then
22:40 < wumpus> NO NO NO NO
22:40 < Luke-Jr> wouldn't an append-only be safe?
22:40 < wumpus> don't write to bitcoin.conf
22:40 < wumpus> goddamnit 
22:40 < Luke-Jr> sigh
22:40 < gmaxwell> then you have the "how do you find bitcoin.conf" problem.
22:40 < wumpus> no it's not safe, software should not write to its configuration file,  it can't even be asssumed to be writable
22:40 < dgenr8> writing to bitcoin.conf should be controlled by a setting in bitcoin.conf
22:40 < Luke-Jr> gmaxwell: that's at least possible to solve
22:40 < wumpus> that's why I went with the cookie solution in the first place
22:41 < gmaxwell> Luke-Jr: it reduces to the same problem, finding the data directory.
22:41 < wumpus> otherwise I'd just have made it write a rpcuser and rpcpassword to bitcoin.conf
22:41 < Luke-Jr> gmaxwell: minus QSettings
22:42 < wumpus> bitcoin.conf is usually in the same directory as the cookie so it won't avoid *any* problems
22:42 < Luke-Jr> if the data directory cannot be overridden by QSettings, the problem is solved.
22:42 < wumpus> yes, let's rip that feature out again
22:42 < wumpus> why would people want a user friendly dialog to choose the datadir
22:42 < wumpus> what a stupid thing
22:42 < Luke-Jr> …
22:43 < gmaxwell> Luke-Jr: yes if you make the datadir not actually configurable then the issue of finding it goes away...
22:43 < wumpus> maybe 1% of users actually use bitcoin-qt with bitcoin-cli, 0.1% uses it with a changed datadir through qt
22:43 < wumpus> most people that want to use RPC with bitcoin-qt will use the debug console
22:44 < gmaxwell> wumpus: it is a bit broken that changing your datadir breaks bitcoind / bitcoin-cli from finding it. 
22:44 < Luke-Jr> wumpus: my main concern is BFGMiner, not bitcoin-cli
22:44 < gmaxwell> wumpus: e.g. joinmarket and bfgminer and such need to find the rpc stuff too.
22:44 < wumpus> gmaxwell: qsettings is the qt equivalent of adding command line arguments, you can pass a datadir to bitcoin-cli and it will work
22:45 < gmaxwell> wumpus: datadir isn't a qt specific thing. Finding the default datadir via the registery is the reasonable thing to do on windows, sure. requiring QT for that is less so.
22:46 < wumpus> yes because we really want to write our own registry/everyOSsettingsmechanism wrappers...
22:46 < Luke-Jr> I'm sure there's some way to avoid Qt for it, but that means implementing each platform's stuff
22:46 < wumpus> Qt is not strictly required though, other applications can read bitcon's datadir from the registry without qt
22:46 -!- ParadoxSpiral [~ParadoxSp@p508B8F19.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
22:46 < gmaxwell> wumpus: sometimes we have to... there are dozens of windows ifdefs in the code.  Unless you think linking bitcoind/bitcoin-cli to QT is a better plan. :)
22:47 < wumpus> but we use qt because that's available anyway
22:47 < wumpus> and we don't want piles of extra codes to maintain
22:47 < wumpus> sigh
22:47 < wumpus> there's tons of windows ifdefs in the code so let's add even more
22:48 < gmaxwell> wumpus: take a step back, ignore how its implemented. The behavior of our own compoents looking in different places due to internal architecture reasons and to no benefit to the user is surprising and suboptimal.
22:48 < wumpus> I'd prefer to reduce the amount of platform dependent code
22:48 < wumpus> well at least it's working for most people now, it's one of the things that is hardly ever complained about
22:48 < gmaxwell> I prefer to reduce the amount of platform dependant code too. But that doesn't mean that we should be disfunctional in some cases where a bit is needed to prevent disfunction.
22:48 < wumpus> there are tons of things *really* broken, this is not one of them!
22:50 < wumpus> no, it's not disfunctional... never mind
22:51 < wumpus> go ahead, implement it some way else, just make really sure it's backward compatible
22:54 < gmaxwell> Luke-Jr: I think we could probably just add code that reads the registry in the same way RandAddSeedPerfmon and looks to the same place QT looks, and call that from bitcoind/bitcoin-cli on windows, and document the location so other programs can look. No?
22:55 < Luke-Jr> gmaxwell: wouldn't make implementing it externally any easier than how it currently is.
22:56 < Luke-Jr> I'm sure QSettings has some well-defined location/format so things are backward compatible.
22:56 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-macuigubwwfjmatj] has joined #bitcoin-core-dev
22:56 < gmaxwell> Luke-Jr: well externally is going to have to deal with the OS specific way of finding things, regardless. But that can be made arbritarily easier through better documentation.
22:57  * wumpus really likes 'better documentation' instead of 'adding piles of code'
22:58 < Luke-Jr> supporting cookies was already going to be a major chore, so I'm inclined to just not do so at this point
22:58 < gmaxwell> Luke-Jr: this has nothing to do with cookies though.
22:58 < gmaxwell> You'd fail to find the config location.
22:58 < gmaxwell> wumpus: I'd still suggest adding (hopefully) 1/2 LOC: code to use RegQuery to find the same location in bitcoind/bitcoin-cli.
22:58 < wumpus> indeed it's the same for finding bitcoin.conf
22:59 < Luke-Jr> does bitcoin-qt use strDataDir for the config location too? :/
22:59 < wumpus> yes
22:59 < Luke-Jr> gmaxwell: you're forgetting Mac and Linux..
22:59 < wumpus> it uses it to set -datadir
22:59 < wumpus> (which generally, unless you override it with -conf, specifies the configuration file location as well)
22:59 < Luke-Jr> bleh
23:00 < wumpus> bitcoin, by design, only has one datadir. If you move it, everything moves with it
23:00 < gmaxwell> Luke-Jr: nothing is special on linux. There is no magical registry path location there.  I'm not well enough informed about the mac parallel.
23:00 < Luke-Jr> gmaxwell: hehehe.. yes it is
23:00 < Luke-Jr> ~/.config/Bitcoin/Bitcoin-Qt.conf
23:00 < wumpus> in linux it's just a file
23:01 < gmaxwell> what do we have an installer just setting a gconf thing for it on linux too?
23:01 < Luke-Jr> gmaxwell: it's not part of the installer
23:01 < wumpus> however you turn it, finding the datadir was always going to be an OS-specific affair
23:02 < Luke-Jr> wumpus: hm, that's a point.. I guess I must already have some ifdefs going on
23:03 < gmaxwell> even if it wasn't configurable, the defaults are different.
23:12 -!- NLNico [~NLNico@unaffiliated/nlnico] has joined #bitcoin-core-dev
23:40 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
23:45 < GitHub126> [bitcoin] laanwj opened pull request #6970: Fix crash in validateaddress with -disablewallet (master...2015_11_rpc_validateaddress_crash) https://github.com/bitcoin/bitcoin/pull/6970