12016-10-18T00:05:27  <achow101> michagogo: I made an issue here https://github.com/devrandom/gitian-builder/issues/128 about it. There is also a corresponding issue about this in lxc/lxc. Also, if you go back to IRC logs around that same time (end of august), you should be able to find some info I said there about the same problem
   22016-10-18T00:06:44  <michagogo> tulip: yep, that was missed
   32016-10-18T00:08:50  <michagogo> tulip: 01:17:13 <GitHub81> [bitcoin] laanwj pushed 1 new commit to 0.13: https://github.com/bitcoin/bitcoin/commit/a5cef7b0777f13ac83312759ebf576c9d773599f
   42016-10-18T00:08:53  <michagogo> 01:17:13 <GitHub81> bitcoin/0.13 a5cef7b Wladimir J. van der Laan: Bump version to 0.13.1
   52016-10-18T00:09:30  <michagogo> achow101: hmm. I seem to remember (from quite a while back…) that I tried doing it on Xenial and failed too
   62016-10-18T00:10:08  <michagogo> I feel like I might have gotten past the shm thing just to have it fail a different way
   72016-10-18T00:10:14  <michagogo> Or maybe I'm misremembering
   82016-10-18T00:10:32  <michagogo> Works for me on the Trusty Tahr, though
   92016-10-18T00:11:19  * sipa realizes that he never knew what the part after 'Trusty' in the ubuntu version name was
  102016-10-18T00:11:43  <achow101> Maybe I'll try it in a VM with trusty then. I've been running 16.04 which is what I do the builds on
  112016-10-18T00:11:58  <achow101> it previously worked on 15.10 for a while then broke
  122016-10-18T00:12:20  *** alpalp has joined #bitcoin-core-dev
  132016-10-18T00:12:28  <achow101> but it would be great if this could be fixed since multiple people have run into the same problem recently
  142016-10-18T00:15:20  *** mol has joined #bitcoin-core-dev
  152016-10-18T00:18:32  *** molz has quit IRC
  162016-10-18T00:22:50  *** fengling__ has joined #bitcoin-core-dev
  172016-10-18T00:32:40  *** murch has quit IRC
  182016-10-18T00:37:04  *** Ylbam has quit IRC
  192016-10-18T00:37:22  *** fengling__ has quit IRC
  202016-10-18T00:50:08  <achow101> for some reason I can't do the osx build now
  212016-10-18T00:51:26  <achow101> it is failing at installing stuff. the install.log says "E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution)."
  222016-10-18T00:53:32  <achow101> well, it isn't just osx apparently, something is broken on my gitian
  232016-10-18T00:54:57  <achow101> michagogo:
  242016-10-18T00:55:47  <michagogo> But you somehow managed windows and Linux? o_o
  252016-10-18T00:56:17  <achow101> I just tried to do windows and linux again and it failed.
  262016-10-18T00:56:25  <achow101> I guess it got through them before it broke
  272016-10-18T00:56:27  <michagogo> sipa: yep. I wonder if I remember them all
  282016-10-18T00:56:51  <michagogo> achow101: odd. I wonder what could have changed
  292016-10-18T00:58:02  <achow101> my computer almost crashed during the build since I tried starting a vm. Maybe that corrupted something in memory which corrupted something on disk?
  302016-10-18T01:11:27  *** Alopex has quit IRC
  312016-10-18T01:12:32  *** Alopex has joined #bitcoin-core-dev
  322016-10-18T01:18:45  <achow101> wtf. I just redownloaded and setup gitian and now it's asking me for the password for the vm in order to do stuff
  332016-10-18T01:21:27  <gmaxwell> My voice is my passport. Verify me.
  342016-10-18T01:24:59  <tulip> achow101: you mustn't have had your pentagon configured correctly.
  352016-10-18T01:27:19  <michagogo> achow101: the VM you're running gitian in?
  362016-10-18T01:27:34  <michagogo> The same one as before?
  372016-10-18T01:28:05  <achow101> the vm that gitian creates
  382016-10-18T01:28:13  <michagogo> Hmm.
  392016-10-18T01:28:29  <michagogo> It shouldn't be doing that, I think
  402016-10-18T01:28:37  <tulip> I managed to find two NODE_SEGWIT peers with #8949 but I don't know if that's luck or not.
  412016-10-18T01:28:52  <michagogo> Did you create the previous one the same way?
  422016-10-18T01:29:01  <achow101> yes
  432016-10-18T01:29:11  <michagogo> 🤔
  442016-10-18T01:30:04  <achow101> I used my gitian build script with the setup option to setup the gitian environment. the script is in  the repo in contrib/
  452016-10-18T01:40:06  *** Alopex has quit IRC
  462016-10-18T01:41:11  *** Alopex has joined #bitcoin-core-dev
  472016-10-18T01:41:51  *** fengling__ has joined #bitcoin-core-dev
  482016-10-18T01:42:13  *** CodeShark has quit IRC
  492016-10-18T01:42:37  *** CodeShark has joined #bitcoin-core-dev
  502016-10-18T01:47:15  *** ibrightly has quit IRC
  512016-10-18T01:48:56  *** ibrightly has joined #bitcoin-core-dev
  522016-10-18T01:50:02  <tulip> 2016-10-18 01:43:35.372446 connect() to [::0.0.255.255]:20720 failed: No route to host (65)
  532016-10-18T01:50:02  <tulip> 2016-10-18 01:42:29.613434 connect() to [a586:2a57:100::]:0 failed: Can't assign requested address (49)
  542016-10-18T01:50:02  <tulip> 2016-10-18 01:43:18.827390 connect() to [d50e:7f57:100::]:0 failed: Can't assign requested address (49)
  552016-10-18T01:50:29  <tulip> gmaxwell: I guess this means there's only junk in addrman with the NODE_WITNESS service?
  562016-10-18T01:51:01  *** btcdrak has quit IRC
  572016-10-18T01:54:25  *** btcdrak has joined #bitcoin-core-dev
  582016-10-18T01:55:24  <tulip> no wait, there we go. from a very old node state with no sensible peers to 4 NODE_WITNESS peers in about 6 minutes.
  592016-10-18T02:02:57  <gmaxwell> tulip: thats better than I expirenced.
  602016-10-18T02:03:52  <gmaxwell> I have one node that after being upgraded, run for three houres, and restart... has no nodewitness peers.
  612016-10-18T02:03:59  <gmaxwell> (thus the PR that I opened)
  622016-10-18T02:04:12  <tulip> gmaxwell: that's with your patch.
  632016-10-18T02:04:16  <gmaxwell> ah okay!
  642016-10-18T02:04:23  <tulip> it had no NODE_WITNESS peers beforehand.
  652016-10-18T02:04:41  <gmaxwell> yea, with the patch it will be pretty much guarenteed to find some... often 4. :)
  662016-10-18T02:05:35  <tulip> curious why we are even trying to connect to nodes with port zero, is anyone really going to be running a privileged port Bitcoin node?
  672016-10-18T02:06:04  <tulip> (I assumed 0-1023 would be masked out entirely)
  682016-10-18T02:06:13  <gmaxwell> well we only try connecting to non-standard ports if we've been failing to connect for a while, but port 0 is braindamaged.
  692016-10-18T02:06:55  <gmaxwell> someone might plausably run a bitcoin node on port 80 or port 443 since it's a little more likely to make it through firewalls.
  702016-10-18T02:08:09  <gmaxwell> port 0 is just stupid though. We should probably filter out port 0 from ever going into addrman.
  712016-10-18T02:16:15  *** mturquette has quit IRC
  722016-10-18T02:18:15  *** mturquette has joined #bitcoin-core-dev
  732016-10-18T02:25:48  *** Giszmo has quit IRC
  742016-10-18T03:00:20  *** Chris_Stewart_5 has quit IRC
  752016-10-18T03:05:30  *** zooko has joined #bitcoin-core-dev
  762016-10-18T03:06:58  *** alpalp is now known as alpalpwi
  772016-10-18T03:07:02  *** alpalpwi is now known as alpalp
  782016-10-18T03:24:38  *** molz has joined #bitcoin-core-dev
  792016-10-18T03:27:44  <morcos> gmaxwell: at the risk of beating a dead horse, can you try again to explain to me the logic behind writing down the mempool every 10 mins?
  802016-10-18T03:28:04  <gmaxwell> every ten minutes I care less about than at clean shutdown.
  812016-10-18T03:28:07  *** mol has quit IRC
  822016-10-18T03:28:11  <morcos> i can somewhat reluctantly accept that it might be useful on shutdown, and could see it being beneficial on demand (maybe via rpc)
  832016-10-18T03:28:28  <morcos> but writing it every 10 mins just seems like a way to clog up your node doing useless crap
  842016-10-18T03:28:30  <gmaxwell> the 10 minute thing is something sipa added that wasn't in my requirements document. :P
  852016-10-18T03:29:05  <morcos> and in particular if somehow some bad tx in your mempool crashed your block creation code, maybe you don't want to reload with that mempool (but i guess you could do that manually)
  862016-10-18T03:29:45  <gmaxwell> I don't think we disagree.  (The goals in saving it: prevent being utterly cold on newly recieved blocks after you do a simple restart for config changes, to not lose your transaction prioritization, to not reject dependant transactions as orphans which you never recieve, to not needlessly end up mining small blocks for an hour after a boring restart...)
  872016-10-18T03:30:25  <gmaxwell> well if you're crashing you can delete the file. I'm not particularly worried about that, and the import path goes through the normal accept logic, it's not just crammed back into the mempool. (meaning a network peer could give you the same garbage)
  882016-10-18T03:31:38  <morcos> ok, i guess just making your node to extensive disk access every 10 minutes gives me the heebie jeebies
  892016-10-18T03:31:47  <gmaxwell> the lack of the saving/loading also means that all of us spend far too much time messing around with nodes in unrepresentative states, throwing off benchmarking, and risking that we don't see issues that only show up with the mempool nice and fat.
  902016-10-18T03:32:01  <morcos> instead of roughly writing 1MB every 10 mins, now you'll write 300
  912016-10-18T03:32:13  <gmaxwell> Yea, well, I'm not a fan of the 10 minute thing. I'd be happier if it was on shutdown and had a rpc to trigger, and if you want 10 minutes you can call the rpc yourself. :)
  922016-10-18T03:32:34  <morcos> i would be way happier with that
  932016-10-18T03:33:06  <gmaxwell> I think the rational for the 10 minute saves is to make it useful across crashes. Which has merit, but-- I'd rather just not crash. :)
  942016-10-18T03:33:31  <morcos> looking back at the PR discussion, i think sipa wanted prioritization info to be saved in the event of a crash
  952016-10-18T03:33:39  <morcos> but do people actually have nodes that crash?
  962016-10-18T03:33:42  <morcos> is that a thing?
  972016-10-18T03:33:57  <gmaxwell> horrifyingly, yes. But we don't have to embrace all of reality.
  982016-10-18T03:34:24  *** achow101 has quit IRC
  992016-10-18T03:34:49  <gmaxwell> (a main audience for this is miners, some of whom may have custimization that crashes; or be running on mystermeat hardware and not really appricate that it shoud not EVER crash)
 1002016-10-18T03:35:58  <morcos> ok.. i'll comment on the PR with my thoughts then since they don't seem too objectionable
 1012016-10-18T03:42:25  *** achow101 has joined #bitcoin-core-dev
 1022016-10-18T03:43:30  <gmaxwell> I'd love to have some crash detection wrapper around bitcoin core that told people "THIS SHOULD NEVER CRASH. IF IT CRASHES WE WANT TO KNOW _NOW_" .. but unfortunately virtually all crashes I've seen from users are bad hardware, and we don't really want to know. :)
 1032016-10-18T03:44:33  *** DigiByteDev has joined #bitcoin-core-dev
 1042016-10-18T03:47:09  <morcos> heh, i offered one of the industry exec's a 1 BTC bounty for every non hardware caused crash he had on his bitcoinds because he was complaining bitcoind crashes all the time.
 1052016-10-18T03:47:25  <morcos> that was like a year ago, no claims yet.
 1062016-10-18T03:47:33  *** alpalp has quit IRC
 1072016-10-18T03:48:23  <gmaxwell> :)
 1082016-10-18T03:48:43  <gmaxwell> I've heard those sorts of claims going around, and wasted a lot of time trying to find ways to make it crash.
 1092016-10-18T03:49:16  <luke-jr> heh
 1102016-10-18T03:49:49  <luke-jr> I wonder if the hardware-induced crashes are such that we can detect them with a repeat easily
 1112016-10-18T03:50:03  <luke-jr> (and then complain to the user that their hardware is certainly faulty)
 1122016-10-18T03:50:17  <gmaxwell> "Non-determinstic hardware detected (this is bad)"
 1132016-10-18T03:51:07  <luke-jr> "It's not that we don't like you overclocking, but rather that your overclocking has actually given us the wrong answer to math, which is kinda important to Bitcoin working right."
 1142016-10-18T03:52:30  <TD-Linux> probably not without crash telemetry, which I think users would be pretty averse to...
 1152016-10-18T03:56:05  <luke-jr> btw, +1 on RPC trigger to write mempool before exit
 1162016-10-18T03:56:35  <luke-jr> if someone wants to write every 10 minutes, they can cronjob it
 1172016-10-18T03:56:40  *** Cory has joined #bitcoin-core-dev
 1182016-10-18T03:58:14  <TD-Linux> also the existing PR fsync()'s on every write, which is probably fine on exit but is not great for interactive performance, especially on linux
 1192016-10-18T03:58:41  * luke-jr wonders how much performance gain we'd get by using the file-specific fsync calls
 1202016-10-18T04:00:08  <TD-Linux> luke-jr, it already does, the problem is on Linux other accesses will be queued behind the gigantic write
 1212016-10-18T04:00:31  <tulip> TD-Linux: manual telemetry can be a thing, sort of. rather than asking users to dig around for things in a debug.log you can make a cohesive blob and a message that says "report this to your handler if you want to".
 1222016-10-18T04:10:15  <luke-jr> TD-Linux: hmm, some filesystems on Linux seem to have another ioctl for fsyncing a specific file; I guess the normal one does it to a specific fd as well.. not sure what the difference is
 1232016-10-18T04:14:56  <TD-Linux> luke-jr, not sure, but the buffering issue is lower level: https://lwn.net/Articles/682582/
 1242016-10-18T04:16:40  <TD-Linux> tulip, that would help. here's an example of what a hardware bug looks like on mozilla telemetry: https://crash-stats.mozilla.com/signature/?signature=adapt_probs&date=%3E%3D2016-10-11T04%3A06%3A00.000Z&date=%3C2016-10-18T04%3A06%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#aggregations
 1252016-10-18T04:16:54  <TD-Linux> (hint: pick the "aggregate on" drop down and choose cpu info)
 1262016-10-18T04:29:31  *** Alopex has quit IRC
 1272016-10-18T04:30:37  *** Alopex has joined #bitcoin-core-dev
 1282016-10-18T04:31:44  *** zooko has quit IRC
 1292016-10-18T04:32:11  *** kadoban has quit IRC
 1302016-10-18T04:36:47  <gmaxwell> morcos: more like 150MB of data, fwiw, ... mempool limit is on the in memory form, saving it out currently uses the p2p serilization.
 1312016-10-18T04:42:32  *** DigiByteDev has quit IRC
 1322016-10-18T04:45:11  *** molz has quit IRC
 1332016-10-18T04:50:35  *** whphhg has quit IRC
 1342016-10-18T04:53:18  *** whphhg has joined #bitcoin-core-dev
 1352016-10-18T04:58:25  *** moli has joined #bitcoin-core-dev
 1362016-10-18T04:58:48  *** achow101 has quit IRC
 1372016-10-18T05:00:20  *** dermoth has quit IRC
 1382016-10-18T05:00:56  *** dermoth has joined #bitcoin-core-dev
 1392016-10-18T05:03:15  <cfields_> gitian builders: v0.13.1rc1 detached sigs are pushed
 1402016-10-18T05:04:27  <gmaxwell> wtf. why does sendtoaddress' help have an actual bitcoin address in the example? O_o we worked hard elsewhere to keep real addresses out of examples.
 1412016-10-18T05:05:40  *** achow101 has joined #bitcoin-core-dev
 1422016-10-18T05:09:06  <gmaxwell> hmph. a long time ago in fact.
 1432016-10-18T05:29:10  <tulip> TD-Linux: you're right, bitcoin users wouldn't appreciate that much
 1442016-10-18T05:30:49  <tulip> yuck, the sentoaddress "example" is even a political one.
 1452016-10-18T05:31:53  <tulip> well, no political but it's for a "cause" which isn't ideal.
 1462016-10-18T05:33:14  *** moli has quit IRC
 1472016-10-18T05:33:25  <luke-jr> there are probably worse causes it could be
 1482016-10-18T05:33:42  *** moli has joined #bitcoin-core-dev
 1492016-10-18T05:34:02  <gmaxwell> yea sure. still. obviously it should be my address there
 1502016-10-18T05:34:44  <luke-jr> ☺
 1512016-10-18T05:35:28  <luke-jr> should be a testnet address ☺
 1522016-10-18T05:47:05  *** Ylbam has joined #bitcoin-core-dev
 1532016-10-18T05:48:10  <GitHub197> [bitcoin] jl2012 opened pull request #8950: Update gitian signing key of jl2012 (master...patch-18) https://github.com/bitcoin/bitcoin/pull/8950
 1542016-10-18T05:59:02  *** fengling__ is now known as fengling
 1552016-10-18T05:59:33  *** moli has quit IRC
 1562016-10-18T06:00:01  *** moli has joined #bitcoin-core-dev
 1572016-10-18T06:07:53  <btcdrak> what is si objectionable about writing 150-300MB down every 10 mins?
 1582016-10-18T06:08:24  <luke-jr> put it that way and it sounds pretty bad. probably will cause seconds of hanging on my PC
 1592016-10-18T06:08:32  <btcdrak> the mempool is mostly quite small. sounds like over optimisation worrying about that.
 1602016-10-18T06:09:12  <btcdrak> oh come on.. even a PI can write that with no sweat. this isnt 1990
 1612016-10-18T06:09:40  <btcdrak> mempool is usually what 5-10MB at peak?
 1622016-10-18T06:09:49  <luke-jr> seriously?
 1632016-10-18T06:10:13  <paveljanik> btcdrak, mempool is usually ~300MB ;-)
 1642016-10-18T06:11:10  <btcdrak> still doesnt invalidate what I am saying. 300MB flush every 10 mins isnt a big deal. this is 2016
 1652016-10-18T06:11:37  <luke-jr> 314572800 bytes (315 MB) copied, 2.67949 s, 117 MB/s
 1662016-10-18T06:11:40  <luke-jr> ok, not so bad I guess
 1672016-10-18T06:28:06  *** molz has joined #bitcoin-core-dev
 1682016-10-18T06:31:09  *** moli has quit IRC
 1692016-10-18T06:32:00  <TD-Linux> seriously can't tell if that was sarcasm or not...
 1702016-10-18T06:39:13  *** BashCo has quit IRC
 1712016-10-18T06:49:21  <paveljanik> this was from luke-jr's high-end 64bit workstation...
 1722016-10-18T06:49:56  <paveljanik> let's wait for the numbers from wumpus' arm small boxes. Still writing...
 1732016-10-18T06:50:00  <luke-jr> XD
 1742016-10-18T06:52:04  <btcdrak> my computer 314572800 bytes (315 MB) copied, 0.629238 s, 500 MB/s
 1752016-10-18T06:52:34  <luke-jr> SSD?
 1762016-10-18T06:52:41  <btcdrak> yes
 1772016-10-18T06:53:02  <btcdrak> going to check my pine64
 1782016-10-18T06:53:51  <btcdrak> well my laptop with HDD is 314572800 bytes (315 MB) copied, 0.892623 s, 352 MB/s
 1792016-10-18T06:54:04  <btcdrak> that's only a 5200rpm thing too
 1802016-10-18T06:54:26  <luke-jr> I did it on btrfs since I expect poorer performance from it
 1812016-10-18T06:54:34  <luke-jr> but a relatively new drive, so
 1822016-10-18T06:56:29  <TD-Linux> btcdrak, that's implausibly high for a spinning disk. you're not syncing afterwards
 1832016-10-18T06:58:38  * luke-jr also forgot to sync :x
 1842016-10-18T06:59:00  <luke-jr> real    0m6.677s
 1852016-10-18T06:59:15  <luke-jr> so 47 MB/s
 1862016-10-18T07:00:05  <luke-jr> (sync before starting it too)
 1872016-10-18T07:06:19  <TD-Linux> right, I'm not so much concerned about speed as the impact on other i/o while that is happening. I think it's probably acceptable, but it's possible to do better
 1882016-10-18T07:07:00  <btcdrak> why does actual sync matter? Why are we concerned about the background processes of the host computer?
 1892016-10-18T07:12:11  <paveljanik> btcdrak, it is 300+MB in the default config. And in the typical use case (nonstop, no failure run), we write, write, write and do not use the written data at all.
 1902016-10-18T07:12:27  <paveljanik> slowly killing the disks...
 1912016-10-18T07:15:59  *** BashCo has joined #bitcoin-core-dev
 1922016-10-18T07:17:30  *** BashCo_ has joined #bitcoin-core-dev
 1932016-10-18T07:19:46  <luke-jr> btcdrak: background process I/O is dreadfully annoying
 1942016-10-18T07:19:51  <gmaxwell> 150 MB, not 300.
 1952016-10-18T07:20:09  <gmaxwell> But creating a 3 second IO stall (luke's example) would be unfortunate. :)
 1962016-10-18T07:20:20  <luke-jr> gmaxwell: 7 seconds, it turns out
 1972016-10-18T07:20:39  *** BashCo has quit IRC
 1982016-10-18T07:21:09  <gmaxwell> besides, writing the mempool is just wasting SSD write endurance. Bitcoin Core doesn't crash. If you're in some weird enviroment where you care, you can call the rpc yourself.
 1992016-10-18T07:21:13  <luke-jr> are we locking the mempool while it writes too? :x
 2002016-10-18T07:21:40  <TD-Linux> luke-jr, the patch does an in-memory copy first to make the lock time minimal
 2012016-10-18T07:21:45  <luke-jr> ah, ok
 2022016-10-18T07:21:58  <luke-jr> though that alone might annoy some users
 2032016-10-18T07:22:14  <paveljanik> in memory copy?
 2042016-10-18T07:22:29  <GitHub141> [bitcoin] luke-jr opened pull request #8951: RPC/Mining: getblocktemplate: Update and fix formatting of help (master...gbt_help_update) https://github.com/bitcoin/bitcoin/pull/8951
 2052016-10-18T07:22:30  <paveljanik> So if I have 1G mempool, bitcoind will allocate one more G?
 2062016-10-18T07:22:36  <paveljanik> hmm
 2072016-10-18T07:23:00  <luke-jr> ^ please tag for backport
 2082016-10-18T07:26:18  <gmaxwell> paveljanik: No. the transactions themselves are shared pointers.
 2092016-10-18T07:29:24  *** murch has joined #bitcoin-core-dev
 2102016-10-18T07:43:36  *** _mn3monic has quit IRC
 2112016-10-18T07:45:35  <btcdrak> gmaxwell: is 8949 aimed for 0.13.1 backport? (seems like it should be).
 2122016-10-18T07:46:04  <gmaxwell> Yes, assuming people find it acceptable for master.
 2132016-10-18T07:46:08  <gmaxwell> I think it's needed.
 2142016-10-18T07:46:40  <gmaxwell> at least my expirence and tulip's is that absent it, 0.13.1rc1 is prone to not getting any witness peers.
 2152016-10-18T07:47:00  <gmaxwell> (I somewhat expected this, but we didn't see it on testnet in part because testnet doesn't have that many healthy working peers to begin with)
 2162016-10-18T07:47:18  *** harrymm has quit IRC
 2172016-10-18T07:50:30  *** cdecker has joined #bitcoin-core-dev
 2182016-10-18T07:55:42  <btcdrak> gmaxwell: I can confirm the same problem
 2192016-10-18T07:58:12  <gmaxwell> In any case, my PR is reported to resolve the issue.
 2202016-10-18T08:06:46  *** harrymm has joined #bitcoin-core-dev
 2212016-10-18T08:16:05  *** paveljanik has quit IRC
 2222016-10-18T08:27:12  *** MarcoFalke has joined #bitcoin-core-dev
 2232016-10-18T08:37:48  <GitHub18> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/763828df499f...47ace4240a4e
 2242016-10-18T08:37:48  <GitHub18> bitcoin/master 21f5a63 Luke Dashjr: Qt: Add "Copy URI" to payment request context menu
 2252016-10-18T08:37:49  <GitHub18> bitcoin/master 47ace42 Wladimir J. van der Laan: Merge #8918: Qt: Add "Copy URI" to payment request context menu...
 2262016-10-18T08:38:03  <GitHub57> [bitcoin] laanwj closed pull request #8918: Qt: Add "Copy URI" to payment request context menu (master...gui_req_copy_uri) https://github.com/bitcoin/bitcoin/pull/8918
 2272016-10-18T08:44:17  <GitHub134> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/47ace4240a4e...cd761fb85a24
 2282016-10-18T08:44:17  <GitHub134> bitcoin/master 1ab21cf Matt Corallo: Remove bogus assert on number of oubound connections....
 2292016-10-18T08:44:18  <GitHub134> bitcoin/master cd761fb Wladimir J. van der Laan: Merge #8944: Remove bogus assert on number of oubound connections....
 2302016-10-18T08:44:36  <GitHub70> [bitcoin] laanwj closed pull request #8944: Remove bogus assert on number of oubound connections. (master...2016-10-bad-assert) https://github.com/bitcoin/bitcoin/pull/8944
 2312016-10-18T08:46:19  *** rabidus has joined #bitcoin-core-dev
 2322016-10-18T08:47:01  <GitHub155> [bitcoin] laanwj pushed 2 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/c418c0550db3...907c314057b0
 2332016-10-18T08:47:02  <GitHub155> bitcoin/0.13 c9ffe90 Micha: Add historical release notes for v0.13.0...
 2342016-10-18T08:47:02  <GitHub2> [bitcoin] laanwj closed pull request #8947: Add historical release notes for v0.13.0 (0.13...0.13) https://github.com/bitcoin/bitcoin/pull/8947
 2352016-10-18T08:47:02  <GitHub155> bitcoin/0.13 907c314 Wladimir J. van der Laan: Merge #8947: Add historical release notes for v0.13.0...
 2362016-10-18T08:47:49  *** Victorsueca has joined #bitcoin-core-dev
 2372016-10-18T08:49:32  <wumpus> 7 witness connections now on my upgraded node
 2382016-10-18T08:53:14  <gmaxwell> 1 witness connection, inbound. on one of my nodes.
 2392016-10-18T08:54:08  *** dgenr8 has quit IRC
 2402016-10-18T08:55:02  <wumpus> here 5 inbound + 2 outbound
 2412016-10-18T08:55:15  <gmaxwell> 6 on another node, one is outbound but it's an addnode to sipa. The rest are inbound.
 2422016-10-18T09:00:54  <gmaxwell> sipa's seeder database only has 7, and one is v6 and the other is onion.
 2432016-10-18T09:01:05  <gmaxwell> though I know there are more of them, I guess it hasn't found them yet.
 2442016-10-18T09:01:44  <gmaxwell> heh. one of them claims be be 0.12.99 0_o and it fails sipa's 'good' test.
 2452016-10-18T09:02:16  <gmaxwell> presumably because it's 32177 blocks behind.
 2462016-10-18T09:09:37  *** MarcoFalke has left #bitcoin-core-dev
 2472016-10-18T09:40:37  *** _mn3monic has joined #bitcoin-core-dev
 2482016-10-18T09:45:36  <GitHub126> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/cd761fb85a24...614d522c3e44
 2492016-10-18T09:45:36  <GitHub126> bitcoin/master b0aea80 BtcDrak: Sync bitcoin-tx with tx version policy
 2502016-10-18T09:45:37  <GitHub126> bitcoin/master 614d522 Wladimir J. van der Laan: Merge #8932: Allow bitcoin-tx to create v2 transactions...
 2512016-10-18T09:45:46  <GitHub89> [bitcoin] laanwj closed pull request #8932: Allow bitcoin-tx to create v2 transactions (master...bitcointx2) https://github.com/bitcoin/bitcoin/pull/8932
 2522016-10-18T09:47:21  <Victorsueca> has anybody ever got compiling on windows to work?
 2532016-10-18T09:48:05  <wumpus> Victorsueca: yes, some people did, but all the current devs just cross-build from ubuntu
 2542016-10-18T09:48:43  <wumpus> Victorsueca: this may be useful to you (building with WSL) https://github.com/bitcoin/bitcoin/pull/8935
 2552016-10-18T09:48:54  <cdecker> Checking the hashes produced by gitian I noticed that jl2012 produced different results
 2562016-10-18T09:49:12  <jl2012> which one?
 2572016-10-18T09:49:22  <cdecker> The linux hashes
 2582016-10-18T09:49:37  <jl2012> i didn't check. Let me see
 2592016-10-18T09:50:00  <wumpus> if you are really masochistic you can try to build bitcoin core with MSVC, most of the hassle is getting eventhing into the build system + setting config.h parameters manually
 2602016-10-18T09:50:02  <jl2012> it seems windows and MAC are the same
 2612016-10-18T09:50:12  <cdecker> https://gist.github.com/d2014467aa28dc0d20d74b652950ceb1
 2622016-10-18T09:50:21  <cdecker> jl2012: yep those seem to check out
 2632016-10-18T09:50:30  <wumpus> I did so in 2012 or so, but that was on my wxp VM which I've nuked by now so don't have any of that anymore
 2642016-10-18T09:50:39  <tulip> on my unpatched IPv4-only node I'm seeing 2 NODE_WITNESS, but I think that's a function of being in a busy ASN and having a low number of non-junk peers to begin with.
 2652016-10-18T09:51:22  *** dgenr8 has joined #bitcoin-core-dev
 2662016-10-18T09:52:07  <jl2012> cdecker: everyone got the same except me? I'll try again
 2672016-10-18T09:52:31  <cdecker> And I seem to have botched the windows build myself
 2682016-10-18T09:52:35  <cdecker> :-)
 2692016-10-18T09:53:10  <Victorsueca> wumpus: yeah, i'm going to do it on a Linux VM, but the curious thing is that when I tried it on windows the failure seemed to be at the directory name characters
 2702016-10-18T09:53:49  <Victorsueca> i was getting error like directory does not exist or character "|" being unexpected
 2712016-10-18T09:54:54  <luke-jr> Victorsueca: were you trying to build in a path with spaces?
 2722016-10-18T09:55:05  <tulip> (lots are fake-looking bitcoinj, and someone who took the time to recompile 0.13.1 with a 0.9 subversion)
 2732016-10-18T09:55:44  <luke-jr> tulip: AWS BitcoinJ is bogus obviously
 2742016-10-18T09:56:01  <gmaxwell> tulip: I posted a banlist specifically for those things.
 2752016-10-18T09:57:04  <wumpus> cross-building from ubuntu 14.04 is the safest way to build for windows, 16.04 (and I guess 16.10) has still some issues: https://github.com/bitcoin/bitcoin/projects/1
 2762016-10-18T10:05:31  *** jtimon has joined #bitcoin-core-dev
 2772016-10-18T10:08:53  <Victorsueca> luke-jr: only letters, numbers, dots and dashes
 2782016-10-18T10:09:11  <Victorsueca> no spaces
 2792016-10-18T10:10:44  <Victorsueca> also says that "Makefile" is not a command, but I thought that came with MinGW
 2802016-10-18T10:13:37  <sipa> make is command
 2812016-10-18T10:14:02  <sipa> Makefile is the file with the project specific build instructions
 2822016-10-18T10:14:29  <sipa> and none of that will easily work in windows
 2832016-10-18T10:14:45  <sipa> you'll need to write the build instructions yourself
 2842016-10-18T10:14:59  <Victorsueca> so why does it think "Makefile" is suposed to be a command instead of a file?
 2852016-10-18T10:15:04  <luke-jr> if it were me, I'd try to build with MSYS
 2862016-10-18T10:15:16  <luke-jr> Victorsueca: what does?
 2872016-10-18T10:16:29  <Victorsueca> luke-jr: when it try to build it tells me that "Makefile" is a unknown command
 2882016-10-18T10:17:00  <luke-jr> when what try to build?
 2892016-10-18T10:17:11  <luke-jr> you're the one issuing commands..
 2902016-10-18T10:17:36  <Victorsueca> trying to build 0.13.1rc1
 2912016-10-18T10:17:53  <Victorsueca> the only command I issued so far is >make HOST=i686-w64-mingw32 -j4
 2922016-10-18T10:18:29  <luke-jr> where did you get the impression that was a way to build?
 2932016-10-18T10:18:45  <Victorsueca> here https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md
 2942016-10-18T10:20:50  <luke-jr> oh, in depends
 2952016-10-18T10:21:34  <sipa> that's to build for windows, not on windows
 2962016-10-18T10:22:15  <Victorsueca> sipa: i'm trying to build for windows on windows
 2972016-10-18T10:22:41  <sipa> Victorsueca: good luck
 2982016-10-18T10:22:53  <sipa> but none of the existing documentation will be of any use
 2992016-10-18T10:23:17  <Victorsueca> I have a linux VM anyway, but i'm trying to see if it's possible to build on windows without having to edit too much files manually or being a pain in the arse
 3002016-10-18T10:23:42  <luke-jr> Victorsueca: it might be possible in MSYS, but don't expect anything to just work
 3012016-10-18T10:24:22  <sipa> Victorsueca: unless you're experienced with developing software using a mingw/msys build environment already, i expect that will take days of work to figure things out
 3022016-10-18T10:25:18  <Victorsueca> sipa: that sounds like a pain in the arse, i'll just use the linux VM then
 3032016-10-18T10:25:38  <sipa> yes, building via cross compiling is the only supported mechanism
 3042016-10-18T10:27:15  <michagogo> Victorsueca: are you on Windows 10?
 3052016-10-18T10:27:22  <Victorsueca> michagogo: yep
 3062016-10-18T10:27:39  *** tulip has quit IRC
 3072016-10-18T10:28:01  <michagogo> Because then you could cross compile for windows on Ubuntu on Windows
 3082016-10-18T10:28:10  *** tulip has joined #bitcoin-core-dev
 3092016-10-18T10:28:10  <michagogo> No need for a VM
 3102016-10-18T10:29:00  <michagogo> (It's kinda amusing that you're cross-compiling for Windows on a Windows machine…)
 3112016-10-18T10:29:14  <Victorsueca> michagogo: yeah lol
 3122016-10-18T10:29:31  <Victorsueca> but there are no docs for windows compiling AFAIK
 3132016-10-18T10:29:42  <michagogo> Actually, maybe that was already possible -- does anyone know if anyone's tried cross-compiling for Windows in Cygwin?
 3142016-10-18T10:29:47  <michagogo> Victorsueca: that's the thing
 3152016-10-18T10:30:00  <michagogo> If you do it in Ubuntu you just follow the Linux instructions
 3162016-10-18T10:30:38  <Victorsueca> i'll just use the VM
 3172016-10-18T10:32:54  <jtimon> Ubuntu on windows to build for windows, hehe
 3182016-10-18T10:33:44  <michagogo> As of 0.10, this is all you needed to do to cross-compile for Windows:  https://www.irccloud.com/pastebin/W6gIBKMf
 3192016-10-18T10:33:52  <michagogo> I assume it's pretty similar
 3202016-10-18T10:34:09  <michagogo> (I don't think much has changed with the depends/build system since then?)
 3212016-10-18T10:34:46  <michagogo> Victorsueca: well, doing it in Ubuntu On Windows should be pretty much identical to doing it in the VM AFAIK
 3222016-10-18T10:39:37  *** MarcoFalke has joined #bitcoin-core-dev
 3232016-10-18T10:49:02  *** ratoder has joined #bitcoin-core-dev
 3242016-10-18T10:52:11  *** fengling has quit IRC
 3252016-10-18T11:16:46  <wumpus> Victorsueca: I pointed you to: https://github.com/bitcoin/bitcoin/pull/8935 right? that adds instructions for building on windows 10 using the built in ubuntu 14.04 subsystem
 3262016-10-18T11:17:17  <wumpus> would help if someone tested those steps
 3272016-10-18T11:18:01  <Victorsueca> wumpus: testing required? sure, I'll try it
 3282016-10-18T11:18:12  <wumpus> it *looks* easy
 3292016-10-18T11:20:38  <sipa> seriously, who would have believed you if 10 years ago someone told you that a future version of windows would ship with a built-in ubuntu environment...
 3302016-10-18T11:21:08  <sipa> it still boggles my mind how much changed
 3312016-10-18T11:21:13  <wumpus> yes. it's extremely surprising to me, even now. I intend to try it out but haven't found the time yet
 3322016-10-18T11:21:23  <wumpus> indeed
 3332016-10-18T11:22:42  <wumpus> the list of top OS-es includes a Linux and a BSD derivative, and windows is not doing that well
 3342016-10-18T11:24:19  <wumpus> no one would have believed that in the 90's, heck not even any science fiction precited it :)
 3352016-10-18T11:32:26  <GitHub176> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/614d522c3e44...dd07c6b2cc90
 3362016-10-18T11:32:26  <GitHub176> bitcoin/master b26a7b5 Jorge Timón: RPC: Chainparams: Remove Chainparams::fTestnetToBeDeprecatedFieldRPC
 3372016-10-18T11:32:27  <GitHub176> bitcoin/master dd07c6b Wladimir J. van der Laan: Merge #8921: RPC: Chainparams: Remove Chainparams::fTestnetToBeDeprecatedFieldRPC...
 3382016-10-18T11:32:35  <GitHub47> [bitcoin] laanwj closed pull request #8921: RPC: Chainparams: Remove Chainparams::fTestnetToBeDeprecatedFieldRPC (master...0.13-rpc-chain) https://github.com/bitcoin/bitcoin/pull/8921
 3392016-10-18T11:32:44  *** justanotheruser has quit IRC
 3402016-10-18T11:33:21  <Victorsueca> linux on windows feels much like the universe is going to implode
 3412016-10-18T11:34:42  <GitHub192> [bitcoin] pedrobranco opened pull request #8952: Add selection options to listunspent RPC call (master...enhancement/improve-rpc-listunspent) https://github.com/bitcoin/bitcoin/pull/8952
 3422016-10-18T11:52:36  *** Naphex has quit IRC
 3432016-10-18T12:04:59  *** davec has quit IRC
 3442016-10-18T12:05:46  *** davec has joined #bitcoin-core-dev
 3452016-10-18T12:09:35  <michagogo> 14:20:40 <sipa> seriously, who would have believed you if 10 years ago someone told you that a future version of windows would ship with a built-in ubuntu environment...
 3462016-10-18T12:10:12  <michagogo> AIUI it's more like a built-in, disabled-by-default, hook that can then proceed to download an Ubuntu environment
 3472016-10-18T12:11:36  <michagogo> i.e. you first need the computer in dev mode, then you go to the "enable/disable optional features" panel - same place you can enable things like built in telnet client, and all kinds of other niche stuff
 3482016-10-18T12:12:06  <michagogo> Then that installs the "bash" stub that kicks off the install proces
 3492016-10-18T12:12:52  <michagogo> wumpus: and yeah, from what I've read it seems there shouldn't really be any reason for it not to work
 3502016-10-18T12:13:11  <michagogo> I mean, it's a full Ubuntu environment, running actual Linux binaries
 3512016-10-18T12:13:29  <michagogo> And the software build process doesn't exactly involve any exotic syscalls...
 3522016-10-18T12:13:46  <luke-jr> somehow I doubt it supports LXC or KVM
 3532016-10-18T12:13:56  <luke-jr> so probably can't do gitian at least
 3542016-10-18T12:14:03  <michagogo> (Things like lxc, mknods, chroots, etc reportedly don't work)
 3552016-10-18T12:14:07  <wumpus> luke-jr: that's not what is described there, though
 3562016-10-18T12:14:08  <michagogo> luke-jr: right
 3572016-10-18T12:14:16  <sipa> just depends build would be nice
 3582016-10-18T12:14:27  <michagogo> sipa: yeah, I'm pretty sure that should work
 3592016-10-18T12:14:27  <wumpus> but I'd assume the same - user namespaces support is quite esoteric
 3602016-10-18T12:14:48  <michagogo> I'll see if my mom will let me put WSL on her computer
 3612016-10-18T12:16:02  <luke-jr> michagogo: does chattr +i work? :P
 3622016-10-18T12:16:42  <wumpus> extended attributes? I'd bet not
 3632016-10-18T12:16:46  <michagogo> ;;Google chattr
 3642016-10-18T12:16:46  <gribble> chattr - Wikipedia: <https://en.wikipedia.org/wiki/Chattr>; chattr (1): change file attribs on file system - Linux man page: <https://linux.die.net/man/1/chattr>; 5 ' chattr ' Commands to Make Important Files IMMUTABLE - Tecmint: <http://www.tecmint.com/chattr-command-examples/>
 3652016-10-18T12:16:58  <Victorsueca> installing WSL right now on my dev machine...
 3662016-10-18T12:17:15  <wumpus> I'd already be surprised if they somehow properly map posix ACLs to linux ones
 3672016-10-18T12:17:20  <wumpus> eh to windows ones
 3682016-10-18T12:19:09  <jonasschnelli> does the WIN10 WSL comes with a window manager in a windows-window? Probably no...
 3692016-10-18T12:19:50  <wumpus> heh seems in the same year OpenBSD removed support for linux executables, windows added it
 3702016-10-18T12:20:02  <wumpus> jonasschnelli: no, it doesn't come with GUI support
 3712016-10-18T12:20:23  <wumpus> libwin32gui on ubuntu would be kind of interesting, though heretical :)
 3722016-10-18T12:22:12  <wumpus> though I doubt there's anything preventing your from running a windows X server on windows and connect to that
 3732016-10-18T12:22:25  <wumpus> circuitous, but meh
 3742016-10-18T12:22:33  <luke-jr> wumpus: chattr is non-extended attributes though! :P
 3752016-10-18T12:22:35  <michagogo> WSL File System Support – Windows Subsystem for Linux https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/
 3762016-10-18T12:23:46  <wumpus> is there any use for chattr +i besides sadist trolling of linux newbies?
 3772016-10-18T12:24:08  <luke-jr> wumpus: making sure I don't delete very important files :P
 3782016-10-18T12:24:15  <wumpus> ooh :D
 3792016-10-18T12:24:46  <luke-jr> find -type f | xargs chattr +i # in my family photos
 3802016-10-18T12:25:51  <michagogo> Ooh
 3812016-10-18T12:26:03  <michagogo> WSL may make it possible to run Gitian in a real VM!
 3822016-10-18T12:26:13  <michagogo> On Windows, without nesting, I mean!
 3832016-10-18T12:27:05  <jtimon> ping #8855 (testchains easier to create, less use of globals)
 3842016-10-18T12:29:33  <GitHub180> [bitcoin] laanwj closed pull request #8909: Change bundle identifiers (master...bc) https://github.com/bitcoin/bitcoin/pull/8909
 3852016-10-18T12:32:40  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 3862016-10-18T12:33:53  <GitHub117> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/dd07c6b2cc90...6e094e54f7ff
 3872016-10-18T12:33:53  <GitHub117> bitcoin/master d51f182 jnewbery: Don't return the address of a P2SH of a P2SH.
 3882016-10-18T12:33:54  <GitHub117> bitcoin/master 6e094e5 Wladimir J. van der Laan: Merge #8845: Don't return the address of a P2SH of a P2SH...
 3892016-10-18T12:34:02  <GitHub116> [bitcoin] laanwj closed pull request #8845: Don't return the address of a P2SH of a P2SH (master...trivial-P2SH-P2SH) https://github.com/bitcoin/bitcoin/pull/8845
 3902016-10-18T12:36:01  <michagogo> luke-jr: chattr: inappropriate ioctl for device while reading flags on test
 3912016-10-18T12:36:09  *** MarcoFalke has left #bitcoin-core-dev
 3922016-10-18T12:41:51  *** Chris_Stewart_5 has quit IRC
 3932016-10-18T12:42:25  <GitHub22> [bitcoin] laanwj pushed 2 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/907c314057b0...685e4c78f8ed
 3942016-10-18T12:42:26  <GitHub22> bitcoin/0.13 3f508ed Wladimir J. van der Laan: rpc: Generate auth cookie in hex instead of base64...
 3952016-10-18T12:42:26  <GitHub22> bitcoin/0.13 685e4c7 Matt Corallo: Remove bogus assert on number of oubound connections....
 3962016-10-18T12:45:16  <michagogo> Got WSL up and running, doing what I said before (13:33:46 <michagogo> As of 0.10, this is all you needed to do to cross-compile for Windows:  https://www.irccloud.com/pastebin/W6gIBKMf)
 3972016-10-18T12:45:33  <michagogo> So far so good -- needed to install make
 3982016-10-18T12:45:43  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 3992016-10-18T12:46:16  <michagogo> Depends is running now -- managed to build ccache, so that's good -- downloading boost right now
 4002016-10-18T12:47:22  <GitHub136> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/6e094e54f7ff...c71a654c5fff
 4012016-10-18T12:47:22  <GitHub136> bitcoin/master f2e939b fanquake: [Doc] Update Doxygen configuration file
 4022016-10-18T12:47:23  <GitHub136> bitcoin/master c71a654 Wladimir J. van der Laan: Merge #8890: [Doc] Update Doxygen configuration file...
 4032016-10-18T12:47:28  <wumpus> michagogo: great!
 4042016-10-18T12:47:37  <GitHub49> [bitcoin] laanwj closed pull request #8890: [Doc] Update Doxygen configuration file (master...update-doxyfile-1-8-12) https://github.com/bitcoin/bitcoin/pull/8890
 4052016-10-18T12:48:21  <achow101> michagogo: I've been able to compile both linux and windows binaries on WSL
 4062016-10-18T12:48:29  <achow101> but I haven't gotten gitian to work yet
 4072016-10-18T12:49:49  * wumpus would be really surprised if you get gitian to work as-is. You could try to launch the descriptors without VM (as michagogo said), and build like that, after all it's the same OS as unsed in the internal VM in gitian. But you may have some work getting the same output as others
 4082016-10-18T12:50:29  <michagogo> wumpus: not what I meant
 4092016-10-18T12:50:40  <michagogo> I meant, run gitian itself in WSL
 4102016-10-18T12:50:44  <michagogo> And use VBox
 4112016-10-18T12:50:55  <wumpus> you can't run gitian in WSL, there's no virtualization support
 4122016-10-18T12:51:15  * luke-jr wonders if WSL can call Windows-build qemu
 4132016-10-18T12:51:15  <michagogo> No, but maybe it can control native vbox
 4142016-10-18T12:51:26  <michagogo> Or ^^
 4152016-10-18T12:51:44  <wumpus> luke-jr: indeed, if you can launch native exes
 4162016-10-18T12:52:07  <wumpus> windows qemu is strange though
 4172016-10-18T12:52:09  <luke-jr> at least in the kqemu days, IIRC there was virt support for qemu on windows
 4182016-10-18T12:52:34  <wumpus> I tried that once, and was unable to get accelerated virtualization to work
 4192016-10-18T12:53:12  <luke-jr> kqemu is pretty old stuff :p
 4202016-10-18T12:53:17  <luke-jr> pre-VT-x
 4212016-10-18T12:53:28  <michagogo> Hrm
 4222016-10-18T12:53:30  <wumpus> it may need some special driver that needs to be installed as admin, dunno
 4232016-10-18T12:53:38  <michagogo> Nope, it looks like it's a full environment
 4242016-10-18T12:53:41  <michagogo> Not like cygwin
 4252016-10-18T12:54:35  <michagogo> bash: /mnt/c/Windows/System32/gpupdate.exe: cannot execute binary file: Exec format error
 4262016-10-18T12:55:22  <michagogo> Looks like within WSL it's Linux-only
 4272016-10-18T12:55:38  <michagogo> I wonder if there's a way to workaround it
 4282016-10-18T12:56:34  <achow101> wine in wsl ;D
 4292016-10-18T12:57:18  <michagogo> Hmmmmm
 4302016-10-18T12:57:40  <wumpus> hahha OSS people aren't happy until they can do a full emualtion roundtrip
 4312016-10-18T12:59:36  <Victorsueca> would it be possible to do WSL on Wine on WSL.... :P
 4322016-10-18T12:59:50  <Victorsueca> Inception!
 4332016-10-18T13:00:16  <wumpus> :')
 4342016-10-18T13:01:43  <wumpus> shouldn't be to difficult to support the WSL syscalls in wine
 4352016-10-18T13:03:00  <michagogo> Wine doesn't want to install
 4362016-10-18T13:03:16  <michagogo> Looks like a bunch of i386 packages not coming in
 4372016-10-18T13:03:20  <wumpus> I'd expected so
 4382016-10-18T13:03:28  <luke-jr> wumpus: lol
 4392016-10-18T13:03:39  <michagogo> I wish apt were better at showing actual cause
 4402016-10-18T13:04:12  <michagogo> It says winehq-devel : Depends: wine-devel
 4412016-10-18T13:04:15  <timothy> hi, do you think can be good to add support for rpc to tor?
 4422016-10-18T13:04:22  <timothy> actually only 8333 is supported
 4432016-10-18T13:04:23  <wumpus> not just a matter of sudo dpkg --add-architecture i386  ?
 4442016-10-18T13:04:25  <michagogo> (Unmet dependency)
 4452016-10-18T13:04:29  <michagogo> wumpus: I did that first
 4462016-10-18T13:04:47  <timothy> (integrated, I mean. ofc you can use the "standard" tor feature to add rpc port)
 4472016-10-18T13:04:49  <michagogo> And it says "you have held broken packages", which is misleading
 4482016-10-18T13:05:09  <michagogo> Anyway, wine-devel then depends on wine-devel-i386
 4492016-10-18T13:05:12  <wumpus> timothy: if you really want to expose your RPC port on a Tor hidden service that's possible
 4502016-10-18T13:05:37  <michagogo> And that, in turn, depends on a whole lot of :i386 packages
 4512016-10-18T13:05:39  <wumpus> timothy: wouldn't advice doing it by default though, a lot of scope to mess up
 4522016-10-18T13:05:46  <timothy> wumpus: actually I use it only for opentimestamps
 4532016-10-18T13:05:48  <michagogo> Some say "but it is not going to be installed"
 4542016-10-18T13:05:56  <timothy> I don't have any wallets here
 4552016-10-18T13:06:02  <michagogo> But then some say "but it is not installable"
 4562016-10-18T13:06:20  <wumpus> at the least don't give the onion address to anyone (or link it anywhere public) otherwise it will be picked up and probed by projects like onionscan
 4572016-10-18T13:06:32  <michagogo> Maybe I could poke at it and figure out what's going on, but a. I don't really care enough
 4582016-10-18T13:06:43  <michagogo> And b. I doubt I'd be able to figure it out anyway :P
 4592016-10-18T13:06:44  <timothy> wumpus: ofc it's only for private use and on another port (not 8332)
 4602016-10-18T13:07:30  <wumpus> if you have no wallet on the node it's certainly safer, though still: RPC is not a public interface, it's not as hardened against DoS and other attacks as the P2P
 4612016-10-18T13:07:45  <michagogo> Would be nice if depends could multitask
 4622016-10-18T13:08:00  <timothy> wumpus: so do you suggest me to add another layer like stunnel with client cert?
 4632016-10-18T13:08:09  <wumpus> timothy: for private use it's fine
 4642016-10-18T13:08:31  <luke-jr> michagogo: it can't?
 4652016-10-18T13:08:56  <wumpus> timothy: no need for that, tor has hs security built-in, look into "hidden service authentication"
 4662016-10-18T13:09:40  <wumpus> with HidServAuth something you can restrict who can connect to your hidden service with certain keys
 4672016-10-18T13:09:41  <michagogo> luke-jr: I mean, maybe -jx works within a build
 4682016-10-18T13:09:54  <michagogo> But I mean, for example, download and build different packages in parallel
 4692016-10-18T13:10:09  <timothy> wumpus: not bad, thank you
 4702016-10-18T13:10:11  <luke-jr> michagogo: make -jN in depends/?
 4712016-10-18T13:10:17  <michagogo> luke-jr: I did that
 4722016-10-18T13:10:29  <michagogo> Maybe each individual compilation job is multitasking
 4732016-10-18T13:10:36  <michagogo> But it's doing one package at a time
 4742016-10-18T13:10:58  *** MarcoFalke has joined #bitcoin-core-dev
 4752016-10-18T13:11:00  <luke-jr> weird
 4762016-10-18T13:11:02  <michagogo> So as OpenSSL.org is feeding me the file at 1000 bytes a second, it's holding up the whole thing
 4772016-10-18T13:11:03  <GitHub106> [bitcoin] MarcoFalke opened pull request #8954: contrib: Add README for pgp keys (master...Mf1610-docKeys) https://github.com/bitcoin/bitcoin/pull/8954
 4782016-10-18T13:11:29  <michagogo> Oh, wait -- we have a fallback to our server, right?
 4792016-10-18T13:11:36  * michagogo kills curl
 4802016-10-18T13:11:54  <michagogo> Hah. Pulled it from bitcoincore.org in like 10 secs
 4812016-10-18T13:12:04  <Victorsueca> lol
 4822016-10-18T13:12:44  <michagogo> Anyway, depends build in WSL chugging along
 4832016-10-18T13:12:49  <michagogo> Building BDB now
 4842016-10-18T13:13:00  <Victorsueca> libboost is taking a eternity to unpack here
 4852016-10-18T13:13:02  <michagogo> (I told make NO_QT=1)
 4862016-10-18T13:13:12  <michagogo> Victorsueca: SSDs ftw
 4872016-10-18T13:13:55  <michagogo> Depends done!
 4882016-10-18T13:14:07  <wumpus> libboost takes longer to unpack than to build, generally
 4892016-10-18T13:14:30  <wumpus> (at least in depends; we severly restrict the subset of boost that is built)
 4902016-10-18T13:17:02  <GitHub53> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c71a654c5fff...f628d9a29a2d
 4912016-10-18T13:17:03  <GitHub53> bitcoin/master 1724a40 R E Broadley: Display minimum ping in debug window.
 4922016-10-18T13:17:03  <GitHub53> bitcoin/master f628d9a Wladimir J. van der Laan: Merge #8925: qt: Display minimum ping in debug window....
 4932016-10-18T13:17:19  <GitHub157> [bitcoin] laanwj closed pull request #8925: qt: Display minimum ping in debug window. (master...DebugWindowMinPing) https://github.com/bitcoin/bitcoin/pull/8925
 4942016-10-18T13:17:49  <wumpus> jtimon: will take a look at that
 4952016-10-18T13:18:21  <jtimon> wumpus: cool, thanks
 4962016-10-18T13:18:26  <michagogo> Configured! Now for the moment of truth:
 4972016-10-18T13:18:51  <wumpus> < michagogo> (I told make NO_QT=1) <- oh no but then you won't get the GUI, which all windows users really want!
 4982016-10-18T13:18:55  * michagogo make -j8
 4992016-10-18T13:19:07  <michagogo> wumpus: yeah, but this is a poc
 5002016-10-18T13:19:22  <michagogo> I don't want to download and build qt for this
 5012016-10-18T13:19:23  <wumpus> michagogo: right
 5022016-10-18T13:19:35  <wumpus> yes, agreed, that takes ages
 5032016-10-18T13:19:40  <michagogo> (Unless you think there's a chance it might not work where everything else might?)
 5042016-10-18T13:20:21  <wumpus> there's some small chance of that because of the cross-build X stuff, and all the other deps qt drags in, but it'll probably work
 5052016-10-18T13:20:48  <michagogo> https://usercontent.irccloud-cdn.com/file/5BV08yei/1476796841.JPG
 5062016-10-18T13:21:23  <wumpus> uh scratch that... no, no X stuff.. you're cross-building for windows
 5072016-10-18T13:22:46  <michagogo> 🎉 https://usercontent.irccloud-cdn.com/file/CZ2ckANc/1476796939.JPG
 5082016-10-18T13:23:34  *** cryptapus has joined #bitcoin-core-dev
 5092016-10-18T13:23:57  <wumpus> motion blurred pixels, woo almost the matrix
 5102016-10-18T13:24:20  <michagogo> It works! https://usercontent.irccloud-cdn.com/file/d2GHULdO/1476797054.JPG
 5112016-10-18T13:25:01  <wumpus> -help works at least :-)
 5122016-10-18T13:25:16  <michagogo> Well, no args in this case
 5132016-10-18T13:25:18  <michagogo> But yeah
 5142016-10-18T13:25:26  <Victorsueca> michagogo: try to query the genesis block
 5152016-10-18T13:25:30  <michagogo> But the binary executes!
 5162016-10-18T13:25:33  <MarcoFalke> test_bitcoin.exe
 5172016-10-18T13:25:50  <michagogo> Victorsueca: nah, not gonna run it and set up a datadir on this machine
 5182016-10-18T13:26:16  <wumpus> test_bitcoin is a good suggestion
 5192016-10-18T13:26:30  <michagogo> Is that self-contained?
 5202016-10-18T13:26:38  <wumpus> if that passes we can tested-ACK and merge #8935
 5212016-10-18T13:26:42  <wumpus> yes
 5222016-10-18T13:27:18  <michagogo> Running 212 test cases…
 5232016-10-18T13:29:07  <wumpus> congrats, you've succeeded building bitcoin core for windows on windows before I succeeded building bitcoin core for android on android
 5242016-10-18T13:29:19  <michagogo> Heh
 5252016-10-18T13:29:32  <michagogo> Well, to be fair, Microsoft and Canonical made it really easy
 5262016-10-18T13:32:28  <michagogo> BTW, where is bitcoincore.org?
 5272016-10-18T13:32:54  <michagogo> Looks like it's only 2 hops past the last hop that resolves to a name including my ISO
 5282016-10-18T13:32:56  <michagogo> ISP
 5292016-10-18T13:34:06  <michagogo> Oh, in the meantime:
 5302016-10-18T13:34:14  <michagogo> *** No errors detected
 5312016-10-18T13:34:20  <wumpus> good!
 5322016-10-18T13:35:37  <GitHub112> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f628d9a29a2d...0306978394db
 5332016-10-18T13:35:37  <GitHub112> bitcoin/master 7c1716f poole_party: Documentation for Building on Windows with WSL...
 5342016-10-18T13:35:37  <GitHub112> bitcoin/master 0306978 Wladimir J. van der Laan: Merge #8935: Documentation: Building on Windows with WSL...
 5352016-10-18T13:35:51  <GitHub40> [bitcoin] laanwj closed pull request #8935: Documentation: Building on Windows with WSL (master...windows_build_docs) https://github.com/bitcoin/bitcoin/pull/8935
 5362016-10-18T13:37:03  <Victorsueca> I'm going to compile it with GUI support and try it out on a actual datadir
 5372016-10-18T13:37:25  *** jlopp has joined #bitcoin-core-dev
 5382016-10-18T13:37:56  <wumpus> Victorsueca: great
 5392016-10-18T13:39:46  <michagogo> This series of commands seems to be all that's needed, on a completely fresh WSL: https://www.irccloud.com/pastebin/W6gIBKMf
 5402016-10-18T13:40:22  <wumpus> michagogo: may make sense to add that to build-windows.md, in as far as it's not the same as alredy in there
 5412016-10-18T13:40:47  <wumpus> it's impressive how few commands it is though
 5422016-10-18T13:41:49  <michagogo> Kudos to cfields_ for the depends system...
 5432016-10-18T13:41:51  <wumpus> michagogo: bitcoincore.org is behind cloudflare, so that's probably one of their co-located "spy servers" close to you :)
 5442016-10-18T13:42:06  <michagogo> wumpus: ah, yeah, that explains the speed too
 5452016-10-18T13:44:18  <michagogo> Who's
 5462016-10-18T13:44:21  <michagogo> Whoa*
 5472016-10-18T13:44:50  <michagogo> QT on an SSD with -j9 on a quad-core i5-6600K is really not so bad
 5482016-10-18T13:45:35  <GitHub63> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0306978394db...cdfb7755a6af
 5492016-10-18T13:45:36  <GitHub63> bitcoin/master 5eaaa83 Wladimir J. van der Laan: Kill insecure_random and associated global state...
 5502016-10-18T13:45:36  <GitHub63> bitcoin/master cdfb775 Wladimir J. van der Laan: Merge #8914: Kill insecure_random and associated global state...
 5512016-10-18T13:45:49  <GitHub104> [bitcoin] laanwj closed pull request #8914: Kill insecure_random and associated global state (master...2016_10_kill_insecurerandom) https://github.com/bitcoin/bitcoin/pull/8914
 5522016-10-18T13:45:58  <michagogo> It was certainly a few minutes, but not nearly as bad as in gitian
 5532016-10-18T13:46:14  <GitHub174> [bitcoin] laanwj closed pull request #7753: zmq: mempool notifications (master...2016_03_zmq_mempool_notifications) https://github.com/bitcoin/bitcoin/pull/7753
 5542016-10-18T13:46:22  <michagogo> (I'm also not sure I've done a gitian build with a qt bump since upgrading to an SSD...)
 5552016-10-18T13:46:42  <wumpus> what parallelism do you use in gitian?
 5562016-10-18T13:46:53  <michagogo> -j5, maybe?
 5572016-10-18T13:47:05  <michagogo> It's in a VM, on an i7-3610QM
 5582016-10-18T13:47:19  <michagogo> I think the VM might have 3 cores, though
 5592016-10-18T13:48:14  <michagogo> Also: cache is nice
 5602016-10-18T13:48:31  <michagogo> ccache*
 5612016-10-18T13:48:46  <michagogo> Watching the build with Qt fly by
 5622016-10-18T13:49:24  <molz> michagogo, do you need to install all the dependencies first before using https://www.irccloud.com/pastebin/W6gIBKMf  ?
 5632016-10-18T13:49:32  *** cryptapus has quit IRC
 5642016-10-18T13:49:39  <michagogo> molz: which dependencies?
 5652016-10-18T13:49:55  <michagogo> The ones for Bitcoin are downloaded and built by those commands
 5662016-10-18T13:50:03  <michagogo> (The cd depends;make HOST...)
 5672016-10-18T13:50:25  <molz> oh..
 5682016-10-18T13:50:30  <michagogo> The apt-get command installs everything that the build process needs
 5692016-10-18T13:51:17  <michagogo> Like I said, if you install WSL completely fresh from scratch (or for that matter, "real" Ubuntu 14.04...), those commands are everything you need to produce Bitcoin-qt.exe
 5702016-10-18T13:51:23  <michagogo> (And all the others)
 5712016-10-18T13:52:44  <michagogo> wumpus: what is test_bitcoin-qt.exe supposed to do?
 5722016-10-18T13:52:57  <michagogo> It seems to just return to the command line immediately
 5732016-10-18T13:52:59  <michagogo> No output
 5742016-10-18T13:53:01  <sipa> run the bitcoin-qt unit test
 5752016-10-18T13:53:46  <michagogo> sipa: is it supposed to output anything, like test_bitcoin.exe does?
 5762016-10-18T13:53:48  <wumpus> it should print something about Start Testing Finished Testing, normally
 5772016-10-18T13:53:54  <sipa> unsure
 5782016-10-18T13:54:04  <michagogo> Doesn't look like it?
 5792016-10-18T13:54:06  <wumpus> but I've never tried it in windows
 5802016-10-18T13:54:15  <molz> michagogo, ok i'm not on win10, can the irccloud guide be used on Ubuntu 14.4 VM ?
 5812016-10-18T13:54:15  <michagogo> I just get the prompt back
 5822016-10-18T13:54:28  <molz> i'm installing Ubuntu 14.4 on the VM right now
 5832016-10-18T13:54:28  <wumpus> maybe it's accidentally compiled as a UI subsystem instead of console subsystem executable?
 5842016-10-18T13:54:47  <michagogo> molz: yeah, those commands should work on a fresh install of 14.04
 5852016-10-18T13:54:55  <sipa> wumpus: maybe not accidentally... a qt app may need to be gui
 5862016-10-18T13:54:58  <molz> ok, thanks, going to try it now
 5872016-10-18T13:55:04  <MarcoFalke> Anything holding back https://github.com/bitcoin/bitcoin/pull/8928
 5882016-10-18T13:55:22  <wumpus> sipa: it doesn't need to be, console will just open a console at startup, it can still use the UI APIs
 5892016-10-18T13:55:33  <sipa> ah
 5902016-10-18T13:55:46  <wumpus> (though none of the Qt unit tests does anything with UI)
 5912016-10-18T13:55:55  <michagogo> We don't seem to ship test_bitcoin-qt.exe
 5922016-10-18T13:56:04  <wumpus> that's on purpose - it's silly right now
 5932016-10-18T13:56:20  <michagogo> The win64 zip for 0.13.0 from Bitcoin.org has test_bitcoin.exe but not -qt
 5942016-10-18T13:56:20  <wumpus> it's a huge executable when statically linking, pulling in much of qt, for no good reason
 5952016-10-18T13:56:42  <michagogo> So I'm guessing it's not something wrong with this build setup
 5962016-10-18T13:56:49  <wumpus> yes, test_bitcoin.exe is suposed to be in there
 5972016-10-18T13:56:54  <wumpus> I'm guessing the same
 5982016-10-18T13:57:12  <michagogo> If I run Bitcoin-Qt.exe with a -datadir argument, does it leave traces of itself anywhere but that directory?
 5992016-10-18T13:57:34  <sipa> it shouldn't
 6002016-10-18T13:57:37  <wumpus> yes - in the registry
 6012016-10-18T13:57:46  <wumpus> bitcoind.exe shouldn't, though
 6022016-10-18T13:58:03  <michagogo> Anything outside a simple key named for the app?
 6032016-10-18T13:58:24  <wumpus> no, it's one 'directory' named bitcoin-qt or such
 6042016-10-18T13:58:27  <wumpus> with qt settings
 6052016-10-18T13:59:04  <michagogo> Okay, that's tolerable
 6062016-10-18T13:59:12  *** Chris_Stewart_5 has quit IRC
 6072016-10-18T13:59:37  *** fengling has joined #bitcoin-core-dev
 6082016-10-18T13:59:45  <GitHub53> [bitcoin] mruddy opened pull request #8955: trivial: update 0.13.0 release note info on linux arm builds (master...relnote) https://github.com/bitcoin/bitcoin/pull/8955
 6092016-10-18T13:59:52  *** Guyver2 has joined #bitcoin-core-dev
 6102016-10-18T14:00:17  <Victorsueca> cpp not working here
 6112016-10-18T14:01:41  <Victorsueca> error C++ processort /lib/cpp fails sanity check
 6122016-10-18T14:01:46  <Victorsueca> processor*
 6132016-10-18T14:02:17  <sipa> what are you doing
 6142016-10-18T14:03:23  <michagogo> WSL-built 0.13.1rc1 is running!
 6152016-10-18T14:03:24  <wumpus> michagogo: HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt and HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt-testnet
 6162016-10-18T14:03:31  *** aalex has joined #bitcoin-core-dev
 6172016-10-18T14:04:09  <michagogo> Also: looks like tailf doesn't work in WSL
 6182016-10-18T14:04:35  <michagogo> tailf: <path>: cannot add inotify watch.: Invalid argument
 6192016-10-18T14:05:10  <michagogo> (Looks like all my peers have WITNESS in services
 6202016-10-18T14:05:11  <michagogo> )
 6212016-10-18T14:05:29  <michagogo> 3 claim to be 0.13.0, 2 0.13.1, and 2 0.13.99
 6222016-10-18T14:05:42  <Victorsueca> sipa: this https://gist.github.com/Victorsueca/62d3dc1c3db26da2326ed24e4308617d
 6232016-10-18T14:06:05  <michagogo> (Oh, right -- rc1 still calls itself .0)
 6242016-10-18T14:06:22  <wumpus> yes
 6252016-10-18T14:06:30  <michagogo> Victorsueca: did you install g++?
 6262016-10-18T14:06:39  <michagogo> Pretty sure that was in my paste
 6272016-10-18T14:06:48  <wumpus> the 0.13.0 ones are rc1, 0.13.1 ones are 0.13 branch, 0.13.99 is master. It checks out
 6282016-10-18T14:07:16  <Victorsueca> michagogo: I'm not following your paste, i'm using the docs
 6292016-10-18T14:07:20  <Victorsueca> thanks,i'll try that
 6302016-10-18T14:07:40  <michagogo> Maybe we should copy my paste to the docs
 6312016-10-18T14:07:56  <wumpus> sanity check failures in configure 99% of the time mean that the compiler just isn't installed
 6322016-10-18T14:08:06  <michagogo> (Also, maybe go over and check that that is the absolute minimum)
 6332016-10-18T14:08:43  <wumpus> (unless you happen to be overriding the compiler to a static analysis tool etc)
 6342016-10-18T14:09:41  <Victorsueca> seems to be working now
 6352016-10-18T14:10:43  <Victorsueca> nope, autoconf is missing
 6362016-10-18T14:10:59  *** To7 has quit IRC
 6372016-10-18T14:11:12  <jlopp> I asked these questions in wizards yesterday; crossposting for more visibility:
 6382016-10-18T14:11:24  <jlopp> I'm trying to better understand the purpose and future use of checkpoints in Bitcoin. My understanding is that the checkpoints are in place in order to prevent attackers from spamming nodes with low PoW block headers at low chain heights. And that a side effect of checkpoints is a performance speedup in initial block download due to skipping signature verification.
 6392016-10-18T14:11:37  <jlopp> Though I thought that since libsecp256k1 drastically increases signature validation performance, the speedup is negligible now.
 6402016-10-18T14:11:47  <jlopp> back in 2013, gmaxwell said "When headers first syncing is merged, just by adding a "must be this tall" minimum sum difficulty check we'll be able to remove checkpoints for all DOS purposes, and we'll also be able to remove them for syncing acceleration (using random sampling for ECDSA in the deeply buried chain)."
 6412016-10-18T14:11:56  <jlopp> seems like sipa also thought headers-first sync would enable removal of checkpoints... https://bitcoin.stackexchange.com/questions/7826/what-alternatives-are-there-to-hardcoding-checkpoints-into-the-bitcoin-client
 6422016-10-18T14:11:58  <wumpus> jlopp: helps to read https://github.com/bitcoin/bitcoin/issues/7591
 6432016-10-18T14:12:31  <wumpus> checkpoints really need to go, and are not part of the security model, however they are still used for three of so tasks which haven't been replaced with other implementations
 6442016-10-18T14:13:45  <wumpus> there's always the -checkpoints=0 option if you can't wait for them to be removed
 6452016-10-18T14:14:00  <jlopp> Am I correct in stating that it wouldn't be possible to feed any alternative chain of blocks to a full node if that alternative chain's starting point was prior to block 295000? It's also not clear to me why there are 13 checkpoints rather than just the last one at 295000
 6462016-10-18T14:14:26  *** bsm117532 has joined #bitcoin-core-dev
 6472016-10-18T14:15:50  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 6482016-10-18T14:15:51  <Victorsueca> https://gist.github.com/Victorsueca/442d36e6c16b490d5dc15399855810bc <--- no idea what went wrong now
 6492016-10-18T14:16:05  <BlueMatt> so....fibre....want more than one group/person to run a public network based on it
 6502016-10-18T14:16:06  <Victorsueca> the docs don't really explain what libraries you should get
 6512016-10-18T14:16:11  <BlueMatt> also want to shut down the rn on dec 1
 6522016-10-18T14:16:20  <BlueMatt> so that leaves....a week or two to get networks up
 6532016-10-18T14:18:14  *** Giszmo has joined #bitcoin-core-dev
 6542016-10-18T14:18:53  <sipa> BlueMatt: maybe someone at dci?
 6552016-10-18T14:19:29  <BlueMatt> that was suggested, I can reach out to neha and see if there are any students interested in running one
 6562016-10-18T14:19:50  <BlueMatt> I'm happy to run one, but want to use real servers which implies no longer wanting to pay for it out-of-pocket
 6572016-10-18T14:20:01  <BlueMatt> (and only if there is an additional one run by someone else)
 6582016-10-18T14:20:45  <neha> We can probably run one.  What are the bw/hard drive/mem/etc requirements?
 6592016-10-18T14:21:50  <BlueMatt> neha: i mean a network, not node
 6602016-10-18T14:22:17  <BlueMatt> which means dedicated servers roughly in similar locations as those on the map at http://bitcoinrelaynetwork.org/
 6612016-10-18T14:22:25  <nsh> cc musalbas
 6622016-10-18T14:22:35  <neha> a network starts with one node?  :) ok let me know what the requirements are and we can talk about it.  there probably will be student interest
 6632016-10-18T14:22:50  <BlueMatt> probably 100-200/mo per server (say, 5 of them + some auxillary stuff) if you're lazy about finding deals, maybe as low as 50
 6642016-10-18T14:23:13  <sipa> units?
 6652016-10-18T14:23:16  <sipa> what is a mo
 6662016-10-18T14:23:22  <wumpus> month
 6672016-10-18T14:23:36  <BlueMatt> usd/cad/eur/gbp/etc
 6682016-10-18T14:23:39  <BlueMatt> any of them are valid
 6692016-10-18T14:24:13  <sipa> ah
 6702016-10-18T14:24:15  <neha> could we get multiple universities to run nodes as part of one network?
 6712016-10-18T14:24:53  <BlueMatt> neha: because of the weird trust-all-nodes-in-the-network requirement if you want to run with cut-through on, thats....awkward
 6722016-10-18T14:25:19  <BlueMatt> neha: i mean could turn off the cut-through and do it
 6732016-10-18T14:25:37  <BlueMatt> if its on a fast-single-threading server with good peak bw that might be ok
 6742016-10-18T14:26:02  <sipa> the only issue is that the nodes within the network could dos each other, right?
 6752016-10-18T14:26:28  <BlueMatt> if you do trusted mode any node can break propagation for a block to the entire network
 6762016-10-18T14:26:31  <wumpus> so it's mainly miners using this right: aren't any miners/mining pools interested in setting up a network like this?
 6772016-10-18T14:26:56  <neha> do the nodes need to be geo-distributed?
 6782016-10-18T14:27:04  <neha> (i need to read more about fibre)
 6792016-10-18T14:27:16  <BlueMatt> wumpus: i have no idea why miners seemingly only ever provide lip-service to things like this :/
 6802016-10-18T14:27:30  <wumpus> BlueMatt: I was afraid you were going to say that
 6812016-10-18T14:27:48  <sipa> wumpus: arguably, it's more in the interest of the network at large that such a network exists, as opposed to miners running their own private setups that are harder to enter as an outsider
 6822016-10-18T14:27:49  <BlueMatt> wumpus: well, i do know, for many of them it doesnt matter because they just do spy-mining
 6832016-10-18T14:28:01  *** fengling has quit IRC
 6842016-10-18T14:28:02  <BlueMatt> neha: otherwise how are you propagating around the world? :p
 6852016-10-18T14:28:14  <sipa> BlueMatt: neutrinos.
 6862016-10-18T14:28:26  <BlueMatt> oooo bitcoin-over-neutrino
 6872016-10-18T14:28:37  <BlueMatt> might want to get ip-over-neutrino to work first, though
 6882016-10-18T14:28:39  <neha> this might be a good thing for a network of universities to do.
 6892016-10-18T14:28:52  <neha> don't need to worry too much about schools (intentionally) dos'ing each other
 6902016-10-18T14:28:54  <BlueMatt> neha: indeed, universities tend to have good low-latency bw between each other, too
 6912016-10-18T14:29:04  <Victorsueca> ip-over-dark-matter is better
 6922016-10-18T14:29:08  <BlueMatt> neha: well, I think it'd still need to run in non-trusted mode
 6932016-10-18T14:29:34  <BlueMatt> neha: you do need to worry about someone randomly fucking with one node to screw over block prop. for a given pool at unis
 6942016-10-18T14:29:47  <BlueMatt> security at uni-hosting places tends to be.......
 6952016-10-18T14:30:17  <Victorsueca> deficient? is that the word you're searching?
 6962016-10-18T14:30:29  <wumpus> Victorsueca: ip-over-microwormholes
 6972016-10-18T14:30:29  <sipa> BlueMatt: can you have two tiers? different orgs running their own nodes, internally cut-through, but not cut-through across orgs
 6982016-10-18T14:30:32  *** Chris_Stewart_5 has quit IRC
 6992016-10-18T14:30:36  <BlueMatt> sipa: yes
 7002016-10-18T14:30:41  <Victorsueca> wumpus: lol
 7012016-10-18T14:30:51  <sipa> BlueMatt: and then have maybe one org colocate one of their nodes inside or nearby another org's node
 7022016-10-18T14:31:08  <Victorsueca> wumpus: with that you could recieve data even before it's sent
 7032016-10-18T14:31:21  <BlueMatt> sipa: not sure how required the second part is...you just end up having a reconstruction-latency on the first hop into an org always
 7042016-10-18T14:31:30  <sipa> right
 7052016-10-18T14:31:37  <BlueMatt> sipa: fibre is rather packet-loss-insensitive :)
 7062016-10-18T14:34:39  <sipa> BlueMatt: well, in any case, it's probably easier to get people interested in this technology and infrastructure if you first ask to run just a node in an exisitng network
 7072016-10-18T14:35:17  <BlueMatt> sipa: true
 7082016-10-18T14:35:22  <neha> agree
 7092016-10-18T14:36:41  <neha> it would be helpful to think about how interested parties at a school could just stand up a node as part of an existing network
 7102016-10-18T14:37:02  <neha> we have almost "free" access to compute resources, but only locally.
 7112016-10-18T14:37:12  <BlueMatt> hmm, for that to be useful I think I'd have to run an actual network and let people peer into it
 7122016-10-18T14:37:56  <BlueMatt> which I'd gladly do, but dont want to funt it myself anymore if I'm gonna stand up a real network
 7132016-10-18T14:38:08  <neha> bitcoin foundation?
 7142016-10-18T14:38:17  <neha> or us i suppose depending on costs
 7152016-10-18T14:38:18  <BlueMatt> they dont have any $$$ left
 7162016-10-18T14:38:40  <neha> wouldnt your "network" be very small, with most of the resources provided being from people peering?
 7172016-10-18T14:38:59  <michagogo> Victorsueca: is there something wrong with that last gist?
 7182016-10-18T14:39:46  <michagogo> And in terms of all the libraries, if you mean the ones that go into Bitcoin Core (OpenSSL, Qt, boost, etc.), the whole beauty of the depends system is that you don't need to know about that
 7192016-10-18T14:39:58  <sipa> BlueMatt: we'll need a SF to commit to error correction packets :)
 7202016-10-18T14:40:20  <BlueMatt> sipa: yes, probalem is putting it in the coinbase is expensive, so we need a HF to commit to ECC packets :p
 7212016-10-18T14:40:22  <Victorsueca> michagogo: no idea, the console seemed to error out, but after spamming the make command a few times it started working
 7222016-10-18T14:40:30  <michagogo> Victorsueca: what did the consoel look like?
 7232016-10-18T14:41:01  <sipa> BlueMatt: last tx?
 7242016-10-18T14:41:07  <Victorsueca> michagogo: lots of error being spammed out, stuff outside of the directory, automake is not available....
 7252016-10-18T14:41:08  <sipa> BlueMatt: which you require to be small
 7262016-10-18T14:41:42  <BlueMatt> sipa: just traversing down the merkle tree is non-trivial in byte count when you only have <1500 bytes to play with
 7272016-10-18T14:41:49  <Victorsueca> I apt-get'd autoconf but still didn't work
 7282016-10-18T14:41:56  <michagogo> Okay, I just reset my WSL
 7292016-10-18T14:42:06  <michagogo> Going to figure out what's necessary and sufficient
 7302016-10-18T14:42:29  <Victorsueca> after spamming the make command a few times and now seems to work tho
 7312016-10-18T14:45:28  <Victorsueca> now it's doing checks....
 7322016-10-18T14:56:19  *** To7 has joined #bitcoin-core-dev
 7332016-10-18T14:56:55  <jtimon> Is nMaxTries in generateBlocks() [rpc/mining.cpp] very used and loved?
 7342016-10-18T14:58:20  <BlueMatt> one option for a fibre network: be super lazy and spin up servers primarily on softlayer - ~$1500/mo to softlayer and probably another 200 to other providers to bridge the gaps
 7352016-10-18T14:59:44  *** jlopp has quit IRC
 7362016-10-18T15:00:21  <achow101> BlueMatt: I may be able to run a fibre server at my school. It just depends on whether I can figure out how to get one from the school and if they will let me run it
 7372016-10-18T15:04:01  *** mturquette has quit IRC
 7382016-10-18T15:07:10  <Victorsueca> damn, missing pkg-config
 7392016-10-18T15:08:12  <michagogo> Yep, already got that on the list
 7402016-10-18T15:10:25  *** mturquette has joined #bitcoin-core-dev
 7412016-10-18T15:10:55  <michagogo> Interesting
 7422016-10-18T15:11:17  <michagogo> Looks like b2 (boost build tool) is passed -j2 regardless of the depends make -j argument
 7432016-10-18T15:11:22  <michagogo> (assuming it means the same thing there)
 7442016-10-18T15:12:25  <michagogo> Yep, hard-coded:   ./b2 -d2 -j2 -d1 --prefix=$($(package)_staging_prefix_dir) $($(package)_config_opts) stage
 7452016-10-18T15:12:41  <michagogo> cfields_: any particular reason for that?
 7462016-10-18T15:12:59  <wumpus> michagogo: does -j do the same for b2 as for make?
 7472016-10-18T15:13:09  <michagogo> Yeom just checked that
 7482016-10-18T15:13:12  <michagogo> Yep,*
 7492016-10-18T15:13:18  <michagogo> -j N
 7502016-10-18T15:13:18  <michagogo> Run up to N commands in parallel.
 7512016-10-18T15:13:27  <michagogo> from http://www.boost.org/build/doc/html/bbv2/overview/invocation.html
 7522016-10-18T15:13:36  <cfields_> michagogo: hmm, no reason. Just got left in after testing i guess
 7532016-10-18T15:13:38  <wumpus> ok. Probably accidental then
 7542016-10-18T15:13:50  <cfields_> I'm pretty sure you can grab the parallel value from make somehow
 7552016-10-18T15:14:15  <Victorsueca> I use make with -j4
 7562016-10-18T15:14:22  <michagogo> Hm, OpenSSL forces -j1
 7572016-10-18T15:14:32  <wumpus> yes, openssl is broken otherwise
 7582016-10-18T15:14:39  <wumpus> (the build, not the library)
 7592016-10-18T15:14:47  <cfields_> yes, that one's on purpose
 7602016-10-18T15:14:54  <michagogo> ah
 7612016-10-18T15:15:50  <wumpus> don't know if that's still the case with more recent openssl, but it used to be that there was a race between some parts of the builds (esp. when assembly enabled) preventing paralellel builds
 7622016-10-18T15:16:05  <Victorsueca> damn, can't reash confdefs.h No such file or directory
 7632016-10-18T15:16:09  <Victorsueca> read*
 7642016-10-18T15:16:21  <michagogo> Based on miniupnpc, I'm guessing that it inherits if not specified
 7652016-10-18T15:16:28  <michagogo> Oh, wait, for boost that doesn't work
 7662016-10-18T15:16:30  <wumpus> Victorsueca: I'm baffled that michagogo had such an easy time building while you seem to stumble into every possible issue :)
 7672016-10-18T15:16:52  <Victorsueca> wumpus: yeah, that usually hapens to me when compiling software
 7682016-10-18T15:16:55  <Victorsueca> lol
 7692016-10-18T15:17:22  <michagogo> Victorsueca: you're not on insider preview, are you?
 7702016-10-18T15:17:32  <Victorsueca> nope
 7712016-10-18T15:18:08  <Victorsueca> just plain windows 10 with aniversary update
 7722016-10-18T15:18:10  <michagogo> `lsb_release -r` shows 14.04?
 7732016-10-18T15:18:23  <michagogo> Packages all updated?
 7742016-10-18T15:19:00  <Victorsueca> yes, it's 14.04
 7752016-10-18T15:19:11  <Victorsueca> and apt-get upgrade shows everything updated
 7762016-10-18T15:23:21  <michagogo> Wait a minute, depends builds protobuf _twice_?
 7772016-10-18T15:23:31  <michagogo> I could have sworn it did that at the beginning
 7782016-10-18T15:24:13  <Victorsueca> I thought something may be corrupt on the source files and I deleted everything and started over
 7792016-10-18T15:24:56  <Victorsueca> I use the v0.13.1rc1 zipball from github
 7802016-10-18T15:25:25  <wumpus> try following exactly what michagogo does in his pastebin
 7812016-10-18T15:25:31  <wumpus> e.g. check out the tag from git
 7822016-10-18T15:25:37  <michagogo> I'm working on updating that right now
 7832016-10-18T15:25:41  <wumpus> ok
 7842016-10-18T15:25:43  <Victorsueca> ok
 7852016-10-18T15:26:02  <michagogo> So far, looks like this might be what's necessary and sufficient to make it work: https://www.irccloud.com/pastebin/W0iBQZbU/
 7862016-10-18T15:26:32  <Victorsueca> this is what the console show on the last moments of my last build attempt https://softnet.homenet.org/zerobin/?daf8a2764645a2bd#4llQib8JOqG6NNxNocDMs5tjND22lO+3+fVr2W8oots=
 7872016-10-18T15:26:36  <michagogo> If it fails I'll add g++-mingw-w64,  and if that fails I'll add mingw-w64
 7882016-10-18T15:26:44  <Victorsueca> now will try michagogo's pastebin
 7892016-10-18T15:31:04  <GitHub199> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/cdfb7755a6af...1e1b8ceb5ebc
 7902016-10-18T15:31:05  <GitHub199> bitcoin/master aa9d3c9 Steven: add software-properties-common...
 7912016-10-18T15:31:05  <GitHub199> bitcoin/master 1e1b8ce Wladimir J. van der Laan: Merge #8929: add software-properties-common...
 7922016-10-18T15:31:18  <GitHub70> [bitcoin] laanwj closed pull request #8929: add software-properties-common (master...patch-6) https://github.com/bitcoin/bitcoin/pull/8929
 7932016-10-18T15:33:05  <GitHub120> [bitcoin] rebroad opened pull request #8957: Additional UpdateBlockAvailability (master...AddUpdateBlockAvailability) https://github.com/bitcoin/bitcoin/pull/8957
 7942016-10-18T15:41:27  <GitHub185> [bitcoin] jl2012 closed pull request #8950: Update gitian signing key of jl2012 (master...patch-18) https://github.com/bitcoin/bitcoin/pull/8950
 7952016-10-18T15:43:02  <GitHub90> [bitcoin] rebroad opened pull request #8958: Improve logic for advertising blocks (master...BetterBroadcastLogic) https://github.com/bitcoin/bitcoin/pull/8958
 7962016-10-18T15:44:59  <wumpus> sigh
 7972016-10-18T15:45:35  <Victorsueca> wumpus: what's up?
 7982016-10-18T15:45:51  <wumpus> oh, rebroad spamming pr's again
 7992016-10-18T15:45:59  <Victorsueca> ahh lol
 8002016-10-18T15:46:03  <GitHub3> [bitcoin] rebroad opened pull request #8959: Fix sort arrow in peer table (master...FixPeerTableSort) https://github.com/bitcoin/bitcoin/pull/8959
 8012016-10-18T15:46:37  *** cryptapus has joined #bitcoin-core-dev
 8022016-10-18T15:46:37  *** cryptapus has joined #bitcoin-core-dev
 8032016-10-18T15:46:45  <michagogo> Good news
 8042016-10-18T15:47:09  <michagogo> https://www.irccloud.com/pastebin/W0iBQZbU/ does indeed seem to be necessary and sufficient for cross-compiling for 64-bit Windows
 8052016-10-18T15:47:24  <michagogo> On a completely fresh WSL 14.04
 8062016-10-18T15:47:47  <Victorsueca> still compiling here, will see if it works this time
 8072016-10-18T15:47:53  <GitHub117> [bitcoin] mruddy opened pull request #8960: doc: update 0.13.1 release note info on linux arm builds (0.13...relnote131) https://github.com/bitcoin/bitcoin/pull/8960
 8082016-10-18T15:49:00  <michagogo> (if you also want to build 32-bit, drop the -x86-64 at the end of l1)
 8092016-10-18T15:50:24  * wumpus wonders if anyone is still using 32-bit windows builds
 8102016-10-18T15:50:44  <Victorsueca> I was just about to ask if x32 computers are still a thing
 8112016-10-18T15:50:48  <wumpus> (except by accident on a 64-bit system)
 8122016-10-18T15:50:50  <GitHub192> [bitcoin] rebroad opened pull request #8961: Headers announcement for nodes that can do headers. (master...AnnounceUsingHeaders) https://github.com/bitcoin/bitcoin/pull/8961
 8132016-10-18T15:51:34  <wumpus> x86 32-bit is pretty much dead, I think it's still used for some obscure small VPSes, but who would still use it for windows
 8142016-10-18T15:53:05  <wumpus> this may be something that would make sense to ask on btctalk/reddit though, or maybe twitter
 8152016-10-18T15:53:21  <Victorsueca> gee, this is taking a eternitiy to build
 8162016-10-18T15:54:15  <michagogo> Victorsueca: Are you on a spinning disk or ssd?
 8172016-10-18T15:54:51  <michagogo> Looks like the whole thing including depends took a bit over an hour
 8182016-10-18T15:55:04  <michagogo> But that includes downloads of packages
 8192016-10-18T15:55:11  <michagogo> both apt-get, and depedns sources
 8202016-10-18T15:55:41  <molz> it took me half a day trying to build windows on debian VM and still didn't succeed
 8212016-10-18T15:55:44  <Victorsueca> michagogo: it finished just now, it's postprocessing ATM
 8222016-10-18T15:55:56  <michagogo> Victorsueca: postprocessing what?>
 8232016-10-18T15:56:03  <Victorsueca> openssl
 8242016-10-18T15:56:26  <GitHub64> [bitcoin] rebroad opened pull request #8962: Correct checksum error message (and debug node id) (master...CorrectChecksumError) https://github.com/bitcoin/bitcoin/pull/8962
 8252016-10-18T15:58:39  <michagogo> wumpus: Okay, so at some point I'll try to remember to PR my findings (in terms of packages)
 8262016-10-18T15:59:01  <michagogo> I have the week off, which is nice -- holiday season is nice
 8272016-10-18T15:59:23  <Victorsueca> postprocessing libevent now
 8282016-10-18T15:59:28  <michagogo> g2g for now, though -- gotta eat
 8292016-10-18T15:59:50  <Victorsueca> michagogo: see you
 8302016-10-18T15:59:58  <michagogo> (Oh, and the 0.13.1rc1 I produced earlier, ran, and forgot to stop is still running just fine)
 8312016-10-18T16:00:22  <michagogo> Up to block 312577, 2 hours after startup
 8322016-10-18T16:00:25  <michagogo> Killing it now, tho
 8332016-10-18T16:01:40  <GitHub24> [bitcoin] rebroad opened pull request #8963: NodeId missing from this debug line (master...SocketSendErrorNodeId) https://github.com/bitcoin/bitcoin/pull/8963
 8342016-10-18T16:02:27  <Victorsueca> is that rebroad guy just spamming crap or he is actually contributing?
 8352016-10-18T16:02:31  <wumpus> :-(
 8362016-10-18T16:02:55  <wumpus> he's done some constructive changes, but most is just 'change a debug message' here or there
 8372016-10-18T16:03:12  <wumpus> or weird broken changes to the P2P code
 8382016-10-18T16:03:28  <wumpus> a lot of review overhead for very little gain
 8392016-10-18T16:04:28  <GitHub62> [bitcoin] rebroad opened pull request #8964: Don't request compact blocks in blocksonly mode (master...NoCompactBlocksOnly) https://github.com/bitcoin/bitcoin/pull/8964
 8402016-10-18T16:04:59  <wumpus> fucking damnit
 8412016-10-18T16:05:24  <Victorsueca> I would swear I have already seen 3 PRs related to compact blocks
 8422016-10-18T16:05:39  <Victorsueca> can't he just PR all them in one?
 8432016-10-18T16:06:19  <wumpus> that would make sense
 8442016-10-18T16:07:23  <GitHub69> [bitcoin] laanwj closed pull request #8964: Don't request compact blocks in blocksonly mode (master...NoCompactBlocksOnly) https://github.com/bitcoin/bitcoin/pull/8964
 8452016-10-18T16:07:50  <Victorsueca> headshot
 8462016-10-18T16:08:02  <Victorsueca> laanwj the PR sniper
 8472016-10-18T16:10:32  <wumpus> trying, but will take more than a one-man-army to defend against PR spamming of this scale :)
 8482016-10-18T16:17:52  <Victorsueca> just wondering.... would it be possible to make a x168 system?
 8492016-10-18T16:18:03  <Victorsueca> x128*
 8502016-10-18T16:20:11  *** BashCo_ has quit IRC
 8512016-10-18T16:25:43  <Victorsueca> ohhh shit, 0 FPS, screen went unresponsive while compiling
 8522016-10-18T16:27:30  <wumpus> possible, sure. 128-bit address bus would make no sense, but for the ALU it might in some cases. E.g. faster bigint arithmetic for cryptographic purposes
 8532016-10-18T16:28:20  *** To7 has quit IRC
 8542016-10-18T16:30:40  <Victorsueca> what am I supposed to do now? kill it with the power button or wait?
 8552016-10-18T16:31:20  <wumpus> hm AS/400 apparently did have 128-bit pointers. CHERI (capability-based architecture research project) has 256-bit pointers, even.
 8562016-10-18T16:31:30  <wumpus> so yes it can always get bigger and crazier :)
 8572016-10-18T16:32:19  <Victorsueca> wumpus: if I kill it now would it resume the build later?
 8582016-10-18T16:32:58  <wumpus> Victorsueca: yes
 8592016-10-18T16:33:12  *** [Author] has quit IRC
 8602016-10-18T16:34:16  <Victorsueca> good to know
 8612016-10-18T16:35:02  <Victorsueca> does it make sense to have such huge pointers other than bigger integers?
 8622016-10-18T16:35:50  <sipa> zfs internally has a 256-bit hash associated with every "pointer" to a disk location, with a hash off the data record pointed to
 8632016-10-18T16:35:59  <sipa> arguably that is part of the pointer
 8642016-10-18T16:36:15  <GitHub59> [bitcoin] laanwj closed pull request #8960: doc: update 0.13.1 release note info on linux arm builds (0.13...relnote131) https://github.com/bitcoin/bitcoin/pull/8960
 8652016-10-18T16:36:15  <GitHub58> [bitcoin] laanwj pushed 2 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/685e4c78f8ed...2c0913d0b3e1
 8662016-10-18T16:36:15  <GitHub58> bitcoin/0.13 d179eed mruddy: doc: update 0.13.1 release note info on linux arm builds...
 8672016-10-18T16:36:16  <GitHub58> bitcoin/0.13 2c0913d Wladimir J. van der Laan: Merge #8960: doc: update 0.13.1 release note info on linux arm builds...
 8682016-10-18T16:37:00  <wumpus> sipa: so the entire disk uses content-addressable storage?
 8692016-10-18T16:37:34  <wumpus> sipa: ah yes this is what you were talking about in Milan
 8702016-10-18T16:37:42  <sipa> wumpus: no, there are still actual disk locations
 8712016-10-18T16:38:14  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 8722016-10-18T16:42:12  <GitHub105> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1e1b8ceb5ebc...80a707824489
 8732016-10-18T16:42:13  <GitHub105> bitcoin/master 83c0f7f mruddy: trivial: update 0.13.0 release note info on linux arm builds
 8742016-10-18T16:42:13  <GitHub105> bitcoin/master 80a7078 Wladimir J. van der Laan: Merge #8955: doc: update 0.13.0 release note info on linux arm builds...
 8752016-10-18T16:42:25  <GitHub14> [bitcoin] laanwj closed pull request #8955: doc: update 0.13.0 release note info on linux arm builds (master...relnote) https://github.com/bitcoin/bitcoin/pull/8955
 8762016-10-18T16:47:14  <wumpus> sipa: right. Would be hard to imagine how the entire disk could work in content-addressable way, at some point there must be a way to map hashes to the the location on the disk where something is stored.
 8772016-10-18T16:49:55  *** BashCo has joined #bitcoin-core-dev
 8782016-10-18T16:50:23  <wumpus> https://twitter.com/orionwl/status/788413453593698304
 8792016-10-18T16:59:35  <Victorsueca> ok, back to building, looks like it resumed correctly where it was
 8802016-10-18T17:21:11  *** Guyver2 has quit IRC
 8812016-10-18T17:24:33  <GitHub48> [bitcoin] anduck opened pull request #8965: Mention that PPA doesn't support Debian (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8965
 8822016-10-18T17:27:45  <gmaxwell> wumpus: perhaps we should do a release for w32 that pops up a box and asks the user to report their usage.
 8832016-10-18T17:28:10  <BlueMatt> just make a http request to X.onion.to :p
 8842016-10-18T17:33:22  *** BCBot has quit IRC
 8852016-10-18T17:33:22  *** Lauda has quit IRC
 8862016-10-18T17:33:22  *** owowo has quit IRC
 8872016-10-18T17:33:22  *** rabidus has quit IRC
 8882016-10-18T17:33:22  *** warren has quit IRC
 8892016-10-18T17:33:23  *** mappum has quit IRC
 8902016-10-18T17:33:23  *** wallet42 has quit IRC
 8912016-10-18T17:33:23  *** kinlo has quit IRC
 8922016-10-18T17:33:23  *** phantomcircuit has quit IRC
 8932016-10-18T17:33:24  *** morcos has quit IRC
 8942016-10-18T17:33:24  *** bad_duck has quit IRC
 8952016-10-18T17:33:24  *** sipa has quit IRC
 8962016-10-18T17:33:24  *** aspect_ has quit IRC
 8972016-10-18T17:33:24  *** blkdb has quit IRC
 8982016-10-18T17:33:24  *** tadasv has quit IRC
 8992016-10-18T17:33:24  *** arubi has quit IRC
 9002016-10-18T17:33:24  *** Lightsword has quit IRC
 9012016-10-18T17:33:25  *** asoltys has quit IRC
 9022016-10-18T17:33:29  *** rabidus_ has joined #bitcoin-core-dev
 9032016-10-18T17:33:31  *** kcud_dab has joined #bitcoin-core-dev
 9042016-10-18T17:33:31  *** kinlo has joined #bitcoin-core-dev
 9052016-10-18T17:33:32  *** asoltys_ has joined #bitcoin-core-dev
 9062016-10-18T17:33:34  <Victorsueca> wow netsplit
 9072016-10-18T17:33:35  *** phantomcircuit has joined #bitcoin-core-dev
 9082016-10-18T17:33:35  *** BCBot has joined #bitcoin-core-dev
 9092016-10-18T17:33:37  *** arubi has joined #bitcoin-core-dev
 9102016-10-18T17:33:39  *** morcos has joined #bitcoin-core-dev
 9112016-10-18T17:33:41  *** warren has joined #bitcoin-core-dev
 9122016-10-18T17:33:53  *** warren has quit IRC
 9132016-10-18T17:33:54  *** warren has joined #bitcoin-core-dev
 9142016-10-18T17:33:56  *** owowo has joined #bitcoin-core-dev
 9152016-10-18T17:34:06  <Victorsueca> gee, qt takes a lot to compile
 9162016-10-18T17:34:09  <TD-Linux> building bitcoin under the Ubuntu for Windows environment is supported now?
 9172016-10-18T17:34:24  <Victorsueca> TD-Linux: i'm doing it right now lol
 9182016-10-18T17:34:26  *** Lauda has joined #bitcoin-core-dev
 9192016-10-18T17:34:32  *** Lauda has quit IRC
 9202016-10-18T17:34:32  *** Lauda has joined #bitcoin-core-dev
 9212016-10-18T17:34:45  *** Lightsword has joined #bitcoin-core-dev
 9222016-10-18T17:35:27  <wumpus> gmaxwell: I'm surprised with how long Microsoft is waiting to deprecate 32-bit windows
 9232016-10-18T17:36:02  *** tadasv has joined #bitcoin-core-dev
 9242016-10-18T17:36:05  <wumpus> hadn't expected a w10 release for it
 9252016-10-18T17:36:45  *** BCBot has quit IRC
 9262016-10-18T17:36:58  *** BCBot has joined #bitcoin-core-dev
 9272016-10-18T17:37:01  *** blkdb has joined #bitcoin-core-dev
 9282016-10-18T17:37:15  <wumpus> but I have the feeling no one is using it for bitcoin core, and at least up until now responses seem to confirm that
 9292016-10-18T17:38:00  <Victorsueca> what about the number of downloads from bitcoin.org? that would be a good indicative of x32 usage
 9302016-10-18T17:38:18  <wumpus> we don't have that information
 9312016-10-18T17:38:45  *** sipa has joined #bitcoin-core-dev
 9322016-10-18T17:38:49  <wumpus> also it's very possible that people download the 32-bit version by accident even though they're on 64-bit
 9332016-10-18T17:39:13  <Victorsueca> doesn't the page detect your OS and arch?
 9342016-10-18T17:39:23  <wumpus> of the browser
 9352016-10-18T17:39:31  <Victorsueca> ahh right
 9362016-10-18T17:39:42  <Victorsueca> the browser could be x32 by accident
 9372016-10-18T17:39:52  <gmaxwell> that was an issue for fedora for a long time, they recommended 32bit as the main download because it was the most downloaded one... meanwhile the overwhelming majority of users were on 64bit hardware.
 9382016-10-18T17:40:26  <TD-Linux> Victorsueca, or on purpose. most browser plugins are 32 bit only
 9392016-10-18T17:40:30  *** aspect_ has joined #bitcoin-core-dev
 9402016-10-18T17:40:54  <Victorsueca> gmaxwell: sounds like a loop, it's obviously going to be the most downloaded one if it's the main download
 9412016-10-18T17:41:01  <sipa> Victorsueca: x32 is not the same as 32-bit x86 :)
 9422016-10-18T17:41:06  *** wallet42 has joined #bitcoin-core-dev
 9432016-10-18T17:41:24  <Victorsueca> sipa: it's ok if I call it ia32?
 9442016-10-18T17:41:39  <Victorsueca> i'm too lazy to write the word "bit" :P
 9452016-10-18T17:42:14  <wumpus> TD-Linux: that was the case in 2008 or so, but is that still the case?
 9462016-10-18T17:42:24  <sipa> as far as i'm concerned you can call it blampowoozie, just making sure you're not saying something that's interpreted different than what you intended
 9472016-10-18T17:43:12  *** mappum has joined #bitcoin-core-dev
 9482016-10-18T17:43:13  <gmaxwell> wumpus: other than build costs is 32bit windows a burden on you/us?
 9492016-10-18T17:43:17  <wumpus> is anyone still using browser plugins in the first place?
 9502016-10-18T17:43:25  <TD-Linux> wumpus, yes, though the complete death of NPAPI is soon approaching, so once that happens at least firefox is going to do in place 32->64 upgrades
 9512016-10-18T17:43:40  <Victorsueca> wumpus: I use chrome extensions at most
 9522016-10-18T17:43:44  *** Guyver2 has joined #bitcoin-core-dev
 9532016-10-18T17:43:44  <wumpus> gmaxwell: well it goes mainly untested
 9542016-10-18T17:43:54  <wumpus> gmaxwell: none of the devs uses windows, let alone 32-bit
 9552016-10-18T17:44:10  <wumpus> Victorsueca: extensions are extensively used and a completely different thing :)
 9562016-10-18T17:44:15  <sipa> it'd be nice if ubuntu shipped with a built-in windows environment too.
 9572016-10-18T17:44:51  <btcdrak> fractal OS
 9582016-10-18T17:44:59  <wumpus> gmaxwell: I just don't think it's used anymore in practice. What was the last 32-bit only CPU?
 9592016-10-18T17:45:07  <TD-Linux> wumpus, lots of antivirus installs browser plugins (one of the reasons to remove it actually), also realplayer-tier stuff like United's inflight video
 9602016-10-18T17:45:11  <wumpus> (I mean commonly used intel one, not ARM)
 9612016-10-18T17:45:18  <Victorsueca> sipa: I think that's called wine, but i don't think it comes pre-installed, you have to apt-get it
 9622016-10-18T17:46:16  <wumpus> TD-Linux: that doesn't sound like something desirable :)
 9632016-10-18T17:46:23  <wumpus> "many malware is still 32-bit" hehe
 9642016-10-18T17:47:22  <TD-Linux> wumpus, indeed, but then you tempt the antivirus vendors to binary patch your executable instead.
 9652016-10-18T17:48:53  <sipa> wumpus: even windows 10 still supports ia32
 9662016-10-18T17:49:16  <wumpus> sipa: I know, I was surprised about that a few messages back
 9672016-10-18T17:49:26  <wumpus> sipa: that doesn't mean anyone is using it though
 9682016-10-18T17:50:49  <wumpus> I don't really feel like arguing about this though, if everyone here feels that supporting windows 32 bit is still worth it, let's keep doing that, please also help with support if issues come up tho
 9692016-10-18T17:50:52  <Lightsword> wumpus, doesn’t luke-jr use 32 bit userspace or something strange?
 9702016-10-18T17:50:59  <wumpus> Lightsword: on linux, yes
 9712016-10-18T17:51:00  <TD-Linux> likely because they wanted to migrate all windows 7 and 8 installs to 10, and doing an upgrade to a different arch is high risk
 9722016-10-18T17:51:26  <sipa> wumpus: oh, i'm not arguing - i'm just as curious as you about actual usefulness of 32-bit windows
 9732016-10-18T17:51:52  <wumpus> linux 32-bit is still used on VPSes with small memory (nano instances and such) so there's a reasonable user base
 9742016-10-18T17:52:11  <Lightsword> my guess is it might not be all that uncommon for people to want a full node on some ancient systems they have lying around so 32 bit windows might be useful for that
 9752016-10-18T17:52:25  <wumpus> but we deprecated 32-bit Mac ages ago, and windows really is in the same ballpark as that, an end-user OS
 9762016-10-18T17:52:26  <Lightsword> as a dedicated box they stick in a closet or something
 9772016-10-18T17:53:03  <Lightsword> wumpus, yeah but apple deprecated 32-bit mac right?
 9782016-10-18T17:53:08  <wumpus> let hem install inux, then
 9792016-10-18T17:53:12  <wumpus> :p
 9802016-10-18T17:53:49  <wumpus> but *how old* is that anyhow? what and when was the last (commonly used) 32-bit only x86 CPU?
 9812016-10-18T17:54:10  *** kadoban has joined #bitcoin-core-dev
 9822016-10-18T17:54:12  <Lightsword> wumpus, netbook atoms?
 9832016-10-18T17:54:13  <TD-Linux> gmaxwell, instead of a box in the executable that pops up, you could put it on bitcoin.org
 9842016-10-18T17:54:48  <gmaxwell> realistically, most hardware like atoms will be too non-performance to run bitcoin core anymore. :(
 9852016-10-18T17:54:51  <wumpus> Lightsword: I don't think any of those really caught on, for running windows at least
 9862016-10-18T17:55:15  <Lightsword> wumpus, I used them at one point with windows 7 32 bit…years ago
 9872016-10-18T17:55:32  <gmaxwell> I worry more about users on fast hardware that happen to be running 32bit OSes because of ignorance or compatiblity with other things.
 9882016-10-18T17:55:46  <wumpus> ok, never mind about his
 9892016-10-18T17:55:59  <wumpus> seems everyone else feels this is still worth supporting, well go ahead :)
 9902016-10-18T17:56:34  <Victorsueca> What about people who has a x64 OS but has low memory and wants to use bitcoin ia32 to save memory?
 9912016-10-18T17:56:44  <wumpus> so are there any of those, using windows?
 9922016-10-18T17:57:01  <wumpus> if you have low memory you probaly shouldn't be using that
 9932016-10-18T17:57:13  <wumpus> same for small embedded hw
 9942016-10-18T17:57:39  <gmaxwell> Victorsueca: using bitcoin ia32 should not be considerably more memory efficient.
 9952016-10-18T17:58:31  <sipa> i think they are
 9962016-10-18T17:58:47  <sipa> mempool, cpu cache, block index... they're all considerably smaller on 32-bit systems
 9972016-10-18T17:59:09  <sipa> not a factor 2, but perhaps 20-30%
 9982016-10-18T17:59:51  <Victorsueca> also you can't use bitcoin x64 on a ia32 os tho even if your system supports x64 you may want to use ia32 OS and that would actually save a lot of memory
 9992016-10-18T18:00:50  <wumpus> so, who is volunteering to do 32-bit windows testing for bitcoin core?
