12017-03-08T00:11:21  *** tripleslash has joined #bitcoin-core-dev
  22017-03-08T00:17:40  <cfields> gitian builders: v0.14.0 detached sigs are pushed
  32017-03-08T00:29:13  *** Chris_Stewart_5 has joined #bitcoin-core-dev
  42017-03-08T00:46:09  *** droark has joined #bitcoin-core-dev
  52017-03-08T00:57:22  *** slsdhl has quit IRC
  62017-03-08T00:59:54  *** abpa has quit IRC
  72017-03-08T01:01:15  <midnightmagic> cfields: \o thanks
  82017-03-08T01:09:39  *** gkhan__ has joined #bitcoin-core-dev
  92017-03-08T01:12:00  *** gkhan__ has quit IRC
 102017-03-08T01:23:21  *** dstadulis has joined #bitcoin-core-dev
 112017-03-08T01:24:58  *** harrymm1 has joined #bitcoin-core-dev
 122017-03-08T01:27:57  *** harrymm has quit IRC
 132017-03-08T01:44:04  *** Ylbam has quit IRC
 142017-03-08T02:45:41  *** dstadulis has quit IRC
 152017-03-08T02:46:56  *** wudayoda has quit IRC
 162017-03-08T03:17:07  *** Chris_Stewart_5 has quit IRC
 172017-03-08T03:28:09  *** Victor_sueca has joined #bitcoin-core-dev
 182017-03-08T03:30:28  *** Victorsueca has quit IRC
 192017-03-08T04:02:27  *** dodomojo has joined #bitcoin-core-dev
 202017-03-08T04:03:24  *** dodomojo has quit IRC
 212017-03-08T04:06:18  *** pedrobranco has joined #bitcoin-core-dev
 222017-03-08T04:06:38  *** dodomojo has joined #bitcoin-core-dev
 232017-03-08T04:10:38  *** pedrobranco has quit IRC
 242017-03-08T04:40:52  *** dodomojo has quit IRC
 252017-03-08T04:47:30  *** wudayoda has joined #bitcoin-core-dev
 262017-03-08T04:48:30  *** PRab has quit IRC
 272017-03-08T04:49:48  *** PRab has joined #bitcoin-core-dev
 282017-03-08T04:52:08  *** wudayoda has quit IRC
 292017-03-08T05:10:52  *** JackH has quit IRC
 302017-03-08T05:36:40  *** dstadulis has joined #bitcoin-core-dev
 312017-03-08T05:39:05  *** dstadulis has quit IRC
 322017-03-08T05:56:31  *** justanotheruser has joined #bitcoin-core-dev
 332017-03-08T05:57:07  *** [Author] has quit IRC
 342017-03-08T05:58:28  *** justan0theruser has quit IRC
 352017-03-08T06:04:20  *** Cheeseo has joined #bitcoin-core-dev
 362017-03-08T06:04:21  *** Cheeseo has joined #bitcoin-core-dev
 372017-03-08T06:06:52  *** warren has quit IRC
 382017-03-08T06:06:58  *** RoyceX has quit IRC
 392017-03-08T06:08:38  *** adam3us has quit IRC
 402017-03-08T06:16:42  *** adam3us has joined #bitcoin-core-dev
 412017-03-08T06:17:11  *** warren has joined #bitcoin-core-dev
 422017-03-08T06:22:31  <wumpus> all gitian signatures match this time, this is great
 432017-03-08T06:25:14  <wumpus> thanks cfields
 442017-03-08T06:32:30  *** [Author] has joined #bitcoin-core-dev
 452017-03-08T06:34:50  <sipa> awesome!
 462017-03-08T06:37:38  * gmaxwell reloads the mailing list archive webpage
 472017-03-08T06:48:29  *** wudayoda has joined #bitcoin-core-dev
 482017-03-08T06:49:30  *** pedrobranco has joined #bitcoin-core-dev
 492017-03-08T06:53:24  *** wudayoda has quit IRC
 502017-03-08T06:54:00  *** pedrobranco has quit IRC
 512017-03-08T06:58:48  *** phantomcircuit has quit IRC
 522017-03-08T07:10:06  *** phantomcircuit has joined #bitcoin-core-dev
 532017-03-08T07:11:59  *** arubi has quit IRC
 542017-03-08T07:11:59  *** wasi has quit IRC
 552017-03-08T07:11:59  *** afk11 has quit IRC
 562017-03-08T07:12:14  *** afk11 has joined #bitcoin-core-dev
 572017-03-08T07:12:22  *** arubi has joined #bitcoin-core-dev
 582017-03-08T07:12:25  *** wasi has joined #bitcoin-core-dev
 592017-03-08T07:34:27  <warren> anyone having problems with gitian where it gets stuck at "Checking if target is up"  ?
 602017-03-08T07:37:26  *** BashCo has quit IRC
 612017-03-08T07:43:14  <jonasschnelli> warren: what are you using LXC/KVM?
 622017-03-08T07:43:35  <jonasschnelli> warren: maybe check the gitian-builder/logs directory. Cat target.log / install.log
 632017-03-08T07:46:18  <warren> KVM ... qemu-system-x86_64 gets stuck with 100% CPU usage, target.log is blank
 642017-03-08T08:04:24  *** BashCo has joined #bitcoin-core-dev
 652017-03-08T08:24:59  <sipa> on what hardware
 662017-03-08T08:25:01  <sipa> ?
 672017-03-08T08:31:01  <sipa> in particular: do you have hardware acceleration?
 682017-03-08T08:31:18  <sipa> if running inside a VM, it may be resorting to software emulation
 692017-03-08T08:31:24  *** Guyver2 has joined #bitcoin-core-dev
 702017-03-08T08:45:30  <warren> model name      : Intel(R) Core(TM) i5-4690S CPU @ 3.20GHz
 712017-03-08T08:45:50  <warren> used KVM on this hardware before, I'll figure it out
 722017-03-08T08:49:23  *** wudayoda has joined #bitcoin-core-dev
 732017-03-08T08:49:47  *** JackH has joined #bitcoin-core-dev
 742017-03-08T08:53:27  *** wudayoda has quit IRC
 752017-03-08T09:04:56  *** Ylbam has joined #bitcoin-core-dev
 762017-03-08T09:28:22  <jonasschnelli> prioritisetransaction <txid> 0 100000000 should lead to (always) include the transaction in the next getblocktemplate call, right?
 772017-03-08T09:29:59  <gmaxwell> no, due to caching.
 782017-03-08T09:30:20  <gmaxwell> if the block doesn't change IIRC we'll cache the CNB result for up to 30 seconds.
 792017-03-08T09:30:41  <jonasschnelli> Is there a way to drain the cache?
 802017-03-08T09:30:52  <gmaxwell> mine a new block.
 812017-03-08T09:31:10  <gmaxwell> don't call getblocktemplate for (IIRC) 30 seconds before.
 822017-03-08T09:31:53  <jonasschnelli> okay... thanks gmaxwell!
 832017-03-08T09:32:09  <gmaxwell> Sorry I don't have a more useful suggestion!
 842017-03-08T09:33:25  <jonasschnelli> Well... that's already useful. I know now why.
 852017-03-08T09:36:58  *** JackH has quit IRC
 862017-03-08T09:39:46  *** BashCo_ has joined #bitcoin-core-dev
 872017-03-08T09:43:09  *** BashCo has quit IRC
 882017-03-08T09:45:05  <Lauda> ping wumpus
 892017-03-08T09:48:10  <gmaxwell> what is the gpg undocumented option to restrict recv-key to only fetch a key it already knows?
 902017-03-08T09:48:48  *** belcher has quit IRC
 912017-03-08T09:54:35  *** Victor_sueca is now known as Victorsueca
 922017-03-08T09:55:08  <gmaxwell> --refresh-keys ah ha
 932017-03-08T09:55:12  <gmaxwell> Lauda: thanks
 942017-03-08T09:59:03  *** belcher has joined #bitcoin-core-dev
 952017-03-08T10:02:24  <bitcoin-git> [bitcoin] jonasschnelli opened pull request #9947: Add true/false return value to prioritisetransaction (master...2017/03/ptx) https://github.com/bitcoin/bitcoin/pull/9947
 962017-03-08T10:26:18  *** pedrobranco has joined #bitcoin-core-dev
 972017-03-08T10:31:51  *** Victorsueca has quit IRC
 982017-03-08T10:32:59  *** Victorsueca has joined #bitcoin-core-dev
 992017-03-08T10:33:10  *** norotartagen has quit IRC
