1 2015-11-22 09:07:12 <BW^-> bitcoind --gen=0 -printtoconsole -d /bitcoind_data -conf /bitcoin.conf
 2 2015-11-22 09:07:14 <BW^-> =>  "There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead."
 3 2015-11-22 09:07:28 <BW^-> how do you start BitcoinD nowadays??
 4 2015-11-22 09:09:05 <BW^-> this is 0.11.2
 5 2015-11-22 09:09:50 <BW^-> https://github.com/bitcoin/bitcoin/blob/master/src/bitcoind.cpp
 6 2015-11-22 09:22:52 <BW^-> if (!IsSwitchChar(argv[i][0]) && !boost::algorithm::istarts_with(argv[i], "bitcoin:"))                fCommandLine = true;
 7 2015-11-22 09:23:02 <BW^-> ..  if (fCommandLine)     { fprintf(stderr, "Error: There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead
 8 2015-11-22 09:23:42 <jouke> shouldn't you use double dash everywhere?
 9 2015-11-22 09:23:47 <BW^-> ahaaaa, no space between "-d" and the datadir
10 2015-11-22 09:23:57 <BW^-> jouke: what do you mean?
11 2015-11-22 09:24:27 <BW^-> jouke: /bitcoind --printtoconsole --d /bitcoind_data --conf /bitcoin.conf => Error: There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead.
12 2015-11-22 09:24:27 <BW^-> nope
13 2015-11-22 09:24:32 <BW^-> you should just write them together
14 2015-11-22 09:24:53 <jouke> --conf=?
15 2015-11-22 09:25:36 <jouke> I don't have bitcoind on this laptop.
16 2015-11-22 09:26:45 <BW^-> jouke: ah right, when I did "-dmydir" it didn't work - let's try
17 2015-11-22 09:27:13 <BW^-> jouke: still not! :(((((((
18 2015-11-22 09:27:23 <BW^-> jouke: /bitcoind --server=0 --printtoconsole --d=/bitcoind_data --conf=/bitcoin.conf
19 2015-11-22 09:28:45 <BW^-> jouke: ah so, /bitcoind -server=0 -printtoconsole -datadir=/bitcoind_data -conf=/bitcoin.conf
20 2015-11-22 09:29:54 <BW^-> jouke: it's not a problem to run bitcoind without a configuration file, is it?
21 2015-11-22 09:32:01 <jouke> BW^-: I don't know what happens with server=0.
22 2015-11-22 09:32:07 <jouke> I'm just another user
23 2015-11-22 09:40:55 <BW^-> jouke: it disables the RPC server.
24 2015-11-22 09:41:07 <BW^-> jouke: anyhow, solved now :D  - thanks for giving a thought :)
25 2015-11-22 12:17:53 <JackH> !seen matjjs
26 2015-11-22 12:17:54 <gribble> I have not seen matjjs.
27 2015-11-22 14:35:21 <BW^-> Bitcoin Core is singlethreaded, isn't it, so why does it take 182.08% CPU? =)         maybe my OS has a weird cpu meter?
28 2015-11-22 14:35:25 <BW^-> it's syncing
29 2015-11-22 14:35:47 <sipa> BW^-: it's not single threaded
30 2015-11-22 14:36:10 <sipa> script verification in particular uses as many cores as possible
31 2015-11-22 14:38:00 <BW^-> sipa: aha... can i force it to use 1 core only?
32 2015-11-22 14:38:41 <BW^-> sipa: i mean, at least with the current max 8 transactions per second, it's not exactly CPU-heavy right?
33 2015-11-22 14:38:56 <BW^-> sipa: so it's basically only full sync where cpu speed really impacts things?
34 2015-11-22 14:40:34 <sipa> BW^-: -par=1
35 2015-11-22 14:40:49 <sipa> BW^-: no, for block validation it matters too
36 2015-11-22 14:41:13 <sipa> BW^-: because a block is a sudden burst of transactions that need to be validated, and when the signature cache doesn't have them validated already, that's a problem
37 2015-11-22 14:42:19 <BW^-> sipa: you mean validation implies IO too so that's why more cores are beneficial?
38 2015-11-22 14:43:06 <sipa> BW^-: no, when a new block comes in, you want to verify it as fast as possible to it can be relayed to the network
39 2015-11-22 14:43:19 <sipa> BW^-: that's up to a few 1000 transactions you have never seen at once
40 2015-11-22 14:43:27 <sipa> BW^-: those are validated in parallel
41 2015-11-22 14:44:21 <BW^-> ah
42 2015-11-22 14:44:29 <BW^-> sipa: is there any DoS potential here, ever?
43 2015-11-22 14:44:43 <BW^-> sipa: how much CPU time are we talking , at most, on say a 1-core smartphone?
44 2015-11-22 14:44:46 <BW^-> for a block
45 2015-11-22 14:45:10 <sipa> seconds
46 2015-11-22 14:46:00 <sipa> though the bottleneck will perhaps be looking up the outputs in the utxo set so they can be spent
47 2015-11-22 15:18:22 <BW^-> sipa: what's BitcoinD's worstcase RAM use usecase today?
48 2015-11-22 15:18:43 <BW^-> a ton of unverified transactions that could cost infinite RAM and sink *all* bitcoin nodes that are not protected, I hope not? =)
49 2015-11-22 16:03:01 <BW^-> what's the Absolutely Worst Case mempool size, is there any theoretical upper limit or is it infinity?
50 2015-11-22 16:20:09 <sturles> BW^-: It is theoretically limited by the UTXO set.  You can't spend each more than once, and each transaction has a maximum size.
51 2015-11-22 16:21:15 <sturles> If you run Bitcoin Core from git (not reccomended), you can specify a maximum mempool size.
52 2015-11-22 16:40:49 <BW^-> sturles: wait, UTXO:s are more or less unlimited in amount (we're talking about billions anyhow), so that's not a big help is it
53 2015-11-22 16:41:08 <BW^-> sturles: is there any way that i could limit it in the build process? if that cap would be reached, what would happen?
54 2015-11-22 17:09:48 <BW^-> sturles: where's the code for specifying max mempool size?  i just want a very crude measure to ensure my instance doesn't go down, but instead auto-heals in some fashion at least slowly if there's a DoS
55 2015-11-22 17:12:50 <BW^-> anything more graceful than hard crashes, hm.
56 2015-11-22 17:17:31 <BW^-> could we say that if BitcoinD takes more than 1GB memory then the network is really compromised and we're waiting for a DoS to pass??
57 2015-11-22 19:44:16 <sturles> BW^-: I don't have time to look up individual patches, but in current git it is a command line parameter.  When the limit is reached, transactions will get evicted based on fee per KB only.  Unfortunately, since it fails to take priority into account, this will evict many of the transactions which are likely to get confirmed in the next block as well.
58 2015-11-22 19:48:51 <BW^-> stures: wait, what do you mean by priority here+
59 2015-11-22 19:54:31 <gijensen> BW^-: I'm assuming "priority = sum(input_value_in_base_units * input_age)/size_in_bytes", explained on the wiki.
60 2015-11-22 20:19:16 <BW^-> gijensen,sturles: aha, so maybe it's relevant for me to switch over to the git head then.    thanks for pointing out!
61 2015-11-22 20:21:01 <gijensen> Anytime :)
62 2015-11-22 21:27:27 <lorenzoasr> hello, anyone knows a bitcoin-rpc python3 library ? I've tested http://laanwj.github.io/bitcoin-python/doc/ but it doesnt seem to work and it wasnt updated in the last 2 years, thank you
63 2015-11-22 21:31:11 <petertodd> lorenzoasr: try python-bitcoinlib, https://github.com/petertodd/python-bitcoinlib
64 2015-11-22 21:31:41 <lorenzoasr> thank you peter, im gonna try that
65 2015-11-22 21:32:00 <petertodd> lorenzoasr: good luck!
66 2015-11-22 21:32:54 <petertodd> lorenzoasr: bitcoin.rpc is the RPC interface; also available on pypi