1 2017-09-14 04:28:41 <GypsyScotty> I'm using json-rpc to bitcoind. Using request method "getwalletinfo", does anybody know if the transaction count "txcount" value returned from the api will reliably increase for every incoming and outgoing transaction associated with the private keys in the wallet, and if so does it have an upper limit or any gotchas I should know about?  I'm considering using it as an indicator as to
 2 2017-09-14 04:28:41 <GypsyScotty> whether or not my script should "ListTransactions" and account for any new transactions. If anybody knows of a better way that info would be welcome too, of course. :-) Link to Docs https://bitcoin.org/en/developer-reference#getwalletinfo
 3 2017-09-14 04:29:52 <GypsyScotty> not sure if this is a questoin I should put into #bitcoin-core-dev but figured I should ask here first.
 4 2017-09-14 04:30:51 <mr_burdell> maybe wallet notify would be a better option
 5 2017-09-14 04:31:04 <GypsyScotty> cool, i'll check that :-)
 6 2017-09-14 04:31:31 <GypsyScotty> is that a part of the json-rpc API into bitcoin-core ?
 7 2017-09-14 04:33:08 <mr_burdell> -walletnotify=<cmd>	Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
 8 2017-09-14 04:33:11 <GypsyScotty> i do see an "alert" https://bitcoin.org/en/developer-reference#alert   but that looks like it's been depricated out
 9 2017-09-14 04:33:24 <mr_burdell> you add it to the config