1002017-03-08T10:34:25  <Lauda> You're welcome.
1012017-03-08T10:46:02  *** slsdhl has joined #bitcoin-core-dev
1022017-03-08T10:49:59  *** wudayoda has joined #bitcoin-core-dev
1032017-03-08T10:53:07  *** dcousens_ has joined #bitcoin-core-dev
1042017-03-08T10:53:35  *** BashCo has joined #bitcoin-core-dev
1052017-03-08T10:54:22  *** paulyb has joined #bitcoin-core-dev
1062017-03-08T10:54:27  *** wudayoda has quit IRC
1072017-03-08T10:56:04  *** BashCo_ has quit IRC
1082017-03-08T10:58:51  <jonasschnelli> Should we allow to add a fee delta on txn's that are not in the mempool, ... right now we do. I hink we can't change that behavior..
1092017-03-08T10:59:01  *** norotartagen has joined #bitcoin-core-dev
1102017-03-08T10:59:35  <dcousens_> Yeah,  I personally use the current behaviour of "CAmount &delta = mapDeltas[hash]; delta += nFeeDelta;"  to prioritize transactions before they are in the mempool
1112017-03-08T11:00:39  <gmaxwell> jonasschnelli: it is an intentional feature that took extra effort to support. Without it, priority is much less effective.
1122017-03-08T11:01:05  <gmaxwell> since txn you want to prioritize might not otherwise make it into your mempool at all.
1132017-03-08T11:01:14  <jonasschnelli> Yes. I see... maybe the return value then should be wether the transaction was already in the mempool or now.
1142017-03-08T11:01:16  <jonasschnelli> *not
1152017-03-08T11:07:52  <dcousens_> ooi,  in the above statement,  "Amount &delta = mapDeltas[hash]; delta += nFeeDelta;",  mapDeltas[hash] if unitialized, does it get default constructed to 0 somehow?
1162017-03-08T11:08:34  <jonasschnelli> Can anyone help me understand why CreateTransaction (CDummySigner VerifyScript seems to be the problem) if I want to use watch-only addresses (no pubkeys available).
1172017-03-08T11:09:05  <jonasschnelli> If the address is P2PKH, it should be capable to calculate the fee, right...
1182017-03-08T11:09:14  <jonasschnelli> Guess not possible for P2SH
1192017-03-08T11:09:46  <jonasschnelli> *[...] understand why CreateTransaction *fails*
1202017-03-08T11:18:36  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/47510ad3dd51...ac23a7c1f19b
1212017-03-08T11:18:37  <bitcoin-git> bitcoin/master 6c1fb73 John Newbery: Improve logging in bctest.py if there is a formatting mismatch
1222017-03-08T11:18:37  <bitcoin-git> bitcoin/master ac23a7c MarcoFalke: Merge #9945: Improve logging in bctest.py if there is a formatting mismatch...
1232017-03-08T11:18:57  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #9945: Improve logging in bctest.py if there is a formatting mismatch (master...improve_bctest_logging) https://github.com/bitcoin/bitcoin/pull/9945
1242017-03-08T11:19:04  *** jtimon has quit IRC
1252017-03-08T11:28:32  <bitcoin-git> [bitcoin] practicalswift opened pull request #9949: [bench] Avoid function call arguments which are pointers to uninitialized values (master...avoid-pointers-to-unitialized-values-in-function-calls) https://github.com/bitcoin/bitcoin/pull/9949
1262017-03-08T11:29:33  *** paulyb has quit IRC
1272017-03-08T11:58:27  *** To7 has quit IRC
1282017-03-08T11:59:11  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #9790: doc/release-notes: Various cleanups (0.14...0.14-relnotes) https://github.com/bitcoin/bitcoin/pull/9790
1292017-03-08T12:01:54  *** harrymm1 has quit IRC
1302017-03-08T12:13:37  *** jannes has quit IRC
1312017-03-08T12:14:13  *** jannes has joined #bitcoin-core-dev
1322017-03-08T12:17:39  *** harrymm has joined #bitcoin-core-dev
1332017-03-08T12:42:26  <NicolasDorier> jonasschnelli: you may encounter the same problem I stumbled upon while doing my watchonlyhd stuff
1342017-03-08T12:42:30  <NicolasDorier> take a look at https://github.com/bitcoin/bitcoin/pull/9728/files#diff-b2bb174788c7409b671c46ccc86034bdL1859
1352017-03-08T12:43:28  <NicolasDorier> basically, watchonly addresses are untrusted if not confirmed
1362017-03-08T12:43:34  <NicolasDorier> might be your problem
1372017-03-08T12:46:21  <jonasschnelli> NicolasDorier. Thanks... ill have a look
1382017-03-08T12:46:43  <NicolasDorier> jonasschnelli: this PR https://github.com/bitcoin/bitcoin/pull/9830 expose the istrusted flag, it might help you to debug
1392017-03-08T12:50:46  *** belcher has quit IRC
1402017-03-08T12:50:48  *** wudayoda has joined #bitcoin-core-dev
1412017-03-08T12:53:18  *** belcher has joined #bitcoin-core-dev
1422017-03-08T12:55:30  *** wudayoda has quit IRC
1432017-03-08T13:03:49  *** paulyb has joined #bitcoin-core-dev
1442017-03-08T13:10:45  *** paulyb has quit IRC
1452017-03-08T13:18:05  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ac23a7c1f19b...8bfa13b15b84
1462017-03-08T13:18:05  <bitcoin-git> bitcoin/master fdab309 practicalswift: [trivial] Fix typos introduced in 7184e25c80aa8b1629a700bb7a7e290ad0bb2792
1472017-03-08T13:18:06  <bitcoin-git> bitcoin/master 8bfa13b MarcoFalke: Merge #9936: [trivial] Fix three typos introduced into walletdb.h in commit 7184e25...
1482017-03-08T13:18:25  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #9936: [trivial] Fix three typos introduced into walletdb.h in commit 7184e25 (master...fix-typos-introduced-in-commit-7184e25c) https://github.com/bitcoin/bitcoin/pull/9936
1492017-03-08T13:23:33  *** Chris_Stewart_5 has joined #bitcoin-core-dev
1502017-03-08T13:28:35  *** Chris_Stewart_5 has quit IRC
1512017-03-08T13:29:56  *** Chris_Stewart_5 has joined #bitcoin-core-dev
1522017-03-08T14:09:01  *** nemgun has joined #bitcoin-core-dev
1532017-03-08T14:19:02  *** d9b4bef9 has quit IRC
1542017-03-08T14:20:07  *** d9b4bef9 has joined #bitcoin-core-dev
1552017-03-08T14:23:56  *** MarcoFalke has left #bitcoin-core-dev
1562017-03-08T14:32:26  *** BashCo has quit IRC
1572017-03-08T14:33:02  *** BashCo has joined #bitcoin-core-dev
1582017-03-08T14:34:03  *** nemgun has quit IRC
1592017-03-08T14:34:35  *** nemgun has joined #bitcoin-core-dev
1602017-03-08T14:37:16  *** BashCo has quit IRC
1612017-03-08T14:39:47  *** warpo has joined #bitcoin-core-dev
1622017-03-08T14:48:06  <bitcoin-git> [bitcoin] laanwj opened pull request #9951: Wallet database handling abstractions/simplifications (master...2017_03_wallet_dbwrapper) https://github.com/bitcoin/bitcoin/pull/9951
1632017-03-08T14:51:30  *** wudayoda has joined #bitcoin-core-dev
1642017-03-08T14:52:28  *** bityogi has joined #bitcoin-core-dev
1652017-03-08T14:53:26  <bitcoin-git> [bitcoin] laanwj closed pull request #9900: Ban "invalid messagestart" nodes (master...patch-2) https://github.com/bitcoin/bitcoin/pull/9900
1662017-03-08T14:56:12  *** wudayoda has quit IRC
1672017-03-08T15:01:31  *** wudayoda has joined #bitcoin-core-dev
1682017-03-08T15:02:40  *** BashCo has joined #bitcoin-core-dev
1692017-03-08T15:04:05  <BlueMatt> wumpus: (or someone) should set v0.14.0 as a release on github (https://github.com/bitcoin/bitcoin/releases)
1702017-03-08T15:05:46  <wumpus> yes
1712017-03-08T15:23:53  <bitcoin-git> [bitcoin] laanwj opened pull request #9952: Add historical release notes for 0.14.0 (master...2017_03_014_release_notes) https://github.com/bitcoin/bitcoin/pull/9952
1722017-03-08T15:26:36  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/8bfa13b15b84...6996e066b538
1732017-03-08T15:26:36  <bitcoin-git> bitcoin/master 2de6930 Wladimir J. van der Laan: Add historical release notes for 0.14.0
1742017-03-08T15:26:37  <bitcoin-git> bitcoin/master 6996e06 Wladimir J. van der Laan: Merge #9952: Add historical release notes for 0.14.0...
1752017-03-08T15:26:59  <arubi> release notes link on github releases is wrong, points to master (which also 404s)
1762017-03-08T15:27:01  <bitcoin-git> [bitcoin] laanwj closed pull request #9952: Add historical release notes for 0.14.0 (master...2017_03_014_release_notes) https://github.com/bitcoin/bitcoin/pull/9952
1772017-03-08T15:27:12  <wumpus> arubi: should be fixed now
1782017-03-08T15:27:17  <wumpus> arubi: you checked too early
1792017-03-08T15:27:18  <arubi> ah yes
1802017-03-08T15:27:33  <arubi> well it still says master :)
1812017-03-08T15:27:49  <arubi> oh, that's where it's pointing, thought it should point to the tag?
1822017-03-08T15:28:13  *** warpo has quit IRC
1832017-03-08T15:28:15  <wumpus> that's on purpose. It points at the historical release notes in master, that's the most recent version of the release notes for a version
1842017-03-08T15:28:31  <arubi> understood
1852017-03-08T15:29:01  <wumpus> the one in the tag may be older, e.g. sometimes there are post-mortem fixes, and it can no longer be changed
1862017-03-08T15:29:58  <arubi> yea, now I figure the one it points to is kept up to date with the release
1872017-03-08T15:40:19  *** aalex_ has joined #bitcoin-core-dev
1882017-03-08T15:43:00  *** Vinnie_win has joined #bitcoin-core-dev
1892017-03-08T15:44:07  *** aalex__ has quit IRC
1902017-03-08T15:48:39  <wumpus> normally release notes aren't edited after the release, but it sometimes happens if there's something very wrong
1912017-03-08T16:00:26  <arubi> I see where I got confused then, I thought for some reason the link would point to the 0.14 branch, and not the 0.14.0 tag, so at some point when 0.14.1 is released then the link points to the same place, but really no reason for it to work like that :)
1922017-03-08T16:04:59  *** nemgun1 has joined #bitcoin-core-dev
1932017-03-08T16:07:48  *** nemgun has quit IRC
1942017-03-08T16:26:55  <bitcoin-git> [bitcoin] TheBlueMatt opened pull request #9953: Fix shutdown hang with >= 8 -addnodes set (master...2017-03-exit-with-addnode) https://github.com/bitcoin/bitcoin/pull/9953
1952017-03-08T16:36:47  *** aalex__ has joined #bitcoin-core-dev
1962017-03-08T16:40:36  *** aalex_ has quit IRC
1972017-03-08T16:41:04  *** slsdhl has quit IRC
1982017-03-08T16:52:43  *** pedrobranco has quit IRC
1992017-03-08T16:52:58  *** pedrobranco has joined #bitcoin-core-dev
2002017-03-08T16:53:11  *** abpa has joined #bitcoin-core-dev
2012017-03-08T17:00:41  *** slsdhl has joined #bitcoin-core-dev
2022017-03-08T17:13:17  *** laurentmt has joined #bitcoin-core-dev
2032017-03-08T17:14:57  *** laurentmt has quit IRC
2042017-03-08T17:16:46  *** pedrobranco has quit IRC
2052017-03-08T17:17:03  *** pedrobranco has joined #bitcoin-core-dev
2062017-03-08T17:17:34  *** slsdhl has quit IRC
2072017-03-08T17:18:43  *** afk11 has quit IRC
2082017-03-08T17:19:42  *** pedrobranco has quit IRC
2092017-03-08T17:23:32  *** afk11 has joined #bitcoin-core-dev
2102017-03-08T17:28:20  *** dgenr8 has quit IRC
2112017-03-08T17:28:57  *** dgenr8 has joined #bitcoin-core-dev
2122017-03-08T18:24:27  *** wudayoda has quit IRC
2132017-03-08T18:25:00  *** wudayoda has joined #bitcoin-core-dev
2142017-03-08T18:40:07  *** CubicEarth has joined #bitcoin-core-dev
2152017-03-08T18:43:01  *** d9b4bef9 has quit IRC
2162017-03-08T18:44:08  *** d9b4bef9 has joined #bitcoin-core-dev
2172017-03-08T18:45:48  *** Alina-malina has quit IRC
2182017-03-08T18:45:54  <CubicEarth> What would be the computational bottle neck if validation was parallelized to the point of being able to run on a GPU? During chain-sync for example.
2192017-03-08T18:47:25  <arubi> I think if you could get signature validation on a GPU that would be cool CubicEarth :)
2202017-03-08T18:48:14  *** Alina-malina has joined #bitcoin-core-dev
2212017-03-08T18:48:41  <gmaxwell> CubicEarth: I would be mildly surprised if it were possible to make it faster that way.
2222017-03-08T18:48:48  *** CubicEarth has quit IRC
2232017-03-08T18:48:52  <arubi> :(
2242017-03-08T18:49:08  <arubi> oh this is -core-dev, sorry
2252017-03-08T18:49:20  *** Alina-malina has joined #bitcoin-core-dev
2262017-03-08T18:49:22  *** Alina-malina has joined #bitcoin-core-dev
2272017-03-08T18:49:29  *** CubicEarth has joined #bitcoin-core-dev
2282017-03-08T18:49:59  *** nemgun1 has quit IRC
2292017-03-08T18:52:26  <wumpus> GPUs are fking unstable on most user's computers
2302017-03-08T18:53:05  <gmaxwell> big lesson from mining there, remarkable how bad it was ... I hope things have improved?
2312017-03-08T18:53:10  <wumpus> utilizing the CPU and GPU during verification by default would be a good way to cause fires and such :)
2322017-03-08T18:53:22  *** jtimon has joined #bitcoin-core-dev
2332017-03-08T18:54:46  <wumpus> doesn't seem so, especially on laptops it's bad, even if it doesn't overheat immediately there's usually crash issues with ancient drivers, strange edge cases, and so on. Unless you have to deal with GPUs (e.g. game develpoment) I"d suggest staying far from using them for anything to be used by end-users. For research in well-controlled settings/hardware they're ok.
2342017-03-08T18:56:12  <wumpus> at least you can troubleshoot on-site then...
2352017-03-08T19:02:29  <BlueMatt> gmaxwell: i had to replace the gpu in my workstation because a reasonably-high-end consumer gpu was unstable randomly on a machine that literally only ever displays terminals
2362017-03-08T19:02:39  <BlueMatt> they're fucking terrible
2372017-03-08T19:03:27  <BlueMatt> the workstation-class ones seem to be stable, but its clear literally no one ever bothered to test the drivers against them
2382017-03-08T19:03:37  <CubicEarth> that makes sense for laptops... I was imaging using a typical 4-card mining rig
2392017-03-08T19:09:38  <gmaxwell> What was thefeeling around eliminating the requirement for gbtresults on segwit activation? IMO we shouldn't have behavior changes like that triggered by network events, if it is at all possible to avoid.  And also changing the version returned to include segwit, even if the flag isn't set-- we're enforce the rules, which is what matters.
2402017-03-08T19:10:02  <gmaxwell> and there are plenty of miners who will already process transactions.
2412017-03-08T19:21:24  *** e4xit_ has quit IRC
2422017-03-08T19:28:20  *** CubicEarth has quit IRC
2432017-03-08T19:38:14  <sdaftuar> gmaxwell: i'm on board, i was just thinking today abotu coding that up and suggesting it as a backport to the 0.14 branch
2442017-03-08T19:39:02  <gmaxwell> yes, well the addnode bug matt is fixing will call for a 0.14.1 at some point. so I was just thinking it would be good to get that done and in it too.
2452017-03-08T19:39:08  <sdaftuar> agreed
2462017-03-08T19:39:32  <gmaxwell> I'm sorry guys. Didn't make it 24 hours after release before finding something that calls for a 0.14.1. :(
2472017-03-08T19:45:53  <BlueMatt> gmaxwell: yea sucks, but oh well
2482017-03-08T19:56:22  <warren> wumpus: Recently a friend asked what I thought about some startup that aims to accelerate SATA controllers with "low cost desktop GPU's" ...
2492017-03-08T19:58:55  <gmaxwell> I'm sure you must have misheard something.
2502017-03-08T19:59:36  <gmaxwell> for example, maybe they intend to accelerate 200 disk raid with 10 disks of parity.
2512017-03-08T20:01:30  <TD-Linux> warren, just wait until people ask you to solve all their problems with FPGAs
2522017-03-08T20:07:10  *** wudayoda_ has joined #bitcoin-core-dev
2532017-03-08T20:07:23  *** wudayoda has quit IRC
2542017-03-08T20:10:21  <warren> gmaxwell: hand wavy "everything is possible" presentation including that and somehow blockchains.  My first question was "Is this reliable?"
2552017-03-08T20:11:30  <BlueMatt> ok, whos' blocked getting review/merge?
2562017-03-08T20:11:50  * BlueMatt very much is on #9725, and am willing to trade review of that for other things
2572017-03-08T20:11:52  <gribble> https://github.com/bitcoin/bitcoin/issues/9725 | CValidationInterface Cleanups by TheBlueMatt · Pull Request #9725 · bitcoin/bitcoin · GitHub
2582017-03-08T20:16:21  <sdaftuar> gmaxwell: how important do you think it is that CreateNewBlock be fast, when invoked post-segwit activation by a miner that doesn't support it?  in order to be fast, we'd have to cache extra information in the mempool, which i'm not eager to do unless really necessary
2592017-03-08T20:17:01  <sdaftuar> (making it work at all, on the other hand, is not very hard)
2602017-03-08T20:23:17  *** aalex_ has joined #bitcoin-core-dev
2612017-03-08T20:24:22  <gmaxwell> sdaftuar: I think it would be okay if it became slower in that case.
2622017-03-08T20:25:48  <gmaxwell> my expectation is that we'd eventually go back to the current behavior in a later release. (basically: I think it's fine for a new release to change the interface, it's not so fine for network events to change the interface, if it can be avoided.)
2632017-03-08T20:26:35  *** aalex__ has quit IRC
2642017-03-08T20:35:29  *** aalex__ has joined #bitcoin-core-dev
2652017-03-08T20:39:32  *** aalex_ has quit IRC
2662017-03-08T20:46:35  *** moli_ has quit IRC
2672017-03-08T20:52:00  *** moli_ has joined #bitcoin-core-dev
2682017-03-08T20:54:50  <luke-jr> BlueMatt: why remove virtual?
2692017-03-08T20:55:49  <BlueMatt> luke-jr: because I was told you normally remove virtual if you're using override to indicate that you are the implementor of an interface and not something which will be subclassed and overriden
2702017-03-08T20:56:00  <BlueMatt> I dont care either way, talk to ryanofsky
2712017-03-08T20:58:37  <ryanofsky> i don't care much either. i suggested it mainly to be consistent with our other code which uses override. and fwiw, google style guide says "For clarity, use exactly one of override, final, or virtual when declaring an override."
2722017-03-08T21:00:39  <luke-jr> I was under the impression *only* virtuals could have an override, and unless a method is virtual, overrides would de facto get ignored
2732017-03-08T21:02:04  <BlueMatt> no, you have to be implementing a virtual to get override
2742017-03-08T21:02:09  <ryanofsky> it's a compile error to write override on a method that's not virtual, so writing both virtual and override is redundant
2752017-03-08T21:02:10  <BlueMatt> but dont, yourself, have to be virtual
2762017-03-08T21:02:19  *** JackH has joined #bitcoin-core-dev
2772017-03-08T21:04:06  <luke-jr> oh, I see, these are on subclasses
2782017-03-08T21:10:58  <paveljanik> BlueMatt, should I make torControlThread static as well (one line below gBase in src/torcontrol.cpp)?
2792017-03-08T21:11:11  <BlueMatt> paveljanik: anything that can be, probably should be
2802017-03-08T21:11:21  <BlueMatt> i mean especially for such a generic name like "base", but I suppose why not
2812017-03-08T21:11:35  <paveljanik> ok
2822017-03-08T21:26:54  *** Chris_Stewart_5 has quit IRC
2832017-03-08T21:30:14  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2842017-03-08T21:36:28  *** Cory has quit IRC
2852017-03-08T21:41:43  *** Pasha has joined #bitcoin-core-dev
2862017-03-08T21:44:54  *** Pasha is now known as Cory
2872017-03-08T22:01:03  <bitcoin-git> [bitcoin] sdaftuar opened pull request #9955: Don't require segwit in getblocktemplate for segwit signalling or mining (master...2017-03-mining-segwit-changes) https://github.com/bitcoin/bitcoin/pull/9955
2882017-03-08T22:02:06  *** moli_ has joined #bitcoin-core-dev
2892017-03-08T22:08:18  *** RoyceX has joined #bitcoin-core-dev
2902017-03-08T22:11:22  *** arubi has quit IRC
2912017-03-08T22:11:30  *** Cheeseo has quit IRC
2922017-03-08T22:13:47  *** arubi has joined #bitcoin-core-dev
2932017-03-08T22:14:08  *** belcher has quit IRC
2942017-03-08T22:19:17  *** laurentmt has joined #bitcoin-core-dev
2952017-03-08T22:19:20  *** laurentmt has quit IRC
2962017-03-08T22:26:57  *** belcher has joined #bitcoin-core-dev
2972017-03-08T22:35:08  *** bityogi has quit IRC
2982017-03-08T22:35:26  *** r0x has joined #bitcoin-core-dev
2992017-03-08T22:38:20  *** veleiro has joined #bitcoin-core-dev
3002017-03-08T22:38:38  *** r0x has left #bitcoin-core-dev
3012017-03-08T22:56:50  *** Guyver2 has quit IRC
3022017-03-08T22:57:09  *** CubicEarth has joined #bitcoin-core-dev
3032017-03-08T23:00:57  *** bityogi has joined #bitcoin-core-dev
3042017-03-08T23:01:33  *** CubicEarth has quit IRC
3052017-03-08T23:01:33  *** wasi has quit IRC
3062017-03-08T23:04:05  <bitcoin-git> [bitcoin] jnewbery opened pull request #9956: Reorganise qa directory (master...reorganise_qa) https://github.com/bitcoin/bitcoin/pull/9956
3072017-03-08T23:05:26  *** jnewbery has quit IRC
3082017-03-08T23:21:09  <warren> Is anyone using gitian with qemu-system-x86_64 (not LXC)?  It seems that the base-trusty-amd64.qcow2 images generated by make-base-vm are currently unbootable.  qemu-system-x86_64 gets stuck with 100% CPU usage on one core, very little memory use, nothing in logs but a localhost:16 VNC port shows it is stuck at trying to boot the disk image.
3092017-03-08T23:44:51  *** CubicEarth has joined #bitcoin-core-dev
3102017-03-08T23:48:03  <luke-jr> warren: I do, but my base VM is somewhat old
3112017-03-08T23:50:10  <achow101> warren: I use qemu with gitian and haven't had any issues with make-base-vm
3122017-03-08T23:51:26  <warren> I did as recently as last month, but using the latest gitian-builder's make-base-vm the new base-trusty-amd64.qcow2 I get no longer works with gbuild.
3132017-03-08T23:51:42  <warren> achow101: how long ago did you make your base image?
3142017-03-08T23:51:56  <achow101> whenever 0.14.0rc3 was tagged
3152017-03-08T23:52:17  <achow101> (last week I think)
3162017-03-08T23:54:58  <bitcoin-git> [bitcoin] deannolan opened pull request #9958: RPC:Refactor: Remove unreachable code refs #9573 (master...RPC_refactor) https://github.com/bitcoin/bitcoin/pull/9958