1 2017-11-19 01:22:00 <satwo> Is every tx in the mempool a descendant and ancestor of itself? I'm trying to get a handle on the data returned from GetRawMempool (Verbose) when using JSON RCP
  2 2017-11-19 06:49:03 <melik> hmmm, looks like ifconfig and /etc/rc.local were deprecated in Debian 9 -- re: https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-setup-gitian-debian.md
  3 2017-11-19 07:01:52 <melik> hmmm something weird with lxc: init.lxc: failed to mount /dev/shm : No such file or directory
  4 2017-11-19 07:06:31 <melik> https://github.com/devrandom/gitian-builder/pull/150
  5 2017-11-19 07:07:07 <melik> ill push commits to replace any instances of ifconfig with brctl/ip
  6 2017-11-19 12:39:35 <txter> The transaction hash, is that a hash of the whole raw transaction?
  7 2017-11-19 12:52:02 <txter> That is, is this correct?
  8 2017-11-19 12:52:05 <txter> 1. The transaction is sent raw to other peers (serialized in hex format).
  9 2017-11-19 12:52:11 <txter> 2. In that raw transaction there is a hashed 'txid' of the previous output raw transaction proving the ownership of the coins.
 10 2017-11-19 14:19:37 <luke-jr> melik: Debian went off the systemd deep end; suggest switching to Devuan
 11 2017-11-19 14:19:47 <luke-jr> txter: this is not a channel for altcoin dev supportp
 12 2017-11-19 14:30:23 <jaromil> luke-jr: <3 we have also the right version of berkleydb in the pipeline for Devuan ASCII
 13 2017-11-19 14:31:34 <jaromil> melik: if you need help with porting the gitian build to Devuan, there are developers here who can help, me included.
 14 2017-11-19 14:33:23 <txter> luke-jr: I'm asking in regards to Bitcoin core
 15 2017-11-19 14:49:08 <luke-jr> txter: you're sneakily not disclosing you're trying to make an altcoin
 16 2017-11-19 15:09:24 <txter> luke-jr: I'm on other alt-coin channels, but I am reading through Mastering Bitcoin right now. I've just finished reading chapter 6 on transactions. One thing that is not covered is how transactions are persisted.
 17 2017-11-19 15:09:46 <txter> My question has nothing to do with alt coins, it's about how Bitcoin persists transactions in leveldb
 18 2017-11-19 15:09:54 <txter> :)
 19 2017-11-19 16:27:33 <Michail1> If you setup a new full node, will setting it to prune (550) mean it will prune as the data comes in, or does it have to download entire chain and then finally prune?
 20 2017-11-19 16:41:22 <txter> This is said about prune in Mastering Bitcoin: 'Prune: Reduce the disk space requirements to this many megabytes, by deleting old blocks. Use this on a resource-constrained node that can't fit the full blockchain'
 21 2017-11-19 16:41:43 <txter> So I'm guessing you will not have to get all the blockchain first, as it is for nodes that can not fit the whole thing
 22 2017-11-19 16:45:59 <Michail1> That doesn't answer the question.
 23 2017-11-19 16:46:28 <arubi> it prunes as it goes
 24 2017-11-19 16:46:49 <Michail1> I understand what it does, but is it afterthefact (Meaning, must download the 150GB first then prune, or it will prune as the data is coming in).
 25 2017-11-19 16:46:55 <Michail1> arubi - thankis.
 26 2017-11-19 16:46:59 <arubi> yw
 27 2017-11-19 16:48:36 <txter> Why does prune need you to first download 150gb of data when it's there so nodes that specifically can't store 150gb can continue working?
 28 2017-11-19 16:49:13 <Michail1> txter - Just a note though.... Yes, you will have to download the entire chain.  There isn't the ability yet (that I know of) in which you can start at a certain point.   Probably an update in the future though when someone can simply start from Jan 1st, 2015 as a start point from a download of a verified chainstate/uxto, etc.   It will happen.
 29 2017-11-19 16:49:14 <arubi> you download so you can verify it
 30 2017-11-19 16:51:20 <spinza> you download, verify and delete keeping only the last X GB as specified in pruning options
 31 2017-11-19 16:51:27 <txter> what if you set prune to 150mb, and as soon as you hit 150mb of chain data it stars discarding earlier data. So when you finally get to this point in time you have 150mb of chain data and you know it's valid since you technically downloaded the whole chain but only keypt around 150mb
 32 2017-11-19 16:51:59 <txter> yeah, basically what spinza said
 33 2017-11-19 16:52:36 <arubi> that's how it works, only the minimum is 550mb
 34 2017-11-19 16:52:54 <spinza> i thouhght the minimum was like 5GB
 35 2017-11-19 16:53:26 <txter> Makes sense to have a minimum
 36 2017-11-19 16:53:27 <arubi> for pruning it's 550mb, but aside from the chain there are other databases that you can't prune so it ends up taking a few gbs
 37 2017-11-19 16:55:16 <txter> Which databases are that?
 38 2017-11-19 16:56:58 <arubi> utxo database, wallet..
 39 2017-11-19 16:57:04 <txter> I'm reading through Mastering Bitcoin and there is one thing I'm trying to figure out that's not in the book, and that is how data is persisted. In my mind after reading the chapter on transactions I thought the key store db stored: key: txid -> value: raw transactoin in HEX
 40 2017-11-19 16:57:24 <txter> but then where would blocks fit in
 41 2017-11-19 16:58:06 <arubi> well we just talked about how blocks can be pruned :)
 42 2017-11-19 16:58:42 <spinza> what data?
 43 2017-11-19 17:01:13 <txter> Well. If I send a transaction to another node, it's going to be put into the mempool (if I remember correctly). There I'm guessing the key value store is (key: txid, value: raw transaction). Is that the leveldb database?
 44 2017-11-19 17:01:33 <txter> then there must be another database for the actual chain. Is that a relational one?
 45 2017-11-19 17:02:01 <txter> I'm just asking these questions cause I havent finished reading the book (currently on chapter 6), but I'm going to look at the bitcoin code after I finish the book
 46 2017-11-19 17:03:04 <arubi> I think it's better to look at code now
 47 2017-11-19 17:04:37 <txter> Yeah I might take a look after this chapter. Will probably fill in the blanks
 48 2017-11-19 19:17:47 <firelegend> Hi all, I created a new bitcoin wallet, unencrypted, I generated an address and immediately tried dump the private key, however I am met with error code - 5
 49 2017-11-19 19:17:52 <firelegend> Any reason for this?
 50 2017-11-19 19:20:18 <arubi> is that reproducible?
 51 2017-11-19 19:21:19 <firelegend> Reproducible how?
 52 2017-11-19 19:21:32 <firelegend> I tried many times, generated a new address, same thing
 53 2017-11-19 19:21:48 <firelegend> I use the request payment box to get a new address
 54 2017-11-19 19:22:02 <firelegend> And then the console for dumpprivkey
 55 2017-11-19 19:22:05 <arubi> what's the exact error say?
 56 2017-11-19 19:22:20 <firelegend> Invalid bitcoin address error code - 5
 57 2017-11-19 19:23:18 <firelegend> Perhaps these addresses are from compressed Public keys?
 58 2017-11-19 19:23:28 <arubi> of course they are
 59 2017-11-19 19:23:33 <firelegend> Ah
 60 2017-11-19 19:23:45 <firelegend> So then dumpprivkey requires uncompressed?
 61 2017-11-19 19:23:50 <arubi> no?
 62 2017-11-19 19:23:59 <firelegend> Then not sure why it doesn't work
 63 2017-11-19 19:24:04 <arubi> do 'validateaddress <address>'
 64 2017-11-19 19:24:13 <arubi> see if errors on invalid address
 65 2017-11-19 19:24:47 <firelegend> Says false
 66 2017-11-19 19:24:59 <firelegend> As in isvalid is false
 67 2017-11-19 19:25:07 <arubi> I'm not sure what you're pasting in there, but it's not addresses
 68 2017-11-19 19:25:22 <firelegend> No way, it ia
 69 2017-11-19 19:25:24 <firelegend> Is
 70 2017-11-19 19:25:27 <arubi> maybe you have 'bitcoin-cli' in your path and it's a symlink to testnet or an altcoin
 71 2017-11-19 19:25:36 <firelegend> Hmm
 72 2017-11-19 19:25:42 <firelegend> That's plausible wait
 73 2017-11-19 19:28:11 <firelegend> Does not seem to be in my path
 74 2017-11-19 19:28:24 <arubi> alias?
 75 2017-11-19 19:28:27 <firelegend> Perhaps it's because I am using a different datadir?
 76 2017-11-19 19:28:39 <arubi> well what's in ~/.bitcoin.conf ?
 77 2017-11-19 19:28:55 <arubi> if it's not an alias, not a wrapper, not a symlink, then it's reading that ^
 78 2017-11-19 19:29:14 <arubi> er, ~/.bitcoin/bitcoin.conf
 79 2017-11-19 19:29:35 <firelegend> But I've set a datadir on the command line parameters
 80 2017-11-19 19:29:51 <firelegend> Also I'm on Windows
 81 2017-11-19 19:30:37 <arubi> oh, try `bitcoin-cli getblockchaininfo`, what does it say for bestblockhash ?
 82 2017-11-19 19:32:38 <firelegend> Alright just a sec
 83 2017-11-19 19:35:13 <firelegend> https://pastebin.com/uw4Q4wxD
 84 2017-11-19 19:36:47 <arubi> can you post a throwaway example of an address that you passed to validateaddress and returned isvalid : false ?
 85 2017-11-19 19:38:02 <arubi> very weird.  I really don't understand where armory's p2sh-p2pk, or whatever it might be relates to all of this
 86 2017-11-19 19:41:48 <firelegend> I run bitcoin core qt
 87 2017-11-19 19:41:53 <firelegend> Version 0.14.2
 88 2017-11-19 19:41:58 <arubi> oh disregard the armory comment, I got confused with the guy in #bitcoin
 89 2017-11-19 19:42:03 <arubi> yea
 90 2017-11-19 19:43:02 <arubi> firelegend, an example of what goes into validateaddress and fails will be helpful.  are you running other daemons at all?
 91 2017-11-19 19:43:13 <arubi> if they're on the same rpc port, it might interfere
 92 2017-11-19 19:45:47 <firelegend> Not that I'm aware of, no
 93 2017-11-19 19:50:40 <firelegend> Is it possible bitcoin core at doesn't pass the datadir parameter to cli?
 94 2017-11-19 19:55:25 <firelegend> Hmm weird
 95 2017-11-19 19:55:39 <firelegend> .it seems to work now after restarting it twice
 96 2017-11-19 20:01:46 <firelegend> Seems like after generating a new address it takes a while for it to appear with dumpprivkey
 97 2017-11-19 20:04:52 <arubi> I haven't tried generate && dump one after another, but it makes sense that accessing these things can take more than a microsecond
 98 2017-11-19 20:06:51 <firelegend> A few minutes
 99 2017-11-19 20:08:01 <firelegend> I'm doing this by hand
