1 2016-05-02 02:15:35 <luke-jr> phantomcircuit: 0.12 should be fine on CentOS
 2 2016-05-02 02:15:53 <luke-jr> but he's tryin gto build some non-standard node implementation
 3 2016-05-02 03:25:46 <Ohai2u> ohi
 4 2016-05-02 03:26:10 <Ohai2u> where is the right place to talk about blockchain and decentralized dev?
 5 2016-05-02 05:56:20 <midnightmagic> Ohai2u: check the topic here. This is specifically for discussion about the *bitcoin* network and *reference software.*
 6 2016-05-02 18:36:43 <JackH> once settxfee through the bitcoin-cli, does it stay until reboot?
 7 2016-05-02 18:37:11 <JackH> once = when setting
 8 2016-05-02 18:49:18 <murch> JackH: Yes
 9 2016-05-02 18:50:37 <JackH> is it right to assume that if I want a different fee set as default, then I have to add it to the .conf file?
10 2016-05-02 18:53:10 <murch> JackH: My source is this one: http://bitcoin.stackexchange.com/a/43927/5406
11 2016-05-02 18:53:41 <Lucifer333> hi
12 2016-05-02 18:53:54 <JackH> ah
13 2016-05-02 18:53:57 <JackH> alright
14 2016-05-02 18:53:59 <Lucifer333> I am analyzing the "getblocks" command from bitcoin
15 2016-05-02 18:54:16 <Lucifer333> I need to create a block locator,
16 2016-05-02 18:55:00 <Lucifer333> How do I know if I am on an orphaned chain, ???  How can I node if a node is telling me the truth?
17 2016-05-02 18:55:23 <Lucifer333> any devs here who can answer this I would appreceate it
18 2016-05-02 18:58:04 <murch> JackH: Sorry, I just had seen that the other day, that's why I knew the first part, but I don't feel knowledgeable to advise you further than that
19 2016-05-02 18:58:15 <JackH> Lucifer333, Bitcoin core 0.12 came with some new things so that I believe you dont need to rely on the cli commands
20 2016-05-02 18:58:35 <JackH> this one Lucifer333 https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md
21 2016-05-02 18:59:28 <JackH> murch, thanks for the answer anyway, I think I got it from here
22 2016-05-02 18:59:47 <JackH> the wiki is just so outdated its impossible to rely on it
23 2016-05-02 19:33:12 <sdaftuar> i have found the developer docs here to be generally pretty good: https://bitcoin.org/en/developer-documentation
24 2016-05-02 19:34:43 <arioBarzan> Does Gavin's commit access still remain revoked?
25 2016-05-02 20:02:19 <ndrchvzz> why does getblockchaininfo say that csv is not started yet when it was meant to start o 1st May ?
26 2016-05-02 20:08:51 <murch> ndrchvzz: Only voting has started, it's not activated
27 2016-05-02 20:10:41 <ndrchvzz> it should be 'defined' until 1 may, then 'started' after 1 may, then 'lockedin' once 1916 blocks are reached, then 'activate' after 2016 blocks. Right?
28 2016-05-02 20:11:36 <ndrchvzz> that's what it says here: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki
29 2016-05-02 20:49:54 <btcdrak> murch: it's not voting. miners signal they are ready.
30 2016-05-02 20:50:45 <murch> btcdrak: Alright. However, if they were to decide not to signal ready that would effectively be a vote against. ;)
31 2016-05-02 20:50:55 <btcdrak> murch: no
32 2016-05-02 20:52:02 <murch> okay, I guess I'll have to take your word for it, since you don't elaborate on the finer points of that distinction. :)
33 2016-05-02 20:52:32 <btcdrak> ndrchvzz: note that the window is between each diff retarget window, so to start signalling requires >=starttime and diff window to start. This is why bitcoind is not signalling at the moment, since starttime was before the next retarget
34 2016-05-02 21:33:51 <esotericnonsense> zmq support in bitcoind looks awesome :) should be able to knock out a lot (all?) polling from my client
35 2016-05-02 21:38:18 <ndrchvzz> ok so at next diff change, the csv state will be 'started', and miners that now are mining version 0x20000000 will mine version 0x20000001