1 2017-12-29 00:54:29 0|meshcollider|warren: translation fixes have to be done on transifex, could you let them know so they can make an account there and join the (German?) translation team?
2 2017-12-29 02:49:09 0|promag|is https://github.com/bitcoin/bitcoin/projects/5 up to date?
3 2017-12-29 04:06:13 0|fanquake|progmag is there something missing that you think should be in there?
4 2017-12-29 04:06:20 0|fanquake|*promag
5 2017-12-29 04:10:55 0|fanquake|I've added some additional PRs
6 2017-12-29 06:00:03 0|meshcollider|fanquake: maybe #11708
7 2017-12-29 06:00:05 0|gribble|https://github.com/bitcoin/bitcoin/issues/11708 | Add P2SH-P2WSH support to signrawtransaction and listunspent RPC by MeshCollider ÷ Pull Request #11708 ÷ bitcoin/bitcoin ÷ GitHub
8 2017-12-29 06:42:32 0|fanquake|meshcollider added
9 2017-12-29 07:28:26 0|cluelessperson|does the regtest mode not accept rpcport options?
10 2017-12-29 07:28:29 0|cluelessperson|or datadir?
11 2017-12-29 07:28:50 0|eck|it will use a datadir relative to the one you specify
12 2017-12-29 07:29:04 0|eck|actually i take that back
13 2017-12-29 07:29:07 0|cluelessperson|because with the regtest, it seems to be still using 8332 (which is taken)
14 2017-12-29 07:30:11 0|sipa|that seems wrong; the regtest default RPC port is 18443
15 2017-12-29 07:31:28 0|cluelessperson|2017-12-29 07:31:05 Binding RPC on address 127.0.0.1 port 8332 failed.
16 2017-12-29 07:31:49 0|sipa|then perhaps it's not actually in regtest mode?
17 2017-12-29 07:32:00 0|sipa|or you explicitly configured the port number?
18 2017-12-29 07:32:49 0|cluelessperson|sipa: at the top of "regtest.conf" is regtest=1
19 2017-12-29 07:33:15 0|sipa|regtest.conf?
20 2017-12-29 07:33:58 0|sipa|there is no such config file, unless you're explicitly configuring it with a -conf= command line argument
21 2017-12-29 07:34:14 0|sipa|generally you should specify the network on the command line
22 2017-12-29 07:35:10 0|cluelessperson|sipa: /var/bitcoin/bitcoind/source/bitcoin/src/bitcoind "-conf=/etc/bitcoind/regtest.conf"
23 2017-12-29 07:35:24 0|sipa|ah, ok!
24 2017-12-29 07:35:27 0|cluelessperson|:P
25 2017-12-29 07:36:15 0|sipa|i'm not sure you can change the network in the config file still, as usually the config file is only determined after choosing the network
26 2017-12-29 07:36:28 0|cluelessperson|sipa: it works for testnet=1 :P
27 2017-12-29 07:36:37 0|cluelessperson|sipa: /var/bitcoin/bitcoind/source/bitcoin/src/bitcoind "-conf=/etc/bitcoind/testnet.conf"
28 2017-12-29 07:36:41 0|sipa|interesting
29 2017-12-29 07:37:03 0|sipa|and regtest.conf does not contain any rpcport=8332 line?
30 2017-12-29 07:39:04 0|cluelessperson|I had an rpcport=18331, then I tried rpcport=28332, but then I removed it, same output, 8332
31 2017-12-29 07:40:01 0|cluelessperson|sipa: I'll try specifying it
32 2017-12-29 08:05:59 0|cluelessperson|sipa: yeah, so it DOES start in regtest most, but it completely ignores the conf
33 2017-12-29 08:06:14 0|cluelessperson|most/mode
34 2017-12-29 08:07:00 0|sipa|cluelessperson: very strange
35 2017-12-29 08:08:06 0|cluelessperson|sipa: to be clear, it seems regtest works when options are specified as arguments, but not when a conf file is given
36 2017-12-29 08:08:59 0|sipa|i can't imagine that's specific to regtest
37 2017-12-29 08:10:55 0|cluelessperson|sipa: https://hastebin.com/raw/seqacuneyu These unit files all work, except regtest
38 2017-12-29 08:11:12 0|cluelessperson|until I add -regtest in there on the ExecStart line
39 2017-12-29 08:13:07 0|sipa|what is the contents of those confog files?
40 2017-12-29 08:17:12 0|cluelessperson|sipa: https://hastebin.com/raw/xipacapexe
41 2017-12-29 08:26:08 0|sipa|cluelessperson: very curious
42 2017-12-29 09:16:32 0|aj|cluelessperson: your regtest.conf doesn't have a -rpcallowip setting? that'll make it ignore rpcbind
43 2017-12-29 09:20:29 0|aj|cluelessperson: hmm, i get similar behaviour switching from cmd line args to -conf though, weird
44 2017-12-29 09:23:10 0|provoostenator|Hooray, QT was using 37 GB RAM again during index (dbcache=5000). It was using 18 threads. I'll cherry-pick #11824 to see if that helps.
45 2017-12-29 09:23:13 0|gribble|https://github.com/bitcoin/bitcoin/issues/11824 | Block ActivateBestChain to empty validationinterface queue by TheBlueMatt ÷ Pull Request #11824 ÷ bitcoin/bitcoin ÷ GitHub
46 2017-12-29 09:25:55 0|aj|cluelessperson: hmm, no i don't; i only get dodgy behaviour when bitcoind doesn't see my conffile; is /etc/bitcoind/regtest.conf unreadable by the bitcoind user maybe?
47 2017-12-29 09:51:52 0|bitcoin-git|[13bitcoin] 15sipa pushed 8 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/5180a86c96bc...d9fdac130a5e
48 2017-12-29 09:51:53 0|bitcoin-git|13bitcoin/06master 1466aa1d5 15Matt Corallo: Refactor ProcessGetData in anticipation of avoiding cs_main for ABC
49 2017-12-29 09:51:53 0|bitcoin-git|13bitcoin/06master 14818075a 15Matt Corallo: Create new mutex for orphans, no cs_main in PLV::BlockConnected...
50 2017-12-29 09:51:54 0|bitcoin-git|13bitcoin/06master 14a734896 15Matt Corallo: Avoid cs_main in net_processing ActivateBestChain calls
51 2017-12-29 09:52:25 0|bitcoin-git|[13bitcoin] 15sipa closed pull request #11824: Block ActivateBestChain to empty validationinterface queue (06master...062017-12-11822-debug) 02 https://github.com/bitcoin/bitcoin/pull/11824
52 2017-12-29 09:56:57 0|provoostenator|This is also the second time that it completely redownloads the blockchain after I force-quit during an re-index. In this case I had copied the blocks folder over from a backup and that files are still there. It turns out you really have to launch with -reindex=1, or I guess it won't even look for those files?
53 2017-12-29 09:57:59 0|provoostenator|Reindexing again now with that potential fix branch, I'll keep an eye on it.
54 2017-12-29 10:02:15 0|xiedeacc|what's CCoinsViewDB::GetHeadBlocks for? I have google a lot, there exists little information
55 2017-12-29 10:03:18 0|xiedeacc|159
56 2017-12-29 10:03:18 0|xiedeacc|160 //! Retrieve the range of blocks that may have been only partially written.
57 2017-12-29 10:03:19 0|xiedeacc|161 //! If the database is in a consistent state, the result is the empty vector.
58 2017-12-29 10:03:19 0|xiedeacc|162 //! Otherwise, a two-element vector is returned consisting of the new and
59 2017-12-29 10:03:19 0|xiedeacc|163 //! the old block hash, in that order.
60 2017-12-29 10:03:35 0|xiedeacc|confused with this comment
61 2017-12-29 10:04:17 0|meshcollider|cluelessperson: does your debug.log have a "Using config file regtest.conf" line, just to confirm its reading the right file?
62 2017-12-29 10:04:52 0|echeveria|provoostenator: force quitting while syncing will cause you problems, you should expect that.
63 2017-12-29 10:06:09 0|provoostenator|I did have to replace blocks/blk00000.dat with the backup, because that got overridden when I relaunched without -reindex. echeveria: I know, but there's not much else you can do if your system need 5 minutes just to wake up the screen because some application decided to OOM :-)
64 2017-12-29 10:06:24 0|provoostenator|(well actually, not OOM)
65 2017-12-29 10:11:11 0|sipa|xiedeacc: i saw you also asked this on stackexchange; i will answer there
66 2017-12-29 10:15:09 0|xiedeacc|ok thanks a lot
67 2017-12-29 10:15:10 0|sipa|provoostenator: it's expectes that your node needs to redo the work since the last flush, and with large dbcache flushing is very infrequwnt - so that may mean redoing frok scratch
68 2017-12-29 10:40:40 0|bitcoin-git|[13bitcoin] 15martinus opened pull request #12048: Use best-fit strategy in Arena, now O(log(n)) instead O(n) (06master...06faster_arena) 02 https://github.com/bitcoin/bitcoin/pull/12048
69 2017-12-29 11:13:05 0|provoostenator|sipa: that would explain re-indexing from scratch, right? But why does it start restart the whole chain download?
70 2017-12-29 11:15:18 0|sipa|provoostenator: because its knowledge about what blocks it has on disk is part of the flush
71 2017-12-29 11:15:51 0|sipa|perhaps that can be improved though
72 2017-12-29 11:16:03 0|provoostenator|Could it check to see if any block****.dat files are present?
73 2017-12-29 11:16:22 0|sipa|we could flush the block index more frequently than the chainstate
74 2017-12-29 11:17:13 0|provoostenator|Maybe when you launch with -reindex, it should do a quick flush at the beginning?
75 2017-12-29 11:17:35 0|provoostenator|Because I don't mind it doing the index again, I just don't want it to do a full download just because I forgot to pass -reindex=1
76 2017-12-29 11:37:32 0|sipa|provoostenator: you're right
77 2017-12-29 11:50:19 0|provoostenator|Mmm, actually I only copied the block****.dat files over, which I'm guess don't include the headers. So the fact that it's downloading the headers might be unlreated. Although when I start with -reindex=1 it reindexes first and then downloads the headers, whereas when I launched without that flag it immedidately fetches the headers.
78 2017-12-29 12:11:25 0|sipa|provoostenator: the index is in blocks/index/
79 2017-12-29 12:11:44 0|sipa|without that, you'll need reindex to scan for blocks that you may have that aren't in the index
80 2017-12-29 12:12:05 0|provoostenator|Oh ok, nvm, I deleted that the second time around.
81 2017-12-29 12:13:45 0|provoostenator|So first time I copied /blocks including index, ran -reindex=1 until it ran out of memory. I then restarted without -reindex and it began downloading headers. I then deleted the index subdirectory and restored blcok00001.dat from my backup (but didn't restore index from that backup). It then reindexed and now it's downloading headers.
82 2017-12-29 12:14:14 0|provoostenator|(using -reindex=1 in that last attempt)
83 2017-12-29 13:21:41 0|provoostenator|Regarding our discussion a few days ago around Lightning implementations needing txindex=1. Turns out c-lightning doesn't, LND found a way to avoid needing it when using RPC and that bitcoind already doesn't need it when using the neutrino protocol: https://github.com/lightningnetwork/lnd/issues/527
84 2017-12-29 13:22:39 0|provoostenator|So no urgent need to make txindex faster, work with pruned nodes, or find some other RPC workaround to help these lightning integrations afaik. Haven't talked to Eclair yet.
85 2017-12-29 13:53:26 0|bayatloo|Hi
86 2017-12-29 13:53:50 0|bayatloo|can i develop Bitcoin with c#
87 2017-12-29 13:56:17 0|provoostenator|bayatloo: https://github.com/MetacoSA/NBitcoin (though outside scope of this channel, I believe they use Gitter for chat)
88 2017-12-29 16:26:06 0|bitcoin-git|[13bitcoin] 15251Labs opened pull request #12050: Implements a virtual destructor on the BaseRequestHandler class. (06master...06patch/BaseRequestHandler-virtual-dtor) 02 https://github.com/bitcoin/bitcoin/pull/12050
89 2017-12-29 16:44:28 0|ossifrage|Any idea what fork is causing this leakage: ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b, bad-diffbits, incorrect proof of work (code 16)
90 2017-12-29 16:44:41 0|ossifrage|[I have 102 of those in my logs]
91 2017-12-29 16:46:24 0|ossifrage|Huh, the most recent one came from a node claiming to be 0.15.1
92 2017-12-29 16:47:01 0|aj|that's a bcash block isn't it?
93 2017-12-29 16:47:21 0|provoostenator|Yes: https://blockdozer.com/insight/block/000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b
94 2017-12-29 16:48:32 0|provoostenator|That's an old one, but shouldn't it complain about the very first one, given the EDA?
95 2017-12-29 16:50:08 0|sipa|ossifrage: it's an invalid block, and your client is correctly rejecting it
96 2017-12-29 16:50:34 0|ossifrage|sipa, yeah, but it was forwarded to my by a node that also should have rejected it?
97 2017-12-29 16:50:36 0|provoostenator|Their first block was 478558, your log is about 478577. Not sure when their first EDA kicked in.
98 2017-12-29 16:51:32 0|sipa|ossifrage: it could be a bcash node you're connected to
99 2017-12-29 16:51:37 0|sipa|or a retarded node
100 2017-12-29 16:51:50 0|provoostenator|Nvm, their replay protection makes even the first block invalid. So why did your node not ban that other node when it got 478558?
101 2017-12-29 16:55:44 0|ossifrage|Most of the bad blocks are coming from /SuperBitcoin:0.16.0.2/
102 2017-12-29 16:56:26 0|ossifrage|and /SpuerBitcoin:0.16.0.2/
103 2017-12-29 16:57:41 0|provoostenator|Probably these guys: https://github.com/superbitcoin/SuperBitcoin/commits/master I wonder if they're doing anything worthy of #bitcoin-airdrop-code-shenanigans
104 2017-12-29 16:58:23 0|ossifrage|I'm more curious why nodes claiming to be Satoshi based are forwarding bad blocks
105 2017-12-29 17:25:18 0|Slackus|help I cannot speak on #bitcoin
106 2017-12-29 17:25:20 0|Slackus|i am +q
107 2017-12-29 17:25:35 0|Slackus|I was just looking at exploit http://saleemrashid.com/2017/08/17/extracting-trezor-secrets-sram/#writing-an-exploit
108 2017-12-29 17:25:40 0|Slackus|oh sorry nvm
109 2017-12-29 17:34:16 0|provoostenator|They currently use the same sighash_fork_id as bcash.
110 2017-12-29 18:10:47 0|provoostenator|What's the fastest EC2 configuration to an IBD? I was thinking about memory optimized r3.4xlarge with 320 GB SSD. sipa?
111 2017-12-29 18:11:30 0|provoostenator|(16 CPU's)
112 2017-12-29 18:15:47 0|jb55|I really need to set up distcc or something for testing prs :S my poor laptop is struggling
113 2017-12-29 18:17:02 0|provoostenator|jb55: ccache helps too
114 2017-12-29 18:18:15 0|jb55|provoostenator: oh nice I've never used that before, will give it a spin
115 2017-12-29 19:40:57 0|luke-jr|FYI, apparently ME neutering leaves the CPU with microcode-level vulnerabilities that compromise Qubes-like setups
116 2017-12-29 20:22:08 0|phantomcircuit|luke-jr, ?
117 2017-12-29 20:33:10 0|luke-jr|phantomcircuit: rumour from 24c3
118 2017-12-29 20:36:59 0|luke-jr|34c3*
119 2017-12-29 20:54:49 0|provoostenator|It would be nice to be able to use sendrawtransaction during IBD, i.e. with some sort "don't check, just relay it"
120 2017-12-29 20:56:25 0|provoostenator|(I'm checking some replay protection behavior in airdrop coins, and rather not have to wait for those things to fully sync)
121 2017-12-29 21:08:42 0|bitcoin-git|[13bitcoin] 15puchu opened pull request #12051: add missing debian contrib files to tarball (06master...06master) 02 https://github.com/bitcoin/bitcoin/pull/12051
122 2017-12-29 21:31:12 0|sipa|provoostenator: use submittx
123 2017-12-29 21:58:07 0|tril|hey
124 2017-12-29 22:21:54 0|bitcoin-git|[13bitcoin] 15cuckoocoin opened pull request #12052: 0.12 (060.11...060.12) 02 https://github.com/bitcoin/bitcoin/pull/12052
125 2017-12-29 22:22:50 0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #12052: 0.12 (060.11...060.12) 02 https://github.com/bitcoin/bitcoin/pull/12052
126 2017-12-29 23:15:26 0|provoostenator|sipa: thanks