10002016-10-18T18:01:59  <gmaxwell> I can do that.
10012016-10-18T18:02:01  <Victorsueca> I could do it, if I ever get to compile the x64 one and get it to work i'll try with the ia32
10022016-10-18T18:02:06  <wumpus> great
10032016-10-18T18:02:53  <wumpus> you should test on a 32-bit OS then, not a 64-bit one
10042016-10-18T18:03:21  <Victorsueca> ^ RIP ia32 lol
10052016-10-18T18:03:42  <Victorsueca> isn't it the same?
10062016-10-18T18:03:49  <wumpus> no, it's not the same
10072016-10-18T18:04:04  <Victorsueca> damn
10082016-10-18T18:04:12  <Victorsueca> gmaxwell: you're the only hope :D
10092016-10-18T18:08:11  <Victorsueca> well, now I think about it... if the main function of the ia32 will be saving memory why don't we just test it in a x64 OS and say there's no support for ia32 OS?
10102016-10-18T18:09:19  <sipa> Victorsueca: well gmaxwell points out that people may be running a 32-bit OS, not knowing their hardware supports x86_64
10112016-10-18T18:10:20  <achow101> I may be able to help test 32 bit windows, depends on what exactly needs to be done in order to test
10122016-10-18T18:10:35  <wumpus> achow101: run a node 24/7 on 32-bit windows at least
10132016-10-18T18:10:42  <wumpus> debug when things crash
10142016-10-18T18:12:41  <wumpus> maybe try running test_bitcoin and the qa tests on it once in a while. But that's fairly well handled by travis and wine, I think most important is actual usage testing and solving problems that come up
10152016-10-18T18:16:42  <achow101> ok. does it matter if it's in a vm?
10162016-10-18T18:17:55  <wumpus> no
10172016-10-18T18:18:40  *** Chris_Stewart_5 has quit IRC
10182016-10-18T18:19:09  <achow101> ok. I'll give it a go
10192016-10-18T18:19:09  *** Chris_Stewart_5 has joined #bitcoin-core-dev
10202016-10-18T18:23:09  *** andytoshi has joined #bitcoin-core-dev
10212016-10-18T18:23:47  *** andytoshi has joined #bitcoin-core-dev
10222016-10-18T18:25:12  <wumpus> thanks
10232016-10-18T18:28:43  <wumpus> still, not one reply from twitter or #bitcoin from an actual user using the 32-bit windows version though. Only one person who knows someone who uses it on windows 32 bit.
10242016-10-18T18:29:11  <Victorsueca> trying to figure out why the heck does my system become unresponsive while compiling qt
10252016-10-18T18:29:27  <Victorsueca> i'm stuck there and can't continue building bitcoin
10262016-10-18T18:29:30  <wumpus> memory full?
10272016-10-18T18:29:42  <Victorsueca> 85%
10282016-10-18T18:29:45  <wumpus> it's c++ code, if you use too much parallelism it's easy tofill up memory
10292016-10-18T18:30:04  <Victorsueca> should I try -j1?
10302016-10-18T18:30:22  <wumpus> yes, you could try
10312016-10-18T18:34:32  <Victorsueca> I just didn't specify that option, how many threads does qt use by default when compiling?
10322016-10-18T18:35:00  <sipa> q
10332016-10-18T18:35:01  <sipa> 1
10342016-10-18T18:35:34  <Victorsueca> 1? and still out of memory? wtf?
10352016-10-18T18:35:43  <sipa> how much memory do you have?
10362016-10-18T18:35:48  <Victorsueca> 4GB
10372016-10-18T18:35:59  <sipa> how much is available for the linux env?
10382016-10-18T18:36:15  <sipa> you need something like 1.5 or 2 GB to compile bitcoin core, i think
10392016-10-18T18:36:16  <wumpus> well it could very well be another problem, my observation was just that it's usually a memory/swap issue if the system becomes unresponsive during compilation
10402016-10-18T18:36:59  <wumpus> I'm sure there's some way to debug that
10412016-10-18T18:37:10  <Victorsueca> is WSL enviroment resource limited?
10422016-10-18T18:38:04  <Victorsueca> or it just can use everything windows has available?
10432016-10-18T18:38:20  <sipa> you tell us
10442016-10-18T18:38:30  <wumpus> yes this is probably not the right place to ask that
10452016-10-18T18:38:43  <Victorsueca> hmmm ok, i'll search on google
10462016-10-18T18:38:49  *** laurentmt has joined #bitcoin-core-dev
10472016-10-18T18:39:41  *** laurentmt has quit IRC
10482016-10-18T18:40:09  <achow101> Victorsueca: WSL should be using everything windows has available. It isn't a vm or emulation
10492016-10-18T18:40:29  <Victorsueca> ^ +1, google searches seems to agree
10502016-10-18T18:41:25  <Victorsueca> so basically I have 4GB - System memory usage
10512016-10-18T18:42:07  <MarcoFalke> it is mostly main and init that consume most ram
10522016-10-18T18:42:24  <Victorsueca> will try j1 and see if it makes any difference
10532016-10-18T18:43:37  <GitHub38> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/80a707824489...932d02ae392b
10542016-10-18T18:43:38  <GitHub38> bitcoin/master fab5ca8 MarcoFalke: contrib: Add README for pgp keys
10552016-10-18T18:43:38  <GitHub38> bitcoin/master 932d02a Wladimir J. van der Laan: Merge #8954: contrib: Add README for pgp keys...
10562016-10-18T18:43:50  <GitHub20> [bitcoin] laanwj closed pull request #8954: contrib: Add README for pgp keys (master...Mf1610-docKeys) https://github.com/bitcoin/bitcoin/pull/8954
10572016-10-18T18:46:26  <Victorsueca> yay, seems to be working
10582016-10-18T18:46:48  <Victorsueca> it's still responsive and memory is a 57% so far
10592016-10-18T18:46:50  <achow101> I forgot that windows takes ages to install...
10602016-10-18T18:47:38  <GitHub198> [bitcoin] laanwj closed pull request #8394: Make sure all ports are 16 bit numbers (master...uint16port) https://github.com/bitcoin/bitcoin/pull/8394
10612016-10-18T18:47:43  <Victorsueca> achow101: lol yeah
10622016-10-18T18:48:25  <Victorsueca> it has to verify itself that it's a crap enough to meet the M$ crap software standards
10632016-10-18T18:48:35  <wumpus> there's really too many PRs open
10642016-10-18T18:49:33  <Victorsueca> wumpus: close them all but the ones made by the bitcoin team, if anybody wants to suggest a feature tell them to first search on closed pull requests and reopen if necessary
10652016-10-18T18:50:01  <wumpus> that makes no sense, everyone is 'the bitcoin team'
10662016-10-18T18:50:45  <Victorsueca> wumpus: I mean that list of people where there are 14 users right now, not sure how's it called
10672016-10-18T18:50:54  <wumpus> but just can't handle the load anymore
10682016-10-18T18:51:06  <Victorsueca> this list https://github.com/orgs/bitcoin/people
10692016-10-18T18:51:35  <sipa> wumpus: i'll help go through things, once i'm in a bit more stable location :)
10702016-10-18T18:51:46  <wumpus> sipa: you're already doing your best
10712016-10-18T18:51:55  <wumpus> sipa: I'm in no means suggesting you shuld do more work
10722016-10-18T18:52:11  <sipa> wumpus: heh, i've hardly looked at the issue/pr list in weeks
10732016-10-18T18:52:15  <wumpus> let the fucking community do their job for once, this is an open source project
10742016-10-18T18:53:13  <Victorsueca> comunity can't manage pull requests, tat's the problem, would be crazy if they could
10752016-10-18T18:53:21  <wumpus> you're just as overworked as me though
10762016-10-18T18:53:35  <wumpus> well they could help with reviewing and testing
10772016-10-18T18:53:51  <Victorsueca> aaaaaaand it's unresponsive again
10782016-10-18T18:53:51  <wumpus> and not just with creating more
10792016-10-18T18:54:26  <Victorsueca> now that's a serious problem, how do I debug this?
10802016-10-18T18:54:31  *** d_t has joined #bitcoin-core-dev
10812016-10-18T18:55:00  <sipa> Victorsueca: i doubt many people here can give an answer to that
10822016-10-18T18:55:14  <michagogo> Victorsueca: got task manager/resource monitor/htop running?
10832016-10-18T18:55:27  <Victorsueca> michagogo: yep
10842016-10-18T18:55:28  <wumpus> again, this is not a windows developer troubleshooting channel
10852016-10-18T18:55:35  <michagogo> 20:36:24 <TD-Linux> building bitcoin under the Ubuntu for Windows environment is supported now? <-- I don't know about Support, but it does seem to work!
10862016-10-18T18:55:41  <wumpus> maybe ##windows?
10872016-10-18T18:55:58  <michagogo> I mean, it's pretty much a full Ubuntu environment, so it's not so surprising
10882016-10-18T18:56:18  <Victorsueca> michagogo: it goes over 85% and a few seconds later it's unresponsive
10892016-10-18T18:56:45  <wumpus> I still bet it's swap trashing though
10902016-10-18T18:57:27  <michagogo> It's an Ubuntu user space and packages, and while more exotic syscalls aren't supported (so no LXC/KVM, no tail -f, etc.), a cross-compile toolchain runs just fine.
10912016-10-18T18:58:11  <Victorsueca> wumpus: how is that suposed to be fixed?
10922016-10-18T18:58:36  <michagogo> Victorsueca: most likely with more resources, unfortunately
10932016-10-18T18:58:52  <Victorsueca> damn
10942016-10-18T18:59:10  <wumpus> I wondered what makes tail -f so exotic, thought it was just a pollign loop, but apparently it uses inotify
10952016-10-18T19:00:02  <Victorsueca> i'll have to use my other computer then, didn't want to restart that one because it's hosting stuff
10962016-10-18T19:00:30  <sipa> wumpus: maybe tail --follow=name works better?
10972016-10-18T19:01:56  <wumpus> sipa: looks like that adds an inotify on both the file *and* the directory it's in :)
10982016-10-18T19:05:02  *** Victor_sueca has joined #bitcoin-core-dev
10992016-10-18T19:05:35  <GitHub11> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/932d02ae392b...e10af96cf450
11002016-10-18T19:05:36  <GitHub11> bitcoin/master fa28bfa MarcoFalke: [wallet] Set fLimitFree = true
11012016-10-18T19:05:36  <GitHub11> bitcoin/master fa8b02d MarcoFalke: [rpc] rawtx: Prepare fLimitFree to make it an option
11022016-10-18T19:05:37  <GitHub11> bitcoin/master e10af96 Wladimir J. van der Laan: Merge #8287: [wallet] Set fLimitFree = true...
11032016-10-18T19:05:41  <GitHub40> [bitcoin] laanwj closed pull request #8287: [wallet] Set fLimitFree = true (master...Mf1607-walletLimitFree) https://github.com/bitcoin/bitcoin/pull/8287
11042016-10-18T19:07:50  *** Chris_Stewart_5 has quit IRC
11052016-10-18T19:08:00  <GitHub60> [bitcoin] MarcoFalke closed pull request #8623: chainparams: Added parametric halving interval for regtest-only mode (master...parametric_halving_interval) https://github.com/bitcoin/bitcoin/pull/8623
11062016-10-18T19:08:29  *** Guyver2 has quit IRC
11072016-10-18T19:15:05  <GitHub24> [bitcoin] laanwj closed pull request #7759: [WIP] rest: Stream entire utxo set (master...2016_03_utxo_streaming) https://github.com/bitcoin/bitcoin/pull/7759
11082016-10-18T19:16:30  <GitHub120> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e10af96cf450...744d2652dda0
11092016-10-18T19:16:30  <achow101> connect in the bitcoin.conf means that it should only connect to the specified ip(s), right?
11102016-10-18T19:16:30  <GitHub120> bitcoin/master 9fce062 Daniel Kraft: [c++11] Use std::unique_ptr for block creation....
11112016-10-18T19:16:31  <GitHub120> bitcoin/master 744d265 Wladimir J. van der Laan: Merge #8223: [c++11] Use std::unique_ptr for block creation....
11122016-10-18T19:16:40  <GitHub0> [bitcoin] laanwj closed pull request #8223: [c++11] Use std::unique_ptr for block creation. (master...miner-uniqueptr) https://github.com/bitcoin/bitcoin/pull/8223
11132016-10-18T19:16:41  <jonasschnelli> achow101: yes.
11142016-10-18T19:17:05  <achow101> well that isn't happening. this is with 32-bit 0.13.0 on win10
11152016-10-18T19:17:06  <jonasschnelli> And IIRC, you can't even ban that node.
11162016-10-18T19:17:25  *** Lauda has quit IRC
11172016-10-18T19:17:31  <jonasschnelli> achow101: maybe post your debug.log?
11182016-10-18T19:17:34  <BlueMatt> #8637 looks merge-able
11192016-10-18T19:17:39  *** Guyver2 has joined #bitcoin-core-dev
11202016-10-18T19:17:43  *** Victorsueca has quit IRC
11212016-10-18T19:18:06  <MarcoFalke> BlueMatt: 8908 should not cause any issues with the ppa?
11222016-10-18T19:18:15  <MarcoFalke> Otherwise, I think it is merge ready as well
11232016-10-18T19:18:29  <BlueMatt> no, that wont hurt anything
11242016-10-18T19:18:46  <wumpus> is that the hack to get the PPA to install on debian instead of ubuntu? it made me scared
11252016-10-18T19:19:01  <BlueMatt> no, its the one that changes the .desktop file
11262016-10-18T19:19:07  <wumpus> @Anduck ^^ :p
11272016-10-18T19:19:33  *** Evel-Knievel has quit IRC
11282016-10-18T19:19:50  *** Evel-Knievel has joined #bitcoin-core-dev
11292016-10-18T19:20:19  <wumpus> ah no that's https://github.com/bitcoin/bitcoin/pull/8965
11302016-10-18T19:20:21  <GitHub94> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/744d2652dda0...0b5a997acfb6
11312016-10-18T19:20:21  <GitHub94> bitcoin/master 02a337d Matt Corallo: Dont remove a "preferred" cmpctblock peer if they provide a block
11322016-10-18T19:20:22  <GitHub94> bitcoin/master fe998e9 Matt Corallo: More agressively filter compact block requests...
11332016-10-18T19:20:22  <GitHub94> bitcoin/master b2e93a3 instagibbs: Add cmpctblock to debug help list
11342016-10-18T19:20:26  <GitHub32> [bitcoin] laanwj closed pull request #8637: Compact Block Tweaks (rebase of #8235) (master...compactblocktweaks) https://github.com/bitcoin/bitcoin/pull/8637
11352016-10-18T19:20:41  <GitHub196> [bitcoin] jonasschnelli pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0b5a997acfb6...df7519cbc1a9
11362016-10-18T19:20:41  <GitHub196> bitcoin/master 164196b matthias: Simple Update to File 'bitcoin-qt.desktop'
11372016-10-18T19:20:41  <GitHub196> bitcoin/master df7519c Jonas Schnelli: Merge #8908: Update bitcoin-qt.desktop...
11382016-10-18T19:20:53  <wumpus> thanks jonasschnelli
11392016-10-18T19:20:56  <GitHub61> [bitcoin] jonasschnelli closed pull request #8908: Update bitcoin-qt.desktop (master...patch-4) https://github.com/bitcoin/bitcoin/pull/8908
11402016-10-18T19:21:00  <achow101> jonasschnelli: http://pastebin.com/TQ1Kr2P9
11412016-10-18T19:21:09  <achow101> I cut out all of the updatetip stuff
11422016-10-18T19:22:02  <jonasschnelli> achow101: did you use -connect=129.2.207.18:x?
11432016-10-18T19:23:06  <achow101> I used connect=172.16.220.1
11442016-10-18T19:23:28  <achow101> It's supposed to be vm to host
11452016-10-18T19:23:31  <michagogo> 22:18:48 <wumpus> is that the hack to get the PPA to install on debian instead of ubuntu? it made me scared
11462016-10-18T19:23:38  <michagogo> Wait, wait, what??
11472016-10-18T19:23:41  *** Chris_Stewart_5 has joined #bitcoin-core-dev
11482016-10-18T19:23:57  <MarcoFalke> michagogo:  https://github.com/bitcoin/bitcoin/pull/8965
11492016-10-18T19:24:03  <michagogo> Nobody should ever mix Ubuntu and Debian
11502016-10-18T19:24:10  <michagogo> That's a recipe for a broken system
11512016-10-18T19:24:32  *** Cory has quit IRC
11522016-10-18T19:24:38  <jonasschnelli> achow101: is the shutdown at the end intentional?
11532016-10-18T19:25:25  <achow101> yes. I shut it down so it wouldn't eat all my data
11542016-10-18T19:25:43  <GitHub23> [bitcoin] TheBlueMatt opened pull request #8968: Don't hold cs_main when calling ProcessNewBlock from a cmpctblock (master...cmpctblock) https://github.com/bitcoin/bitcoin/pull/8968
11552016-10-18T19:25:46  <wumpus> michagogo: comment that in the pull please
11562016-10-18T19:25:50  <jonasschnelli> achow101: It looks like that you have successfully connected to a bunch of nodes in 129.2.207.18
11572016-10-18T19:25:53  <michagogo> https://wiki.debian.org/DontBreakDebian
11582016-10-18T19:26:25  <BlueMatt> wumpus: yea, I just nacked that one
11592016-10-18T19:27:24  *** Lauda has joined #bitcoin-core-dev
11602016-10-18T19:27:27  <achow101> jonasschnelli: that's probably because it's behind the vm nat. That ip address is mine
11612016-10-18T19:27:36  <achow101> but I only run one node
11622016-10-18T19:28:17  <jonasschnelli> achow101: A right. Confused! 129.2.207.18 is you node..
11632016-10-18T19:28:26  <jonasschnelli> maybe try -debug=net and post the debug.log again
11642016-10-18T19:28:43  <achow101> I found the problem. If the option is in the bitcoin.conf, it won't work. I have to put it in the command line. Any idea why?
11652016-10-18T19:29:10  <wumpus> are you using connect= in your bitcoin.conf or -connect=?
11662016-10-18T19:29:21  <wumpus> the former will work, the second will not
11672016-10-18T19:29:22  <achow101> connect= in bitcoin.conf
11682016-10-18T19:29:23  <jonasschnelli> Should work in bitcoin.conf
11692016-10-18T19:29:44  <wumpus> is bitcoin.conf in the right place? does it get parsed at all?
11702016-10-18T19:29:48  <jonasschnelli> Doublecheck bitcoin.conf and -datadir (if passed in CLI)
11712016-10-18T19:29:49  <achow101> This is my conf: prune=550
11722016-10-18T19:29:49  <achow101> connect=172.16.220.1:8333
11732016-10-18T19:29:54  *** Victor_sueca has quit IRC
11742016-10-18T19:30:21  <jonasschnelli> what happens if you telnet 172.16.220.1 8333 (nat?)
11752016-10-18T19:30:57  <achow101> nevermind. it's a windows problem. It stuck a .txt at the end of the file name!
11762016-10-18T19:31:39  <michagogo> Hahaha
11772016-10-18T19:31:40  <wumpus> one lousy way to find out if it's parsed is to put junk at the end, e.g. 'fasdjlfaljdfalfjk' then see if bitcoind gives an error at start :p
11782016-10-18T19:31:45  <jonasschnelli> heh
11792016-10-18T19:31:47  <wumpus> lol okay
11802016-10-18T19:32:00  <michagogo> Yeah, first thing I do at any new Windows box/profile
11812016-10-18T19:32:25  <michagogo> Folder options -> untick "hide extensions for known file types"
11822016-10-18T19:32:29  <wumpus> windows's mysterius hidden extensions and hidden files
11832016-10-18T19:34:26  <GitHub167> [bitcoin] jonasschnelli closed pull request #5905: [Qt][WIP] allow possibility to add a comment to a WalletTx (master...2015/03/qt_tx_comment) https://github.com/bitcoin/bitcoin/pull/5905
11842016-10-18T19:35:22  <GitHub148> [bitcoin] jonasschnelli closed pull request #7107: Qt: Add network port input box to GUI settings (master...qtnetworkport) https://github.com/bitcoin/bitcoin/pull/7107
11852016-10-18T19:36:03  <GitHub125> [bitcoin] jonasschnelli closed pull request #7510: Read/write bitcoin_rw.conf for exposing shared Daemon/GUI options in the GUI (master...rwconf) https://github.com/bitcoin/bitcoin/pull/7510
11862016-10-18T19:36:38  *** d_t has quit IRC
11872016-10-18T19:37:08  <GitHub4> [bitcoin] laanwj closed pull request #6996: Add preciousblock RPC (master...preciousblock) https://github.com/bitcoin/bitcoin/pull/6996
11882016-10-18T19:37:10  <GitHub199> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/df7519cbc1a9...7f71a3c59194
11892016-10-18T19:37:11  <GitHub199> bitcoin/master 5127c4f Pieter Wuille: Add preciousblock RPC...
11902016-10-18T19:37:11  <GitHub199> bitcoin/master 5805ac8 Pieter Wuille: Add preciousblock tests...
11912016-10-18T19:37:12  <GitHub199> bitcoin/master 7f71a3c Wladimir J. van der Laan: Merge #6996: Add preciousblock RPC...
11922016-10-18T19:37:33  <michagogo> Hm, I really hope I find the time to rewrite build-windows.md
11932016-10-18T19:37:47  <michagogo> It seems to tell you to install all the unix dependencies
11942016-10-18T19:37:52  <michagogo> Which is just wrong
11952016-10-18T19:38:04  <michagogo> Or at least, it can be read that way
11962016-10-18T19:38:10  <wumpus> it doesn't hurt, but yeah it's overkill
11972016-10-18T19:38:29  <wumpus> only the high-level arch-independent build stuff would be necessary, autoconf automake etc
11982016-10-18T19:39:16  <michagogo> I mean, molz in #bitcoin was installing all the actual deps, it seems
11992016-10-18T19:39:34  <GitHub123> [bitcoin] MarcoFalke closed pull request #8961: Headers announcement for nodes that can do headers. (master...AnnounceUsingHeaders) https://github.com/bitcoin/bitcoin/pull/8961
12002016-10-18T19:39:48  <michagogo> OpenSSL, BDB, etc etc
12012016-10-18T19:39:56  <michagogo> Which is completely unnecessary
12022016-10-18T19:40:52  <michagogo> When you really just need the actual tool chain skeleton
12032016-10-18T19:41:39  <wumpus> you don't need those for a depends build on unix either
12042016-10-18T19:42:08  <jonasschnelli> wumpus: the preciousblock RPC call needs probably mentioning in the 0.14 releasenots
12052016-10-18T19:42:09  <jonasschnelli> *notes
12062016-10-18T19:42:14  <wumpus> jonasschnelli: yes
12072016-10-18T19:42:23  <MarcoFalke> Yeah, down to 10 pulls
12082016-10-18T19:42:26  <MarcoFalke> in base 128
12092016-10-18T19:42:27  <jonasschnelli> maybe we should open a issue for RN 0.14
12102016-10-18T19:42:40  <wumpus> there's an issue for that IIRC
12112016-10-18T19:42:46  <michagogo> wumpus: right
12122016-10-18T19:42:53  <wumpus> https://github.com/bitcoin/bitcoin/issues/8455
12132016-10-18T19:43:00  <michagogo> But the docs don't talk about running a deps build for unix
12142016-10-18T19:43:36  <wumpus> michagogo: only the docs in depends do :(
12152016-10-18T19:43:39  <michagogo> Build-unix.md walks you through doing a build with system-deps
12162016-10-18T19:43:49  <wumpus> michagogo: it's split all over the place, not always over sensible lines
12172016-10-18T19:43:53  <michagogo> And build-windows points you at build-unix...
12182016-10-18T19:44:07  <wumpus> and build-unix points you at build-openbsd :-)
12192016-10-18T19:44:10  <michagogo> When you really just need to install git make pkg-config libtool autoconf g++ g++-mingw-w64-x86-64
12202016-10-18T19:44:24  <michagogo> Well, it does for openbsd
12212016-10-18T19:44:38  <michagogo> Windows points to unix unconditionally
12222016-10-18T19:44:41  <wumpus> I know, that one makes sense
12232016-10-18T19:45:03  <michagogo> When all you need is git make pkg-config libtool autoconf g++ g++-mingw-w64-x86-64
12242016-10-18T19:45:16  <michagogo> You don't even need all of build-essential
12252016-10-18T19:46:11  <wumpus> that's a lot of micromanagement though. I tdoesn't hurt to install one package too many. Though it should be made clear that you don't need to install dependencies if you're going to do a depends build, just the compiler/toolchain
12262016-10-18T19:46:34  <wumpus> some of that is documented in depends/, but that's somewhat hidden away
12272016-10-18T19:47:15  <michagogo> OTOH, it's just a waste of space to install g++-mingw-w64 when g++-mingw-w64-x86-64 is enough
12282016-10-18T19:47:54  <michagogo> (The former basically pulls in the latter, plus -i686)
12292016-10-18T19:48:58  <michagogo> And I think some of the packages don't even come with build-essential, you need to install them individually anyway
12302016-10-18T19:49:16  <wumpus> I agree, but I think getting the high level understanding clear "depends installs the dependencies for you so you don't need to get them from apt" is more important than whether we mention one package more or less
12312016-10-18T19:50:03  <michagogo> In other words, IMHO, there are few enough necessary packages that it's worth just listing them rather than the metapackages that pull in supersets of some of them
12322016-10-18T19:50:12  <michagogo> Well, yeah
12332016-10-18T19:50:59  <michagogo> I'm hoping to overhaul build-windows on Thursday, if nobody else does it in the meantime
12342016-10-18T19:51:39  <michagogo> Also, maybe build-unix should be updated to present depends as an alternative to system deps
12352016-10-18T19:51:45  <wumpus> I don't think you need to be afraid anyone else will do so in the meantime, I mean no one did in the last months either :)
12362016-10-18T20:01:27  *** Victorsueca has joined #bitcoin-core-dev
12372016-10-18T20:04:18  <GitHub196> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7f71a3c59194...74dc388ab599
12382016-10-18T20:04:19  <GitHub196> bitcoin/master 18dacf9 Russell Yanofsky: Add microbenchmarks to profile more code paths....
12392016-10-18T20:04:19  <GitHub196> bitcoin/master 74dc388 Wladimir J. van der Laan: Merge #8873: Add microbenchmarks to profile more code paths....
12402016-10-18T20:04:29  <GitHub52> [bitcoin] laanwj closed pull request #8873: Add microbenchmarks to profile more code paths. (master...issue-7883-benchmarks) https://github.com/bitcoin/bitcoin/pull/8873
12412016-10-18T20:07:48  <wumpus> jonasschnelli: could you elaborate in #8546 what you mean with " I think its acceptable if it breaks wallets used back in 0.3.x in conjunction with IP transaction". I don't think it'd be acceptable if the client suddenly crashes if someone happens to be using a wallet that still has a pay-to-IP transaction in it.
12422016-10-18T20:08:17  *** cryptapus has quit IRC
12432016-10-18T20:08:17  <wumpus> I'd prefer keeping around a bit of useless code to that
12442016-10-18T20:08:41  <wumpus> OTOH, it's not tested anyway, so if it is safe to remove (no risk of crashes) I'm fine with it
12452016-10-18T20:09:17  <wumpus> to be honest I think #8564 is a bit questionable, I'm not convinced it only removed code to do with ip transactions
12462016-10-18T20:09:30  <wumpus> #8546, sorry
12472016-10-18T20:10:32  <BlueMatt> ;;seen cfields_
12482016-10-18T20:10:32  <gribble> cfields_ was last seen in #bitcoin-core-dev 4 hours, 55 minutes, and 44 seconds ago: <cfields_> yes, that one's on purpose
12492016-10-18T20:10:35  <BlueMatt> ;;seen cfields
12502016-10-18T20:10:36  <gribble> cfields was last seen in #bitcoin-core-dev 5 days, 0 hours, 12 minutes, and 27 seconds ago: <cfields> gmaxwell: for one in every X connections, we could proxy and route messages together for peer-pairs. Then they'd poison their own stats :p
12512016-10-18T20:10:39  <wumpus> we may want to closeit and re-do it at some point, there's no urgency to it
12522016-10-18T20:10:45  <Anduck> i think the docs for ubuntu & debian should be separated totally to hilight that they're indeed different distros and have different sw sources etc. i might do this some day when i have more time
12532016-10-18T20:10:47  <cfields_> BlueMatt: pong?
12542016-10-18T20:11:09  <BlueMatt> cfields_: busy with 13.1? or have you had a chance to review 8865?
12552016-10-18T20:11:25  <wumpus> Anduck: all of the apt package names are the same though
12562016-10-18T20:11:40  <cfields_> BlueMatt: beating my head against the wall with cgminer. I can take a break to review though.
12572016-10-18T20:11:55  <wumpus> unless people mess with software sources, ubuntu and debian can be regarded as having the same build instructions
12582016-10-18T20:12:16  <Anduck> what's the "right" way to obtain libdb4.8 (& libdb4.8++) for debian 8.0 jessie, binary or sources?
12592016-10-18T20:12:17  <wumpus> no need to duplicate things unnecesarily
12602016-10-18T20:12:21  <GitHub128> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/74dc388ab599...23e03f8d26d7
12612016-10-18T20:12:21  <GitHub128> bitcoin/master b55d823 anduck: Explicitly state that PPA is for Ubuntu only
12622016-10-18T20:12:22  <GitHub128> bitcoin/master 23e03f8 MarcoFalke: Merge #8965: Mention that PPA doesn't support Debian...
12632016-10-18T20:12:30  <wumpus> Anduck: build it from source as in the "berkeleydb" section
12642016-10-18T20:12:35  <GitHub54> [bitcoin] MarcoFalke closed pull request #8965: Mention that PPA doesn't support Debian (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8965
12652016-10-18T20:12:57  <BlueMatt> cfields_: yea, still ready to split main and have some exciting things planned, but rather blocked on review (story of bitcoin core, i suppose...)
12662016-10-18T20:13:01  <Anduck> wumpus: it only builds libdb4.8 but libdb4.8++ is also required
12672016-10-18T20:13:09  <BlueMatt> cfields_: I'm happy to trade reviews, if it helps :p
12682016-10-18T20:13:10  <wumpus> Anduck: it builds both actually
12692016-10-18T20:13:23  <wumpus> Anduck: I've followed the instructions zillions of times, I'm sure it does the right thing
12702016-10-18T20:13:24  <Anduck> hmm... i tried it but it complained about libdb4.8++
12712016-10-18T20:13:32  <Anduck> alright
12722016-10-18T20:13:33  <cfields_> BlueMatt: ack. Will do in a little bit, once I get this test on auto-pilot
12732016-10-18T20:13:36  <wumpus> unless something broke anyhow
12742016-10-18T20:13:43  <wumpus> these days I don't use bdb 4.8 anymore tbh
12752016-10-18T20:14:09  <Anduck> are there any recent/known compatibility issues with newer ones?
12762016-10-18T20:14:20  <wumpus> yes, still the same as always
12772016-10-18T20:14:28  <Anduck> ok
12782016-10-18T20:14:38  <wumpus> bdb 5 wallets won't work in 4.8, bdb 6 wallets won't work in 5 and 4.8
12792016-10-18T20:14:57  <Anduck> but it will work perfectly well otherwise?
12802016-10-18T20:16:11  <Anduck> --with-incompatible-bdb raises the question if it's not safe to use it at all, or if it's just simply incompatible with other major bdb versions
12812016-10-18T20:16:13  <wumpus> and to convert between versions one can do  db5.0_dump wallet.dat | db4.8_load wallet.dat.new  , still the same as in 2012 :)
12822016-10-18T20:17:30  <wumpus> I can't guarantee anything about being safe to use, but I've never heard of any inherent issues
12832016-10-18T20:18:20  <wumpus> it's just that different versions' databases are binary incompatible, and if you don't know about that it can be confusing
12842016-10-18T20:18:41  <Anduck> alright. good to know
12852016-10-18T20:19:45  <wumpus> I guess it'd make sense to document that better
12862016-10-18T20:20:04  <Victorsueca> there, back to compiling.... again.....
12872016-10-18T20:20:12  <wumpus> but so much stuff to do
12882016-10-18T20:20:17  <Victorsueca> this time on a better computer, 16 GB ram
12892016-10-18T20:22:52  <Victorsueca> maybe it's an overkill but way we'll know if ram was the problem
12902016-10-18T20:24:09  <wumpus> 16GB is hardly overkill these days
12912016-10-18T20:24:38  <Victorsueca> if it's supposed to be enough with 1.5 or 2....
12922016-10-18T20:25:42  <wumpus> that's for the compiler. The other 14GB is for windows.
12932016-10-18T20:25:51  <Victorsueca> lol
12942016-10-18T20:26:45  <Victorsueca> windows eats at most 4 GB, 2GB usually
12952016-10-18T20:26:59  <Victorsueca> which is still ridiculous....
12962016-10-18T20:28:23  <GitHub128> [bitcoin] laanwj closed pull request #8546: Remove IP transaction check (master...abc123) https://github.com/bitcoin/bitcoin/pull/8546
12972016-10-18T20:35:42  <wumpus> BlueMatt: so I guess you're blocked on 8865?
12982016-10-18T20:37:05  <BlueMatt> wumpus: I mean I can open a flurry of prs that all do small changes like that, but I'd rather go one or two at a time
12992016-10-18T20:37:07  <BlueMatt> so i guess
13002016-10-18T20:37:08  <BlueMatt> yes
13012016-10-18T20:38:18  <BlueMatt> wumpus: I also opened #8930 to get some eyes on verifying that orphan processing doesnt have to remain consistent with cs_main
13022016-10-18T20:38:49  <wumpus> let's get 8865 merged then
13032016-10-18T20:40:23  <wumpus> we kind of failed our goal in Milan to split up main.cpp
13042016-10-18T20:40:57  <BlueMatt> this is true, but segwit is more important
13052016-10-18T20:42:53  <michagogo> Anduck: honestly, the easiest thing, I think, is to just use the depends system
13062016-10-18T20:44:14  <wumpus> michagogo: it is - would be nice if there waa a way to use depends *just* for berkeleydb
13072016-10-18T20:44:37  <michagogo> Yeah
13082016-10-18T20:45:03  <Victorsueca> i think there is some way to use the system library for some dependency instead f the one specified in depends
13092016-10-18T20:45:12  <wumpus> currently you have to either build all dependencies (including qt, which you really don't want to build statically on ubuntu) using depends or none at all
13102016-10-18T20:45:14  <michagogo> I mean, can you just run bdb.mk? Or does that only work when called by the main makedile?
13112016-10-18T20:45:48  <wumpus> maybe it's possible
13122016-10-18T20:46:05  <michagogo> wumpus: can you not make depends NO_QT=1 and point configure at system qt?
13132016-10-18T20:46:23  <wumpus> yea, but that'd stlil pull in boost
13142016-10-18T20:47:00  <wumpus> it's currently not a practical way to build just berkeleydb
13152016-10-18T20:49:16  <GitHub161> [bitcoin] laanwj pushed 9 new commits to master: https://github.com/bitcoin/bitcoin/compare/23e03f8d26d7...05998da5a7e2
13162016-10-18T20:49:17  <GitHub161> bitcoin/master 87e7d72 Matt Corallo: Make validationinterface.UpdatedBlockTip more verbose...
13172016-10-18T20:49:18  <GitHub161> bitcoin/master 0278fb5 Matt Corallo: Remove duplicate nBlocksEstimate cmp (we already checked IsIBD())
13182016-10-18T20:49:18  <GitHub161> bitcoin/master aefcb7b Matt Corallo: Move net-processing logic definitions together in main.h
13192016-10-18T20:49:27  <BlueMatt> wut
13202016-10-18T20:49:30  <GitHub119> [bitcoin] laanwj closed pull request #8865: Decouple peer-processing-logic from block-connection-logic (master...net_processing_1) https://github.com/bitcoin/bitcoin/pull/8865
13212016-10-18T20:49:40  <BlueMatt> did you mean to do that?
13222016-10-18T20:49:44  <wumpus> yes
13232016-10-18T20:50:00  <BlueMatt> ok!
13242016-10-18T20:52:43  <wumpus> does make sense to do a bit of continuous integration tehre instead of leaving the pull open for months
13252016-10-18T20:52:53  <BlueMatt> true
13262016-10-18T20:53:10  <BlueMatt> alright, well I'll open up the next one in a sec when my fibre tests pass
13272016-10-18T20:53:17  <wumpus> awesome
13282016-10-18T21:00:16  <GitHub147> [bitcoin] TheBlueMatt opened pull request #8969: Decouple peer-processing-logic from block-connection-logic (#2) (master...net_processing_2) https://github.com/bitcoin/bitcoin/pull/8969
13292016-10-18T21:08:33  *** cdecker has quit IRC
13302016-10-18T21:13:51  *** Guyver2 has quit IRC
13312016-10-18T21:14:30  *** To7 has joined #bitcoin-core-dev
13322016-10-18T21:15:36  *** ibrightly has quit IRC
13332016-10-18T21:15:58  *** ibrightly has joined #bitcoin-core-dev
13342016-10-18T21:29:36  *** Cory has joined #bitcoin-core-dev
13352016-10-18T21:33:02  *** mkarrer_ has joined #bitcoin-core-dev
13362016-10-18T21:35:20  <cfields_> BlueMatt: heh, I was reviewing it and it was merged under my feet :)
13372016-10-18T21:35:42  <BlueMatt> cfields_: its one of those things that can move forward but still needs posthumous acks
13382016-10-18T21:35:43  <BlueMatt> :p
13392016-10-18T21:35:52  <cfields_> BlueMatt: fwiw, looks good to me though
13402016-10-18T21:35:55  <cfields_> heh
13412016-10-18T21:36:57  <BlueMatt> posthumous acks are important :)
13422016-10-18T21:37:04  *** mkarrer has quit IRC
13432016-10-18T21:38:10  <BlueMatt> cfields_: at least the next ones are easy :)
13442016-10-18T21:38:29  <BlueMatt> probably only ~2 more incl 8969
13452016-10-18T21:39:26  <cfields_> BlueMatt: 8a4a33dc5623c8a5d1413c214f0dfa30667e6b03 is the one you showed in Milan, right?
13462016-10-18T21:39:49  <BlueMatt> yea, should be
13472016-10-18T21:39:52  *** d_t has joined #bitcoin-core-dev
13482016-10-18T21:39:57  <BlueMatt> dont recall if ive rebased or not, but its def the same commit
13492016-10-18T21:40:11  <cfields_> ok good, thanks
13502016-10-18T21:40:20  *** d_t has quit IRC
13512016-10-18T21:41:35  *** d_t has joined #bitcoin-core-dev
13522016-10-18T21:51:26  <luke-jr> Lightsword: wumpus: I no longer use 32-bit anything. I gave up waiting for x32 and just went back to x86_64 a month or so ago.
13532016-10-18T21:55:27  *** MarcoFalke has left #bitcoin-core-dev
13542016-10-18T21:56:38  *** d_t has quit IRC
13552016-10-18T22:23:13  *** justanotheruser has joined #bitcoin-core-dev
13562016-10-18T22:52:37  *** achow101 has quit IRC
13572016-10-18T22:54:46  *** wasi_ has joined #bitcoin-core-dev
13582016-10-18T22:55:18  *** wasi_ has quit IRC
13592016-10-18T23:16:07  <sipa> luke-jr: what is missing for x32?
13602016-10-18T23:16:08  <sipa> or was
13612016-10-18T23:16:35  <luke-jr> sipa: mostly LLVM and Valgrind IIRC
13622016-10-18T23:16:42  <sipa> i guess many things are harder if you don't use a common architecture
13632016-10-18T23:28:52  *** murch has quit IRC
13642016-10-18T23:35:49  *** Victorsueca has quit IRC
13652016-10-18T23:37:18  *** justanotheruser has quit IRC
13662016-10-18T23:43:03  *** wasi_ has joined #bitcoin-core-dev
13672016-10-18T23:43:48  *** wasi_ has left #bitcoin-core-dev
13682016-10-18T23:45:41  *** Victorsueca has joined #bitcoin-core-dev
13692016-10-18T23:53:04  *** alpalp has joined #bitcoin-core-dev
13702016-10-18T23:53:05  *** alpalp has joined #bitcoin-core-dev