1 2016-11-24T00:10:18  <rusty> sipa: trying to find where the relayfeerate changes, other than manual configuration...
  2 2016-11-24T00:10:33  <sipa> rusty: it doesn't
  3 2016-11-24T00:11:29  <rusty> sipa: ah, right.  Indeed, I agree that nodes should be scaling their min output level by feerate.  But as long as they propagate that's a v1.1 problem.
  4 2016-11-24T00:12:35  <sipa> rusty: maybe for DoS reasons it should be changed at some point, but even then i can't imagine that happens in core without making sure it's certain to be consistently higher than actual feerates
  5 2016-11-24T00:14:43  <bitcoin-git> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0de7fd36de57...407d9232ef5c
  6 2016-11-24T00:14:44  <bitcoin-git> bitcoin/master ca8549d Gregory Maxwell: Always drop the least preferred HB peer when adding a new one....
  7 2016-11-24T00:14:44  <bitcoin-git> bitcoin/master 407d923 Pieter Wuille: Merge #9199: Always drop the least preferred HB peer when adding a new one....
  8 2016-11-24T00:14:56  <bitcoin-git> [bitcoin] sipa closed pull request #9199: Always drop the least preferred HB peer when adding a new one. (master...remove_high_bandwidth_zombies) https://github.com/bitcoin/bitcoin/pull/9199
  9 2016-11-24T00:15:02  <rusty> gmaxwell: it's your fault I now have 'while sleep 10; do bitcoin-cli getblocktemplate | awk '/"fee"/ { FEES += $2 } /"height"/ { HEIGHT = $2 } END { print HEIGHT,FEES }'; done' running in a terminal here, BTW.
 10 2016-11-24T00:15:53  <sipa> rusty: i have a patch that builds a max-size block, removes the included transactions from the mempool, then builds another max-size block, etc
 11 2016-11-24T00:16:06  <sipa> rusty: and then store the min feerate of each of those built blocks
 12 2016-11-24T00:16:19  <sipa> last entry:
 13 2016-11-24T00:16:19  <sipa> 1479946521 0.00098826 0.00081403 0.00067987 0.00065261 0.00065000 0.00062687 0.00061134 0.00060031 0.00058407 0.00055922
 14 2016-11-24T00:17:05  <sipa> which means that it would take at least 5 blocks to get the feerate to get accepted down to 65sat/byte
 15 2016-11-24T00:17:25  <rusty> sipa: nice!
 16 2016-11-24T00:19:06  *** Alina-malina has joined #bitcoin-core-dev
 17 2016-11-24T00:20:23  <rusty> So it stops when it can't make a full block?
 18 2016-11-24T00:20:34  <sipa> no, it stops at 10
 19 2016-11-24T00:20:54  <sipa> i can increase it, and probably should right now
 20 2016-11-24T00:27:40  <bitcoin-git> [bitcoin] sipa pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/407d9232ef5c...93566e0c37c5
 21 2016-11-24T00:27:41  <bitcoin-git> bitcoin/master ec4525c Matt Corallo: Move orphan processing to ActivateBestChain...
 22 2016-11-24T00:27:42  <bitcoin-git> bitcoin/master 97e2802 Matt Corallo: Erase orphans per-transaction instead of per-block
 23 2016-11-24T00:27:42  <bitcoin-git> bitcoin/master d2b88f9 Matt Corallo: Move orphan-conflict removal from main logic into a callback...
 24 2016-11-24T00:32:02  *** laurentmt has quit IRC
 25 2016-11-24T00:40:06  *** Chris_Stewart_5 has quit IRC
 26 2016-11-24T00:45:44  *** abhi_ has joined #bitcoin-core-dev
 27 2016-11-24T00:47:07  *** fubu has quit IRC
 28 2016-11-24T00:47:48  *** fubu has joined #bitcoin-core-dev
 29 2016-11-24T01:02:17  *** justanotheruser has quit IRC
 30 2016-11-24T01:15:03  <fubu> ;)
 31 2016-11-24T01:25:56  *** jtimon has quit IRC
 32 2016-11-24T01:27:18  *** Alina-malina has quit IRC
 33 2016-11-24T01:29:37  *** Alina-malina has joined #bitcoin-core-dev
 34 2016-11-24T01:48:15  *** jannes has quit IRC
 35 2016-11-24T01:49:13  *** fubu has quit IRC
 36 2016-11-24T01:49:48  *** fubu has joined #bitcoin-core-dev
 37 2016-11-24T02:02:39  *** Ylbam has quit IRC
 38 2016-11-24T02:03:36  *** fubu has quit IRC
 39 2016-11-24T03:45:07  *** crudel has quit IRC
 40 2016-11-24T03:51:55  * luke-jr wonders why the splashscreen has a copyright line, but nothing indicative of the license terms
 41 2016-11-24T03:52:38  <luke-jr> any objections to adding another line "Available without royalties under a free software license" or something?
 42 2016-11-24T03:58:00  <bitcoin-git> [bitcoin] luke-jr reopened pull request #8889: Qt/ModalOverlay: Use theme tooltip colours (master...overlay_theme) https://github.com/bitcoin/bitcoin/pull/8889
 43 2016-11-24T05:03:36  *** Giszmo has quit IRC
 44 2016-11-24T05:04:43  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 45 2016-11-24T05:15:32  *** Alina-malina has quit IRC
 46 2016-11-24T05:15:33  *** Alina-malina has joined #bitcoin-core-dev
 47 2016-11-24T05:19:27  *** fanquake has joined #bitcoin-core-dev
 48 2016-11-24T05:29:03  *** justanotheruser has joined #bitcoin-core-dev
 49 2016-11-24T05:32:46  *** justanotheruser has quit IRC
 50 2016-11-24T05:33:03  *** justanotheruser has joined #bitcoin-core-dev
 51 2016-11-24T05:35:06  *** Chris_Stewart_5 has quit IRC
 52 2016-11-24T06:26:40  *** Ylbam has joined #bitcoin-core-dev
 53 2016-11-24T06:28:51  *** kadoban has quit IRC
 54 2016-11-24T06:30:31  <luke-jr> http://netpatterns.blogspot.de/2016/01/the-rising-sophistication-of-network.html
 55 2016-11-24T06:35:36  *** rusty has quit IRC
 56 2016-11-24T07:12:13  *** aalex__ has joined #bitcoin-core-dev
 57 2016-11-24T07:18:54  *** aalex__ has quit IRC
 58 2016-11-24T07:26:58  *** aalex__ has joined #bitcoin-core-dev
 59 2016-11-24T07:32:15  *** laurentmt has joined #bitcoin-core-dev
 60 2016-11-24T07:33:03  *** aalex__ has quit IRC
 61 2016-11-24T07:41:59  *** aalex__ has joined #bitcoin-core-dev
 62 2016-11-24T07:42:52  *** laurentmt has quit IRC
 63 2016-11-24T07:47:58  *** aalex__ has quit IRC
 64 2016-11-24T07:57:00  *** aalex__ has joined #bitcoin-core-dev
 65 2016-11-24T08:18:17  *** JackH has joined #bitcoin-core-dev
 66 2016-11-24T08:30:53  *** aalex__ has quit IRC
 67 2016-11-24T08:43:17  *** justanotheruser has quit IRC
 68 2016-11-24T08:55:40  <gmaxwell> http://igoro.com/archive/gallery-of-processor-cache-effects/ some nice examples.
 69 2016-11-24T08:57:33  *** bitcoin358 has joined #bitcoin-core-dev
 70 2016-11-24T08:58:11  <luke-jr> gmaxwell: interesting
 71 2016-11-24T09:00:53  <bitcoin358> hey guys
 72 2016-11-24T09:01:05  <bitcoin358> quick question, at what point does a .13 node start dropping tx from mem pool
 73 2016-11-24T09:01:17  <bitcoin358> assuming default mem pool size of 300mb, when that is reached, what happens?
 74 2016-11-24T09:02:24  <gmaxwell> the lowest feerate transaction is dropped.
 75 2016-11-24T09:02:46  <bitcoin358> thanks greg
 76 2016-11-24T09:02:57  <gmaxwell> and the fee filter is increased to tell peers to stop sending transactions with feerates below that-- until there is room again.
 77 2016-11-24T09:03:13  <bitcoin358> so as a counterpoint
 78 2016-11-24T09:03:23  <bitcoin358> is there any decent way to tell how many mempools still have your transaction in them
 79 2016-11-24T09:03:44  <bitcoin358> basically i'm thinking of a business case where you are sending coins to someone, but it doesn't confirm, and the mempool explodes, and they request that you resend
 80 2016-11-24T09:04:16  <gmaxwell> No. 'how many' isn't particularly important either, what is important is being in the mempools of miners.
 81 2016-11-24T09:04:19  <bitcoin358> is there a decent way to get a feel for what % of the network or mining pools have still in their mempool, so as to alleviate the risk of double payment
 82 2016-11-24T09:04:51  <gmaxwell> Then you resend and conflict with the original transaction, it would _never_ be safe to repay without conflicting, regardless of what some mempool in a forrest of nodes is doing.
 83 2016-11-24T09:05:11  <bitcoin358> I hear you
 84 2016-11-24T09:05:17  <bitcoin358> what about, in the event, that you have chained unconfirmed inputs
 85 2016-11-24T09:05:18  <gmaxwell> A miner could happily include any valid transaction they liked... and some miners have APIs to pay them out of band to poke fees into their blocks.
 86 2016-11-24T09:05:46  <bitcoin358> so customer A wants a manual resend, you do a doublespend with a bigger fee
 87 2016-11-24T09:05:59  <gmaxwell> bitcoin358: add more fees later in the chain and enjoy giving them to miners running Bitcoin Core, since it will happily notice those fees later in the chain.
 88 2016-11-24T09:06:00  <bitcoin358> but customer B also received coins that came after A, and are relying on his inputs
 89 2016-11-24T09:06:08  <bitcoin358> right so
 90 2016-11-24T09:06:13  <bitcoin358> I am actually trying to do just that, right now!
 91 2016-11-24T09:06:20  <bitcoin358> however, the issue is I run into the 64 error, mempool chain too long
 92 2016-11-24T09:06:35  <bitcoin358> I have actually been taking advantage of CPFP the last 48 hours with great success
 93 2016-11-24T09:06:53  <bitcoin358> but I have this one monster transaction I received and I am trying to get it confirmed by spending it forward with a higher fee, and I get the 64 error
 94 2016-11-24T09:07:40  <gmaxwell> welp, --- error means what it says, nodes won't handle more than depth 25 for that fee analysis. You can't add more fees on a chain that deep until part of it confirms.
 95 2016-11-24T09:07:53  <bitcoin358> dang
 96 2016-11-24T09:08:04  <gmaxwell> is there change on a shorter part of the chain you could potentially add fee via?
 97 2016-11-24T09:08:32  <bitcoin358> I think so but unfortunately I'm not the node operator, I just received a payment from them
 98 2016-11-24T09:08:37  <gmaxwell> e.g. A -> B -> D, D'  D -> E -> f ...  but D' is still unspent early in the chain?
 99 2016-11-24T09:08:55  <bitcoin358> I was hoping I could bump their whole cluster of transactions by being generous on my own but yeah