100 2017-11-19 20:08:12 <firelegend> So Def a few seconds in between
101 2017-11-19 20:10:37 <arubi> well good to know.  I mostly stress testing core using regtest, and the datadir is in /dev/shm, so I don't experience a lot of these quirks
102 2017-11-19 20:10:55 <arubi> I'm*
103 2017-11-19 20:11:00 <firelegend> Uhm it's not a test
104 2017-11-19 20:11:07 <arubi> yea I figure
105 2017-11-19 20:11:23 <arubi> that's why I'm assuming I never encountered it
106 2017-11-19 20:11:27 <firelegend> I am simply trying to generate an address, make sure I have the key and send some BTC there
107 2017-11-19 20:11:39 <arubi> well, if you generated it, you do have the key
108 2017-11-19 20:11:52 <arubi> it's enough to run validateaddress
109 2017-11-19 20:11:58 <arubi> it'll say "ismine : true"
110 2017-11-19 20:12:07 <firelegend> Paranoia, plan to use cash and sell it, while making sure my BTC stay safe
111 2017-11-19 20:12:08 <arubi> even better, "solvable : true"
112 2017-11-19 20:12:32 <arubi> paranoia should divert you from dumping private keys
113 2017-11-19 20:13:57 <firelegend> I'm afraid that while this bug occurs, or quirk, neither dumpprivkey work nor validateaddress
114 2017-11-19 20:14:06 <arubi> hm I guess it doesn't say about solvable, where did I see it..
115 2017-11-19 20:14:25 <firelegend> Because they return isvalid:false
116 2017-11-19 20:14:41 <arubi> well, you still haven't posted an example of what you're passing to it
117 2017-11-19 20:14:55 <firelegend> Just the bit on address
118 2017-11-19 20:15:11 <arubi> can you generate a throwaway address and paste it?
119 2017-11-19 20:15:59 <firelegend> 12fG2krj6iEr1GEzGdScERM5Ec9PYXtvX2
120 2017-11-19 20:16:20 <arubi> whaddaya know, it's invalid
121 2017-11-19 20:16:30 <arubi> maybe you have malware :)
122 2017-11-19 20:17:18 <arubi> the first bytes are "1234", comon
123 2017-11-19 20:18:11 <firelegend> Sorry?
124 2017-11-19 20:20:29 <arubi> firelegend, if you don't know what I'm talking about, I suggest you completely reinstall your operating system
125 2017-11-19 20:21:12 <firelegend> Pretty sure I am clean
126 2017-11-19 20:22:04 <arubi> wait
127 2017-11-19 20:22:45 <arubi> yea, my fault.  I was bit by my own symlinks..
128 2017-11-19 20:23:35 <arubi> man that's some coincidence..  I thought you were trolling, the first two bytes of the hash160 is 12, 34.. it seemed so artificial
129 2017-11-19 20:24:11 <arubi> firelegend, the address is valid.  I'm not sure what's been passed through to bitcoin-cli.  can you pase the full command?
130 2017-11-19 20:24:15 <firelegend> Well I am not
131 2017-11-19 20:24:55 <arubi> yea, there's 1 to 2^16 chance of it being an hones 12, 34 address, and it is.  please don't blame me :)
132 2017-11-19 20:25:04 <arubi> s/hones/honest/
133 2017-11-19 20:26:16 <firelegend> Seems to work once more
134 2017-11-19 20:27:13 <arubi> you said you're running 0.14.2, latest is 0.15.1 . maybe try it out and open an issue on github if it doesn't solve the problem
135 2017-11-19 20:27:47 <firelegend> Figured it out
136 2017-11-19 20:27:54 <firelegend> Quotes
137 2017-11-19 20:28:01 <firelegend> Must use quotes
138 2017-11-19 20:30:23 <arubi> oh, that's unexpected..
139 2017-11-19 20:32:17 <firelegend> Still paying 16 dollars as fees is a bit much
140 2017-11-19 20:32:47 <arubi> pay less if you want
141 2017-11-19 20:32:52 <firelegend> I did
142 2017-11-19 20:33:00 <firelegend> 150k Satoshi per kb
143 2017-11-19 20:33:09 <firelegend> Instead of 0.004
144 2017-11-19 20:33:43 <arubi> I usually go with 10-20 sat/byte
145 2017-11-19 20:34:19 <firelegend> And it works?
146 2017-11-19 20:34:28 <arubi> I aim for weekends
147 2017-11-19 20:34:48 <firelegend> Well, I'm about to sell bch all of it so
148 2017-11-19 20:35:04 <firelegend> Maybe I will make it all back
149 2017-11-19 20:35:37 <dviola> arubi: how do you know the size of your tx before sending?
150 2017-11-19 20:35:49 <arubi> you put dummy signatures in it
151 2017-11-19 20:36:33 <dviola> not sure how
152 2017-11-19 20:39:32 <arubi> oh sorry, you mean with the client?
153 2017-11-19 20:40:22 <arubi> I'm not sure if there's a way to tell easily
154 2017-11-19 20:40:36 <arubi> /dinner time
155 2017-11-19 20:41:53 <jb55> put together a script that pulls fee estimtes from your full node: https://github.com/jb55/bitcoin-fees
156 2017-11-19 20:43:35 <dviola> yes, with core
157 2017-11-19 20:43:57 <dviola> I just want to be able to calculate the right fee for my tx
158 2017-11-19 20:44:16 <dviola> I'd like to know how most people do it
159 2017-11-19 20:44:31 <dviola> I've been using the fee estimator in core
160 2017-11-19 20:44:51 <dviola> which is ok, but I wonder if there is a better way
161 2017-11-19 20:45:01 <eck> the median txn is 121 bytes
162 2017-11-19 20:45:23 <eck> err
163 2017-11-19 20:45:25 <eck> 226 bytes
164 2017-11-19 20:45:27 <jb55> ^
165 2017-11-19 20:45:36 <eck> i would start with that unless you have a reason to suspect it would be different
166 2017-11-19 20:45:38 <jb55> that's the default I use for my fee estimation script
167 2017-11-19 20:45:53 <eck> i believe 226 bytes is for 1 input, 2 outputs p2pkh
168 2017-11-19 20:46:56 <firelegend> Mean or median?
169 2017-11-19 20:47:37 <eck> median
170 2017-11-19 20:48:14 <eck> the mean would be larger, i don't know if you can create a transaction smaller than that
171 2017-11-19 20:49:03 <dviola> ok so the more inputs the higher the bytes
172 2017-11-19 20:49:05 <dviola> ?
173 2017-11-19 20:49:16 <jb55> hmm to send 100kb tx in 1-2 blocks would cost $1322 right now :O
174 2017-11-19 20:51:16 <eck> that would be a big tx
175 2017-11-19 20:51:31 <eck> dviola: yes
176 2017-11-19 20:51:48 <dviola> eck: I see, thanks
177 2017-11-19 20:52:15 <dviola> can't believe I overpaid like $20 before
178 2017-11-19 20:54:53 <dviola> well, that tx had 10+ inputs so it's not too bad I guess
179 2017-11-19 21:34:06 <melik> luke-jr, jaromil Ah, I see!
180 2017-11-19 21:35:45 <melik> thanks guys; first time hearing about devuan, i see that it still use sysvinit
181 2017-11-19 21:36:02 <melik> i'll set up a new VM then, thank you :)