--- Day changed Tue Oct 18 2016
00:00 < luke-jr> (sync before starting it too)
00:06 < 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
00:07 < btcdrak> why does actual sync matter? Why are we concerned about the background processes of the host computer?
00:12 < 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.
00:12 < paveljanik> slowly killing the disks...
00:15 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
00:17 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
00:19 < luke-jr> btcdrak: background process I/O is dreadfully annoying
00:19 < gmaxwell> 150 MB, not 300. 
00:20 < gmaxwell> But creating a 3 second IO stall (luke's example) would be unfortunate. :)
00:20 < luke-jr> gmaxwell: 7 seconds, it turns out
00:20 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 252 seconds]     
00:21 < 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.
00:21 < luke-jr> are we locking the mempool while it writes too? :x
00:21 < TD-Linux> luke-jr, the patch does an in-memory copy first to make the lock time minimal
00:21 < luke-jr> ah, ok
00:21 < luke-jr> though that alone might annoy some users
00:22 < paveljanik> in memory copy?
00:22 < 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
00:22 < paveljanik> So if I have 1G mempool, bitcoind will allocate one more G?
00:22 < paveljanik> hmm     
00:23 < luke-jr> ^ please tag for backport
00:26 < gmaxwell> paveljanik: No. the transactions themselves are shared pointers.
00:29 -!- murch [~murch@p4FE388E7.dip0.t-ipconnect.de] has joined #bitcoin-core-dev     
00:43 -!- _mn3monic [~guido@176.9.68.68] has quit [Ping timeout: 260 seconds]     
00:45 < btcdrak> gmaxwell: is 8949 aimed for 0.13.1 backport? (seems like it should be).
00:46 < gmaxwell> Yes, assuming people find it acceptable for master.
00:46 < gmaxwell> I think it's needed.
00:46 < gmaxwell> at least my expirence and tulip's is that absent it, 0.13.1rc1 is prone to not getting any witness peers.
00:47 < 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)
00:47 -!- harrymm [~wayne@104.222.140.64] has quit [Ping timeout: 265 seconds]     
00:50 -!- cdecker [~quassel@2a02:aa16:1105:4a80:6545:7bd0:62a0:613f] has joined #bitcoin-core-dev     
00:55 < btcdrak> gmaxwell: I can confirm the same problem
00:58 < gmaxwell> In any case, my PR is reported to resolve the issue.
01:06 -!- harrymm [~wayne@104.222.140.113] has joined #bitcoin-core-dev     
01:16 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]     
01:27 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has joined #bitcoin-core-dev     
01:37 < GitHub18> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/763828df499f...47ace4240a4e
01:37 < GitHub18> bitcoin/master 21f5a63 Luke Dashjr: Qt: Add "Copy URI" to payment request context menu
01:37 < GitHub18> bitcoin/master 47ace42 Wladimir J. van der Laan: Merge #8918: Qt: Add "Copy URI" to payment request context menu...
01:38 < 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
01:44 < GitHub134> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/47ace4240a4e...cd761fb85a24
01:44 < GitHub134> bitcoin/master 1ab21cf Matt Corallo: Remove bogus assert on number of oubound connections....
01:44 < GitHub134> bitcoin/master cd761fb Wladimir J. van der Laan: Merge #8944: Remove bogus assert on number of oubound connections....
01:44 < 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
01:46 -!- rabidus [~lauri.j@uhiainen.com] has joined #bitcoin-core-dev     
01:47 < GitHub155> [bitcoin] laanwj pushed 2 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/c418c0550db3...907c314057b0
01:47 < GitHub155> bitcoin/0.13 c9ffe90 Micha: Add historical release notes for v0.13.0...
01:47 < 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
01:47 < GitHub155> bitcoin/0.13 907c314 Wladimir J. van der Laan: Merge #8947: Add historical release notes for v0.13.0...
01:47 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
01:49 < wumpus> 7 witness connections now on my upgraded node
01:53 < gmaxwell> 1 witness connection, inbound. on one of my nodes.
01:54 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 260 seconds]     
01:55 < wumpus> here 5 inbound + 2 outbound
01:55 < gmaxwell> 6 on another node, one is outbound but it's an addnode to sipa. The rest are inbound.
02:00 < gmaxwell> sipa's seeder database only has 7, and one is v6 and the other is onion. 
02:01 < gmaxwell> though I know there are more of them, I guess it hasn't found them yet.
02:01 < gmaxwell> heh. one of them claims be be 0.12.99 0_o and it fails sipa's 'good' test.
02:02 < gmaxwell> presumably because it's 32177 blocks behind.
02:09 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has left #bitcoin-core-dev []     
02:40 -!- _mn3monic [~guido@176.9.68.68] has joined #bitcoin-core-dev     
02:45 < GitHub126> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/cd761fb85a24...614d522c3e44
02:45 < GitHub126> bitcoin/master b0aea80 BtcDrak: Sync bitcoin-tx with tx version policy
02:45 < GitHub126> bitcoin/master 614d522 Wladimir J. van der Laan: Merge #8932: Allow bitcoin-tx to create v2 transactions...
02:45 < GitHub89> [bitcoin] laanwj closed pull request #8932: Allow bitcoin-tx to create v2 transactions (master...bitcointx2) https://github.com/bitcoin/bitcoin/pull/8932
02:47 < Victorsueca> has anybody ever got compiling on windows to work?
02:48 < wumpus> Victorsueca: yes, some people did, but all the current devs just cross-build from ubuntu
02:48 < wumpus> Victorsueca: this may be useful to you (building with WSL) https://github.com/bitcoin/bitcoin/pull/8935
02:48 < cdecker> Checking the hashes produced by gitian I noticed that jl2012 produced different results
02:49 < jl2012> which one?
02:49 < cdecker> The linux hashes
02:49 < jl2012> i didn't check. Let me see
02:50 < 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
02:50 < jl2012> it seems windows and MAC are the same
02:50 < cdecker> https://gist.github.com/d2014467aa28dc0d20d74b652950ceb1
02:50 < cdecker> jl2012: yep those seem to check out
02:50 < 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
02:50 < 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. 
02:51 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev     
02:52 < jl2012> cdecker: everyone got the same except me? I'll try again
02:52 < cdecker> And I seem to have botched the windows build myself
02:52 < cdecker> :-)     
02:53 < 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
02:53 < Victorsueca> i was getting error like directory does not exist or character "|" being unexpected
02:54 < luke-jr> Victorsueca: were you trying to build in a path with spaces?
02:55 < tulip> (lots are fake-looking bitcoinj, and someone who took the time to recompile 0.13.1 with a 0.9 subversion)
02:55 < luke-jr> tulip: AWS BitcoinJ is bogus obviously
02:56 < gmaxwell> tulip: I posted a banlist specifically for those things.
02:57 < 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
03:05 -!- jtimon [~quassel@211.28.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
03:08 < Victorsueca> luke-jr: only letters, numbers, dots and dashes
03:09 < Victorsueca> no spaces
03:10 < Victorsueca> also says that "Makefile" is not a command, but I thought that came with MinGW
03:13 < sipa> make is command
03:14 < sipa> Makefile is the file with the project specific build instructions
03:14 < sipa> and none of that will easily work in windows
03:14 < sipa> you'll need to write the build instructions yourself
03:14 < Victorsueca> so why does it think "Makefile" is suposed to be a command instead of a file?
03:15 < luke-jr> if it were me, I'd try to build with MSYS
03:15 < luke-jr> Victorsueca: what does?
03:16 < Victorsueca> luke-jr: when it try to build it tells me that "Makefile" is a unknown command
03:17 < luke-jr> when what try to build?
03:17 < luke-jr> you're the one issuing commands..
03:17 < Victorsueca> trying to build 0.13.1rc1
03:17 < Victorsueca> the only command I issued so far is >make HOST=i686-w64-mingw32 -j4
03:18 < luke-jr> where did you get the impression that was a way to build?
03:18 < Victorsueca> here https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md
03:20 < luke-jr> oh, in depends
03:21 < sipa> that's to build for windows, not on windows
03:22 < Victorsueca> sipa: i'm trying to build for windows on windows
03:22 < sipa> Victorsueca: good luck
03:22 < sipa> but none of the existing documentation will be of any use
03:23 < 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
03:23 < luke-jr> Victorsueca: it might be possible in MSYS, but don't expect anything to just work
03:24 < 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
03:25 < Victorsueca> sipa: that sounds like a pain in the arse, i'll just use the linux VM then
03:25 < sipa> yes, building via cross compiling is the only supported mechanism
03:27 < michagogo> Victorsueca: are you on Windows 10?
03:27 < Victorsueca> michagogo: yep
03:27 -!- tulip [uid192128@gateway/web/irccloud.com/x-xigwywvvqrexjthj] has quit [Read error: Connection reset by peer]     
03:28 < michagogo> Because then you could cross compile for windows on Ubuntu on Windows
03:28 -!- tulip [uid192128@gateway/web/irccloud.com/x-zsjmdpicvqwkknod] has joined #bitcoin-core-dev     
03:28 < michagogo> No need for a VM
03:29 < michagogo> (It's kinda amusing that you're cross-compiling for Windows on a Windows machine…)
03:29 < Victorsueca> michagogo: yeah lol
03:29 < Victorsueca> but there are no docs for windows compiling AFAIK
03:29 < michagogo> Actually, maybe that was already possible -- does anyone know if anyone's tried cross-compiling for Windows in Cygwin?
03:29 < michagogo> Victorsueca: that's the thing
03:30 < michagogo> If you do it in Ubuntu you just follow the Linux instructions
03:30 < Victorsueca> i'll just use the VM
03:32 < jtimon> Ubuntu on windows to build for windows, hehe
03:33 < michagogo> As of 0.10, this is all you needed to do to cross-compile for Windows:  https://www.irccloud.com/pastebin/W6gIBKMf
03:33 < michagogo> I assume it's pretty similar
03:34 < michagogo> (I don't think much has changed with the depends/build system since then?)
03:34 < michagogo> Victorsueca: well, doing it in Ubuntu On Windows should be pretty much identical to doing it in the VM AFAIK
03:39 -!- MarcoFalke [~marco@5.199.182.203] has joined #bitcoin-core-dev     
03:49 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev     
03:52 -!- fengling [~fengling@223.223.187.136] has quit [Ping timeout: 268 seconds]     
04:16 < 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
04:17 < wumpus> would help if someone tested those steps
04:18 < Victorsueca> wumpus: testing required? sure, I'll try it
04:18 < wumpus> it *looks* easy
04:20 < 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...
04:21 < sipa> it still boggles my mind how much changed
04:21 < wumpus> yes. it's extremely surprising to me, even now. I intend to try it out but haven't found the time yet
04:21 < wumpus> indeed
04:22 < wumpus> the list of top OS-es includes a Linux and a BSD derivative, and windows is not doing that well
04:24 < wumpus> no one would have believed that in the 90's, heck not even any science fiction precited it :)
04:32 < GitHub176> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/614d522c3e44...dd07c6b2cc90
04:32 < GitHub176> bitcoin/master b26a7b5 Jorge Timón: RPC: Chainparams: Remove Chainparams::fTestnetToBeDeprecatedFieldRPC
04:32 < GitHub176> bitcoin/master dd07c6b Wladimir J. van der Laan: Merge #8921: RPC: Chainparams: Remove Chainparams::fTestnetToBeDeprecatedFieldRPC...
04:32 < GitHub47> [bitcoin] laanwj closed pull request #8921: RPC: Chainparams: Remove Chainparams::fTestnetToBeDeprecatedFieldRPC (master...0.13-rpc-chain) https://github.com/bitcoin/bitcoin/pull/8921
04:32 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]     
04:33 < Victorsueca> linux on windows feels much like the universe is going to implode
04:34 < 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
04:52 -!- Naphex [~naphex@naphex.rocks] has quit [Quit: leaving]     
05:04 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]     
05:05 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev     
05:09 < 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...
05:10 < michagogo> AIUI it's more like a built-in, disabled-by-default, hook that can then proceed to download an Ubuntu environment
05:11 < 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
05:12 < michagogo> Then that installs the "bash" stub that kicks off the install proces
05:12 < michagogo> wumpus: and yeah, from what I've read it seems there shouldn't really be any reason for it not to work
05:13 < michagogo> I mean, it's a full Ubuntu environment, running actual Linux binaries
05:13 < michagogo> And the software build process doesn't exactly involve any exotic syscalls...
05:13 < luke-jr> somehow I doubt it supports LXC or KVM
05:13 < luke-jr> so probably can't do gitian at least
05:14 < michagogo> (Things like lxc, mknods, chroots, etc reportedly don't work)
05:14 < wumpus> luke-jr: that's not what is described there, though
05:14 < michagogo> luke-jr: right
05:14 < sipa> just depends build would be nice
05:14 < michagogo> sipa: yeah, I'm pretty sure that should work
05:14 < wumpus> but I'd assume the same - user namespaces support is quite esoteric
05:14 < michagogo> I'll see if my mom will let me put WSL on her computer
05:16 < luke-jr> michagogo: does chattr +i work? :P
05:16 < wumpus> extended attributes? I'd bet not
05:16 < michagogo> ;;Google chattr
05:16 < 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/>
05:16 < Victorsueca> installing WSL right now on my dev machine...
05:17 < wumpus> I'd already be surprised if they somehow properly map posix ACLs to linux ones
05:17 < wumpus> eh to windows ones
05:19 < jonasschnelli> does the WIN10 WSL comes with a window manager in a windows-window? Probably no...
05:19 < wumpus> heh seems in the same year OpenBSD removed support for linux executables, windows added it
05:20 < wumpus> jonasschnelli: no, it doesn't come with GUI support
05:20 < wumpus> libwin32gui on ubuntu would be kind of interesting, though heretical :)
05:22 < wumpus> though I doubt there's anything preventing your from running a windows X server on windows and connect to that
05:22 < wumpus> circuitous, but meh
05:22 < luke-jr> wumpus: chattr is non-extended attributes though! :P
05:22 < michagogo> WSL File System Support – Windows Subsystem for Linux https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/
05:23 < wumpus> is there any use for chattr +i besides sadist trolling of linux newbies?
05:24 < luke-jr> wumpus: making sure I don't delete very important files :P
05:24 < wumpus> ooh :D
05:24 < luke-jr> find -type f | xargs chattr +i # in my family photos
05:25 < michagogo> Ooh     
05:26 < michagogo> WSL may make it possible to run Gitian in a real VM!
05:26 < michagogo> On Windows, without nesting, I mean!
05:27 < jtimon> ping #8855 (testchains easier to create, less use of globals)
05:29 < GitHub180> [bitcoin] laanwj closed pull request #8909: Change bundle identifiers (master...bc) https://github.com/bitcoin/bitcoin/pull/8909
05:32 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev     
05:33 < GitHub117> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/dd07c6b2cc90...6e094e54f7ff
05:33 < GitHub117> bitcoin/master d51f182 jnewbery: Don't return the address of a P2SH of a P2SH.
05:33 < GitHub117> bitcoin/master 6e094e5 Wladimir J. van der Laan: Merge #8845: Don't return the address of a P2SH of a P2SH...
05:34 < 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
05:36 < michagogo> luke-jr: chattr: inappropriate ioctl for device while reading flags on test
05:36 -!- MarcoFalke [~marco@5.199.182.203] has left #bitcoin-core-dev []     
05:41 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds]     
05:42 < GitHub22> [bitcoin] laanwj pushed 2 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/907c314057b0...685e4c78f8ed
05:42 < GitHub22> bitcoin/0.13 3f508ed Wladimir J. van der Laan: rpc: Generate auth cookie in hex instead of base64...
05:42 < GitHub22> bitcoin/0.13 685e4c7 Matt Corallo: Remove bogus assert on number of oubound connections....
05:45 < 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)
05:45 < michagogo> So far so good -- needed to install make
05:45 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev     
05:46 < michagogo> Depends is running now -- managed to build ccache, so that's good -- downloading boost right now
05:47 < GitHub136> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/6e094e54f7ff...c71a654c5fff
05:47 < GitHub136> bitcoin/master f2e939b fanquake: [Doc] Update Doxygen configuration file
05:47 < GitHub136> bitcoin/master c71a654 Wladimir J. van der Laan: Merge #8890: [Doc] Update Doxygen configuration file...
05:47 < wumpus> michagogo: great!
05:47 < 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
05:48 < achow101> michagogo: I've been able to compile both linux and windows binaries on WSL
05:48 < achow101> but I haven't gotten gitian to work yet
05: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
05:50 < michagogo> wumpus: not what I meant
05:50 < michagogo> I meant, run gitian itself in WSL
05:50 < michagogo> And use VBox
05:50 < wumpus> you can't run gitian in WSL, there's no virtualization support
05:51  * luke-jr wonders if WSL can call Windows-build qemu
05:51 < michagogo> No, but maybe it can control native vbox
05:51 < michagogo> Or ^^
05:51 < wumpus> luke-jr: indeed, if you can launch native exes
05:52 < wumpus> windows qemu is strange though
05:52 < luke-jr> at least in the kqemu days, IIRC there was virt support for qemu on windows
05:52 < wumpus> I tried that once, and was unable to get accelerated virtualization to work
05:53 < luke-jr> kqemu is pretty old stuff :p
05:53 < luke-jr> pre-VT-x
05:53 < michagogo> Hrm     
05:53 < wumpus> it may need some special driver that needs to be installed as admin, dunno
05:53 < michagogo> Nope, it looks like it's a full environment
05:53 < michagogo> Not like cygwin
05:54 < michagogo> bash: /mnt/c/Windows/System32/gpupdate.exe: cannot execute binary file: Exec format error
05:55 < michagogo> Looks like within WSL it's Linux-only
05:55 < michagogo> I wonder if there's a way to workaround it
05:56 < achow101> wine in wsl ;D
05:57 < michagogo> Hmmmmm
05:57 < wumpus> hahha OSS people aren't happy until they can do a full emualtion roundtrip
05:59 < Victorsueca> would it be possible to do WSL on Wine on WSL.... :P
05:59 < Victorsueca> Inception!
06:00 < wumpus> :')     
06:01 < wumpus> shouldn't be to difficult to support the WSL syscalls in wine
06:03 < michagogo> Wine doesn't want to install
06:03 < michagogo> Looks like a bunch of i386 packages not coming in
06:03 < wumpus> I'd expected so
06:03 < luke-jr> wumpus: lol
06:03 < michagogo> I wish apt were better at showing actual cause
06:04 < michagogo> It says winehq-devel : Depends: wine-devel
06:04 < timothy> hi, do you think can be good to add support for rpc to tor?
06:04 < timothy> actually only 8333 is supported
06:04 < wumpus> not just a matter of sudo dpkg --add-architecture i386  ?
06:04 < michagogo> (Unmet dependency)
06:04 < michagogo> wumpus: I did that first
06:04 < timothy> (integrated, I mean. ofc you can use the "standard" tor feature to add rpc port)
06:04 < michagogo> And it says "you have held broken packages", which is misleading
06:05 < michagogo> Anyway, wine-devel then depends on wine-devel-i386
06:05 < wumpus> timothy: if you really want to expose your RPC port on a Tor hidden service that's possible
06:05 < michagogo> And that, in turn, depends on a whole lot of :i386 packages
06:05 < wumpus> timothy: wouldn't advice doing it by default though, a lot of scope to mess up
06:05 < timothy> wumpus: actually I use it only for opentimestamps
06:05 < michagogo> Some say "but it is not going to be installed"
06:05 < timothy> I don't have any wallets here
06:06 < michagogo> But then some say "but it is not installable"
06:06 < 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
06:06 < michagogo> Maybe I could poke at it and figure out what's going on, but a. I don't really care enough
06:06 < michagogo> And b. I doubt I'd be able to figure it out anyway :P
06:06 < timothy> wumpus: ofc it's only for private use and on another port (not 8332)
06:07 < 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
06:07 < michagogo> Would be nice if depends could multitask
06:08 < timothy> wumpus: so do you suggest me to add another layer like stunnel with client cert?
06:08 < wumpus> timothy: for private use it's fine
06:08 < luke-jr> michagogo: it can't?
06:08 < wumpus> timothy: no need for that, tor has hs security built-in, look into "hidden service authentication"
06:09 < wumpus> with HidServAuth something you can restrict who can connect to your hidden service with certain keys
06:09 < michagogo> luke-jr: I mean, maybe -jx works within a build
06:09 < michagogo> But I mean, for example, download and build different packages in parallel
06:10 < timothy> wumpus: not bad, thank you
06:10 < luke-jr> michagogo: make -jN in depends/?
06:10 < michagogo> luke-jr: I did that
06:10 < michagogo> Maybe each individual compilation job is multitasking
06:10 < michagogo> But it's doing one package at a time
06:10 -!- MarcoFalke [~marco@5.199.182.203] has joined #bitcoin-core-dev     
06:11 < luke-jr> weird
06:11 < michagogo> So as OpenSSL.org is feeding me the file at 1000 bytes a second, it's holding up the whole thing
06:11 < GitHub106> [bitcoin] MarcoFalke opened pull request #8954: contrib: Add README for pgp keys (master...Mf1610-docKeys) https://github.com/bitcoin/bitcoin/pull/8954
06:11 < michagogo> Oh, wait -- we have a fallback to our server, right?
06:11  * michagogo kills curl
06:11 < michagogo> Hah. Pulled it from bitcoincore.org in like 10 secs
06:12 < Victorsueca> lol     
06:12 < michagogo> Anyway, depends build in WSL chugging along
06:12 < michagogo> Building BDB now
06:13 < Victorsueca> libboost is taking a eternity to unpack here
06:13 < michagogo> (I told make NO_QT=1)
06:13 < michagogo> Victorsueca: SSDs ftw
06:13 < michagogo> Depends done!
06:14 < wumpus> libboost takes longer to unpack than to build, generally
06:14 < wumpus> (at least in depends; we severly restrict the subset of boost that is built)
06:17 < GitHub53> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c71a654c5fff...f628d9a29a2d
06:17 < GitHub53> bitcoin/master 1724a40 R E Broadley: Display minimum ping in debug window.
06:17 < GitHub53> bitcoin/master f628d9a Wladimir J. van der Laan: Merge #8925: qt: Display minimum ping in debug window....
06:17 < GitHub157> [bitcoin] laanwj closed pull request #8925: qt: Display minimum ping in debug window. (master...DebugWindowMinPing) https://github.com/bitcoin/bitcoin/pull/8925
06:17 < wumpus> jtimon: will take a look at that
06:18 < jtimon> wumpus: cool, thanks
06:18 < michagogo> Configured! Now for the moment of truth:
06:18 < wumpus> < michagogo> (I told make NO_QT=1) <- oh no but then you won't get the GUI, which all windows users really want!
06:18  * michagogo make -j8
06:19 < michagogo> wumpus: yeah, but this is a poc
06:19 < michagogo> I don't want to download and build qt for this
06:19 < wumpus> michagogo: right
06:19 < wumpus> yes, agreed, that takes ages
06:19 < michagogo> (Unless you think there's a chance it might not work where everything else might?)
06:20 < 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
06:20 < michagogo> https://usercontent.irccloud-cdn.com/file/5BV08yei/1476796841.JPG
06:21 < wumpus> uh scratch that... no, no X stuff.. you're cross-building for windows
06:22 < michagogo> 🎉 https://usercontent.irccloud-cdn.com/file/CZ2ckANc/1476796939.JPG
06:23 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev     
06:23 < wumpus> motion blurred pixels, woo almost the matrix
06:24 < michagogo> It works! https://usercontent.irccloud-cdn.com/file/d2GHULdO/1476797054.JPG
06:25 < wumpus> -help works at least :-)
06:25 < michagogo> Well, no args in this case
06:25 < michagogo> But yeah
06:25 < Victorsueca> michagogo: try to query the genesis block
06:25 < michagogo> But the binary executes!
06:25 < MarcoFalke> test_bitcoin.exe
06:25 < michagogo> Victorsueca: nah, not gonna run it and set up a datadir on this machine
06:26 < wumpus> test_bitcoin is a good suggestion
06:26 < michagogo> Is that self-contained?
06:26 < wumpus> if that passes we can tested-ACK and merge #8935
06:26 < wumpus> yes     
06:27 < michagogo> Running 212 test cases…
06:29 < wumpus> congrats, you've succeeded building bitcoin core for windows on windows before I succeeded building bitcoin core for android on android
06:29 < michagogo> Heh     
06:29 < michagogo> Well, to be fair, Microsoft and Canonical made it really easy
06:32 < michagogo> BTW, where is bitcoincore.org?
06:32 < michagogo> Looks like it's only 2 hops past the last hop that resolves to a name including my ISO
06:32 < michagogo> ISP     
06:34 < michagogo> Oh, in the meantime:
06:34 < michagogo> *** No errors detected
06:34 < wumpus> good!
06:35 < GitHub112> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f628d9a29a2d...0306978394db
06:35 < GitHub112> bitcoin/master 7c1716f poole_party: Documentation for Building on Windows with WSL...
06:35 < GitHub112> bitcoin/master 0306978 Wladimir J. van der Laan: Merge #8935: Documentation: Building on Windows with WSL...
06:35 < GitHub40> [bitcoin] laanwj closed pull request #8935: Documentation: Building on Windows with WSL (master...windows_build_docs) https://github.com/bitcoin/bitcoin/pull/8935
06:37 < Victorsueca> I'm going to compile it with GUI support and try it out on a actual datadir
06:37 -!- jlopp [2d25b77a@gateway/web/freenode/ip.45.37.183.122] has joined #bitcoin-core-dev     
06:37 < wumpus> Victorsueca: great
06:39 < michagogo> This series of commands seems to be all that's needed, on a completely fresh WSL: https://www.irccloud.com/pastebin/W6gIBKMf
06:40 < 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
06:40 < wumpus> it's impressive how few commands it is though
06:41 < michagogo> Kudos to cfields_ for the depends system...
06:41 < wumpus> michagogo: bitcoincore.org is behind cloudflare, so that's probably one of their co-located "spy servers" close to you :)
06:42 < michagogo> wumpus: ah, yeah, that explains the speed too
06:44 < michagogo> Who's
06:44 < michagogo> Whoa*
06:44 < michagogo> QT on an SSD with -j9 on a quad-core i5-6600K is really not so bad
06:45 < GitHub63> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0306978394db...cdfb7755a6af
06:45 < GitHub63> bitcoin/master 5eaaa83 Wladimir J. van der Laan: Kill insecure_random and associated global state...
06:45 < GitHub63> bitcoin/master cdfb775 Wladimir J. van der Laan: Merge #8914: Kill insecure_random and associated global state...
06:45 < 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
06:45 < michagogo> It was certainly a few minutes, but not nearly as bad as in gitian
06:46 < GitHub174> [bitcoin] laanwj closed pull request #7753: zmq: mempool notifications (master...2016_03_zmq_mempool_notifications) https://github.com/bitcoin/bitcoin/pull/7753
06:46 < michagogo> (I'm also not sure I've done a gitian build with a qt bump since upgrading to an SSD...)
06:46 < wumpus> what parallelism do you use in gitian?
06:46 < michagogo> -j5, maybe?
06:47 < michagogo> It's in a VM, on an i7-3610QM
06:47 < michagogo> I think the VM might have 3 cores, though
06:48 < michagogo> Also: cache is nice
06:48 < michagogo> ccache*
06:48 < michagogo> Watching the build with Qt fly by
06:49 < molz> michagogo, do you need to install all the dependencies first before using https://www.irccloud.com/pastebin/W6gIBKMf  ?
06:49 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 260 seconds]     
06:49 < michagogo> molz: which dependencies?
06:49 < michagogo> The ones for Bitcoin are downloaded and built by those commands
06:50 < michagogo> (The cd depends;make HOST...)
06:50 < molz> oh..  
06:50 < michagogo> The apt-get command installs everything that the build process needs
06:51 < 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
06:51 < michagogo> (And all the others)
06:52 < michagogo> wumpus: what is test_bitcoin-qt.exe supposed to do?
06:52 < michagogo> It seems to just return to the command line immediately
06:52 < michagogo> No output
06:53 < sipa> run the bitcoin-qt unit test
06:53 < michagogo> sipa: is it supposed to output anything, like test_bitcoin.exe does?
06:53 < wumpus> it should print something about Start Testing Finished Testing, normally
06:53 < sipa> unsure
06:54 < michagogo> Doesn't look like it?
06:54 < wumpus> but I've never tried it in windows
06:54 < molz> michagogo, ok i'm not on win10, can the irccloud guide be used on Ubuntu 14.4 VM ? 
06:54 < michagogo> I just get the prompt back
06:54 < molz> i'm installing Ubuntu 14.4 on the VM right now
06:54 < wumpus> maybe it's accidentally compiled as a UI subsystem instead of console subsystem executable?
06:54 < michagogo> molz: yeah, those commands should work on a fresh install of 14.04
06:54 < sipa> wumpus: maybe not accidentally... a qt app may need to be gui
06:54 < molz> ok, thanks, going to try it now
06:55 < MarcoFalke> Anything holding back https://github.com/bitcoin/bitcoin/pull/8928
06:55 < wumpus> sipa: it doesn't need to be, console will just open a console at startup, it can still use the UI APIs
06:55 < sipa> ah     
06:55 < wumpus> (though none of the Qt unit tests does anything with UI)
06:55 < michagogo> We don't seem to ship test_bitcoin-qt.exe
06:56 < wumpus> that's on purpose - it's silly right now
06:56 < michagogo> The win64 zip for 0.13.0 from Bitcoin.org has test_bitcoin.exe but not -qt
06:56 < wumpus> it's a huge executable when statically linking, pulling in much of qt, for no good reason
06:56 < michagogo> So I'm guessing it's not something wrong with this build setup
06:56 < wumpus> yes, test_bitcoin.exe is suposed to be in there
06:56 < wumpus> I'm guessing the same
06:57 < michagogo> If I run Bitcoin-Qt.exe with a -datadir argument, does it leave traces of itself anywhere but that directory?
06:57 < sipa> it shouldn't
06:57 < wumpus> yes - in the registry
06:57 < wumpus> bitcoind.exe shouldn't, though
06:58 < michagogo> Anything outside a simple key named for the app?
06:58 < wumpus> no, it's one 'directory' named bitcoin-qt or such
06:58 < wumpus> with qt settings
06:59 < michagogo> Okay, that's tolerable
06:59 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds]     
06:59 -!- fengling [~fengling@43.255.176.6] has joined #bitcoin-core-dev     
06:59 < 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
06:59 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev     
07:00 < Victorsueca> cpp not working here
07:01 < Victorsueca> error C++ processort /lib/cpp fails sanity check
07:01 < Victorsueca> processor*
07:02 < sipa> what are you doing
07:03 < michagogo> WSL-built 0.13.1rc1 is running!
07:03 < wumpus> michagogo: HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt and HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt-testnet
07:03 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev     
07:04 < michagogo> Also: looks like tailf doesn't work in WSL
07:04 < michagogo> tailf: <path>: cannot add inotify watch.: Invalid argument
07:05 < michagogo> (Looks like all my peers have WITNESS in services
07:05 < michagogo> )     
07:05 < michagogo> 3 claim to be 0.13.0, 2 0.13.1, and 2 0.13.99
07:05 < Victorsueca> sipa: this https://gist.github.com/Victorsueca/62d3dc1c3db26da2326ed24e4308617d
07:06 < michagogo> (Oh, right -- rc1 still calls itself .0)
07:06 < wumpus> yes     
07:06 < michagogo> Victorsueca: did you install g++?
07:06 < michagogo> Pretty sure that was in my paste
07:06 < wumpus> the 0.13.0 ones are rc1, 0.13.1 ones are 0.13 branch, 0.13.99 is master. It checks out
07:07 < Victorsueca> michagogo: I'm not following your paste, i'm using the docs
07:07 < Victorsueca> thanks,i'll try that
07:07 < michagogo> Maybe we should copy my paste to the docs
07:07 < wumpus> sanity check failures in configure 99% of the time mean that the compiler just isn't installed
07:08 < michagogo> (Also, maybe go over and check that that is the absolute minimum)
07:08 < wumpus> (unless you happen to be overriding the compiler to a static analysis tool etc)
07:09 < Victorsueca> seems to be working now
07:10 < Victorsueca> nope, autoconf is missing
07:10 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has quit [Quit: Whatever]     
07:11 < jlopp> I asked these questions in wizards yesterday; crossposting for more visibility: 
07:11 < 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. 
07:11 < jlopp> Though I thought that since libsecp256k1 drastically increases signature validation performance, the speedup is negligible now.
07:11 < 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)."
07:11 < 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
07:11 < wumpus> jlopp: helps to read https://github.com/bitcoin/bitcoin/issues/7591
07:12 < 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
07:13 < wumpus> there's always the -checkpoints=0 option if you can't wait for them to be removed
07:14 < 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
07:14 -!- bsm117532 [~mcelrath@38.121.165.30] has joined #bitcoin-core-dev     
07:15 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev     
07:15 < Victorsueca> https://gist.github.com/Victorsueca/442d36e6c16b490d5dc15399855810bc <--- no idea what went wrong now
07:16 < BlueMatt> so....fibre....want more than one group/person to run a public network based on it
07:16 < Victorsueca> the docs don't really explain what libraries you should get
07:16 < BlueMatt> also want to shut down the rn on dec 1
07:16 < BlueMatt> so that leaves....a week or two to get networks up
07:18 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #bitcoin-core-dev     
07:18 < sipa> BlueMatt: maybe someone at dci?
07:19 < BlueMatt> that was suggested, I can reach out to neha and see if there are any students interested in running one
07:19 < 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
07:20 < BlueMatt> (and only if there is an additional one run by someone else)
07:20 < neha> We can probably run one.  What are the bw/hard drive/mem/etc requirements?
07:21 < BlueMatt> neha: i mean a network, not node
07:22 < BlueMatt> which means dedicated servers roughly in similar locations as those on the map at http://bitcoinrelaynetwork.org/
07:22 < nsh> cc musalbas 
07:22 < 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
07:22 < 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
07:23 < sipa> units?
07:23 < sipa> what is a mo
07:23 < wumpus> month
07:23 < BlueMatt> usd/cad/eur/gbp/etc
07:23 < BlueMatt> any of them are valid
07:24 < sipa> ah     
07:24 < neha> could we get multiple universities to run nodes as part of one network?
07:24 < BlueMatt> neha: because of the weird trust-all-nodes-in-the-network requirement if you want to run with cut-through on, thats....awkward
07:25 < BlueMatt> neha: i mean could turn off the cut-through and do it
07:25 < BlueMatt> if its on a fast-single-threading server with good peak bw that might be ok
07:26 < sipa> the only issue is that the nodes within the network could dos each other, right?
07:26 < BlueMatt> if you do trusted mode any node can break propagation for a block to the entire network
07:26 < wumpus> so it's mainly miners using this right: aren't any miners/mining pools interested in setting up a network like this?
07:26 < neha> do the nodes need to be geo-distributed?
07:27 < neha> (i need to read more about fibre)
07:27 < BlueMatt> wumpus: i have no idea why miners seemingly only ever provide lip-service to things like this :/
07:27 < wumpus> BlueMatt: I was afraid you were going to say that
07:27 < 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
07:27 < BlueMatt> wumpus: well, i do know, for many of them it doesnt matter because they just do spy-mining
07:28 -!- fengling [~fengling@43.255.176.6] has quit [Ping timeout: 268 seconds]     
07:28 < BlueMatt> neha: otherwise how are you propagating around the world? :p
07:28 < sipa> BlueMatt: neutrinos.
07:28 < BlueMatt> oooo bitcoin-over-neutrino
07:28 < BlueMatt> might want to get ip-over-neutrino to work first, though
07:28 < neha> this might be a good thing for a network of universities to do. 
07:28 < neha> don't need to worry too much about schools (intentionally) dos'ing each other
07:28 < BlueMatt> neha: indeed, universities tend to have good low-latency bw between each other, too
07:29 < Victorsueca> ip-over-dark-matter is better
07:29 < BlueMatt> neha: well, I think it'd still need to run in non-trusted mode
07:29 < 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
07:29 < BlueMatt> security at uni-hosting places tends to be.......
07:30 < Victorsueca> deficient? is that the word you're searching?
07:30 < wumpus> Victorsueca: ip-over-microwormholes
07:30 < sipa> BlueMatt: can you have two tiers? different orgs running their own nodes, internally cut-through, but not cut-through across orgs
07:30 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds]     
07:30 < BlueMatt> sipa: yes
07:30 < Victorsueca> wumpus: lol
07:30 < sipa> BlueMatt: and then have maybe one org colocate one of their nodes inside or nearby another org's node
07:31 < Victorsueca> wumpus: with that you could recieve data even before it's sent
07:31 < 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
07:31 < sipa> right
07:31 < BlueMatt> sipa: fibre is rather packet-loss-insensitive :)
07:34 < 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
07:35 < BlueMatt> sipa: true
07:35 < neha> agree
07:36 < 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
07:37 < neha> we have almost "free" access to compute resources, but only locally.
07:37 < BlueMatt> hmm, for that to be useful I think I'd have to run an actual network and let people peer into it
07:37 < BlueMatt> which I'd gladly do, but dont want to funt it myself anymore if I'm gonna stand up a real network
07:38 < neha> bitcoin foundation?
07:38 < neha> or us i suppose depending on costs
07:38 < BlueMatt> they dont have any $$$ left
07:38 < neha> wouldnt your "network" be very small, with most of the resources provided being from people peering?
07:38 < michagogo> Victorsueca: is there something wrong with that last gist?
07:39 < 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
07:39 < sipa> BlueMatt: we'll need a SF to commit to error correction packets :)
07:40 < BlueMatt> sipa: yes, probalem is putting it in the coinbase is expensive, so we need a HF to commit to ECC packets :p
07:40 < Victorsueca> michagogo: no idea, the console seemed to error out, but after spamming the make command a few times it started working
07:40 < michagogo> Victorsueca: what did the consoel look like?
07:41 < sipa> BlueMatt: last tx?
07:41 < Victorsueca> michagogo: lots of error being spammed out, stuff outside of the directory, automake is not available....
07:41 < sipa> BlueMatt: which you require to be small
07:41 < BlueMatt> sipa: just traversing down the merkle tree is non-trivial in byte count when you only have <1500 bytes to play with
07:41 < Victorsueca> I apt-get'd autoconf but still didn't work
07:41 < michagogo> Okay, I just reset my WSL
07:42 < michagogo> Going to figure out what's necessary and sufficient
07:42 < Victorsueca> after spamming the make command a few times and now seems to work tho
07:45 < Victorsueca> now it's doing checks....
07:56 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has joined #bitcoin-core-dev     
07:56 < jtimon> Is nMaxTries in generateBlocks() [rpc/mining.cpp] very used and loved?
07:58 < 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
07:59 -!- jlopp [2d25b77a@gateway/web/freenode/ip.45.37.183.122] has quit [Quit: Page closed]     
08:00 < 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
08:04 -!- mturquette [sid66043@gateway/web/irccloud.com/x-qapqxnwniusnufxq] has quit [Ping timeout: 260 seconds]     
08:07 < Victorsueca> damn, missing pkg-config
08:08 < michagogo> Yep, already got that on the list
08:10 -!- mturquette [sid66043@gateway/web/irccloud.com/x-qwldozdxdmyanpcv] has joined #bitcoin-core-dev     
08:10 < michagogo> Interesting
08:11 < michagogo> Looks like b2 (boost build tool) is passed -j2 regardless of the depends make -j argument
08:11 < michagogo> (assuming it means the same thing there)
08:12 < michagogo> Yep, hard-coded:   ./b2 -d2 -j2 -d1 --prefix=$($(package)_staging_prefix_dir) $($(package)_config_opts) stage
08:12 < michagogo> cfields_: any particular reason for that?
08:12 < wumpus> michagogo: does -j do the same for b2 as for make?
08:13 < michagogo> Yeom just checked that
08:13 < michagogo> Yep,*
08:13 < michagogo> -j N
08:13 < michagogo> Run up to N commands in parallel.
08:13 < michagogo> from http://www.boost.org/build/doc/html/bbv2/overview/invocation.html
08:13 < cfields_> michagogo: hmm, no reason. Just got left in after testing i guess
08:13 < wumpus> ok. Probably accidental then
08:13 < cfields_> I'm pretty sure you can grab the parallel value from make somehow
08:14 < Victorsueca> I use make with -j4
08:14 < michagogo> Hm, OpenSSL forces -j1
08:14 < wumpus> yes, openssl is broken otherwise
08:14 < wumpus> (the build, not the library)
08:14 < cfields_> yes, that one's on purpose
08:14 < michagogo> ah     
08:15 < 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
08:16 < Victorsueca> damn, can't reash confdefs.h No such file or directory
08:16 < Victorsueca> read*
08:16 < michagogo> Based on miniupnpc, I'm guessing that it inherits if not specified
08:16 < michagogo> Oh, wait, for boost that doesn't work
08:16 < wumpus> Victorsueca: I'm baffled that michagogo had such an easy time building while you seem to stumble into every possible issue :)
08:16 < Victorsueca> wumpus: yeah, that usually hapens to me when compiling software
08:16 < Victorsueca> lol     
08:17 < michagogo> Victorsueca: you're not on insider preview, are you?
08:17 < Victorsueca> nope
08:18 < Victorsueca> just plain windows 10 with aniversary update
08:18 < michagogo> `lsb_release -r` shows 14.04?
08:18 < michagogo> Packages all updated?
08:19 < Victorsueca> yes, it's 14.04
08:19 < Victorsueca> and apt-get upgrade shows everything updated
08:23 < michagogo> Wait a minute, depends builds protobuf _twice_?
08:23 < michagogo> I could have sworn it did that at the beginning
08:24 < Victorsueca> I thought something may be corrupt on the source files and I deleted everything and started over
08:24 < Victorsueca> I use the v0.13.1rc1 zipball from github
08:25 < wumpus> try following exactly what michagogo does in his pastebin
08:25 < wumpus> e.g. check out the tag from git
08:25 < michagogo> I'm working on updating that right now
08:25 < wumpus> ok     
08:25 < Victorsueca> ok     
08:26 < michagogo> So far, looks like this might be what's necessary and sufficient to make it work: https://www.irccloud.com/pastebin/W0iBQZbU/
08:26 < 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=
08:26 < michagogo> If it fails I'll add g++-mingw-w64,  and if that fails I'll add mingw-w64
08:26 < Victorsueca> now will try michagogo's pastebin
08:31 < GitHub199> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/cdfb7755a6af...1e1b8ceb5ebc
08:31 < GitHub199> bitcoin/master aa9d3c9 Steven: add software-properties-common...
08:31 < GitHub199> bitcoin/master 1e1b8ce Wladimir J. van der Laan: Merge #8929: add software-properties-common...
08:31 < GitHub70> [bitcoin] laanwj closed pull request #8929: add software-properties-common (master...patch-6) https://github.com/bitcoin/bitcoin/pull/8929
08:33 < GitHub120> [bitcoin] rebroad opened pull request #8957: Additional UpdateBlockAvailability (master...AddUpdateBlockAvailability) https://github.com/bitcoin/bitcoin/pull/8957
08:41 < GitHub185> [bitcoin] jl2012 closed pull request #8950: Update gitian signing key of jl2012 (master...patch-18) https://github.com/bitcoin/bitcoin/pull/8950
08:43 < GitHub90> [bitcoin] rebroad opened pull request #8958: Improve logic for advertising blocks (master...BetterBroadcastLogic) https://github.com/bitcoin/bitcoin/pull/8958
08:44 < wumpus> sigh
08:45 < Victorsueca> wumpus: what's up?
08:45 < wumpus> oh, rebroad spamming pr's again
08:45 < Victorsueca> ahh lol
08:46 < GitHub3> [bitcoin] rebroad opened pull request #8959: Fix sort arrow in peer table (master...FixPeerTableSort) https://github.com/bitcoin/bitcoin/pull/8959
08:46 -!- cryptapus [~cryptapus@87.254.202.250] has joined #bitcoin-core-dev     
08:46 -!- cryptapus [~cryptapus@87.254.202.250] has quit [Changing host]     
08:46 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev     
08:46 < michagogo> Good news
08:47 < michagogo> https://www.irccloud.com/pastebin/W0iBQZbU/ does indeed seem to be necessary and sufficient for cross-compiling for 64-bit Windows
08:47 < michagogo> On a completely fresh WSL 14.04
08:47 < Victorsueca> still compiling here, will see if it works this time
08:47 < 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
08:49 < michagogo> (if you also want to build 32-bit, drop the -x86-64 at the end of l1)
08:50  * wumpus wonders if anyone is still using 32-bit windows builds
08:50 < Victorsueca> I was just about to ask if x32 computers are still a thing
08:50 < wumpus> (except by accident on a 64-bit system)
08: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
08:51 < 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
08:53 < wumpus> this may be something that would make sense to ask on btctalk/reddit though, or maybe twitter
08:53 < Victorsueca> gee, this is taking a eternitiy to build
08:54 < michagogo> Victorsueca: Are you on a spinning disk or ssd?
08:54 < michagogo> Looks like the whole thing including depends took a bit over an hour
08:55 < michagogo> But that includes downloads of packages
08:55 < michagogo> both apt-get, and depedns sources
08:55 < molz> it took me half a day trying to build windows on debian VM and still didn't succeed 
08:55 < Victorsueca> michagogo: it finished just now, it's postprocessing ATM
08:55 < michagogo> Victorsueca: postprocessing what?>
08:56 < Victorsueca> openssl
08:56 < GitHub64> [bitcoin] rebroad opened pull request #8962: Correct checksum error message (and debug node id) (master...CorrectChecksumError) https://github.com/bitcoin/bitcoin/pull/8962
08:58 < michagogo> wumpus: Okay, so at some point I'll try to remember to PR my findings (in terms of packages)
08:59 < michagogo> I have the week off, which is nice -- holiday season is nice
08:59 < Victorsueca> postprocessing libevent now
08:59 < michagogo> g2g for now, though -- gotta eat
08:59 < Victorsueca> michagogo: see you
08:59 < michagogo> (Oh, and the 0.13.1rc1 I produced earlier, ran, and forgot to stop is still running just fine)
09:00 < michagogo> Up to block 312577, 2 hours after startup
09:00 < michagogo> Killing it now, tho
09:01 < GitHub24> [bitcoin] rebroad opened pull request #8963: NodeId missing from this debug line (master...SocketSendErrorNodeId) https://github.com/bitcoin/bitcoin/pull/8963
09:02 < Victorsueca> is that rebroad guy just spamming crap or he is actually contributing?
09:02 < wumpus> :-(     
09:02 < wumpus> he's done some constructive changes, but most is just 'change a debug message' here or there
09:03 < wumpus> or weird broken changes to the P2P code
09:03 < wumpus> a lot of review overhead for very little gain
09:04 < GitHub62> [bitcoin] rebroad opened pull request #8964: Don't request compact blocks in blocksonly mode (master...NoCompactBlocksOnly) https://github.com/bitcoin/bitcoin/pull/8964
09:04 < wumpus> fucking damnit
09:05 < Victorsueca> I would swear I have already seen 3 PRs related to compact blocks
09:05 < Victorsueca> can't he just PR all them in one?
09:06 < wumpus> that would make sense
09:07 < GitHub69> [bitcoin] laanwj closed pull request #8964: Don't request compact blocks in blocksonly mode (master...NoCompactBlocksOnly) https://github.com/bitcoin/bitcoin/pull/8964
09:07 < Victorsueca> headshot
09:08 < Victorsueca> laanwj the PR sniper
09:10 < wumpus> trying, but will take more than a one-man-army to defend against PR spamming of this scale :)
09:17 < Victorsueca> just wondering.... would it be possible to make a x168 system?
09:18 < Victorsueca> x128*
09:20 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
09:25 < Victorsueca> ohhh shit, 0 FPS, screen went unresponsive while compiling
09:27 < 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
09:28 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has quit [Quit: Whatever]     
09:30 < Victorsueca> what am I supposed to do now? kill it with the power button or wait?
09:31 < wumpus> hm AS/400 apparently did have 128-bit pointers. CHERI (capability-based architecture research project) has 256-bit pointers, even.
09:31 < wumpus> so yes it can always get bigger and crazier :)
09:32 < Victorsueca> wumpus: if I kill it now would it resume the build later?
09:32 < wumpus> Victorsueca: yes
09:33 -!- [Author] [~Author]@2401:a400:3202:2000:bad:d09:15:90d] has quit [Ping timeout: 268 seconds]     
09:34 < Victorsueca> good to know
09:35 < Victorsueca> does it make sense to have such huge pointers other than bigger integers?
09:35 < 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
09:35 < sipa> arguably that is part of the pointer
09:36 < 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
09:36 < GitHub58> [bitcoin] laanwj pushed 2 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/685e4c78f8ed...2c0913d0b3e1
09:36 < GitHub58> bitcoin/0.13 d179eed mruddy: doc: update 0.13.1 release note info on linux arm builds...
09:36 < GitHub58> bitcoin/0.13 2c0913d Wladimir J. van der Laan: Merge #8960: doc: update 0.13.1 release note info on linux arm builds...
09:37 < wumpus> sipa: so the entire disk uses content-addressable storage?
09:37 < wumpus> sipa: ah yes this is what you were talking about in Milan
09:37 < sipa> wumpus: no, there are still actual disk locations
09:38 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev     
09:42 < GitHub105> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1e1b8ceb5ebc...80a707824489
09:42 < GitHub105> bitcoin/master 83c0f7f mruddy: trivial: update 0.13.0 release note info on linux arm builds
09:42 < GitHub105> bitcoin/master 80a7078 Wladimir J. van der Laan: Merge #8955: doc: update 0.13.0 release note info on linux arm builds...
09:42 < 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
09:47 < 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.
09:49 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
09:50 < wumpus> https://twitter.com/orionwl/status/788413453593698304
09:59 < Victorsueca> ok, back to building, looks like it resumed correctly where it was
10:21 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]     
10:24 < GitHub48> [bitcoin] anduck opened pull request #8965: Mention that PPA doesn't support Debian (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8965
10:27 < gmaxwell> wumpus: perhaps we should do a release for w32 that pops up a box and asks the user to report their usage.
10:28 < BlueMatt> just make a http request to X.onion.to :p
10:33 -!- Netsplit *.net <-> *.split quits: arubi, phantomcircuit, warren, rabidus, tadasv, bad_duck, Lauda, sipa, owowo, Lightsword,  (+8 more, use /NETSPLIT to show all of them)
10:33 -!- rabidus_ [~lauri.j@uhiainen.com] has joined #bitcoin-core-dev     
10:33 -!- kcud_dab [~arthur@area51.powaaa.com] has joined #bitcoin-core-dev     
10:33 -!- Netsplit over, joins: kinlo
10:33 -!- asoltys_ [~bitcoinco@23.94.96.232] has joined #bitcoin-core-dev     
10:33 < Victorsueca> wow netsplit
10:33 -!- Netsplit over, joins: phantomcircuit
10:33 -!- Netsplit over, joins: BCBot
10:33 -!- Netsplit over, joins: arubi
10:33 -!- Netsplit over, joins: morcos
10:33 -!- warren [~warren@198.199.105.216] has joined #bitcoin-core-dev     
10:33 -!- warren [~warren@198.199.105.216] has quit [Changing host]     
10:33 -!- warren [~warren@fedora/wombat/warren] has joined #bitcoin-core-dev     
10:33 -!- Netsplit over, joins: owowo
10:34 < Victorsueca> gee, qt takes a lot to compile
10:34 < TD-Linux> building bitcoin under the Ubuntu for Windows environment is supported now?
10:34 < Victorsueca> TD-Linux: i'm doing it right now lol
10:34 -!- Lauda [~quassel@2a06:8ec0:3::1:b224] has joined #bitcoin-core-dev     
10:34 -!- Lauda [~quassel@2a06:8ec0:3::1:b224] has quit [Changing host]     
10:34 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev     
10:34 -!- Lightsword [~Lightswor@107.170.253.193] has joined #bitcoin-core-dev     
10:35 < wumpus> gmaxwell: I'm surprised with how long Microsoft is waiting to deprecate 32-bit windows
10:36 -!- tadasv [ttttt@gateway/shell/panicbnc/x-spkxovlcbhzhkkgj] has joined #bitcoin-core-dev     
10:36 < wumpus> hadn't expected a w10 release for it
10:36 -!- BCBot [~BCBot@46.101.246.115] has quit [Remote host closed the connection]     
10:36 -!- BCBot [~BCBot@46.101.246.115] has joined #bitcoin-core-dev     
10:37 -!- Netsplit over, joins: blkdb
10:37 < 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
10:38 < Victorsueca> what about the number of downloads from bitcoin.org? that would be a good indicative of x32 usage
10:38 < wumpus> we don't have that information
10:38 -!- Netsplit over, joins: sipa
10:38 < wumpus> also it's very possible that people download the 32-bit version by accident even though they're on 64-bit
10:39 < Victorsueca> doesn't the page detect your OS and arch?
10:39 < wumpus> of the browser
10:39 < Victorsueca> ahh right
10:39 < Victorsueca> the browser could be x32 by accident
10:39 < 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.
10:40 < TD-Linux> Victorsueca, or on purpose. most browser plugins are 32 bit only
10:40 -!- aspect_ [sid151486@gateway/web/irccloud.com/x-zhkltqiqoatszqve] has joined #bitcoin-core-dev     
10:40 < Victorsueca> gmaxwell: sounds like a loop, it's obviously going to be the most downloaded one if it's the main download
10:41 < sipa> Victorsueca: x32 is not the same as 32-bit x86 :)
10:41 -!- wallet42 [sid154231@gateway/web/irccloud.com/x-pkhcocajxfhdmtnj] has joined #bitcoin-core-dev     
10:41 < Victorsueca> sipa: it's ok if I call it ia32?
10:41 < Victorsueca> i'm too lazy to write the word "bit" :P
10:42 < wumpus> TD-Linux: that was the case in 2008 or so, but is that still the case?
10:42 < 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
10:43 -!- mappum [sid43795@gateway/web/irccloud.com/x-hiyshgzeyxnlybwe] has joined #bitcoin-core-dev     
10:43 < gmaxwell> wumpus: other than build costs is 32bit windows a burden on you/us?
10:43 < wumpus> is anyone still using browser plugins in the first place?
10:43 < 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
10:43 < Victorsueca> wumpus: I use chrome extensions at most
10:43 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev     
10:43 < wumpus> gmaxwell: well it goes mainly untested
10:43 < wumpus> gmaxwell: none of the devs uses windows, let alone 32-bit
10:44 < wumpus> Victorsueca: extensions are extensively used and a completely different thing :)
10:44 < sipa> it'd be nice if ubuntu shipped with a built-in windows environment too.
10:44 < btcdrak> fractal OS
10:44 < wumpus> gmaxwell: I just don't think it's used anymore in practice. What was the last 32-bit only CPU?
10:45 < 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
10:45 < wumpus> (I mean commonly used intel one, not ARM)
10:45 < Victorsueca> sipa: I think that's called wine, but i don't think it comes pre-installed, you have to apt-get it
10:46 < wumpus> TD-Linux: that doesn't sound like something desirable :)
10:46 < wumpus> "many malware is still 32-bit" hehe
10:47 < TD-Linux> wumpus, indeed, but then you tempt the antivirus vendors to binary patch your executable instead.
10:48 < sipa> wumpus: even windows 10 still supports ia32
10:49 < wumpus> sipa: I know, I was surprised about that a few messages back
10:49 < wumpus> sipa: that doesn't mean anyone is using it though
10:50 < 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
10:50 < Lightsword> wumpus, doesn’t luke-jr use 32 bit userspace or something strange?
10:50 < wumpus> Lightsword: on linux, yes
10:51 < 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
10:51 < sipa> wumpus: oh, i'm not arguing - i'm just as curious as you about actual usefulness of 32-bit windows
10:51 < wumpus> linux 32-bit is still used on VPSes with small memory (nano instances and such) so there's a reasonable user base
10:52 < 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
10:52 < wumpus> but we deprecated 32-bit Mac ages ago, and windows really is in the same ballpark as that, an end-user OS
10:52 < Lightsword> as a dedicated box they stick in a closet or something
10:53 < Lightsword> wumpus, yeah but apple deprecated 32-bit mac right?
10:53 < wumpus> let hem install inux, then
10:53 < wumpus> :p     
10:53 < wumpus> but *how old* is that anyhow? what and when was the last (commonly used) 32-bit only x86 CPU?
10:54 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev     
10:54 < Lightsword> wumpus, netbook atoms?
10:54 < TD-Linux> gmaxwell, instead of a box in the executable that pops up, you could put it on bitcoin.org
10:54 < gmaxwell> realistically, most hardware like atoms will be too non-performance to run bitcoin core anymore. :(
10:54 < wumpus> Lightsword: I don't think any of those really caught on, for running windows at least
10:55 < Lightsword> wumpus, I used them at one point with windows 7 32 bit…years ago
10:55 < gmaxwell> I worry more about users on fast hardware that happen to be running 32bit OSes because of ignorance or compatiblity with other things.
10:55 < wumpus> ok, never mind about his
10:55 < wumpus> seems everyone else feels this is still worth supporting, well go ahead :)
10:56 < Victorsueca> What about people who has a x64 OS but has low memory and wants to use bitcoin ia32 to save memory?
10:56 < wumpus> so are there any of those, using windows?
10:57 < wumpus> if you have low memory you probaly shouldn't be using that
10:57 < wumpus> same for small embedded hw
10:57 < gmaxwell> Victorsueca: using bitcoin ia32 should not be considerably more memory efficient.
10:58 < sipa> i think they are
10:58 < sipa> mempool, cpu cache, block index... they're all considerably smaller on 32-bit systems
10:59 < sipa> not a factor 2, but perhaps 20-30%
10:59 < 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
11:00 < wumpus> so, who is volunteering to do 32-bit windows testing for bitcoin core?
11:01 < gmaxwell> I can do that.
11:02 < 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
11:02 < wumpus> great
11:02 < wumpus> you should test on a 32-bit OS then, not a 64-bit one
11:03 < Victorsueca> ^ RIP ia32 lol
11:03 < Victorsueca> isn't it the same?
11:03 < wumpus> no, it's not the same
11:04 < Victorsueca> damn
11:04 < Victorsueca> gmaxwell: you're the only hope :D
11:08 < 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?
11:09 < sipa> Victorsueca: well gmaxwell points out that people may be running a 32-bit OS, not knowing their hardware supports x86_64
11:10 < achow101> I may be able to help test 32 bit windows, depends on what exactly needs to be done in order to test
11:10 < wumpus> achow101: run a node 24/7 on 32-bit windows at least
11:10 < wumpus> debug when things crash
11:12 < 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
11:16 < achow101> ok. does it matter if it's in a vm?
11:17 < wumpus> no     
11:18 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]     
11:19 < achow101> ok. I'll give it a go
11:19 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev     
11:23 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #bitcoin-core-dev     
11:23 -!- andytoshi [~apoelstra@wpsoftware.net] has quit [Changing host]     
11:23 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #bitcoin-core-dev     
11:25 < wumpus> thanks
11:28 < 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.
11:29 < Victorsueca> trying to figure out why the heck does my system become unresponsive while compiling qt
11:29 < Victorsueca> i'm stuck there and can't continue building bitcoin
11:29 < wumpus> memory full?
11:29 < Victorsueca> 85%     
11:29 < wumpus> it's c++ code, if you use too much parallelism it's easy tofill up memory
11:30 < Victorsueca> should I try -j1?
11:30 < wumpus> yes, you could try
11:34 < Victorsueca> I just didn't specify that option, how many threads does qt use by default when compiling?
11:34 < sipa> q     
11:35 < sipa> 1     
11:35 < Victorsueca> 1? and still out of memory? wtf?
11:35 < sipa> how much memory do you have?
11:35 < Victorsueca> 4GB     
11:35 < sipa> how much is available for the linux env?
11:36 < sipa> you need something like 1.5 or 2 GB to compile bitcoin core, i think
11:36 < 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
11:36 < wumpus> I'm sure there's some way to debug that
11:37 < Victorsueca> is WSL enviroment resource limited?
11:38 < Victorsueca> or it just can use everything windows has available?
11:38 < sipa> you tell us
11:38 < wumpus> yes this is probably not the right place to ask that
11:38 < Victorsueca> hmmm ok, i'll search on google
11:38 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev     
11:39 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]     
11:40 < achow101> Victorsueca: WSL should be using everything windows has available. It isn't a vm or emulation
11:40 < Victorsueca> ^ +1, google searches seems to agree
11:41 < Victorsueca> so basically I have 4GB - System memory usage
11:42 < MarcoFalke> it is mostly main and init that consume most ram
11:42 < Victorsueca> will try j1 and see if it makes any difference
11:43 < GitHub38> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/80a707824489...932d02ae392b
11:43 < GitHub38> bitcoin/master fab5ca8 MarcoFalke: contrib: Add README for pgp keys
11:43 < GitHub38> bitcoin/master 932d02a Wladimir J. van der Laan: Merge #8954: contrib: Add README for pgp keys...
11:43 < GitHub20> [bitcoin] laanwj closed pull request #8954: contrib: Add README for pgp keys (master...Mf1610-docKeys) https://github.com/bitcoin/bitcoin/pull/8954
11:46 < Victorsueca> yay, seems to be working
11:46 < Victorsueca> it's still responsive and memory is a 57% so far
11:46 < achow101> I forgot that windows takes ages to install...
11:47 < GitHub198> [bitcoin] laanwj closed pull request #8394: Make sure all ports are 16 bit numbers (master...uint16port) https://github.com/bitcoin/bitcoin/pull/8394
11:47 < Victorsueca> achow101: lol yeah
11:48 < Victorsueca> it has to verify itself that it's a crap enough to meet the M$ crap software standards
11:48 < wumpus> there's really too many PRs open
11:49 < 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
11:50 < wumpus> that makes no sense, everyone is 'the bitcoin team'
11:50 < Victorsueca> wumpus: I mean that list of people where there are 14 users right now, not sure how's it called
11:50 < wumpus> but just can't handle the load anymore
11:51 < Victorsueca> this list https://github.com/orgs/bitcoin/people
11:51 < sipa> wumpus: i'll help go through things, once i'm in a bit more stable location :)
11:51 < wumpus> sipa: you're already doing your best
11:51 < wumpus> sipa: I'm in no means suggesting you shuld do more work
11:52 < sipa> wumpus: heh, i've hardly looked at the issue/pr list in weeks
11:52 < wumpus> let the fucking community do their job for once, this is an open source project
11:53 < Victorsueca> comunity can't manage pull requests, tat's the problem, would be crazy if they could
11:53 < wumpus> you're just as overworked as me though
11:53 < wumpus> well they could help with reviewing and testing
11:53 < Victorsueca> aaaaaaand it's unresponsive again
11:53 < wumpus> and not just with creating more
11:54 < Victorsueca> now that's a serious problem, how do I debug this?
11:54 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has joined #bitcoin-core-dev     
11:55 < sipa> Victorsueca: i doubt many people here can give an answer to that
11:55 < michagogo> Victorsueca: got task manager/resource monitor/htop running?
11:55 < Victorsueca> michagogo: yep
11:55 < wumpus> again, this is not a windows developer troubleshooting channel
11:55 < 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!
11:55 < wumpus> maybe ##windows?
11:55 < michagogo> I mean, it's pretty much a full Ubuntu environment, so it's not so surprising
11:56 < Victorsueca> michagogo: it goes over 85% and a few seconds later it's unresponsive
11:56 < wumpus> I still bet it's swap trashing though
11:57 < 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.
11:58 < Victorsueca> wumpus: how is that suposed to be fixed?
11:58 < michagogo> Victorsueca: most likely with more resources, unfortunately
11:58 < Victorsueca> damn
11:59 < wumpus> I wondered what makes tail -f so exotic, thought it was just a pollign loop, but apparently it uses inotify
12:00 < Victorsueca> i'll have to use my other computer then, didn't want to restart that one because it's hosting stuff
12:00 < sipa> wumpus: maybe tail --follow=name works better?
12:01 < wumpus> sipa: looks like that adds an inotify on both the file *and* the directory it's in :)
12:05 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
12:05 < GitHub11> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/932d02ae392b...e10af96cf450
12:05 < GitHub11> bitcoin/master fa28bfa MarcoFalke: [wallet] Set fLimitFree = true
12:05 < GitHub11> bitcoin/master fa8b02d MarcoFalke: [rpc] rawtx: Prepare fLimitFree to make it an option
12:05 < GitHub11> bitcoin/master e10af96 Wladimir J. van der Laan: Merge #8287: [wallet] Set fLimitFree = true...
12:05 < GitHub40> [bitcoin] laanwj closed pull request #8287: [wallet] Set fLimitFree = true (master...Mf1607-walletLimitFree) https://github.com/bitcoin/bitcoin/pull/8287
12:07 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds]     
12:08 < 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
12:08 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Read error: Connection reset by peer]     
12:15 < 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
12:16 < GitHub120> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e10af96cf450...744d2652dda0
12:16 < achow101> connect in the bitcoin.conf means that it should only connect to the specified ip(s), right?
12:16 < GitHub120> bitcoin/master 9fce062 Daniel Kraft: [c++11] Use std::unique_ptr for block creation....
12:16 < GitHub120> bitcoin/master 744d265 Wladimir J. van der Laan: Merge #8223: [c++11] Use std::unique_ptr for block creation....
12:16 < 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
12:16 < jonasschnelli> achow101: yes.
12:17 < achow101> well that isn't happening. this is with 32-bit 0.13.0 on win10
12:17 < jonasschnelli> And IIRC, you can't even ban that node.
12:17 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Quit: DeepSpace took me hostage.]     
12:17 < jonasschnelli> achow101: maybe post your debug.log?
12:17 < BlueMatt> #8637 looks merge-able
12:17 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev     
12:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Quit: Gone frying asparagus or my Windows had a BSOD (how not)]     
12:18 < MarcoFalke> BlueMatt: 8908 should not cause any issues with the ppa?
12:18 < MarcoFalke> Otherwise, I think it is merge ready as well
12:18 < BlueMatt> no, that wont hurt anything
12:18 < wumpus> is that the hack to get the PPA to install on debian instead of ubuntu? it made me scared
12:19 < BlueMatt> no, its the one that changes the .desktop file
12:19 < wumpus> @Anduck ^^ :p
12:19 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Ping timeout: 248 seconds]     
12:19 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev     
12:20 < wumpus> ah no that's https://github.com/bitcoin/bitcoin/pull/8965
12:20 < GitHub94> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/744d2652dda0...0b5a997acfb6
12:20 < GitHub94> bitcoin/master 02a337d Matt Corallo: Dont remove a "preferred" cmpctblock peer if they provide a block
12:20 < GitHub94> bitcoin/master fe998e9 Matt Corallo: More agressively filter compact block requests...
12:20 < GitHub94> bitcoin/master b2e93a3 instagibbs: Add cmpctblock to debug help list
12:20 < GitHub32> [bitcoin] laanwj closed pull request #8637: Compact Block Tweaks (rebase of #8235) (master...compactblocktweaks) https://github.com/bitcoin/bitcoin/pull/8637
12:20 < GitHub196> [bitcoin] jonasschnelli pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0b5a997acfb6...df7519cbc1a9
12:20 < GitHub196> bitcoin/master 164196b matthias: Simple Update to File 'bitcoin-qt.desktop'
12:20 < GitHub196> bitcoin/master df7519c Jonas Schnelli: Merge #8908: Update bitcoin-qt.desktop...
12:20 < wumpus> thanks jonasschnelli 
12:20 < GitHub61> [bitcoin] jonasschnelli closed pull request #8908: Update bitcoin-qt.desktop (master...patch-4) https://github.com/bitcoin/bitcoin/pull/8908
12:21 < achow101> jonasschnelli: http://pastebin.com/TQ1Kr2P9
12:21 < achow101> I cut out all of the updatetip stuff
12:22 < jonasschnelli> achow101: did you use -connect=129.2.207.18:x?
12:23 < achow101> I used connect=172.16.220.1
12:23 < achow101> It's supposed to be vm to host
12:23 < michagogo> 22:18:48 <wumpus> is that the hack to get the PPA to install on debian instead of ubuntu? it made me scared
12:23 < michagogo> Wait, wait, what??
12:23 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev     
12:23 < MarcoFalke> michagogo:  https://github.com/bitcoin/bitcoin/pull/8965
12:24 < michagogo> Nobody should ever mix Ubuntu and Debian
12:24 < michagogo> That's a recipe for a broken system
12:24 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 256 seconds]     
12:24 < jonasschnelli> achow101: is the shutdown at the end intentional?
12:25 < achow101> yes. I shut it down so it wouldn't eat all my data
12:25 < 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
12:25 < wumpus> michagogo: comment that in the pull please
12:25 < jonasschnelli> achow101: It looks like that you have successfully connected to a bunch of nodes in 129.2.207.18
12:25 < michagogo> https://wiki.debian.org/DontBreakDebian
12:26 < BlueMatt> wumpus: yea, I just nacked that one
12:27 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev     
12:27 < achow101> jonasschnelli: that's probably because it's behind the vm nat. That ip address is mine
12:27 < achow101> but I only run one node
12:28 < jonasschnelli> achow101: A right. Confused! 129.2.207.18 is you node..
12:28 < jonasschnelli> maybe try -debug=net and post the debug.log again
12:28 < 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?
12:29 < wumpus> are you using connect= in your bitcoin.conf or -connect=?
12:29 < wumpus> the former will work, the second will not
12:29 < achow101> connect= in bitcoin.conf
12:29 < jonasschnelli> Should work in bitcoin.conf
12:29 < wumpus> is bitcoin.conf in the right place? does it get parsed at all?
12:29 < jonasschnelli> Doublecheck bitcoin.conf and -datadir (if passed in CLI)
12:29 < achow101> This is my conf: prune=550
12:29 < achow101> connect=172.16.220.1:8333
12:29 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 250 seconds]     
12:30 < jonasschnelli> what happens if you telnet 172.16.220.1 8333 (nat?)
12:30 < achow101> nevermind. it's a windows problem. It stuck a .txt at the end of the file name!
12:31 < michagogo> Hahaha
12:31 < 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
12:31 < jonasschnelli> heh     
12:31 < wumpus> lol okay
12:32 < michagogo> Yeah, first thing I do at any new Windows box/profile
12:32 < michagogo> Folder options -> untick "hide extensions for known file types"
12:32 < wumpus> windows's mysterius hidden extensions and hidden files
12:34 < 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
12:35 < 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
12:36 < 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
12:36 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]     
12:37 < GitHub4> [bitcoin] laanwj closed pull request #6996: Add preciousblock RPC (master...preciousblock) https://github.com/bitcoin/bitcoin/pull/6996
12:37 < GitHub199> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/df7519cbc1a9...7f71a3c59194
12:37 < GitHub199> bitcoin/master 5127c4f Pieter Wuille: Add preciousblock RPC...
12:37 < GitHub199> bitcoin/master 5805ac8 Pieter Wuille: Add preciousblock tests...
12:37 < GitHub199> bitcoin/master 7f71a3c Wladimir J. van der Laan: Merge #6996: Add preciousblock RPC...
12:37 < michagogo> Hm, I really hope I find the time to rewrite build-windows.md
12:37 < michagogo> It seems to tell you to install all the unix dependencies
12:37 < michagogo> Which is just wrong
12:38 < michagogo> Or at least, it can be read that way
12:38 < wumpus> it doesn't hurt, but yeah it's overkill
12:38 < wumpus> only the high-level arch-independent build stuff would be necessary, autoconf automake etc
12:39 < michagogo> I mean, molz in #bitcoin was installing all the actual deps, it seems
12:39 < GitHub123> [bitcoin] MarcoFalke closed pull request #8961: Headers announcement for nodes that can do headers. (master...AnnounceUsingHeaders) https://github.com/bitcoin/bitcoin/pull/8961
12:39 < michagogo> OpenSSL, BDB, etc etc
12:39 < michagogo> Which is completely unnecessary
12:40 < michagogo> When you really just need the actual tool chain skeleton
12:41 < wumpus> you don't need those for a depends build on unix either
12:42 < jonasschnelli> wumpus: the preciousblock RPC call needs probably mentioning in the 0.14 releasenots
12:42 < jonasschnelli> *notes
12:42 < wumpus> jonasschnelli: yes
12:42 < MarcoFalke> Yeah, down to 10 pulls
12:42 < MarcoFalke> in base 128
12:42 < jonasschnelli> maybe we should open a issue for RN 0.14
12:42 < wumpus> there's an issue for that IIRC
12:42 < michagogo> wumpus: right
12:42 < wumpus> https://github.com/bitcoin/bitcoin/issues/8455
12:43 < michagogo> But the docs don't talk about running a deps build for unix
12:43 < wumpus> michagogo: only the docs in depends do :(
12:43 < michagogo> Build-unix.md walks you through doing a build with system-deps
12:43 < wumpus> michagogo: it's split all over the place, not always over sensible lines
12:43 < michagogo> And build-windows points you at build-unix...
12:44 < wumpus> and build-unix points you at build-openbsd :-)
12:44 < michagogo> When you really just need to install git make pkg-config libtool autoconf g++ g++-mingw-w64-x86-64
12:44 < michagogo> Well, it does for openbsd
12:44 < michagogo> Windows points to unix unconditionally
12:44 < wumpus> I know, that one makes sense
12:45 < michagogo> When all you need is git make pkg-config libtool autoconf g++ g++-mingw-w64-x86-64
12:45 < michagogo> You don't even need all of build-essential
12:46 < 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
12:46 < wumpus> some of that is documented in depends/, but that's somewhat hidden away
12:47 < michagogo> OTOH, it's just a waste of space to install g++-mingw-w64 when g++-mingw-w64-x86-64 is enough
12:47 < michagogo> (The former basically pulls in the latter, plus -i686)
12:48 < michagogo> And I think some of the packages don't even come with build-essential, you need to install them individually anyway
12:49 < 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
12:50 < 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
12:50 < michagogo> Well, yeah
12:50 < michagogo> I'm hoping to overhaul build-windows on Thursday, if nobody else does it in the meantime
12:51 < michagogo> Also, maybe build-unix should be updated to present depends as an alternative to system deps
12:51 < 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 :)
13:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
13:04 < GitHub196> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7f71a3c59194...74dc388ab599
13:04 < GitHub196> bitcoin/master 18dacf9 Russell Yanofsky: Add microbenchmarks to profile more code paths....
13:04 < GitHub196> bitcoin/master 74dc388 Wladimir J. van der Laan: Merge #8873: Add microbenchmarks to profile more code paths....
13:04 < 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
13:07 < 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.
13:08 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 260 seconds]     
13:08 < wumpus> I'd prefer keeping around a bit of useless code to that
13:08 < wumpus> OTOH, it's not tested anyway, so if it is safe to remove (no risk of crashes) I'm fine with it
13:09 < wumpus> to be honest I think #8564 is a bit questionable, I'm not convinced it only removed code to do with ip transactions
13:09 < wumpus> #8546, sorry
13:10 < BlueMatt> ;;seen cfields_ 
13:10 < gribble> cfields_ was last seen in #bitcoin-core-dev 4 hours, 55 minutes, and 44 seconds ago: <cfields_> yes, that one's on purpose
13:10 < BlueMatt> ;;seen cfields
13:10 < 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
13:10 < wumpus> we may want to closeit and re-do it at some point, there's no urgency to it
13:10 < 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
13:10 < cfields_> BlueMatt: pong?
13:11 < BlueMatt> cfields_: busy with 13.1? or have you had a chance to review 8865?
13:11 < wumpus> Anduck: all of the apt package names are the same though
13:11 < cfields_> BlueMatt: beating my head against the wall with cgminer. I can take a break to review though.
13:11 < wumpus> unless people mess with software sources, ubuntu and debian can be regarded as having the same build instructions
13:12 < Anduck> what's the "right" way to obtain libdb4.8 (& libdb4.8++) for debian 8.0 jessie, binary or sources?
13:12 < wumpus> no need to duplicate things unnecesarily
13:12 < GitHub128> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/74dc388ab599...23e03f8d26d7
13:12 < GitHub128> bitcoin/master b55d823 anduck: Explicitly state that PPA is for Ubuntu only
13:12 < GitHub128> bitcoin/master 23e03f8 MarcoFalke: Merge #8965: Mention that PPA doesn't support Debian...
13:12 < wumpus> Anduck: build it from source as in the "berkeleydb" section
13:12 < GitHub54> [bitcoin] MarcoFalke closed pull request #8965: Mention that PPA doesn't support Debian (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8965
13:12 < 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...)
13:13 < Anduck> wumpus: it only builds libdb4.8 but libdb4.8++ is also required
13:13 < BlueMatt> cfields_: I'm happy to trade reviews, if it helps :p
13:13 < wumpus> Anduck: it builds both actually
13:13 < wumpus> Anduck: I've followed the instructions zillions of times, I'm sure it does the right thing
13:13 < Anduck> hmm... i tried it but it complained about libdb4.8++
13:13 < Anduck> alright
13:13 < cfields_> BlueMatt: ack. Will do in a little bit, once I get this test on auto-pilot
13:13 < wumpus> unless something broke anyhow
13:13 < wumpus> these days I don't use bdb 4.8 anymore tbh
13:14 < Anduck> are there any recent/known compatibility issues with newer ones?
13:14 < wumpus> yes, still the same as always
13:14 < Anduck> ok     
13:14 < wumpus> bdb 5 wallets won't work in 4.8, bdb 6 wallets won't work in 5 and 4.8
13:14 < Anduck> but it will work perfectly well otherwise?
13:16 < 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
13:16 < 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 :)
13:17 < wumpus> I can't guarantee anything about being safe to use, but I've never heard of any inherent issues
13:18 < wumpus> it's just that different versions' databases are binary incompatible, and if you don't know about that it can be confusing
13:18 < Anduck> alright. good to know
13:19 < wumpus> I guess it'd make sense to document that better
13:20 < Victorsueca> there, back to compiling.... again.....
13:20 < wumpus> but so much stuff to do
13:20 < Victorsueca> this time on a better computer, 16 GB ram
13:22 < Victorsueca> maybe it's an overkill but way we'll know if ram was the problem
13:24 < wumpus> 16GB is hardly overkill these days
13:24 < Victorsueca> if it's supposed to be enough with 1.5 or 2....
13:25 < wumpus> that's for the compiler. The other 14GB is for windows.
13:25 < Victorsueca> lol     
13:26 < Victorsueca> windows eats at most 4 GB, 2GB usually
13:26 < Victorsueca> which is still ridiculous....
13:28 < GitHub128> [bitcoin] laanwj closed pull request #8546: Remove IP transaction check (master...abc123) https://github.com/bitcoin/bitcoin/pull/8546
13:35 < wumpus> BlueMatt: so I guess you're blocked on 8865?
13:37 < 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
13:37 < BlueMatt> so i guess
13:37 < BlueMatt> yes     
13:38 < BlueMatt> wumpus: I also opened #8930 to get some eyes on verifying that orphan processing doesnt have to remain consistent with cs_main
13:38 < wumpus> let's get 8865 merged then
13:40 < wumpus> we kind of failed our goal in Milan to split up main.cpp
13:40 < BlueMatt> this is true, but segwit is more important
13:42 < michagogo> Anduck: honestly, the easiest thing, I think, is to just use the depends system
13:44 < wumpus> michagogo: it is - would be nice if there waa a way to use depends *just* for berkeleydb
13:44 < michagogo> Yeah
13:45 < Victorsueca> i think there is some way to use the system library for some dependency instead f the one specified in depends
13:45 < 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
13:45 < michagogo> I mean, can you just run bdb.mk? Or does that only work when called by the main makedile?
13:45 < wumpus> maybe it's possible
13:46 < michagogo> wumpus: can you not make depends NO_QT=1 and point configure at system qt?
13:46 < wumpus> yea, but that'd stlil pull in boost
13:46 < wumpus> it's currently not a practical way to build just berkeleydb
13:49 < GitHub161> [bitcoin] laanwj pushed 9 new commits to master: https://github.com/bitcoin/bitcoin/compare/23e03f8d26d7...05998da5a7e2
13:49 < GitHub161> bitcoin/master 87e7d72 Matt Corallo: Make validationinterface.UpdatedBlockTip more verbose...
13:49 < GitHub161> bitcoin/master 0278fb5 Matt Corallo: Remove duplicate nBlocksEstimate cmp (we already checked IsIBD())
13:49 < GitHub161> bitcoin/master aefcb7b Matt Corallo: Move net-processing logic definitions together in main.h
13:49 < BlueMatt> wut     
13:49 < 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
13:49 < BlueMatt> did you mean to do that?
13:49 < wumpus> yes     
13:50 < BlueMatt> ok!     
13:52 < wumpus> does make sense to do a bit of continuous integration tehre instead of leaving the pull open for months
13:52 < BlueMatt> true
13:53 < BlueMatt> alright, well I'll open up the next one in a sec when my fibre tests pass
13:53 < wumpus> awesome
14:00 < 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
14:08 -!- cdecker [~quassel@2a02:aa16:1105:4a80:6545:7bd0:62a0:613f] has quit [Ping timeout: 250 seconds]     
14:13 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]     
14:14 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has joined #bitcoin-core-dev     
14:15 -!- ibrightly [sid113387@gateway/web/irccloud.com/x-xnnwppeplcyizyex] has quit [Read error: Connection reset by peer]     
14:15 -!- ibrightly [sid113387@gateway/web/irccloud.com/x-feutkruesgcfdspv] has joined #bitcoin-core-dev     
14:29 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev     
14:33 -!- mkarrer_ [~mkarrer@7.red-83-47-85.dynamicip.rima-tde.net] has joined #bitcoin-core-dev     
14:35 < cfields_> BlueMatt: heh, I was reviewing it and it was merged under my feet :)
14:35 < BlueMatt> cfields_: its one of those things that can move forward but still needs posthumous acks
14:35 < BlueMatt> :p     
14:35 < cfields_> BlueMatt: fwiw, looks good to me though
14:35 < cfields_> heh     
14:36 < BlueMatt> posthumous acks are important :)
14:37 -!- mkarrer [~mkarrer@7.red-83-47-85.dynamicip.rima-tde.net] has quit [Ping timeout: 260 seconds]     
14:38 < BlueMatt> cfields_: at least the next ones are easy :)
14:38 < BlueMatt> probably only ~2 more incl 8969
14:39 < cfields_> BlueMatt: 8a4a33dc5623c8a5d1413c214f0dfa30667e6b03 is the one you showed in Milan, right?
14:39 < BlueMatt> yea, should be
14:39 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has joined #bitcoin-core-dev     
14:39 < BlueMatt> dont recall if ive rebased or not, but its def the same commit
14:40 < cfields_> ok good, thanks
14:40 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has quit [Max SendQ exceeded]     
14:41 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has joined #bitcoin-core-dev     
14:51 < 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.
14:55 -!- MarcoFalke [~marco@5.199.182.203] has left #bitcoin-core-dev []     
14:56 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]     
15:23 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
15:52 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 256 seconds]     
15:54 -!- wasi_ [~wasi@25.22.3.213.static.wline.lns.sme.cust.swisscom.ch] has joined #bitcoin-core-dev     
15:55 -!- wasi_ [~wasi@25.22.3.213.static.wline.lns.sme.cust.swisscom.ch] has quit [Read error: Connection reset by peer]     
16:16 < sipa> luke-jr: what is missing for x32?
16:16 < sipa> or was
16:16 < luke-jr> sipa: mostly LLVM and Valgrind IIRC
16:16 < sipa> i guess many things are harder if you don't use a common architecture
16:28 -!- murch [~murch@p4FE388E7.dip0.t-ipconnect.de] has quit [Remote host closed the connection]     
16:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
16:37 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.4]     
16:43 -!- wasi_ [~wasi@25.22.3.213.static.wline.lns.sme.cust.swisscom.ch] has joined #bitcoin-core-dev     
16:43 -!- wasi_ [~wasi@25.22.3.213.static.wline.lns.sme.cust.swisscom.ch] has left #bitcoin-core-dev []     
16:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
16:53 -!- alpalp [~allen@2605:6000:f4d6:d600::3] has joined #bitcoin-core-dev     
16:53 -!- alpalp [~allen@2605:6000:f4d6:d600::3] has quit [Changing host]     
16:53 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev     
17:15 < aj> question: re: https://bitcoincore.org/en/2016/01/26/segwit-benefits/#compact-fraud-proofs -- as it turns out, that didn't make it in, right? those will need an additional merkle tree with an additional coinbase commitment with segwit as implemented, just as they would without segwit, yes/no?
17:15 < gmaxwell> aj: right, or get picked up as part of some other addition that needs an additional commitment.
17:17 < gmaxwell> it can be done with 'external commitments' in the same manner as the proposed commited bloom filters... meaning that it's possible to implement the whole software stack, but not get a commitment from the blockchain for it (instead get it from semitrusted servers or what not).. probably a good way to go to work out the design.
17:19 -!- achow101 [~achow101@unaffiliated/achow101] has joined #bitcoin-core-dev     
17:19 < gmaxwell> aj: why do you ask?
17:24 < aj> gmaxwell: have been pondering a companion segwit-costs/risks page, and when reviewing the benefits page thought that one seemed mistaken now
17:26 < gmaxwell> yea, it's out of date, when god knows who announced segwit would be done in design and implemenation complete in April it just didn't give any time to finalize a design... and better to have fewer commitments than commitments you regret. :)
17:27 < gmaxwell> they same deployment approach could be used though, so basically a straightforward extension.
17:30 < GitHub75> [bitcoin] rebroad closed pull request #8958: Improve logic for advertising blocks (master...BetterBroadcastLogic) https://github.com/bitcoin/bitcoin/pull/8958
17:30 < GitHub120> [bitcoin] rebroad reopened pull request #8958: Improve logic for advertising blocks (master...BetterBroadcastLogic) https://github.com/bitcoin/bitcoin/pull/8958
17:31 < aj> yeah. i thought i remembered some other feature being mentioned that was implemented but wasn't in that list too. not coming to mind immediately though
17:32 < gmaxwell> I don't think there was anything else.
17:33 < gmaxwell> maybe the fact that pruned nodes could skip downloading stuff they wouldn't vakidate or keep?  thats stull true though, commitment structure wise.
17:33 < gmaxwell> maybe you were thinking of the n^2 sighash fix--- for a while that was implemented in the commitment structure but core wasn't making use of it to reduce the hashing, it does now.. however.
17:45 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
17:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Disconnected by services]     
17:46 -!- Victor_sueca is now known as Victorsueca     
17:48 -!- testnet [~testnet@25.22.3.213.static.wline.lns.sme.cust.swisscom.ch] has joined #bitcoin-core-dev     
17:48 < aj> gmaxwell: ah, my irc logs remind me that it was the fix for the "sighash single bug" -- but i'm not entirely sure what that bug is precisely
17:50 < gmaxwell> oh? I don't really consider that much of a bug, it's just a surprising feature. It has some vaguely constructive uses, in theory.
17:52 < aj> gmaxwell: i think it's that "if you use SIGHASH_SINGLE on an input with a higher index in a transaction than the number of outputs, then that signature can be used by anyone to spend any UTXO sent to that address", but post segwit it can only spend that particular coin?
17:56 < gmaxwell> aj: thats not incorrect. 
17:56 < aj> haha, high praise
17:58 < gmaxwell> for non SW txn an out of bound single causes to to sign the 32 byte value 1. For SW it just causes you to sign no particular outputs for that input.
17:58 < gmaxwell> but you still sign the prevouts.
18:04 < Victorsueca> gmaxwell: the how is it prevented that somebody changes the outputs?
18:04 < Victorsueca> then*
18:07 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wvfgqykannazwbwu] has quit [Quit: Connection closed for inactivity]     
18:11  * Victorsueca wonders if he just asked the whole point of segwit and should read the docs instead
18:14 < gmaxwell> Victorsueca: it's sighash single-- you're specifically flagging the signature so people can change outputs.
18:38 -!- fengling [~fengling@223.223.187.136] has joined #bitcoin-core-dev     
18:53 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
19:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
19:06 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has joined #bitcoin-core-dev     
19:10 < Victorsueca> OMG     
19:11 < Victorsueca> A wild bitcoin-qt.exe appeared
19:11 -!- whphhg [~whphhg@unaffiliated/whphhg] has quit [Ping timeout: 256 seconds]     
19:11 < Victorsueca> it's finally compiled
19:13 -!- whphhg [~whphhg@unaffiliated/whphhg] has joined #bitcoin-core-dev     
19:14 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has quit [Ping timeout: 260 seconds]     
19:14 -!- DigiByteDev [~JT2@69.167.28.1] has joined #bitcoin-core-dev     
19:14 -!- DigiByteDev [~JT2@69.167.28.1] has quit [Client Quit]     
19:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
19:36 -!- ill [~ill@108.114.226.118] has joined #bitcoin-core-dev     
19:43 -!- jtimon [~quassel@211.28.134.37.dynamic.jazztel.es] has quit [Ping timeout: 265 seconds]     
19:43 -!- bluerazor [~bluerazor@221.176.33.135] has joined #bitcoin-core-dev     
19:43 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Quit: WeeChat 0.4.2]     
19:50 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 256 seconds]     
19:57 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]     
19:58 -!- ill [~ill@108.114.226.118] has quit [Ping timeout: 260 seconds]     
19:58 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev     
19:59 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
20:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds]     
20:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
20:05 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds]     
20:32 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]     
20:33 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev     
20:44 -!- testnet [~testnet@25.22.3.213.static.wline.lns.sme.cust.swisscom.ch] has quit [Ping timeout: 252 seconds]     
21:03 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]     
21:04 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev     
21:07 -!- JackH [~laptop@79-73-190-13.dynamic.dsl.as9105.com] has quit [Ping timeout: 260 seconds]     
21:17 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Quit: bye]     
21:28 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]     
21:28 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.]     
21:29 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev     
21:39 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]     
21:40 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev     
21:49 < tulip> neat, I now have 11 peers with NODE_WITNESS (but all inbound, less than ideal). 
21:54 < gmaxwell> 4 on my bog standard host, all inbound.
21:54 < tulip> that was on my bog standard host, too.
21:55 < luke-jr> there's probably significantly fewer peers that they'll be willing to connect to
21:56 < tulip> restarted the patched node and it managed 7/8 outbound peers as segwit, ha.
21:57 < luke-jr> I thought it won't tolerate non-witness outbound peers at all?
21:58 < tulip> in r1 you can end up with no NODE_WITNESS peers. 
21:59 < tulip> with #8949 you will continuously search until at least 4 as NODE_WITNESS. 
22:01 < gmaxwell> luke-jr: no, it makes 40 requests to addrman, and if it doesn't get any node_witness results, it gives up and uses a non-nodewitness one.
22:02 < luke-jr> hm     
22:02 < gmaxwell> it turns out on mainnet there are so many non-nodewitness peers and such.. that it's pretty easy for it to get no node witness outbound peers at all, thus my PR.
22:05 -!- bluerazor [~bluerazor@221.176.33.135] has quit [Remote host closed the connection]     
22:06 -!- bluerazor [~bluerazor@221.176.33.135] has joined #bitcoin-core-dev     
22:18 < luke-jr> what are things coming to, when we can't even find a witness peer anymore? :<
22:19 < luke-jr> oh wait, that comment was meant for 2026, but this is 2016
22:20 < jl2012> why 0.13.1rc1 binary is not yet released?
22:21 < jl2012> aj: re SIGHASH_SINGLE: yes, BIP143 sort of fixed the bug
22:22 < jl2012> or removed the unintentional "feature" of making a replay-able signature
22:27 < gmaxwell> jl2012: in the past when we've encountered issues that would call for an RC2 before we shipped the RC1 binary we've sometimes just skipped it. I'm not sure if wumpus is planning on doing that.
22:35 < btcdrak> jl2012: we are skippng RC1 because of the non version bump iirc
22:37 < jl2012> btcdrak: it should be announced earlier so people won't waste time on building.....
22:39 < gmaxwell> good practice? (sorry)
22:40 -!- bluerazor [~bluerazor@221.176.33.135] has quit [Ping timeout: 260 seconds]     
22:50 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has joined #bitcoin-core-dev     
22:51 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has joined #bitcoin-core-dev     
22:55 -!- d_t [~textual@83-244-233-135.cust-83.exponential-e.net] has quit [Ping timeout: 250 seconds]     
23:10 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 252 seconds]     
23:10 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]     
23:10 -!- DigiByteDev [~JT2@n218250011174.netvigator.com] has quit [Quit: DigiByteDev]     
23:11 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev     
23:11 -!- bluerazo_ [~bluerazor@221.176.33.135] has joined #bitcoin-core-dev     
23:13 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev     
23:33 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit []     
23:47 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
23:59 -!- AtashiCon [arnavion@unaffiliated/arnavion] has quit [Quit: AtashiCon]