100 2016-11-24T09:09:20  <bitcoin358> they are running .11.... and causing all sorts of problems
101 2016-11-24T09:09:24  <gmaxwell> you could if not for the depth limit, unfortunately there had to be a cutoff there to avoid the CPFP analysis taking unbounded cpu.
102 2016-11-24T09:09:36  <bitcoin358> i hear you 100%, oh well
103 2016-11-24T09:09:37  *** laurentmt has joined #bitcoin-core-dev
104 2016-11-24T09:09:47  <bitcoin358> hopefully the mempool subsides tomorrow on the holiday and we get a little relief
105 2016-11-24T09:10:18  <gmaxwell> well a luckly run of blocks will happen at some point and clear things out.
106 2016-11-24T09:10:30  <bitcoin358> *fingers crossed* lol
107 2016-11-24T09:10:44  <bitcoin358> I have like 1.5 BTC from this guy stuck in limbo because he paid $2 on a 25 kb transaction ..
108 2016-11-24T09:11:09  <bitcoin358> CPFP is working great otherwise
109 2016-11-24T09:11:11  <bitcoin358> :)
110 2016-11-24T09:11:28  <Lightsword> bitcoin358, if you get stuck for too long I can probably mine it for you
111 2016-11-24T09:11:29  <gmaxwell> yea, I've seen a fair amount of it.
112 2016-11-24T09:11:56  <bitcoin358> thanks man, I will ping you if it doesn't clear in the next day or so
113 2016-11-24T09:12:14  <bitcoin358> I would honestly be down to pay $10 or whatever but the issue is probably that the entire chain it's relying on is maybe ... 100kb? who knows
114 2016-11-24T09:12:31  <gmaxwell> bitcoin358: if you're running modern (0.13+) bitcoind it's easy to find out.
115 2016-11-24T09:12:39  <Lightsword> bitcoin358, what’s the txid?
116 2016-11-24T09:12:41  <bitcoin358> gmaxwell: what's the command?
117 2016-11-24T09:13:01  <bitcoin358> e5a24368c0a68f0b7f6eba48dc0824c265a67300bd486e7b98c2f246c2fb9ce3
118 2016-11-24T09:13:25  <gmaxwell> bitcoin358: getmempoolentry <txid>
119 2016-11-24T09:13:58  <gmaxwell> looks like the whole collection is 58276 bytes.
120 2016-11-24T09:14:00  <bitcoin358> ohh nice
121 2016-11-24T09:14:02  <bitcoin358> I see that :)
122 2016-11-24T09:14:04  <bitcoin358> very cool
123 2016-11-24T09:14:32  <bitcoin358> 495d71e30565278827e4ba0930f1ca939db9e05df2c95b39dc7a81befefb2858 this is the other one
124 2016-11-24T09:14:35  <gmaxwell> that one isn't too deep.. says there are currently 3 ancestors.
125 2016-11-24T09:14:50  <gmaxwell> I don't have that one locally.
126 2016-11-24T09:15:00  <bitcoin358> right, I don't have this one locally in my node either
127 2016-11-24T09:15:02  <bitcoin358> not sure why
128 2016-11-24T09:15:20  <gmaxwell> something could be in its history that doesn't even meet the minrelay fee...
129 2016-11-24T09:15:35  <gmaxwell> CPFP doesn't influence passing the minrelayfee.
130 2016-11-24T09:16:13  <Lightsword> yeah, I get 64: too-long-mempool-chain when trying to sendrawtransaction that one
131 2016-11-24T09:16:26  <Lightsword> https://blockchain.info/tx/495d71e30565278827e4ba0930f1ca939db9e05df2c95b39dc7a81befefb2858?format=hex
132 2016-11-24T09:16:42  <gmaxwell> Whats a txid of one of its parents?
133 2016-11-24T09:17:03  <bitcoin358> I am going to try to raw transact the first one to myself with a higher fee
134 2016-11-24T09:17:52  <bitcoin358> my math seems to suggest if I want it to confirm in 1-2 blocks I need to pay about 0.0392
135 2016-11-24T09:17:54  <bitcoin358> is that math right
136 2016-11-24T09:18:03  *** berndj has quit IRC
137 2016-11-24T09:18:05  <bitcoin358> 56kb paying 7 satoshi/byte
138 2016-11-24T09:18:45  <Lightsword> 0b34a5f31f6bc1ecad957a3af2a927b454992b565a8786c21e8d7f9e7743a6d1 looks like
139 2016-11-24T09:18:54  *** berndj has joined #bitcoin-core-dev
140 2016-11-24T09:19:20  <gmaxwell> 21inc's estimator is saying, about 70 to get in 2 blocks-- though there are at least a few miners that don't CPFP. so.. it would be longer than two blocks perhaps. Nothing you can do about that.
141 2016-11-24T09:19:53  <bitcoin358> ah right, glossed over there's 6 zeros here so you're right
142 2016-11-24T09:19:57  <bitcoin358> 70 satoshi
143 2016-11-24T09:20:07  <bitcoin358> .039 btc alright
144 2016-11-24T09:20:11  <bitcoin358> I'm going to yolo it
145 2016-11-24T09:20:26  <bitcoin358> and tell this dude to upgrade his node and stop making 25 kb transactions
146 2016-11-24T09:20:33  <gmaxwell> Lightsword: yea, I get a count of 25 on that one.
147 2016-11-24T09:21:10  <bitcoin358> weird okay so
148 2016-11-24T09:21:19  <bitcoin358> I just did a rawtx spending the one that's 56kb that only has 2 ancestors
149 2016-11-24T09:21:27  <bitcoin358> and when push I get same 64 error
150 2016-11-24T09:21:37  <bitcoin358> (this one: e5a24368c0a68f0b7f6eba48dc0824c265a67300bd486e7b98c2f246c2fb9ce3)
151 2016-11-24T09:21:49  <Lightsword> well I went ahead and manually prioritized those transactions
152 2016-11-24T09:21:52  <gmaxwell> well it would have gone nowhere.. pastebin it?
153 2016-11-24T09:22:06  <bitcoin358> thanks Lightsword!
154 2016-11-24T09:22:17  <bitcoin358> http://pastebin.com/Na3KrbUJ here's the raw
155 2016-11-24T09:23:12  <Lightsword> gmaxwell, btw you can just put ?format=hex at the end of the url on a blockchain.info transaction page to get the raw hex
156 2016-11-24T09:23:29  <gmaxwell> yea, if it has it, but something his own node rejected...
157 2016-11-24T09:23:34  <bitcoin358> Lightsword: I didn't know that either, thank you for heads up
158 2016-11-24T09:23:45  <gmaxwell> Lightsword: FWIW, Piuk added that at my request in this channel a couple years ago. :)
159 2016-11-24T09:24:17  <bitcoin358> definitely helpful feature
160 2016-11-24T09:25:06  *** Guyver2 has joined #bitcoin-core-dev
161 2016-11-24T09:25:32  <Lightsword> yeah, I can’t add that to mempool due to chain being too long…but the inputs should at least get mined I think
162 2016-11-24T09:26:00  <bitcoin358> thanks man I really appreciate it
163 2016-11-24T09:26:20  <gmaxwell> hm. there are limits other than count...there is a limit of size of 101k... but that shouldn't be exceeded either.
164 2016-11-24T09:26:27  <bitcoin358> alright, appreciate the help gmaxwell/lightsword
165 2016-11-24T09:26:31  <bitcoin358> I am off to bed
166 2016-11-24T09:26:36  <bitcoin358> happy holidays to all
167 2016-11-24T09:26:42  <gmaxwell> bitcoin358: goodnight, hopefully you'll wake to confirmed txn.
168 2016-11-24T09:26:46  <gmaxwell> Cheers.
169 2016-11-24T09:26:50  <bitcoin358> gmaxwell: fingers crossed :)
170 2016-11-24T09:26:56  *** bitcoin358 has quit IRC
171 2016-11-24T09:27:43  <Lightsword> gmaxwell, pushed that transaction to blockchain.info https://blockchain.info/tx/4db1a95e339193ad2faac2e9d02ad59d014d88ee387ad0617885c528ff664e21
172 2016-11-24T09:28:50  <gmaxwell> bitcoin358: (in case you're watching logs) if you do nag the author of this chain of unconfirmed txn, they should really be encouraged to sendmany. This whole graph of unconfirmed txn could have been reduced down to a fraction of its size as a single sendmany.
173 2016-11-24T10:07:01  <fanquake> Just experienced #9212, running master on mainnet
174 2016-11-24T10:07:02  <gribble> https://github.com/bitcoin/bitcoin/issues/9212 | Assertion failed: (nSendVersion != 0), function GetSendVersion, file ./net.h, line 775. · Issue #9212 · bitcoin/bitcoin · GitHub
175 2016-11-24T10:07:57  *** aalex__ has joined #bitcoin-core-dev
176 2016-11-24T10:17:20  *** jannes has joined #bitcoin-core-dev
177 2016-11-24T10:27:54  <paveljanik> fanquake, do you have more lines in the log before this_
178 2016-11-24T10:27:56  <paveljanik> ?
179 2016-11-24T10:29:57  <fanquake> paveljanik Added to the issue, pretty sure these were the preceeding lines.
180 2016-11-24T10:31:18  *** Arid has joined #bitcoin-core-dev
181 2016-11-24T10:33:41  <Arid> Hello, a site that double your bitcoins in 48h is a scam?
182 2016-11-24T10:35:26  *** go1111111 has joined #bitcoin-core-dev
183 2016-11-24T10:36:41  *** Arid has quit IRC
184 2016-11-24T10:41:43  *** aalex__ has quit IRC
185 2016-11-24T10:45:53  *** Arnavion has quit IRC
186 2016-11-24T10:48:50  *** AtashiCon has quit IRC
187 2016-11-24T10:49:01  *** fanquake has quit IRC
188 2016-11-24T10:50:29  *** fanquake has joined #bitcoin-core-dev
189 2016-11-24T10:51:58  *** fanquake has joined #bitcoin-core-dev
190 2016-11-24T11:14:42  <bitcoin-git> [bitcoin] paveljanik opened pull request #9216: Doc: Fix copypasted comment (master...20161124_commentfix_banmap) https://github.com/bitcoin/bitcoin/pull/9216
191 2016-11-24T11:18:16  <bitcoin-git> [bitcoin] laanwj pushed 6 new commits to master: https://github.com/bitcoin/bitcoin/compare/93566e0c37c5...db5e22e0537a
192 2016-11-24T11:18:17  <bitcoin-git> bitcoin/master 47db075 Wladimir J. van der Laan: qt: Plug many memory leaks...
193 2016-11-24T11:18:17  <bitcoin-git> bitcoin/master 693384e Wladimir J. van der Laan: qt: Prevent thread/memory leak on exiting RPCConsole...
194 2016-11-24T11:18:18  <bitcoin-git> bitcoin/master e4f126a Wladimir J. van der Laan: qt: Avoid splash-screen related memory leak...
195 2016-11-24T11:18:31  <bitcoin-git> [bitcoin] laanwj closed pull request #9190: qt: Plug many memory leaks (master...2016_11_plug_leaks) https://github.com/bitcoin/bitcoin/pull/9190
196 2016-11-24T11:41:21  *** wvr has quit IRC
197 2016-11-24T11:45:56  <fanquake> paveljanik re #9144. You want all instances of Result:: changed to Result: ?
198 2016-11-24T11:45:58  <gribble> https://github.com/bitcoin/bitcoin/issues/9144 | [Trivial] Correct waitforblockheight example help text by fanquake · Pull Request #9144 · bitcoin/bitcoin · GitHub
199 2016-11-24T11:46:58  <paveljanik> fanquake, yes please. :: looks strange.
200 2016-11-24T11:47:14  <paveljanik> but this is supermicronit, when we are there...
201 2016-11-24T11:47:18  <paveljanik> thank you!
202 2016-11-24T11:49:04  *** AaronvanW has quit IRC
203 2016-11-24T12:11:21  *** wvr has joined #bitcoin-core-dev
204 2016-11-24T12:14:06  *** AaronvanW has joined #bitcoin-core-dev
205 2016-11-24T12:14:06  *** AaronvanW has quit IRC
206 2016-11-24T12:14:06  *** AaronvanW has joined #bitcoin-core-dev
207 2016-11-24T12:14:52  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/db5e22e0537a...c98f6b3d93a2
208 2016-11-24T12:14:53  <bitcoin-git> bitcoin/master e3c4f7e fanquake: Correct help output for waitfor RPC commands
209 2016-11-24T12:14:53  <bitcoin-git> bitcoin/master c98f6b3 MarcoFalke: Merge #9144: [Trivial] Correct waitforblockheight example help text...
210 2016-11-24T12:15:03  *** MarcoFalke has joined #bitcoin-core-dev
211 2016-11-24T12:15:08  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #9144: [Trivial] Correct waitforblockheight example help text (master...rpc-commands) https://github.com/bitcoin/bitcoin/pull/9144
212 2016-11-24T12:56:47  <fanquake> Have solved the afl-fuzz issue on osx by setting AFL_NO_FORKSRV=1
213 2016-11-24T13:01:22  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c98f6b3d93a2...bc121b0eb197
214 2016-11-24T13:01:22  <bitcoin-git> bitcoin/master f26da35 Pavel Janík: Fix copypasted comment.
215 2016-11-24T13:01:23  <bitcoin-git> bitcoin/master bc121b0 MarcoFalke: Merge #9216: Doc: Fix copypasted comment...
216 2016-11-24T13:01:35  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #9216: Doc: Fix copypasted comment (master...20161124_commentfix_banmap) https://github.com/bitcoin/bitcoin/pull/9216
217 2016-11-24T13:24:12  *** Guest317 has joined #bitcoin-core-dev
218 2016-11-24T13:25:58  *** Guest317 is now known as roidster
219 2016-11-24T13:28:38  *** MarcoFalke has left #bitcoin-core-dev
220 2016-11-24T13:34:18  *** arevutsky has joined #bitcoin-core-dev
221 2016-11-24T13:35:32  <arevutsky> Hi. I updated bitcoind to version	130100. Now I see message "Warning: unknown new rules activated (versionbit 28)". Should I do something?
222 2016-11-24T13:40:35  <bitcoin-git> [bitcoin] laanwj opened pull request #9218: qt: Show progress overlay when clicking spinner icon (master...2016_11_overlay_when_clicking_sync_icon) https://github.com/bitcoin/bitcoin/pull/9218
223 2016-11-24T13:45:40  <jonasschnelli> wumpus: re #9218, .. I mean additionally to the spinner option.
224 2016-11-24T13:45:42  <gribble> https://github.com/bitcoin/bitcoin/issues/9218 | qt: Show progress overlay when clicking spinner icon by laanwj · Pull Request #9218 · bitcoin/bitcoin · GitHub
225 2016-11-24T13:48:16  *** wvr has quit IRC
226 2016-11-24T14:03:59  *** arevutsky has quit IRC
227 2016-11-24T14:09:44  *** Victor_sueca has joined #bitcoin-core-dev
228 2016-11-24T14:12:41  *** Victorsueca has quit IRC
229 2016-11-24T14:16:18  *** echonaut7 has quit IRC
230 2016-11-24T14:16:33  *** echonaut has joined #bitcoin-core-dev
231 2016-11-24T14:31:33  <wumpus> jonasschnelli: yes, makes sense
232 2016-11-24T14:48:27  *** Chris_Stewart_5 has joined #bitcoin-core-dev
233 2016-11-24T14:56:43  *** aalex__ has joined #bitcoin-core-dev
234 2016-11-24T15:00:52  *** aalex__ has quit IRC
235 2016-11-24T15:01:27  *** aalex__ has joined #bitcoin-core-dev
236 2016-11-24T15:02:09  *** laurentmt has quit IRC
237 2016-11-24T15:09:43  *** Giszmo has joined #bitcoin-core-dev
238 2016-11-24T15:10:08  *** aalex__ has quit IRC
239 2016-11-24T15:10:58  *** aalex__ has joined #bitcoin-core-dev
240 2016-11-24T15:13:24  *** aalex__ has quit IRC
241 2016-11-24T15:13:47  *** aalex__ has joined #bitcoin-core-dev
242 2016-11-24T15:19:31  *** Victor_sueca is now known as Victorsueca
243 2016-11-24T15:23:10  *** laurentmt has joined #bitcoin-core-dev
244 2016-11-24T15:51:29  *** To7 has quit IRC
245 2016-11-24T16:13:53  *** chris2000 has joined #bitcoin-core-dev
246 2016-11-24T17:24:56  *** To7 has joined #bitcoin-core-dev
247 2016-11-24T17:38:22  *** laurentmt has quit IRC
248 2016-11-24T18:47:28  *** btcfan has joined #bitcoin-core-dev
249 2016-11-24T18:49:07  *** btcfan has quit IRC
250 2016-11-24T19:10:52  *** haakonn_ has quit IRC
251 2016-11-24T20:10:26  *** windsok has quit IRC
252 2016-11-24T20:14:28  <paveljanik> Looks like more people need fork to eat the dinner today. My son just gave me one to eat the desert...
253 2016-11-24T20:26:45  <Victorsueca> y u no spoon?
254 2016-11-24T20:29:10  *** windsok has joined #bitcoin-core-dev
255 2016-11-24T20:30:30  *** gabridome has joined #bitcoin-core-dev
256 2016-11-24T20:32:19  *** CubicEarth has quit IRC
257 2016-11-24T20:32:48  *** CubicEarth has joined #bitcoin-core-dev
258 2016-11-24T20:33:07  *** CubicEarth has joined #bitcoin-core-dev
259 2016-11-24T20:53:40  <gmaxwell> Can some people other than me run #9188 and report testing results (ideally on testnet) just so I'm not the only person who has tested it...
260 2016-11-24T20:53:42  <gribble> https://github.com/bitcoin/bitcoin/issues/9188 | Make orphan parent fetching ask for witnesses. by gmaxwell · Pull Request #9188 · bitcoin/bitcoin · GitHub
261 2016-11-24T20:53:56  <gmaxwell> I'd like to see it merged soon, since I think we'll want it in a 0.13.2 backport.
262 2016-11-24T20:55:13  <gmaxwell> wumpus: I think #9189 is ready for merge.
263 2016-11-24T20:55:14  <gribble> https://github.com/bitcoin/bitcoin/issues/9189 | Always add default_witness_commitment with GBT client support by sipa · Pull Request #9189 · bitcoin/bitcoin · GitHub
264 2016-11-24T21:20:13  *** wvr has joined #bitcoin-core-dev
265 2016-11-24T21:20:56  <luke-jr> gmaxwell: could that bug be potentially forking if segwit activates? :/
266 2016-11-24T21:21:39  <gmaxwell> 9188? no.
267 2016-11-24T21:22:20  <gmaxwell> just would result in orphan segwit txn not propagating so well.
268 2016-11-24T21:25:15  <luke-jr> is there any way to tell if it's working, once I have it running?
269 2016-11-24T21:27:06  <gmaxwell> debug net will no longer show it making non-witness tx fetches towards witness peers.
270 2016-11-24T21:28:45  <luke-jr> going to run 0.13 with this backported
271 2016-11-24T21:29:34  <luke-jr> (minor conflict on the shadowing stuff, but no big deal just a var rename)
272 2016-11-24T21:33:28  *** jannes has quit IRC
273 2016-11-24T21:33:46  *** mrkent has joined #bitcoin-core-dev
274 2016-11-24T21:33:48  <luke-jr> ok, node is up
275 2016-11-24T21:34:07  <instagibbs> can someone briefly explain the use/life cycle of CReserveKey?
276 2016-11-24T21:34:39  *** gabridome has quit IRC
277 2016-11-24T21:35:18  <luke-jr> instagibbs: it removes it from the memory keypool immediately, but only from disk when you keep it
278 2016-11-24T21:42:13  *** gabridome has joined #bitcoin-core-dev
279 2016-11-24T21:43:49  <instagibbs> ok thanks
280 2016-11-24T21:54:50  *** marcoagner has joined #bitcoin-core-dev
281 2016-11-24T21:54:59  *** CubicEarth has quit IRC
282 2016-11-24T21:55:12  *** marcoagner has joined #bitcoin-core-dev
283 2016-11-24T22:12:13  *** gabridome has quit IRC
284 2016-11-24T22:35:26  *** marcoagner has quit IRC
285 2016-11-24T22:38:05  *** Guyver2 has quit IRC
286 2016-11-24T22:43:14  *** bitcoin308 has joined #bitcoin-core-dev
287 2016-11-24T22:43:31  <bitcoin308> hey guys just wanted to thank everyone for the help last night, the massive unconf chain / backlog finally cleared out for us :)
288 2016-11-24T22:48:19  *** bitcoin308 is now known as sictransitgloria
289 2016-11-24T22:49:47  <gmaxwell> sictransitgloria: good to hear that!
290 2016-11-24T23:00:23  *** sictransitgloria is now known as oddcomet
291 2016-11-24T23:14:00  <midnightmagic> God dammit.
292 2016-11-24T23:15:42  *** Chris_Stewart_5 has quit IRC
293 2016-11-24T23:21:59  *** laurentmt has joined #bitcoin-core-dev
294 2016-11-24T23:24:01  *** Chris_Stewart_5 has joined #bitcoin-core-dev
295 2016-11-24T23:25:13  *** roidster has quit IRC
296 2016-11-24T23:28:07  *** btcdrak has quit IRC
297 2016-11-24T23:32:22  *** MarcoFalke has joined #bitcoin-core-dev
298 2016-11-24T23:33:01  <oddcomet> midnightmagic: ?
299 2016-11-24T23:37:30  <midnightmagic> oddcomet: wrong channel. I was about to ask someone to help me remember something stupid I forgot. :(
300 2016-11-24T23:40:46  *** dcousens has joined #bitcoin-core-dev
301 2016-11-24T23:46:18  *** dcousens has quit IRC
302 2016-11-24T23:46:21  *** rusty has joined #bitcoin-core-dev
303 2016-11-24T23:46:38  *** dcousens has joined #bitcoin-core-dev
304 2016-11-24T23:51:30  *** juscamarena has joined #bitcoin-core-dev