1 2017-12-08 02:27:13 0|binarycat|.
2 2017-12-08 02:34:55 0|binarycat|I have a Bitcoin Core wallet.dat which I've had forever. Today, I made a fresh wallet.dat, created a receive address and went back to the original wallet.dat and transferred almost all of the Bitcoins to the new one, for the sake of being able to safely "claim" Bitcoin Gold/Cash/whatever without risking that the software just steals my Bitcoin instead of giving me other coins (and also to put the new wallet.dat in offline storage.... But the
3 2017-12-08 02:34:55 0|binarycat|problem I now face is that the old (now almost empty) wallet.dat still contains my full transaction history with the internal labels I've entered. I don't want that info to "get out", obviously. How do I work around this? What's the solution?
4 2017-12-08 02:46:31 0|phantomcircuit|binarycat, dump the private keys and load them into a new wallet
5 2017-12-08 02:46:35 0|sipa|#bitcoin
6 2017-12-08 02:46:39 0|phantomcircuit|oh right
7 2017-12-08 02:52:13 0|binarycat|Can't chat in that stupid room.
8 2017-12-08 02:52:32 0|binarycat|Some idiot-head must have abused this VPN in there.
9 2017-12-08 02:52:45 0|binarycat|phantomcircuit: "Dump the private keys" how?
10 2017-12-08 03:41:12 0|valval|hi, anyone able to assists me in setting up of bitcoin core for modification?
11 2017-12-08 03:41:44 0|cluelessperson|binarycat: I'm confused, if you simply don't want the labels to "get out", just delete them
12 2017-12-08 03:41:50 0|cluelessperson|or delete the file and keep the privat ekeys.
13 2017-12-08 03:42:01 0|valval|im trying to see if i can make any form of optimization and i'd like to possibly do this using an IDE. Netbeans doesnt seem to work well in terms of building because its constantly hanging due to lack of memory
14 2017-12-08 03:44:22 0|sipa|valval: i think most people use simple text editors to develop
15 2017-12-08 03:45:01 0|valval|is there any form of source code walkthrough?
16 2017-12-08 03:45:14 0|valval|like where i can start off to understand the structure of the codes
17 2017-12-08 03:45:31 0|valval|http://embedded-design-vic.blogspot.sg/2017/07/bitcoin-core-tutorial-and-source-code.html is this a good source?
18 2017-12-08 03:56:19 0|sipa|that looks like a very small random dubset of function
19 2017-12-08 03:57:02 0|sipa|i don't think there is much of a guide, and certainly no up to date one
20 2017-12-08 04:47:51 0|spence|valval: do you know C++ pretty well? I've modified the Core code before, but as a C++ noob it was pretty difficult.
21 2017-12-08 05:05:59 0|binarycat|cluelessperson: "Just" delete them? Manually, one by one?
22 2017-12-08 05:06:17 0|binarycat|cluelessperson: "or delete the file and keep the privat ekeys" <-- I really don't get what you mean by this.
23 2017-12-08 05:09:06 0|sipa|binarycat: not here
24 2017-12-08 05:10:26 0|binarycat|sipa: What?
25 2017-12-08 05:11:34 0|sipa|binarycat: this is a development channel, not support
26 2017-12-08 05:11:51 0|binarycat|It's an idle channel, just like every other place.
27 2017-12-08 05:11:58 0|binarycat|And you ALWAYS fucking tell me it's off-topic. Fuck off.
28 2017-12-08 05:12:40 0|sipa|you're welcome
29 2017-12-08 05:45:21 0|achow101|lol
30 2017-12-08 06:25:26 0|esotericnonsense|binarycat | Some idiot-head must have abused this VPN in there.
31 2017-12-08 06:25:47 0|esotericnonsense|totally not that he's likely banned for being a royal arsehole. :>
32 2017-12-08 12:07:30 0|bitcoin-git|[13bitcoin] 15ryanofsky opened pull request #11851: scripted-diff: Rename wallet database classes (06master...06pr/wren) 02https://github.com/bitcoin/bitcoin/pull/11851
33 2017-12-08 15:31:48 0|GAit|any reason not to disable building the samples for libevent make's depends? helps with building on NDK and as far as I understand they are not needed/used, seems a waste to build them each time
34 2017-12-08 16:26:25 0|adiabat|regarding the weird fee estimates mentioned yesterday, I have similar behavior on mainnet with bitcoin-qt right now
35 2017-12-08 16:27:25 0|adiabat|6 block fee is 128740 sat/KB, 12 blocks in 111776, and 24 block is back up to 128740
36 2017-12-08 16:27:47 0|adiabat|and it stays at 128 sat/B for all the longer times
37 2017-12-08 16:28:05 0|adiabat|this is on 0.15.0 though
38 2017-12-08 16:30:45 0|adiabat|so anyway doesn't seem to be testnet only, at least in 0.15.0, don't think it's changed since though
39 2017-12-08 17:00:44 0|BlueMatt|adiabat: can you a) shutdown and copy over your fee_estimates.dat or at least b) with debug=feeest (which you can turn on without restarting from logging rpc) can you do the fee estimate rpc calls again and get the FeeEst debug.log entries?
40 2017-12-08 17:01:10 0|BlueMatt|adiabat: and then can you post those things at #11800 ?
41 2017-12-08 17:01:12 0|gribble|https://github.com/bitcoin/bitcoin/issues/11800 | Bitcoin is returning higher fees for 36 block window than 2 block window (on testnet) ÷ Issue #11800 ÷ bitcoin/bitcoin ÷ GitHub
42 2017-12-08 17:01:57 0|adiabat|BlueMatt: a couple blocks later, the estimates now make sense
43 2017-12-08 17:02:09 0|adiabat|it was right after syncing up
44 2017-12-08 17:02:35 0|adiabat|but can get the current fee_estimates.dat file
45 2017-12-08 17:03:36 0|BlueMatt|ah, ok, shame
46 2017-12-08 17:04:10 0|adiabat|have the fee_estimates.dat and will save a copy but when I shut it down it was ok and higher, something like 500 sat/B
47 2017-12-08 17:04:52 0|adiabat|the weird dip only lasted for a block or two. Wouldn't have noticed, but was looking for it since someone mentioned yesterday
48 2017-12-08 17:05:10 0|BlueMatt|yea, ok, well thanks for the note anyway
49 2017-12-08 17:05:39 0|adiabat|ok sure, will try again and grab the .dat if I see it
50 2017-12-08 17:57:00 0|bitcoin-git|[13bitcoin] 15ryanofsky opened pull request #11854: Split up key and script metadata for better type safety (06master...06pr/scriptmet) 02https://github.com/bitcoin/bitcoin/pull/11854
51 2017-12-08 19:27:07 0|morcos|adiabat: had you recently restarted that node?
52 2017-12-08 19:28:53 0|morcos|if you had debug on, could you also grep for lines that contain FeeEst around that time
53 2017-12-08 19:45:00 0|adiabat|morcos: yes, had started the node after ~2 days offline, and it had just finished sync when I checked the fees
54 2017-12-08 19:45:36 0|adiabat|Didn't have debug, just regular logs. I do have the fee_estimates.dat though from when I shutdown
55 2017-12-08 19:50:56 0|gyanp534|heey
56 2017-12-08 22:05:30 0|bitcoin-git|[13bitcoin] 15sipa closed pull request #10149: gentlejack (06master...060.12.1-bitcore) 02https://github.com/bitcoin/bitcoin/pull/10149
57 2017-12-08 23:08:06 0|cluelessperson|Question, does a prunine Bitcoin Core node keep a certain number of blocks?
58 2017-12-08 23:08:44 0|sipa|yes
59 2017-12-08 23:09:05 0|sipa|the minimum pruning target setting is 550 MB
60 2017-12-08 23:09:23 0|cluelessperson|ah, so easily a good number of blocks back
61 2017-12-08 23:09:26 0|cluelessperson|that's good enough for me
62 2017-12-08 23:09:44 0|sipa|a pruned node can't reorg past its pruning depth
63 2017-12-08 23:14:47 0|jamesob|is the indentation in this logging output meaningful in some way? I'd assumed it was, but parent times obv aren't the sum of their children https://gist.github.com/jamesob/a203bb0e50737bbfdad0d8847bf94635
64 2017-12-08 23:18:01 0|sipa|jamesob: it's meaningful when read in backward order
65 2017-12-08 23:18:20 0|sipa|so Connect is a subnode of Verify
66 2017-12-08 23:18:40 0|sipa|and Sanity, Fork, Verify, Index, Callbacks are subnodes of Connect total
67 2017-12-08 23:19:06 0|jamesob|sipa: ahh gotcha
68 2017-12-08 23:23:29 0|sipa|would be neat to buffer them up and print them out in backwards order to make it more readable
69 2017-12-08 23:25:19 0|jamesob|yup; will submit a patch
70 2017-12-08 23:27:21 0|cluelessperson|sipa: how can I verify the fee of transactions incoming against the UTXO set?
71 2017-12-08 23:28:35 0|sipa|cluelessperson: i assume your question is: how do i verify the fee of incoming transactions is not negative?
72 2017-12-08 23:29:36 0|cluelessperson|yes?
73 2017-12-08 23:31:18 0|sipa|by looking up the UTXOs being spent, summing their value, and comparing that with the value of all outputs of the transaction
74 2017-12-08 23:32:46 0|cluelessperson|sipa: is there a method I can use to look them up myself?
75 2017-12-08 23:33:01 0|cluelessperson|sipa: say I'm iterating over all the txes in a new block?
76 2017-12-08 23:33:57 0|sipa|cluelessperson: CCoinsView::AccessCoin
77 2017-12-08 23:34:51 0|cluelessperson|sipa: over RPC?
78 2017-12-08 23:35:15 0|sipa|cluelessperson: no
79 2017-12-08 23:35:23 0|sipa|there is a gettxout RPC though
80 2017-12-08 23:41:03 0|sipa|cluelessperson: but that won't work for the transaction in a new block, as as soon as the node learns about that blocks, those UTXOs will be gone
81 2017-12-08 23:46:19 0|cluelessperson|sipa: basically, I'm trying to get fee information about every transaction in the mempool and in each new block
82 2017-12-08 23:54:12 0|Sentineo|cluelessperson: http://node.ispol.sk/#!/mempool
83 2017-12-08 23:54:49 0|Sentineo|cluelessperson: look in the sources for server.js (rawtx event) for how I do it ...
84 2017-12-08 23:55:10 0|Sentineo|not sure though if you want something like that ..