12016-01-20T00:08:25  *** dayZh has joined #bitcoin-core-dev
  22016-01-20T00:12:52  *** dayZh has quit IRC
  32016-01-20T00:23:59  *** dayZh has joined #bitcoin-core-dev
  42016-01-20T00:28:24  *** dayZh has quit IRC
  52016-01-20T00:52:12  *** drnet has joined #bitcoin-core-dev
  62016-01-20T00:54:31  *** dcousens has joined #bitcoin-core-dev
  72016-01-20T00:54:44  <dcousens> Hmph,  I just got a bunch of RPC server socket timeouts over 1.5 days old lol
  82016-01-20T00:56:03  <dcousens> socket sending timeout: 85865s
  92016-01-20T00:56:48  <dcousens> Maybe under 1.5 days, but over 1 day.  Anyway,  entering a line feed to STDIN unlocked the file descriptor?  Suddenly got "socket send error Bad file descriptor (9)"
 102016-01-20T00:56:57  <dcousens> And now my node has resumed catching up on the last day of missed blocks
 112016-01-20T00:57:44  *** dayZh has joined #bitcoin-core-dev
 122016-01-20T00:58:31  <dcousens> Any ideas? Wondering where I should start with debugging this
 132016-01-20T00:59:20  <dcousens> (obviously an RPC call didn't give up CS_MAIN until the socket closed?)
 142016-01-20T01:02:08  *** dayZh has quit IRC
 152016-01-20T01:06:57  *** adnn has quit IRC
 162016-01-20T01:10:13  *** adnn_ has joined #bitcoin-core-dev
 172016-01-20T01:34:56  *** bsm117532 has quit IRC
 182016-01-20T01:35:49  *** bsm1175321 has joined #bitcoin-core-dev
 192016-01-20T01:35:51  *** bsm1175321 is now known as bsm117532
 202016-01-20T01:36:24  *** drnet has quit IRC
 212016-01-20T01:40:23  *** afk11 has joined #bitcoin-core-dev
 222016-01-20T01:43:15  *** dayZh has joined #bitcoin-core-dev
 232016-01-20T01:47:50  *** dayZh has quit IRC
 242016-01-20T01:55:34  *** afk11 has quit IRC
 252016-01-20T02:00:05  <gijensen> Shorter timeouts? What was the last RPC call you made?
 262016-01-20T02:04:00  *** dayZh has joined #bitcoin-core-dev
 272016-01-20T02:05:55  *** zookolaptop has quit IRC
 282016-01-20T02:06:00  *** GAit has quit IRC
 292016-01-20T02:08:08  *** dayZh has quit IRC
 302016-01-20T02:16:32  *** afk11 has joined #bitcoin-core-dev
 312016-01-20T02:18:22  *** Ylbam has quit IRC
 322016-01-20T02:25:10  *** afk11 has quit IRC
 332016-01-20T02:28:44  *** dayZh has joined #bitcoin-core-dev
 342016-01-20T02:33:48  *** warren has quit IRC
 352016-01-20T02:36:20  *** brg444 has joined #bitcoin-core-dev
 362016-01-20T02:36:38  *** dayZh has quit IRC
 372016-01-20T02:39:19  *** afk11 has joined #bitcoin-core-dev
 382016-01-20T02:47:15  *** afk11_ has joined #bitcoin-core-dev
 392016-01-20T02:47:31  *** afk11 has quit IRC
 402016-01-20T02:47:31  *** afk11_ is now known as afk11
 412016-01-20T02:49:23  *** dayZh has joined #bitcoin-core-dev
 422016-01-20T02:55:26  *** belcher has quit IRC
 432016-01-20T02:55:29  *** dayZh has quit IRC
 442016-01-20T02:55:35  *** dayZh has joined #bitcoin-core-dev
 452016-01-20T03:04:12  *** afk11 has quit IRC
 462016-01-20T03:22:21  *** afk11 has joined #bitcoin-core-dev
 472016-01-20T03:23:29  *** zookolaptop has joined #bitcoin-core-dev
 482016-01-20T03:23:33  *** dcousens has quit IRC
 492016-01-20T03:25:30  *** dcousens has joined #bitcoin-core-dev
 502016-01-20T03:27:57  *** zookolap` has joined #bitcoin-core-dev
 512016-01-20T03:29:47  *** zookolaptop has quit IRC
 522016-01-20T03:39:22  *** dayZh has quit IRC
 532016-01-20T03:46:45  *** warren has joined #bitcoin-core-dev
 542016-01-20T03:53:25  <wangchun> BlueMatt: ping
 552016-01-20T03:54:13  <BlueMatt> wangchun: yea, I mean I definitely understand what you're proposing, but I dont believe that any such soft fork would ever occur
 562016-01-20T03:54:21  <wangchun> so if you merge a patch that remove the block size limit completely NOW, but this patch does not take into effect until 2017-01-01
 572016-01-20T03:54:23  <BlueMatt> once its in there, the political pressure to not remove it is too strong
 582016-01-20T03:55:04  <BlueMatt> and, what do you set the limit to?
 592016-01-20T03:55:14  <wangchun> And time now is 2016-09-30, we have a consensus to upgrade to 2MB, that is fine, merge another patch for 2MB,
 602016-01-20T03:55:26  <BlueMatt> the political pressure to set the limit to something like 10mb at that time from people like coinbase would be huge...and 10mb would result in 0 fees for a long time to come
 612016-01-20T03:55:37  <wangchun> this new patch is soft fork for those running 0.12+, only hard fork for those running 0.11 or lower
 622016-01-20T03:56:23  <wangchun> and if no consensus on 2016-09-30, we can just remove the earlier patch, that nothing happens for those running 0.11 or lower, and it is a soft fork for those running 0.12+
 632016-01-20T03:56:30  <BlueMatt> suresure, but how do we pick the number in 2016-09?
 642016-01-20T03:56:36  <wangchun> this buys lots of time for waiting for the consensus
 652016-01-20T03:56:41  <BlueMatt> like, the selection of the number would fall to miners
 662016-01-20T03:56:47  <BlueMatt> how would miners pick the block size at that point?
 672016-01-20T03:57:07  <wangchun> three months buffer for a soft fork is enough
 682016-01-20T03:57:15  <wangchun> but for hard fork, we need probably a year
 692016-01-20T03:57:27  <wangchun> that's how these numbers are chosen
 702016-01-20T03:57:38  <BlueMatt> I understand that part, sure
 712016-01-20T03:57:54  <BlueMatt> but how will *you* pick the block size come 2016-09
 722016-01-20T03:58:06  <BlueMatt> and how will you, and the other miners agree on something in 2016-09?
 732016-01-20T03:58:18  <BlueMatt> otherwise we end up with an infinite blocksize and bitcoin blows up :/
 742016-01-20T03:58:25  <wangchun> any block size below 33.5MB is soft fork to those have upgraded
 752016-01-20T03:58:40  <BlueMatt> 33M will clearly break bitcoin in many way
 762016-01-20T03:58:40  <BlueMatt> s
 772016-01-20T03:59:01  <BlueMatt> and what if we cant get 51% to agree to a number?
 782016-01-20T03:59:13  <BlueMatt> then we end up with 33M and we have no fees and massive blocks :(
 792016-01-20T03:59:13  <wangchun> just change it back to 1MB
 802016-01-20T03:59:25  <BlueMatt> but there is no "just change it"
 812016-01-20T03:59:32  <BlueMatt> it has to be a soft fork, so miners have to agree to do it
 822016-01-20T03:59:33  <wangchun> it is soft fork for those upgraded
 832016-01-20T03:59:41  <BlueMatt> but miners have to agree
 842016-01-20T03:59:50  <wangchun> yes, it is
 852016-01-20T04:00:05  <kanzure> no way to change back
 862016-01-20T04:00:07  <BlueMatt> yes, it is a soft fork
 872016-01-20T04:00:13  <BlueMatt> but miners have to agree to do a soft fork
 882016-01-20T04:00:41  <wangchun> change it back is soft fork for those have upgraded, and it is no fork for those havn't.
 892016-01-20T04:01:10  <wangchun> OK, I explain it again...
 902016-01-20T04:01:15  <BlueMatt> nono, I understand
 912016-01-20T04:01:24  <BlueMatt> it is a soft fork for those who have upgraded, I agree
 922016-01-20T04:01:39  <wangchun> We schedule a "virtual" hard fork NOW, but only active it one year into the future
 932016-01-20T04:01:41  <dcousens> gijensen: sendrawtx
 942016-01-20T04:02:29  <BlueMatt> but my point is that a soft fork is not an upgrade by users, it is an upgrade by miners...what we're doing is setting the blocksize to 32M in 2017 if miners do nothing. Miners can soft fork it back down to something else before 2017, but they have to agree
 952016-01-20T04:02:33  <wangchun> after 9 months, if we have a detailed hard fork specs ready by then, go ahead,
 962016-01-20T04:02:33  <warren> wangchun: You have certainty that the bandwidth situation will be better a year from now?
 972016-01-20T04:02:39  <wangchun> otherwise change it back to what it was
 982016-01-20T04:02:41  <kanzure> wangchun: there is no way to ensure agreement about reverting to 1 MB in the event of catastrophic failure...... bitcoin miners will still continue to mine, even if 32 MB breaks the network.
 992016-01-20T04:02:58  <kanzure> wangchun: so they have no reason to agree to activate the soft-fork to "change it back".....
1002016-01-20T04:03:00  <wangchun> The hard fork is just an option for the future
1012016-01-20T04:03:15  <kanzure> even if everything is broken, maybe they will be OK with this
1022016-01-20T04:03:31  *** NLNico has joined #bitcoin-core-dev
1032016-01-20T04:03:59  <wangchun> Who are "they"?
1042016-01-20T04:04:18  <kanzure> miners.
1052016-01-20T04:04:19  <BlueMatt> wangchun: once its in the code it is no longer an option. it is an option for miners to soft-fork to decrease it again or set it to 1M, but if miners do not, then it is not an option
1062016-01-20T04:05:06  <kanzure> wangchun: bluematt's concern is the following scenario: (1) hard-fork block size increase, (2) the bitcoin network is broken, (3) miners disagree with #2, (4) miners do NOT activate soft-fork to "change it back".
1072016-01-20T04:05:10  <wangchun> OK, merge 2MB now but not activate it until 2017-01-01
1082016-01-20T04:05:15  <jl2012> wangchun, would you please elaborate you rationale of completing removing limit?
1092016-01-20T04:05:25  <warren> wangchun: Keep in mind that those miners who want to agree to a soft-fork might be at a significant orphan disadvantage to others who have greater connectivity.  It could be dangerous to make any assumptions about what the network and mining power distribution will look like in the future.
1102016-01-20T04:05:39  <wangchun> completely remove the limit is better, as it gives an option for any proposals
1112016-01-20T04:05:42  <wangchun> not just 2MB
1122016-01-20T04:05:44  <BlueMatt> jl2012: the rationale is that we know a hard fork needs at least a year to be deployed, so his proposal is to start it now
1132016-01-20T04:05:49  <BlueMatt> jl2012: by removing the limit, +/-
1142016-01-20T04:05:54  <BlueMatt> jl2012: and then soft fork it back down
1152016-01-20T04:06:01  <jl2012> but not completely removing
1162016-01-20T04:06:15  <BlueMatt> jl2012: well, remove up to the network message size limit, ie ~32M
1172016-01-20T04:06:27  <jl2012> that's basically completely remove
1182016-01-20T04:06:39  <BlueMatt> yes
1192016-01-20T04:07:08  <wangchun> sure, when the activate date getting close, add another patch soft fork it back to the consensus we have by then
1202016-01-20T04:07:13  <jl2012> if the consensus is X MB is tolerable, than X MB, not >X MB
1212016-01-20T04:07:34  <jl2012> wangchun, what if miners do not do to SF?
1222016-01-20T04:08:15  <wangchun> It will be no worse than the current debate we have.
1232016-01-20T04:08:22  <jl2012> much worse
1242016-01-20T04:08:26  <kanzure> the network will be broken, though. much worse.
1252016-01-20T04:08:36  <BlueMatt> wangchun: my big concern is we have no idea /who/ "the miners" will be in a year...bitfury may be 50% by themselves...
1262016-01-20T04:08:59  <kanzure> the scenario was (2) the network is broken, and (3) miners disagree.
1272016-01-20T04:08:59  <jl2012> yes, don't forget their new chips
1282016-01-20T04:09:33  <BlueMatt> or (2) the network is broken and (3) bitfury disagrees, since they have better bandwidth than other people
1292016-01-20T04:09:55  <wangchun> How about merge 2MB now schedule it one year later?
1302016-01-20T04:09:57  <kanzure> that's true, bitfury has good bandwidth
1312016-01-20T04:09:57  <jl2012> "2MB now but not activate it until 2017-01-01" is basically another BIP102. Personally I don't think it is bad, if the date is far enough
1322016-01-20T04:10:00  <BlueMatt> (if anyone from bitfury is reading this, I dont mean to pick on y'all...just needed to pick someone...I mean ffs in a year /I/ might be 50% of the network...)
1332016-01-20T04:10:26  *** dcousens has quit IRC
1342016-01-20T04:10:30  <gijensen> dcousens, I have no idea where you'd start. I thought the timeout for RPC was limited to "timeout" too, so I didn't think that could happen.
1352016-01-20T04:10:37  <jl2012> just my 2 cents
1362016-01-20T04:10:47  <morcos> wangchun: I also like the idea.  I think we have spent too long trying to solve a technical problem when we really have a social problem.
1372016-01-20T04:11:07  <kanzure> agreed with morcos.
1382016-01-20T04:11:07  <BlueMatt> wangchun: you mean 4mb in a year
1392016-01-20T04:11:23  <BlueMatt> we're already doing 2mb...scheduling 2mb now means 4mb
1402016-01-20T04:11:36  <wangchun> Many people do not want hard fork just because it is risky,
1412016-01-20T04:11:47  <jl2012> BlueMatt, no need to mix segwit in this discussion
1422016-01-20T04:11:48  <wangchun> then we give them enough time to prepare the fork
1432016-01-20T04:11:54  <wangchun> that is the point
1442016-01-20T04:11:58  <jl2012> segwit can adapt a HF
1452016-01-20T04:12:19  <warren> wangchun: Say for example, the network breaks in some way with huge blocks, but miners with super fast centralized servers and very fast connectivity between each other decide they like it this way.  Miners with less bandwidth would have less ability to influence a soft-fork vote since they are orphaned out often due to the huge blocks.  It could be quite dangerous to make any assumptions about what the network and mining power distribution
1462016-01-20T04:12:19  <warren>  will look like in the future.
1472016-01-20T04:12:20  <BlueMatt> jl2012: hmm? no, its rather important? if we just want 2mb, no need to do that in a hf (if people are worried about a hf, lets increase the nonce space instead)
1482016-01-20T04:12:54  <jl2012> BIP141 will allow only 1.75MB with normal use
1492016-01-20T04:13:04  <jl2012> and assuming 100% people use it
1502016-01-20T04:13:04  <wangchun> warren: just 2mb or 4mb won't "break the network"
1512016-01-20T04:13:18  <BlueMatt> as for a 2.5/3ish mb hf, if I knew people would work on better relay mechanisms, I would be fine with that, mostly...but so far I'm +/- the only person at all who has worked on better relay
1522016-01-20T04:13:23  <BlueMatt> no, sorry, thats a lie, wangchun has as well
1532016-01-20T04:13:25  <wangchun> the problem is those nodes left behind a hard fork will be at risk
1542016-01-20T04:13:36  <wangchun> that is the issue this is trying to solve
1552016-01-20T04:13:40  <BlueMatt> but I'm not aware of anyone except for wangchun and I who have spent any serious time implementing better relay
1562016-01-20T04:13:53  <BlueMatt> 0.12 was a big step, but we need better relay, not just validation time for another step
1572016-01-20T04:14:08  <Luke-Jr> +1 for more nonce space; sadly, I'm sure Classic would reject that too :\
1582016-01-20T04:14:16  <jl2012> wangchun, yes, that's the biggest risk of hardfork. That's why the flag date has to be far enough
1592016-01-20T04:14:20  * Luke-Jr might as well throw it out there just in case
1602016-01-20T04:14:54  <wangchun> but now we do not have the consensus, we need something to buy us some time. That it is.
1612016-01-20T04:15:16  <jl2012> people are running legacy clients. E.g. I'm still running 0.9.5 for other applications to work
1622016-01-20T04:19:11  <BlueMatt> wangchun: in any case, I think there is some agreement on something around 2mb...if people really dont think the 1.75 of segwit is enough, forming consensus around a 2mb hf just to bump up segwith by .25mb is probably not hard, and could be done rather quickly, I think
1632016-01-20T04:19:36  <BlueMatt> wangchun: given 0.12 is adopted quickly, block process times and p2p relay should be improved enough that 2mb wont hurt decentralization incentives
1642016-01-20T04:19:52  <wangchun> Then we need to get the code merged as soon as possible
1652016-01-20T04:20:01  <wangchun> Activation date is not that important
1662016-01-20T04:20:06  <wangchun> but it should be far enough
1672016-01-20T04:20:21  * BlueMatt will complain loudly if its any less than a year from when the code is released
1682016-01-20T04:20:21  <jl2012> wangchun, I think consensus has been reached that 2MB is tolerable. The only remaining question is how to archive 2MB
1692016-01-20T04:20:28  <BlueMatt> thats probably still really tight, but I'd say at least a year
1702016-01-20T04:20:56  <wangchun> BlueMatt: I agree
1712016-01-20T04:21:20  <wangchun> Then we are talking something not happen until 2017
1722016-01-20T04:21:23  <gijensen> dcousens, ignore that. "timeout" doesn't effect RPC. I'm curious if it lasted longer than the specified RPC timeout though (set by bundling a timeout parameter via RPC or -rpcclienttimeout on bitcoin-cli)
1732016-01-20T04:21:31  <wangchun> Until it is too late, we need to do something
1742016-01-20T04:28:29  *** cypherBlock has joined #bitcoin-core-dev
1752016-01-20T04:34:52  <BlueMatt> warren: how about we go jointly propose a hard fork that activates in like late feb 2017 that also includes more nonce space (so that people cant argue its too trivial a change for a hard fork) :)
1762016-01-20T04:34:55  <BlueMatt> wangchun:
1772016-01-20T04:34:58  <BlueMatt> is who I meant to tag
1782016-01-20T04:35:14  *** yifu has joined #bitcoin-core-dev
1792016-01-20T04:35:23  <wangchun> good to me
1802016-01-20T04:35:36  <BlueMatt> maybe early march, but whatever, first half of 2017
1812016-01-20T04:36:20  *** zookolap` has quit IRC
1822016-01-20T04:36:51  *** yifu has quit IRC
1832016-01-20T04:36:56  *** AdrianG has joined #bitcoin-core-dev
1842016-01-20T04:50:06  *** arubi has quit IRC
1852016-01-20T04:58:34  <Luke-Jr> BlueMatt: jtoomim is already opposing more nonce space though, implying all sorts of nonsense accusations
1862016-01-20T04:59:12  <jtoomim> changing the headers probably breaks compatibility with SPV wallets.
1872016-01-20T04:59:21  <BlueMatt> jtoomim: it doesnt change the headers in any meaningful way
1882016-01-20T05:00:03  <jtoomim> hmm, let me look through the irc chat first
1892016-01-20T05:00:13  <jtoomim> i got linked into this discussion without context
1902016-01-20T05:00:21  <jtoomim> and i've been running into a lot of trolls trying to add bugs to Classic
1912016-01-20T05:00:22  <Luke-Jr> jtoomim: changing anything should break compatibility with SPV wallets; that it doesn't just goes to show the "SPV" wallets out there are buggy
1922016-01-20T05:00:38  <jtoomim> so i'm in super-pessimistic mode rightnow
1932016-01-20T05:00:54  <Luke-Jr> jtoomim: if you mean me, it's in your head only
1942016-01-20T05:01:12  <jtoomim> no, not you luke
1952016-01-20T05:01:16  <jtoomim> mostly james
1962016-01-20T05:01:22  <jtoomim> by the way, i wanted to apologize to you
1972016-01-20T05:01:38  <jtoomim> i think i accused you of being a troll, but in retrospect, you were innocent
1982016-01-20T05:01:52  <jtoomim> changing the PoW function is a reasonable thing in this context, just not for classic
1992016-01-20T05:02:09  <jtoomim> it's a reasonable thing for the minority branch to do
2002016-01-20T05:02:12  <warren> jtoomim: It's quite dangerous to do a HF to fullnodes that is seen as a SF to SPV?
2012016-01-20T05:02:21  <jtoomim> although i think it would be better to use AuxPoW and merge-mine
2022016-01-20T05:02:44  <jtoomim> is that a question or a statement!
2032016-01-20T05:02:53  <jtoomim> s/!/./
2042016-01-20T05:02:54  <warren> Wondering your opinion on that.
2052016-01-20T05:03:15  <jtoomim> i don't think it's quite dangerous, no, but i do think we should be careful during testing to make sure it goes as expected
2062016-01-20T05:03:25  <warren> Err ... I mean the SPV clients can't tell the difference, and that's dangerous.
2072016-01-20T05:03:42  <jtoomim> well, only if you think that the fork is going to be contentious
2082016-01-20T05:03:48  <Luke-Jr> warren: it'd be a 200k proof, but SPV clients *could* tell if they did fraud proofs
2092016-01-20T05:03:58  <jtoomim> but SPV wallets can either wait it out, or import their keys, or watch the block versions or something
2102016-01-20T05:05:03  <jtoomim> i've been thinking about including an increase to the coinbase scriptsig size in the HF
2112016-01-20T05:05:28  <jtoomim> i don't think that would affect SPV wallets
2122016-01-20T05:05:59  <jtoomim> but i really want to keep the change count as low as is safe for this HF
2132016-01-20T05:06:37  <jtoomim> which means mostly just tx validation cost limits (bytes hashed), versionbits logic, and the blocksize limit itself
2142016-01-20T05:08:19  *** cryptojonathan has joined #bitcoin-core-dev
2152016-01-20T05:08:33  <Luke-Jr> jtoomim: how about expanding versionbits to use all 32 bits?
2162016-01-20T05:08:55  <Luke-Jr> jtoomim: right now it's like 30 bits to avoid hardforking only
2172016-01-20T05:08:58  <randy-waterhouse> can't see how this discussion should be in bitcoin-core-dev ... take it too bitcoin-dev or bitcoin-classic?
2182016-01-20T05:09:08  <Luke-Jr> randy-waterhouse: fair
2192016-01-20T05:09:17  <jtoomim> luke-jr, it would break compatibiltiy with SPV.
2202016-01-20T05:09:35  <jtoomim> unless no SPV wallets even look at the nVersion field
2212016-01-20T05:09:37  <jtoomim> which i doubt
2222016-01-20T05:09:47  <jtoomim> ok
2232016-01-20T05:18:36  *** T23WS_ has joined #bitcoin-core-dev
2242016-01-20T05:19:36  *** adnn_ has quit IRC
2252016-01-20T05:21:03  <warren> BlueMatt: wangchun: Just throwing out ideas here ... it's certainly positive to add reasons to make a hardfork more worthwhile than 1.75MB -> 2MB like adding extra nonce space.  I think we could do even better than that, as we have had a hardfork wishlist for years and this gives us an opportunity to fix more than one problem.  I wonder if people would be OK with agreeing on the current roadmap to get us to an effective 1.75MB+ in a few mon
2262016-01-20T05:21:03  <warren> ths, and also set a deadline for HF wishlist item implementation (BIPs and code) for a scheduled hardfork in early 2017.  Whatever isn't fully approved in peer tech review before that deadline is cut.  Everyone could become far more productive if we agreed to end the drama and work on real improvements together in this manner?
2272016-01-20T05:21:12  *** T23WS has quit IRC
2282016-01-20T05:26:27  *** AndChat|221969 has joined #bitcoin-core-dev
2292016-01-20T05:27:38  *** cryptojonathan has quit IRC
2302016-01-20T05:38:48  *** arubi has joined #bitcoin-core-dev
2312016-01-20T05:48:50  *** jtoomim has quit IRC
2322016-01-20T05:51:02  *** JackH has quit IRC
2332016-01-20T05:56:39  *** JackH has joined #bitcoin-core-dev
2342016-01-20T06:08:35  *** priver__ has joined #bitcoin-core-dev
2352016-01-20T06:14:03  *** priver__ has quit IRC
2362016-01-20T06:16:51  *** cypherBlock has quit IRC
2372016-01-20T06:30:06  *** d_t has quit IRC
2382016-01-20T06:30:42  *** d_t has joined #bitcoin-core-dev
2392016-01-20T06:32:39  <Lightsword> BlueMatt, btw looks like ckpool now has what is essentially an internal relay network for multi-node regional deployments, but only works for trusted stratum server nodes
2402016-01-20T06:37:57  *** Ylbam has joined #bitcoin-core-dev
2412016-01-20T06:43:17  <BlueMatt> Lightsword: yea, if we all spv mine it's fine! :/
2422016-01-20T06:45:08  <Lightsword> BlueMatt, yeah….it’s different from the HO mining at least since it ships around ckpool’s workinfos between nodes or something like that
2432016-01-20T06:46:17  *** rubensayshi has quit IRC
2442016-01-20T06:51:45  <BlueMatt> suresure, if its your own nodes I get it
2452016-01-20T06:56:08  *** paveljanik has joined #bitcoin-core-dev
2462016-01-20T06:56:08  *** paveljanik has joined #bitcoin-core-dev
2472016-01-20T06:59:32  *** rubensayshi has joined #bitcoin-core-dev
2482016-01-20T07:01:31  *** brg444 has quit IRC
2492016-01-20T07:14:51  *** jtimon has quit IRC
2502016-01-20T07:40:07  *** murch has joined #bitcoin-core-dev
2512016-01-20T08:04:32  *** MRIO has quit IRC
2522016-01-20T08:05:15  *** jonasschnelli has quit IRC
2532016-01-20T08:07:58  *** jonasschnelli has joined #bitcoin-core-dev
2542016-01-20T08:13:50  *** paveljanik has quit IRC
2552016-01-20T08:21:27  *** eragmus has joined #bitcoin-core-dev
2562016-01-20T08:35:24  *** jouke has quit IRC
2572016-01-20T08:35:25  *** jouke has joined #bitcoin-core-dev
2582016-01-20T08:37:35  *** laurentmt has joined #bitcoin-core-dev
2592016-01-20T08:38:57  *** laurentmt has quit IRC
2602016-01-20T08:38:58  *** BashCo_ has quit IRC
2612016-01-20T09:03:13  *** MarcoFalke has joined #bitcoin-core-dev
2622016-01-20T09:04:12  *** p15 has quit IRC
2632016-01-20T09:05:09  *** BashCo has joined #bitcoin-core-dev
2642016-01-20T09:05:28  *** p15 has joined #bitcoin-core-dev
2652016-01-20T09:06:17  <GitHub67> [bitcoin] MarcoFalke opened pull request #7381: [walletdb] Fix syntax error in key parser (master...Mf1601-walletdbKeyparserFix) https://github.com/bitcoin/bitcoin/pull/7381
2662016-01-20T09:06:19  <MarcoFalke> At least I know where I lost all the coins to...
2672016-01-20T09:14:20  *** d_t has quit IRC
2682016-01-20T09:21:45  <murch> Good morning. I started running 0.12rc01 recently. Today my node was not running, it was reporting a corrupted database. debug.log only appears to have the last hour, is there anything else useful that I can provide for more information?
2692016-01-20T09:23:58  <murch> https://github.com/bitcoin/bitcoin/issues/7382
2702016-01-20T09:51:04  *** guruvan has joined #bitcoin-core-dev
2712016-01-20T09:54:08  *** BananaLotus has joined #bitcoin-core-dev
2722016-01-20T10:28:43  *** kang_ has joined #bitcoin-core-dev
2732016-01-20T10:29:28  <wumpus> MarcoFalke, you lost coins to that bug?
2742016-01-20T10:34:47  <MarcoFalke> Only cheap altcoins where it is not worth to backup
2752016-01-20T10:35:04  <MarcoFalke> And travis lost regcoins
2762016-01-20T10:35:18  <MarcoFalke> See issue 7379
2772016-01-20T10:41:23  *** randy-waterhouse has quit IRC
2782016-01-20T10:41:51  *** Chris_Stewart_5 has quit IRC
2792016-01-20T10:48:50  <wumpus> it's strange that the problem seems to happen intermittently
2802016-01-20T10:51:43  <MarcoFalke> Not all keys have value. You won't detect it if you lose keys without value.
2812016-01-20T10:52:18  <wumpus> right
2822016-01-20T11:05:53  *** wallet42 has joined #bitcoin-core-dev
2832016-01-20T11:18:36  *** wallet42 has quit IRC
2842016-01-20T11:29:02  *** Alina-malina has joined #bitcoin-core-dev
2852016-01-20T11:30:36  *** Thireus has joined #bitcoin-core-dev
2862016-01-20T11:38:12  *** Alina-malina has left #bitcoin-core-dev
2872016-01-20T11:48:42  *** Guyver2 has joined #bitcoin-core-dev
2882016-01-20T11:52:09  *** ronbo has quit IRC
2892016-01-20T12:05:05  <jonasschnelli> #7382 reminded me that we where once looking for alternatives for leveldb. What was the sqlite result? to slow?
2902016-01-20T12:08:28  <GitHub147> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f9fd4c288484...545c5f920ebb
2912016-01-20T12:08:28  <GitHub147> bitcoin/master fa6d4cc MarcoFalke: [walletdb] Fix syntax error in key parser
2922016-01-20T12:08:29  <GitHub147> bitcoin/master 545c5f9 Wladimir J. van der Laan: Merge #7381: [walletdb] Fix syntax error in key parser...
2932016-01-20T12:08:33  <GitHub12> [bitcoin] laanwj closed pull request #7381: [walletdb] Fix syntax error in key parser (master...Mf1601-walletdbKeyparserFix) https://github.com/bitcoin/bitcoin/pull/7381
2942016-01-20T12:09:33  <GitHub17> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/621bbd88baf7e8f50a015905070e19f71a53f8b9
2952016-01-20T12:09:33  <GitHub17> bitcoin/0.12 621bbd8 MarcoFalke: [walletdb] Fix syntax error in key parser...
2962016-01-20T12:09:59  <GitHub86> [bitcoin] laanwj pushed 1 new commit to 0.11: https://github.com/bitcoin/bitcoin/commit/c40ec1421048e7ddb9eb1878e4c65ff27aa066c8
2972016-01-20T12:09:59  <GitHub86> bitcoin/0.11 c40ec14 MarcoFalke: [walletdb] Fix syntax error in key parser...
2982016-01-20T12:10:28  <GitHub123> [bitcoin] laanwj pushed 1 new commit to 0.10: https://github.com/bitcoin/bitcoin/commit/b0c97ce31a93caa0037c67a0dc133b8873911070
2992016-01-20T12:10:28  <GitHub123> bitcoin/0.10 b0c97ce MarcoFalke: [walletdb] Fix syntax error in key parser...
3002016-01-20T12:11:47  *** GAit has joined #bitcoin-core-dev
3012016-01-20T12:16:44  <GitHub24> [bitcoin] laanwj closed pull request #6700: bloom_tests: Do not depend on specific serialisations (master...bloom_tests_not_ser) https://github.com/bitcoin/bitcoin/pull/6700
3022016-01-20T12:22:58  *** davec has quit IRC
3032016-01-20T12:24:08  *** davec has joined #bitcoin-core-dev
3042016-01-20T12:25:32  <GitHub114> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/545c5f920ebb...53fa09f04d96
3052016-01-20T12:25:33  <GitHub42> [bitcoin] laanwj closed pull request #7060: build: Make networking work inside LXC builder in gitian-building.md (master...2015_11_gitian_building) https://github.com/bitcoin/bitcoin/pull/7060
3062016-01-20T12:25:33  <GitHub114> bitcoin/master 99fda26 Wladimir J. van der Laan: doc: Make networking work inside builder in gitian-building.md...
3072016-01-20T12:25:34  <GitHub114> bitcoin/master 3b468a0 Wladimir J. van der Laan: gitian: Need `ca-certificates` and `python` for LXC builds
3082016-01-20T12:25:34  <GitHub114> bitcoin/master 53fa09f Wladimir J. van der Laan: Merge #7060: build: Make networking work inside LXC builder in gitian-building.md...
3092016-01-20T12:27:05  *** murch has quit IRC
3102016-01-20T12:27:29  <GitHub20> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/5bb3e263e25077cd02e6f425468ad8823f0cdd7f
3112016-01-20T12:27:30  <GitHub20> bitcoin/0.12 5bb3e26 Wladimir J. van der Laan: build: Make networking work inside LXC builder in gitian-building.md...
3122016-01-20T12:29:09  <GitHub37> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/53fa09f04d96...f48e59df0a9d
3132016-01-20T12:29:10  <GitHub37> bitcoin/master b07b103 BtcDrak: Update project URL
3142016-01-20T12:29:10  <GitHub37> bitcoin/master f48e59d Wladimir J. van der Laan: Merge #7328: Update README.md website link...
3152016-01-20T12:29:19  <GitHub15> [bitcoin] laanwj closed pull request #7328: Update README.md website link (master...website) https://github.com/bitcoin/bitcoin/pull/7328
3162016-01-20T12:32:10  <GitHub175> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/64612f182036cf18c1aef45b88fb284c11b35680
3172016-01-20T12:32:10  <GitHub175> bitcoin/0.12 64612f1 BtcDrak: Update project URL...
3182016-01-20T12:39:01  <GitHub45> [bitcoin] laanwj pushed 6 new commits to master: https://github.com/bitcoin/bitcoin/compare/f48e59df0a9d...55781444130c
3192016-01-20T12:39:02  <GitHub45> bitcoin/master 57c77fe Philip Kaufmann: banlist: update set dirty to be more fine grained...
3202016-01-20T12:39:03  <GitHub45> bitcoin/master ce479aa Philip Kaufmann: banlist: better handling of banlist in StartNode()...
3212016-01-20T12:39:04  <GitHub45> bitcoin/master 2977c24 Philip Kaufmann: banlist: add more banlist infos to log / add GUI signal...
3222016-01-20T12:39:06  <GitHub131> [bitcoin] laanwj closed pull request #7350: Banlist updates (master...20150703_banlist_updates) https://github.com/bitcoin/bitcoin/pull/7350
3232016-01-20T12:39:50  <GitHub148> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/55781444130c...e6f97efbca63
3242016-01-20T12:39:51  <GitHub148> bitcoin/master da6d18b Wladimir J. van der Laan: devtools: replace github-merge with python version...
3252016-01-20T12:39:51  <GitHub148> bitcoin/master e6f97ef Wladimir J. van der Laan: Merge pull request #7378...
3262016-01-20T12:39:58  <GitHub75> [bitcoin] laanwj closed pull request #7378: devtools: replace github-merge with python version (master...2016_01_python_github_merge) https://github.com/bitcoin/bitcoin/pull/7378
3272016-01-20T12:47:15  *** GAit has quit IRC
3282016-01-20T12:50:58  <GitHub69> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e6f97efbca63...82429d08610e
3292016-01-20T12:50:58  <GitHub69> bitcoin/master eaa8d27 Suhas Daftuar: RPC: indicate which transactions are replaceable...
3302016-01-20T12:50:59  <GitHub69> bitcoin/master 82429d0 Wladimir J. van der Laan: Merge #7222: RPC: Indicate which transactions are signaling opt-in RBF...
3312016-01-20T12:51:03  <GitHub167> [bitcoin] laanwj closed pull request #7222: RPC: Indicate which transactions are signaling opt-in RBF (master...add-optin-info) https://github.com/bitcoin/bitcoin/pull/7222
3322016-01-20T12:51:33  <GitHub135> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/e25b158ab8812abaad2a83b04db6b821154a6a0f
3332016-01-20T12:51:33  <GitHub135> bitcoin/0.12 e25b158 Suhas Daftuar: RPC: indicate which transactions are replaceable...
3342016-01-20T12:51:53  <GitHub155> [bitcoin] laanwj closed pull request #7151: Revert default block priority size to 50k (master...revert_priodef) https://github.com/bitcoin/bitcoin/pull/7151
3352016-01-20T13:00:52  <GitHub150> [bitcoin] laanwj closed pull request #7169: [Trivial] Disable compiler warnings about unused functions (master...20151204_scheduler_tests_warning) https://github.com/bitcoin/bitcoin/pull/7169
3362016-01-20T13:05:39  *** AndChat|221969 has quit IRC
3372016-01-20T13:08:26  <jonasschnelli> Anyone interested in testing: https://github.com/bitcoin/bitcoin/pull/7307/files
3382016-01-20T13:10:24  <wumpus> jonasschnelli, it's one of the next pulls I plan on looking at
3392016-01-20T13:10:34  <jonasschnelli> Nice. Thanks!
3402016-01-20T13:11:55  <wumpus> it's a one step towards getting rid of #ifdef DISABLE_WALLETs in bitcoin_server code, which currently causes a circular dependency between the server and the wallet libraries
3412016-01-20T13:15:03  <jonasschnelli> wumpus: Yes. I have some changes that fully removes #ifdef DISABLE_WALLET
3422016-01-20T13:15:25  <jonasschnelli> So.. I'm slowly picking out parts, carefully rewrite them and submit them as sep. PR.
3432016-01-20T13:15:53  <jonasschnelli> Otherwise the review burden is to heigh.
3442016-01-20T13:15:56  <wumpus> yes, doing this step by step is good
3452016-01-20T13:17:20  <GitHub41> [bitcoin] laanwj closed pull request #7359: Disable SSLv3 for QT < 5.5 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/7359
3462016-01-20T13:19:20  *** ronbo has joined #bitcoin-core-dev
3472016-01-20T13:20:34  *** Guyver2 has quit IRC
3482016-01-20T13:42:41  *** p15x has joined #bitcoin-core-dev
3492016-01-20T13:47:15  *** PRab_ has joined #bitcoin-core-dev
3502016-01-20T13:48:14  *** p15x_ has joined #bitcoin-core-dev
3512016-01-20T13:49:00  *** geemon has joined #bitcoin-core-dev
3522016-01-20T13:51:12  *** [\\\] has joined #bitcoin-core-dev
3532016-01-20T13:51:16  *** harding_ has joined #bitcoin-core-dev
3542016-01-20T13:51:31  *** _mm_1 has joined #bitcoin-core-dev
3552016-01-20T13:51:34  *** crescendo has joined #bitcoin-core-dev
3562016-01-20T13:51:35  *** sotisoti_ has joined #bitcoin-core-dev
3572016-01-20T13:51:40  *** roasbeef_ has joined #bitcoin-core-dev
3582016-01-20T13:51:52  *** dagurval_ has joined #bitcoin-core-dev
3592016-01-20T13:53:21  *** mr_burdell_ has joined #bitcoin-core-dev
3602016-01-20T13:54:16  *** da2ce7_ has joined #bitcoin-core-dev
3612016-01-20T13:55:08  *** lclc_ has joined #bitcoin-core-dev
3622016-01-20T13:55:16  *** afk11_ has joined #bitcoin-core-dev
3632016-01-20T13:55:16  *** Prattler_ has joined #bitcoin-core-dev
3642016-01-20T13:56:00  *** ronbo has quit IRC
3652016-01-20T13:56:01  *** p15x has quit IRC
3662016-01-20T13:56:01  *** p15 has quit IRC
3672016-01-20T13:56:02  *** afk11 has quit IRC
3682016-01-20T13:56:02  *** tripleslash has quit IRC
3692016-01-20T13:56:05  *** da2ce7 has quit IRC
3702016-01-20T13:56:05  *** Yoghur114 has quit IRC
3712016-01-20T13:56:05  *** Amnez777 has quit IRC
3722016-01-20T13:56:07  *** amiller has quit IRC
3732016-01-20T13:56:07  *** isis has quit IRC
3742016-01-20T13:56:08  *** crescend1 has quit IRC
3752016-01-20T13:56:08  *** haakonn has quit IRC
3762016-01-20T13:56:09  *** gmaxwell has quit IRC
3772016-01-20T13:56:11  *** sotisoti has quit IRC
3782016-01-20T13:56:11  *** dagurval has quit IRC
3792016-01-20T13:56:11  *** roasbeef has quit IRC
3802016-01-20T13:56:12  *** BananaLotus has quit IRC
3812016-01-20T13:56:14  *** PRab has quit IRC
3822016-01-20T13:56:14  *** Prattler has quit IRC
3832016-01-20T13:56:15  *** harding has quit IRC
3842016-01-20T13:56:17  *** pmienk has quit IRC
3852016-01-20T13:56:17  *** mr_burdell has quit IRC
3862016-01-20T13:56:19  *** lclc has quit IRC
3872016-01-20T13:56:19  *** [b__b] has quit IRC
3882016-01-20T13:56:19  *** mm_1 has quit IRC
3892016-01-20T13:56:21  *** devrandom has quit IRC
3902016-01-20T13:56:23  *** Prattler_ is now known as Prattler
3912016-01-20T13:56:24  *** _mm_1 is now known as mm_1
3922016-01-20T13:56:24  *** afk11_ is now known as afk11
3932016-01-20T13:56:26  *** mr_burdell_ is now known as mr_burdell
3942016-01-20T13:56:30  *** Yoghur114 has joined #bitcoin-core-dev
3952016-01-20T13:56:55  *** zookolaptop has joined #bitcoin-core-dev
3962016-01-20T13:56:56  *** BananaLotus has joined #bitcoin-core-dev
3972016-01-20T13:56:56  *** mr_burdell is now known as Guest75253
3982016-01-20T13:57:22  *** devrandom has joined #bitcoin-core-dev
3992016-01-20T13:57:56  *** gmaxwell has joined #bitcoin-core-dev
4002016-01-20T13:58:22  *** gmaxwell is now known as Guest57119
4012016-01-20T13:58:26  *** Amnez777 has joined #bitcoin-core-dev
4022016-01-20T13:58:56  *** isis has joined #bitcoin-core-dev
4032016-01-20T13:59:10  *** amiller_ has joined #bitcoin-core-dev
4042016-01-20T14:00:49  *** Amnez777 has quit IRC
4052016-01-20T14:00:49  *** Amnez777 has joined #bitcoin-core-dev
4062016-01-20T14:01:18  <GitHub3> [bitcoin] jonasschnelli opened pull request #7383: [Qt] rename "amount" to "received amount" in receive coins table (master...2016/01/qt_req_amount) https://github.com/bitcoin/bitcoin/pull/7383
4072016-01-20T14:01:32  *** [b__b] has joined #bitcoin-core-dev
4082016-01-20T14:04:04  *** pmienk has joined #bitcoin-core-dev
4092016-01-20T14:04:16  *** rsx has joined #bitcoin-core-dev
4102016-01-20T14:16:32  <GitHub73> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/9982710e88687706686bb132d3737ce3befd8eeb
4112016-01-20T14:16:32  <GitHub73> bitcoin/master 9982710 Wladimir J. van der Laan: Merge #7307: [RPC, Wallet] Move RPC dispatch table registration to wallet/ code...
4122016-01-20T14:16:36  <GitHub117> [bitcoin] laanwj closed pull request #7307: [RPC, Wallet] Move RPC dispatch table registration to wallet/ code (master...2016/01/corewallet) https://github.com/bitcoin/bitcoin/pull/7307
4132016-01-20T14:18:30  *** geemon has quit IRC
4142016-01-20T14:21:49  *** frankenmint has joined #bitcoin-core-dev
4152016-01-20T14:23:55  *** treehug88 has joined #bitcoin-core-dev
4162016-01-20T14:28:20  <Yoghur114> is there a reason things like 'free transaction rejected by rate limiter', 'inputs already spent', 'nonstandard transaction: dust', etc. log messages are logged as an error?
4172016-01-20T14:31:00  <jonasschnelli> Yoghur114: Agree. This is not ideal.
4182016-01-20T14:31:09  <jonasschnelli> Should be a INFO:
4192016-01-20T14:31:24  <jonasschnelli> Feel free to change it. :)
4202016-01-20T14:39:58  *** T23WS_ has quit IRC
4212016-01-20T14:43:30  <wumpus> Yoghur114: that should be no longer the case with 0.12
4222016-01-20T14:44:29  <wumpus> by default, validation errors for incoming P2P transactions aren't even logged anymore, unless -debug=mempoolrej is set, in which case you get a debug message not an ERROR
4232016-01-20T14:50:22  *** d_t has joined #bitcoin-core-dev
4242016-01-20T14:52:53  *** kang_ has quit IRC
4252016-01-20T14:55:26  <GitHub19> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/9982710e8868...b92ea98503e6
4262016-01-20T14:55:26  <GitHub19> bitcoin/master 96efcad Murch: Improved readability of sorting for coin selection....
4272016-01-20T14:55:27  <GitHub19> bitcoin/master b92ea98 Wladimir J. van der Laan: Merge #7183: Improved readability of ApproximateBestSubset...
4282016-01-20T14:55:30  <GitHub182> [bitcoin] laanwj closed pull request #7183: Improved readability of ApproximateBestSubset (master...Fix-#7182) https://github.com/bitcoin/bitcoin/pull/7183
4292016-01-20T14:57:05  *** GAit has joined #bitcoin-core-dev
4302016-01-20T14:58:50  *** laurentmt has joined #bitcoin-core-dev
4312016-01-20T15:01:10  *** p15x_ has quit IRC
4322016-01-20T15:02:19  *** T23WS has joined #bitcoin-core-dev
4332016-01-20T15:03:49  <Yoghur114> wumpus: oh - great :)
4342016-01-20T15:04:29  *** laurentmt has quit IRC
4352016-01-20T15:13:12  *** T23WS has quit IRC
4362016-01-20T15:13:43  *** rsx has quit IRC
4372016-01-20T15:17:06  *** drnet has joined #bitcoin-core-dev
4382016-01-20T15:22:07  *** T23WS has joined #bitcoin-core-dev
4392016-01-20T15:42:57  *** GAit has quit IRC
4402016-01-20T15:43:52  *** T23WS_ has joined #bitcoin-core-dev
4412016-01-20T15:46:30  *** T23WS has quit IRC
4422016-01-20T15:48:48  *** zookolaptop has quit IRC
4432016-01-20T15:51:56  *** GAit has joined #bitcoin-core-dev
4442016-01-20T15:54:13  *** Guest87 has joined #bitcoin-core-dev
4452016-01-20T15:58:45  *** GAit has quit IRC
4462016-01-20T15:58:48  *** Guest87 has quit IRC
4472016-01-20T16:06:14  *** GAit has joined #bitcoin-core-dev
4482016-01-20T16:20:21  *** treehug88 has quit IRC
4492016-01-20T16:23:33  *** zookolaptop has joined #bitcoin-core-dev
4502016-01-20T16:33:07  *** treehug88 has joined #bitcoin-core-dev
4512016-01-20T16:35:20  *** laurentmt has joined #bitcoin-core-dev
4522016-01-20T16:37:56  *** drnet has quit IRC
4532016-01-20T16:40:22  *** laurentmt has quit IRC
4542016-01-20T16:50:54  *** GAit has quit IRC
4552016-01-20T16:54:25  *** GAit has joined #bitcoin-core-dev
4562016-01-20T16:58:29  *** T23WS has joined #bitcoin-core-dev
4572016-01-20T17:00:45  *** T23WS_ has quit IRC
4582016-01-20T17:02:46  *** murch has joined #bitcoin-core-dev
4592016-01-20T17:03:31  *** BashCo has quit IRC
4602016-01-20T17:05:56  *** d_t has quit IRC
4612016-01-20T17:11:15  *** GAit has quit IRC
4622016-01-20T17:12:05  *** paveljanik has joined #bitcoin-core-dev
4632016-01-20T17:12:05  *** GAit has joined #bitcoin-core-dev
4642016-01-20T17:16:20  *** GAit has quit IRC
4652016-01-20T17:16:58  *** GAit has joined #bitcoin-core-dev
4662016-01-20T17:19:30  *** NLNico has quit IRC
4672016-01-20T17:34:03  *** haakonn has joined #bitcoin-core-dev
4682016-01-20T17:36:09  *** GAit has quit IRC
4692016-01-20T17:36:25  *** haakonn has quit IRC
4702016-01-20T17:36:47  *** BashCo has joined #bitcoin-core-dev
4712016-01-20T17:41:34  <Luke-Jr> hmm
4722016-01-20T17:41:56  <Luke-Jr> single we have the dust rule nowadays, would it make sense to require transactions with an OP_RETURN to have <dust> more tx fee?
4732016-01-20T17:42:02  <Luke-Jr> s/single/since*
4742016-01-20T17:42:23  <Luke-Jr> maybe too trivial to matter
4752016-01-20T17:49:56  *** brg444 has joined #bitcoin-core-dev
4762016-01-20T17:54:24  *** GAit has joined #bitcoin-core-dev
4772016-01-20T18:04:30  *** zookolaptop has quit IRC
4782016-01-20T18:06:14  *** GAit has quit IRC
4792016-01-20T18:14:39  *** zookolaptop has joined #bitcoin-core-dev
4802016-01-20T18:15:56  *** Chris_Stewart_5 has joined #bitcoin-core-dev
4812016-01-20T18:16:10  *** warren_ has joined #bitcoin-core-dev
4822016-01-20T18:16:14  *** zookolaptop has joined #bitcoin-core-dev
4832016-01-20T18:17:29  *** petertod1 has joined #bitcoin-core-dev
4842016-01-20T18:17:42  *** lclc_ is now known as lclc
4852016-01-20T18:17:57  *** sdaftuar_ has joined #bitcoin-core-dev
4862016-01-20T18:18:00  *** morcos_ has joined #bitcoin-core-dev
4872016-01-20T18:20:37  *** jl2012_ has joined #bitcoin-core-dev
4882016-01-20T18:22:01  *** afk11 has quit IRC
4892016-01-20T18:22:02  *** warren has quit IRC
4902016-01-20T18:22:03  *** jl2012 has quit IRC
4912016-01-20T18:22:04  *** morcos has quit IRC
4922016-01-20T18:22:05  *** sdaftuar has quit IRC
4932016-01-20T18:22:06  *** petertodd has quit IRC
4942016-01-20T18:22:06  *** jl2012_ is now known as jl2012
4952016-01-20T18:23:37  *** afk11 has joined #bitcoin-core-dev
4962016-01-20T18:27:20  *** sdaftuar_ is now known as sdaftuar
4972016-01-20T18:29:32  *** Guyver2 has joined #bitcoin-core-dev
4982016-01-20T18:32:58  *** zookolaptop has quit IRC
4992016-01-20T18:34:57  *** zookolaptop has joined #bitcoin-core-dev
5002016-01-20T18:36:40  *** zookolaptop has quit IRC
5012016-01-20T18:37:22  *** zookolaptop has joined #bitcoin-core-dev
5022016-01-20T18:41:05  *** T23WS has quit IRC
5032016-01-20T18:42:01  *** dagurval_ is now known as dagurval
5042016-01-20T18:56:24  *** cryptojonathan has joined #bitcoin-core-dev
5052016-01-20T18:58:36  *** brg444 has quit IRC
5062016-01-20T18:58:36  *** brg444 has joined #bitcoin-core-dev
5072016-01-20T18:59:18  *** jl2012 has quit IRC
5082016-01-20T18:59:18  *** jl2012 has joined #bitcoin-core-dev
5092016-01-20T19:01:39  *** morcos_ is now known as morcos
5102016-01-20T19:14:33  *** warren_ is now known as warren
5112016-01-20T19:17:24  *** neilf has joined #bitcoin-core-dev
5122016-01-20T19:40:21  *** Guest57119 has quit IRC
5132016-01-20T19:40:22  *** Guest57119 has joined #bitcoin-core-dev
5142016-01-20T19:40:34  *** Guest57119 is now known as gmaxwell
5152016-01-20T19:41:18  *** zookolaptop has quit IRC
5162016-01-20T19:41:34  *** cryptojonathan has quit IRC
5172016-01-20T19:53:39  *** drnet has joined #bitcoin-core-dev
5182016-01-20T19:58:34  *** haakonn has joined #bitcoin-core-dev
5192016-01-20T20:04:13  *** frankenmint has quit IRC
5202016-01-20T20:07:11  *** zookolaptop has joined #bitcoin-core-dev
5212016-01-20T20:10:24  *** drnet has quit IRC
5222016-01-20T20:10:31  <GitHub101> [bitcoin] MarcoFalke closed pull request #6696: [wallet] Adjust MIN_CHANGE (master...MarcoFalke-2015-walletFixMinChange) https://github.com/bitcoin/bitcoin/pull/6696
5232016-01-20T20:17:13  *** MarcoFalke has quit IRC
5242016-01-20T20:24:08  *** treehug88 has quit IRC
5252016-01-20T20:26:34  *** MarcoFalke has joined #bitcoin-core-dev
5262016-01-20T20:39:48  *** dcousens has joined #bitcoin-core-dev
5272016-01-20T20:40:40  *** treehug88 has joined #bitcoin-core-dev
5282016-01-20T20:51:46  *** arowser has quit IRC
5292016-01-20T20:52:17  *** arowser has joined #bitcoin-core-dev
5302016-01-20T20:58:04  *** zookolaptop has quit IRC
5312016-01-20T20:58:51  *** ronbo has joined #bitcoin-core-dev
5322016-01-20T21:05:22  *** Thireus has quit IRC
5332016-01-20T21:09:29  *** [\\\] is now known as tripleslash
5342016-01-20T21:25:07  *** paveljanik has quit IRC
5352016-01-20T21:26:31  *** cryptojonathan has joined #bitcoin-core-dev
5362016-01-20T21:36:27  *** Thireus has joined #bitcoin-core-dev
5372016-01-20T21:41:32  *** randy-waterhouse has joined #bitcoin-core-dev
5382016-01-20T21:51:53  *** zookolaptop has joined #bitcoin-core-dev
5392016-01-20T21:58:27  *** treehug88 has quit IRC
5402016-01-20T22:01:24  *** zookolaptop is now known as zooko
5412016-01-20T22:05:47  *** frankenmint has joined #bitcoin-core-dev
5422016-01-20T22:10:12  *** frankenmint has quit IRC
5432016-01-20T22:14:23  *** MarcoFalke has quit IRC
5442016-01-20T22:17:18  *** laurentmt has joined #bitcoin-core-dev
5452016-01-20T22:18:35  *** laurentmt has quit IRC
5462016-01-20T22:20:24  <morcos> As anyone ever tried downgrading from 0.12
5472016-01-20T22:20:36  *** Guyver2 has quit IRC
5482016-01-20T22:20:41  <morcos> I just tried (in order to try to replicate the pruning issue 7382)
5492016-01-20T22:20:46  <morcos> And I got this error:
5502016-01-20T22:20:51  <morcos> main.cpp:1836: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.
5512016-01-20T22:29:24  *** Cory has joined #bitcoin-core-dev
5522016-01-20T22:49:44  <morcos> wumpus: sipa: sdaftuar: See this ^
5532016-01-20T22:51:15  <morcos> This seems suspiciously like something I might have introduce with messing around with ModifyNewCoins and BatchWrite in PR's 5967 and 6932
5542016-01-20T22:52:08  <morcos> But I couldn't see antyhing in a quick scan.  For some reason I added a check to make sure hashBlock wasn't NULL in the coins_tests.cpp  No idea why now.  But the test passes without that.
5552016-01-20T22:52:31  <phantomcircuit> wumpus, 192.99.46.190/debug.log.tail.xz
5562016-01-20T22:52:33  <morcos> I will try to look more if I get a chance, but won't be around the computer too much.
5572016-01-20T22:53:49  <morcos> phantomcircuit: is that your pruning issue?
5582016-01-20T22:54:05  <morcos> did you have that with just 0.12 or was it also on the upgrade from 0.11.2 to 0.12?
5592016-01-20T22:54:06  <phantomcircuit> i dont think it's pruning related actually
5602016-01-20T22:54:41  <morcos> ok interesting...
5612016-01-20T22:59:17  *** murch has quit IRC
5622016-01-20T23:00:40  *** cryptojonathan has quit IRC
5632016-01-20T23:04:11  *** bsm117532 has quit IRC
5642016-01-20T23:04:47  *** instagibbs has quit IRC
5652016-01-20T23:05:36  *** instagibbs has joined #bitcoin-core-dev
5662016-01-20T23:06:52  *** frankenmint has joined #bitcoin-core-dev
5672016-01-20T23:12:06  *** frankenmint has quit IRC
5682016-01-20T23:18:23  *** Thireus has quit IRC
5692016-01-20T23:19:39  *** zooko is now known as zooko|afk
5702016-01-20T23:22:27  *** GAit has joined #bitcoin-core-dev
5712016-01-20T23:28:21  <cfields> morcos: sure it's not the obfuscated chainstate messing you up?
5722016-01-20T23:33:52  *** blur3d has joined #bitcoin-core-dev
5732016-01-20T23:40:44  *** bsm117532 has joined #bitcoin-core-dev
5742016-01-20T23:44:00  *** petertod1 is now known as petertodd
5752016-01-20T23:44:12  *** blur3d has quit IRC
5762016-01-20T23:44:52  *** drnet has joined #bitcoin-core-dev
5772016-01-20T23:46:03  *** GAit has quit IRC
5782016-01-20T23:47:06  *** GAit has joined #bitcoin-core-dev
5792016-01-20T23:47:06  *** dcousens has quit IRC
5802016-01-20T23:54:51  *** dcousens has joined #bitcoin-core-dev