10 2017-09-14 04:33:25 <GypsyScotty> ahhhhhh interesting
11 2017-09-14 04:34:56 <GypsyScotty> that sounds quite handy.. that way I don't have to "poll" the bitcoin-core daemon...    except... hummm.. i wonder how fault tollerent it is... i'd probalby have to take precations so the system would resume properly if any part of it failed for any duration..
12 2017-09-14 04:35:25 <GypsyScotty> which of course i'll have to do no matter what... hummm
13 2017-09-14 04:35:30 <mr_burdell> you could use -blocknotify and just poll on each block
14 2017-09-14 04:35:45 <mr_burdell> or both
15 2017-09-14 04:36:18 <luke-jr> GypsyScotty: listsinceblock?
16 2017-09-14 04:36:32 <GypsyScotty> I much appreciate all the ideas :-)
17 2017-09-14 04:36:32 <mr_burdell> there's also ZMQ to get updates
18 2017-09-14 04:36:49 <luke-jr> mr_burdell: ZMQ is (in general, not bitcoin-related) unreliable
19 2017-09-14 04:37:14 <mr_burdell> ah ok... I haven't used it much
20 2017-09-14 04:37:22 <GypsyScotty> hummm ListSinceBlock might be perfect... i'm going to have to cron/daemon some of my functions no matter what... book-keeping stuff.
21 2017-09-14 04:38:02 <luke-jr> GypsyScotty: for payment confirmation, it only makes sense to check when a new block comes in (-blocknotify); for UI stuff, you may want to check more often for unconfirmed txs
22 2017-09-14 04:39:26 <GypsyScotty> makes sense
23 2017-09-14 16:36:39 <boltzar> hey guys! i see the new version of bitcoin core is out. do you know when can i update bitcoind on my server ?
24 2017-09-14 16:37:19 <boltzar> i use ubuntu, if it matters
25 2017-09-14 16:40:16 <boltzar> i have tried to upgrade via apt-get but i get the same version when i start it : "version": 140200
26 2017-09-14 16:42:34 <wxxs> they won't be in the ubuntu repository yet, the new release has only been tagged for a few days
27 2017-09-14 16:43:01 <boltzar> oh, so i have to wait for it to get in the ubunto repo right ?
28 2017-09-14 16:43:31 <wxxs> you can compile from source or try the binaries here: https://bitcoin.org/bin/bitcoin-core-0.15.0/
29 2017-09-14 16:44:36 <boltzar> thanks
30 2017-09-14 16:44:58 <boltzar> do you know what's the problem with the network ? why aren't the transactions getting confirmed ?
31 2017-09-14 16:46:50 <wxxs> the mempool is filling up, what fee are you using?
32 2017-09-14 16:47:03 <boltzar> about 2 $
33 2017-09-14 16:47:38 <wxxs> in sat/byte?
34 2017-09-14 16:47:53 <boltzar> 140
35 2017-09-14 16:48:53 <boltzar> and i have some transactions from earlier today that i can't do anything with them...those are smaller... 14 sat/B
36 2017-09-14 16:50:12 <wxxs> 140 sat/byte tx should be confirmed in the next block, 14 sat/byte is going to have to wait until the backlog is cleared
37 2017-09-14 16:50:32 <wxxs> i am checking here: https://btc.com/stats/unconfirmed-tx#fees_recommended_sb
38 2017-09-14 16:50:43 <wxxs> and here: https://core.jochen-hoenicke.de/queue/#8h
39 2017-09-14 16:50:57 <wxxs> in case you want to see it yourself
40 2017-09-14 16:51:59 <boltzar> 140 sat/byte and it's unconfirmed for a 2 hours now...but i will wait...
41 2017-09-14 16:58:57 <boltzar> already 30k transactions unconfirmed.
42 2017-09-14 16:59:11 <boltzar> by the end of the day it will get to 60k i guess.
43 2017-09-14 19:52:09 <CryptAxe> Does anyone happen to know a txid I could look at on a block explorer with a segwit output?
44 2017-09-14 20:07:40 <Chris_Stewart_5> CryptAxe: https://www.smartbit.com.au/tx/c586389e5e4b3acb9d6c8be1c19ae8ab2795397633176f5a6442a261bbdefc3a
45 2017-09-14 20:07:40 <cluelessperson> Not found.
46 2017-09-14 20:08:02 <Chris_Stewart_5> sipas first segwit tx
47 2017-09-14 20:09:04 <CryptAxe> Thank you!!!
48 2017-09-14 20:09:09 <CryptAxe> Been looking for a while
49 2017-09-14 20:09:55 <CryptAxe> cluelessperson it works for me
50 2017-09-14 20:12:57 <cluelessperson> hm
51 2017-09-14 20:15:16 <cluelessperson> CryptAxe: ah, looks like the library I'm using doesn't support SegWit TXes
52 2017-09-14 20:16:12 <cluelessperson> petertodd: python-bitcoinlib finally broke.  (but thank you for your service)  :)
53 2017-09-14 20:21:05 <cluelessperson> SegWit Transaction Found, but not yet supported by bitcoinlib :(
54 2017-09-14 20:21:06 <cluelessperson> c586389e5e4b3acb9d6c8be1c19ae8ab2795397633176f5a6442a261bbdefc3a
55 2017-09-14 20:21:13 <cluelessperson> CryptAxe: ^ there, because I'm lazy
56 2017-09-14 20:44:06 <CryptAxe> Thank you cluelessperson :)
57 2017-09-14 21:20:02 <petertodd> cluelessperson: heh, yeah, see the release notes for the latest v0.8.0 (?) release for the workaround; segwit is in git master, but I'm sure some details of the API will change when I get a chance to look at it properly
58 2017-09-14 21:20:30 <petertodd> cluelessperson: https://github.com/petertodd/opentimestamps-server/tree/2017-08-segwit <- example of a project using git master via subtrees
59 2017-09-14 21:20:43 <cluelessperson> petertodd: thanks
60 2017-09-14 21:20:50 <petertodd> cluelessperson: np!
61 2017-09-14 21:21:59 <cluelessperson> thankth
62 2017-09-14 21:37:42 <lrvick> So I am running bitcoind with: bitcoind -regtest -rpcuser=indexer -rpcpassword=indexer -rpcbind=0.0.0.0 -txindex -disablewallet=1 -rpcthreads=50 -rpcallowip=::/0
63 2017-09-14 21:38:08 <lrvick> netstat -tulpn shows "tcp        0      0 0.0.0.0:18444           0.0.0.0:*               LISTEN""
64 2017-09-14 21:38:28 <lrvick> but I can't get the CLI to connect
65 2017-09-14 21:39:00 <lrvick> bitcoin-cli -regtest -rpcuser=indexer -rpcpassword=indexer -rpcconnect=localhost -rpcport=18444 setgenerate true 101
66 2017-09-14 21:39:38 <lrvick> error: couldn't connect to server: EOF reached (code 1)
67 2017-09-14 21:40:44 <lrvick> I tried to RTFM but this is just not behaving how I expect. Trying to do some integration tests.
68 2017-09-14 21:45:59 <achow101> Irvick: bitcoind is not bound to localhost
69 2017-09-14 21:47:53 <lrvick> -rpcconnect=0.0.0.0 has the same problem
70 2017-09-14 21:48:23 <lrvick> or the external IP of the machine
71 2017-09-14 22:03:47 <CryptAxe> Are you trying to use the CLI from the same system?
72 2017-09-14 22:05:22 <CryptAxe> ./bitcoind -regtest -rpcuser=cryptaxe -rpcpassword=pass -server=1 -connect=localhost
73 2017-09-14 22:05:24 <CryptAxe> works for me
74 2017-09-14 23:24:08 <lrvick> CryptAxe: bitcoind and the cli won't be on the same system, in my setup.
75 2017-09-14 23:24:36 <lrvick> thus me trying to listen on and connect via 0.0.0.0
76 2017-09-14 23:24:48 <lrvick> which works as expected for modes other than regtest as best as I can tell
77 2017-09-14 23:25:23 <lrvick> Either regtest breaks the ability to accept incoming connections from any ip, or I am doing it wrong
78 2017-09-14 23:25:26 <lrvick> betting on the latter