--- Log opened Sat Feb 23 00:00:58 2019
00:02 -!- Karyon [~karyon@unaffiliated/karyon] has quit [Quit: Leaving]
00:12 -!- mildly_risky [~~mildly_r@n1164984127.netvigator.com] has quit [Read error: Connection reset by peer]
00:14 < wumpus> helllo
00:23 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
00:41 -!- IZooo [~IzZzoOo@78.192.31.65] has quit [Ping timeout: 250 seconds]
00:44 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
00:46 < promag_> fanquake: hi, need something?
00:58 < warren> https://github.com/bitcoin/bitcoin/pull/15277 Hoping people can help with what is hopefully a simple environment difference between Ubuntu and this other distro. dongcarl is really close to a deterministic replacement for gitian's toolchain. It may only be a matter of figuring out this linker issue then writing a wrapper around the entire thing.
01:05 < luke-jr> warren: FWIW, our current binaries aren't actually portable, so I'm not sure how important a 1:1 match on linkage is
01:06 < luke-jr> (I can't run the ones gitian makes)
01:08 < warren> luke-jr: oh did you report the issue? what distro are you running on?
01:08 < luke-jr> Gentoo, IIRC someone reported it years ago
01:08 < luke-jr> https://github.com/bitcoin/bitcoin/issues/6628
01:08 < warren> are you still using that oddball x32 arch?
01:08 < luke-jr> no, never migrated to it, only had it in a chroot for testing (and since gave up on it and deleted)
01:09 < luke-jr> I'm pretty sure it's something to blame Gentoo for, but who knows
01:09 < warren> I'm guessing this isn't more widespread?
01:10 < luke-jr> the glibc ebuild seems to carry some weird patch touching __chk_fail stuff
01:10 < luke-jr> dunno
01:10 < warren> We should be more concerned about the reason why we've wanted a deterministic toolchain to replace gitian.
01:12 < fanquake> promag_ a few thoughts/questions about 15204, but might just put them into the PR
01:12 < promag_> #15204
01:12 < gribble> https://github.com/bitcoin/bitcoin/issues/15204 | gui: Add Open External Wallet action by promag · Pull Request #15204 · bitcoin/bitcoin · GitHub
01:13 < promag_> go ahead
01:20 < fanquake> promag_ One is wether we should just be creating a new "wallet" in any directory selected from that menu.
01:20 < fanquake> It's not exactly obvious that's what will happen (or if it should be the default behaviour), rather than a "No wallet to load popup/error".
01:20 < promag_> it should not create
01:21 < fanquake> Right. At the moment I can select any directory on the system, wallet directory or not, and if it's not, it's turned into one. 
01:21 < promag_> later create wallet can have a "select other destination" or something
01:21 < promag_> yeah I know
01:22 < promag_> I want to be able to just open, not createOrOpen
01:23 < fanquake> Yea, that would be the preferred behaviour
01:28 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 258 seconds]
01:37 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
01:46 < wumpus> luke-jr: it's also not portable to systems that don't use glibc at all-in my experience the gitian-produced executables work on a wide range of systems in the wild, but undoubtly there's always a limit to portability
01:47 < wumpus> and we all know that full static linking has its own slew of issues 
01:49 < wumpus> the modern way of shipping portable applications for linux are these universal package things such as snap, flatpak, appimage
01:51 < wumpus> it prevents issues from the variance in possible environments by running in a predictable environment with predictable versions of libc and other libraries
02:09 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
02:09 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
02:22 < gmaxwell> IIRC years ago I tried using bitcoind on a uclibc system (or musl?) but I think I couldn't get boost working.
02:23 < luke-jr> I think at least musl has improved a lot since then
02:24 < promag> gmaxwell: https://github.com/ruimarinho/docker-bitcoin-core/blob/master/0.17/alpine/Dockerfile
02:24 < promag> alpine uses musl iirc
02:30 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
02:31 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:45 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
02:47 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
03:13 -!- IZooo [~IzZzoOo@78.192.31.65] has joined #bitcoin-core-dev
03:26 -!- zhangzf [~zhangzf@223.72.85.106] has joined #bitcoin-core-dev
03:45 -!- commavir_ is now known as commavir
04:04 -!- booyah_ is now known as booyah
04:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:07 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:11 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
04:17 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
04:22 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 256 seconds]
04:24 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev
04:39 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
04:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:42 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:43 -!- Aaronvan_ is now known as AaronvanW_
04:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
05:03 -!- IZooo [~IzZzoOo@78.192.31.65] has quit [Ping timeout: 245 seconds]
05:08 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
05:11 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
05:11 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
05:16 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:31 -!- AaronvanW_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]
05:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
05:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
06:29 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
06:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
06:39 -!- volkov [~volkov@gateway/tor-sasl/volkov] has joined #bitcoin-core-dev
06:49 -!- volkov [~volkov@gateway/tor-sasl/volkov] has quit [Quit: volkov]
06:50 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
06:52 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
06:59 -!- profmac [~ProfMac@2001:470:1f0f:226:cd9c:c140:342b:7ce5] has quit [Ping timeout: 250 seconds]
07:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 255 seconds]
07:09 -!- Karyon [~karyon@unaffiliated/karyon] has joined #bitcoin-core-dev
07:10 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
07:11 -!- IZooo [~IzZzoOo@78.192.31.65] has joined #bitcoin-core-dev
07:23 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
07:25 -!- zhangzf [~zhangzf@223.72.85.106] has quit [Remote host closed the connection]
07:32 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
07:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:46 < bitcoin-git> [bitcoin] ken2812221 opened pull request #15468: wallet: Use fsbridge::ifstream to fix Windows path issue (master...win-wallet-fix) https://github.com/bitcoin/bitcoin/pull/15468
07:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:21 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has quit [Remote host closed the connection]
08:22 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
08:23 -!- kelemen [b00c6b84@gateway/web/freenode/ip.176.12.107.132] has joined #bitcoin-core-dev
08:24 -!- kelemen [b00c6b84@gateway/web/freenode/ip.176.12.107.132] has left #bitcoin-core-dev []
08:24 -!- kelemen [b00c6b84@gateway/web/freenode/ip.176.12.107.132] has joined #bitcoin-core-dev
08:30 -!- kelemen [b00c6b84@gateway/web/freenode/ip.176.12.107.132] has quit [Quit: Page closed]
08:47 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
08:53 -!- qubenix [~qubenix@66.172.11.228] has quit [Ping timeout: 244 seconds]
08:53 -!- OneFive [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev
09:14 -!- IZooo [~IzZzoOo@78.192.31.65] has quit [Read error: Connection reset by peer]
09:20 -!- Karyon_ [~karyon@unaffiliated/karyon] has joined #bitcoin-core-dev
09:23 -!- Karyon [~karyon@unaffiliated/karyon] has quit [Ping timeout: 250 seconds]
09:23 -!- profmac [~ProfMac@2001:470:1f0f:226:a5b8:640b:1339:ee57] has joined #bitcoin-core-dev
10:02 -!- Karyon_ is now known as Karyon
10:26 -!- JackH_ [~laptop@host81-155-233-158.range81-155.btcentralplus.com] has joined #bitcoin-core-dev
10:28 -!- JackH [~laptop@host86-134-40-210.range86-134.btcentralplus.com] has quit [Ping timeout: 250 seconds]
10:50 -!- mn9495881 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
10:52 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
11:13 -!- mischa010 [4dadf2fe@gateway/web/freenode/ip.77.173.242.254] has joined #bitcoin-core-dev
11:14 < mischa010> hi, im trying to understand how peers are ranked, for example, do peers that take less time to transmit things get priority somehow? what's the relevant bit of code?
11:15 < mischa010> gmaxwell? :)
11:15 < gmaxwell> priority for what?
11:15 < mischa010> sending an inv for example
11:16 < mischa010> or getting headers
11:16 < mischa010> what determines which peer gets one first
11:16 < gmaxwell> transaction invs are batched and are done at totally random times... the only real priority there is that the random times are more frequent for outbound peers.
11:17 < mischa010> why is it random instead of immediately?
11:17 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 240 seconds]
11:17 -!- Karyon_ [~karyon@unaffiliated/karyon] has joined #bitcoin-core-dev
11:17 < gmaxwell> because immediately would be toxic for privacy and would waste more bandwidth from INVs crossing in flight (so two peers would INV each other the same txn, which happens quite rarely now)
11:19 < mischa010> interesting
11:19 -!- Karyon [~karyon@unaffiliated/karyon] has quit [Ping timeout: 264 seconds]
11:22 < sipa> mischa010: the delay is in the order of a few seconds usually
11:23 < mischa010> and blocks? those aren't delayed right?
11:24 < sipa> indeed
11:24 < mischa010> but there'
11:24 < sipa> they're relayed as fast as possible
11:24 < mischa010> but there's no peer priority/ranking in relaying blocks? so it's possible a block is relayed to a slow peer instead of the n fastest ones?
11:25 < sipa> usually blocks are relayed using compact blocks, which are just a few kb
11:25 < sipa> which is too little to cause much contention on most uplinks
11:29 < mischa010> but outbound nodes have priority in some cases right?
11:30 < mischa010> there's a comment in net_processing.cpp about 'nice' peers
11:32 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
11:38 -!- qubenix [~qubenix@66.172.11.228] has joined #bitcoin-core-dev
11:43 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit]
11:48 -!- qubenix [~qubenix@66.172.11.228] has joined #bitcoin-core-dev
11:52 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has quit [Quit: Leaving]
11:55 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
11:59 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
12:10 -!- Karyon_ [~karyon@unaffiliated/karyon] has quit [Quit: Leaving]
12:11 -!- Soligor [~soligor@unaffiliated/soligor] has joined #bitcoin-core-dev
12:17 -!- irc_viewer_test [irc_viewer@gateway/vpn/privateinternetaccess/ircviewertest/x-06412631] has joined #bitcoin-core-dev
12:18 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Remote host closed the connection]
12:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
12:26 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
12:28 -!- LeMiner [~LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev
12:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
12:35 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
12:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 272 seconds]
12:38 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
12:41 -!- irc_viewer_test [irc_viewer@gateway/vpn/privateinternetaccess/ircviewertest/x-06412631] has quit [Quit: irc_viewer_test]
12:45 -!- LeMiner [~LeMiner@unaffiliated/leminer] has quit [Read error: Connection reset by peer]
12:45 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev
12:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 245 seconds]
13:04 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
13:07 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
13:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
13:16 -!- Karyon_ [~karyon@unaffiliated/karyon] has joined #bitcoin-core-dev
13:33 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
13:44 -!- fabianfabian [~fabianfab@D9656CCE.cm-27.dynamic.ziggo.nl] has joined #bitcoin-core-dev
13:45 -!- Karyon_ [~karyon@unaffiliated/karyon] has quit [Quit: Leaving]
13:50 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
13:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
13:58 < mischa010> in this thread it's claimed that compact blocks does indeed rank peers by their speed? https://www.reddit.com/r/Bitcoin/comments/5zo2ku/how_do_i_configure_my_node_to_use_highbandwidth/
13:58 < mischa010> is this true>
13:58 < mischa010> ?
14:01 < sipa> every node picks 3 peers which it asks to send compact blocks directly, instead of having them first announce the block
14:02 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:06 -!- Karyon [~Karyon@unaffiliated/karyon] has joined #bitcoin-core-dev
14:11 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
14:13 < captjakk> Does anyone know why I would be getting a "connection refused" when connecting my lnd to my remote bitcoind instance
14:13 < captjakk> to be clear, I'm talking about the zmq port
14:13 < captjakk> also zmq isn't refusing connections from localhost
14:13 < captjakk> ufw (ubuntu) has been set to allow the zmq ports as well
14:20 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 268 seconds]
14:25 -!- owowo [~ovovo@185.204.1.186] has joined #bitcoin-core-dev
14:25 -!- owowo [~ovovo@185.204.1.186] has quit [Changing host]
14:25 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
14:30 < captjakk> looks like my zmq interface was set only to 127.0.0.1
14:32 -!- captjakk_ [~captjakk@c-65-50-169-164.hs.gigamonster.net] has joined #bitcoin-core-dev
14:34 < echeveria> you really don’t want to bind ZMQ to anywhere but local host.
14:34 < echeveria> if anyone is telling you otherwise, they’re probably being insanely stupid.
14:35 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Ping timeout: 245 seconds]
14:51 < captjakk_> even if i want to subscribe to zmq updates from a different machine?
14:54 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:54 -!- skyikot [~skyikot@gateway/tor-sasl/skyikot] has joined #bitcoin-core-dev
14:56 < jimpo>  
15:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
15:01 < sipa>  
15:03 < echeveria> captjakk_: like, don’t.
15:03 < echeveria> it’s not authenticated. it’s not secure. it has a large attack surface. use a VPN if you have to.
15:03 < sipa> echeveria: within a local network it's fine
15:03 < sipa> but don't exoose it to the internet...
15:06 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds]
15:08 < gmaxwell> ZMQ also requires both end be running the same library version, so that also makes it not so attractive for things that aren't very tightly coupled.
15:09 -!- IGHOR [~quassel@93.178.216.72] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
15:09 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
15:10 < gmaxwell> mischa010: thats why I asked you to be specific earlier.
15:10 < gmaxwell> 11:14:57 < mischa010> hi, im trying to understand how peers are ranked, for 
15:10 < gmaxwell>                       example, do peers that take less time to transmit things 
15:10 < gmaxwell>                       get priority somehow? what's the relevant bit of code?
15:10 < gmaxwell> 11:15:20 < mischa010> gmaxwell? :)
15:10 < gmaxwell> 11:15:38 < gmaxwell> priority for what?
15:10 < gmaxwell> 11:15:46 < mischa010> sending an inv for example
15:10 < gmaxwell> INVs aren't used for relaying blocks except as a backwards compatible fallback.
15:11 < gmaxwell> Peers request the last three distinct peers to first provide them a block to request to compact blocks to them without first asking (alowing 0.5 RTT transmission in most cases).
15:12 < gmaxwell> when a block comes in, those requests are services first-- in partcular because they can be serviced prior to validation.
15:12 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev
15:13 < gmaxwell> The 'order' doesn't really matter (at least not much) because CB messages are very small (10kb or so), and transmission is non-blocking.
15:14 < gmaxwell> I tried before trying to sort sends by the nodes own CB preference, but I was unable to measure an improvement even in a pretty contrived setup, so it wasn't worth PRing.
15:31 -!- captjakk_ [~captjakk@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
15:32 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
15:33 -!- captjakk_ [~captjakk@c-65-50-169-164.hs.gigamonster.net] has joined #bitcoin-core-dev
15:36 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Ping timeout: 244 seconds]
15:41 -!- IGHOR [~quassel@93.178.216.72] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
15:50 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
15:52 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
15:54 -!- captjakk_ [~captjakk@c-65-50-169-164.hs.gigamonster.net] has quit [Remote host closed the connection]
15:55 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]
15:55 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev
16:01 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
16:03 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
16:10 -!- koop487 [b89935bc@gateway/web/freenode/ip.184.153.53.188] has joined #bitcoin-core-dev
16:11 -!- jimmysong_ [~jimmysong@72-48-253-51.dyn.grandenetworks.net] has quit [Read error: Connection reset by peer]
16:11 -!- jimmysong_ [~jimmysong@72-48-253-51.dyn.grandenetworks.net] has joined #bitcoin-core-dev
16:12 -!- koop487 [b89935bc@gateway/web/freenode/ip.184.153.53.188] has quit [Client Quit]
16:31 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
16:41 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 256 seconds]
16:54 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
16:55 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev
16:57 -!- captjakk_ [~captjakk@75-166-189-210.hlrn.qwest.net] has joined #bitcoin-core-dev
17:00 -!- captjakk_ [~captjakk@75-166-189-210.hlrn.qwest.net] has quit [Remote host closed the connection]
17:01 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Ping timeout: 245 seconds]
17:12 -!- koop487 [b89935bc@gateway/web/freenode/ip.184.153.53.188] has joined #bitcoin-core-dev
17:12 < koop487> hi guys
17:12 < koop487> anyone willing to help me with my firsts steps?
17:13 < koop487> i downloaded the repo, installed alle the dependencies, and run the make command
17:13 < koop487> i m reading the documentation but it is a little unclear what should i obtain from this repo >.<
17:13 < koop487> am i missimng any documentation?
17:15 < koop487> in other words, i made the compilation, how do i run it now, and what exactly am i running 
17:20 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
17:28 < mischa010> koop487: ./bitcoind i guess?
17:29 < koop487> didn't get it
17:29 < koop487> what s the question?
17:30 < koop487> if you were providing a command, i don't have any file with that name
17:30 < mischa010> then the compile failed, check for errors
17:31 < mischa010> gmaxwell, thanks
17:37 -!- zhangzf [~zhangzf@223.72.50.93] has joined #bitcoin-core-dev
17:40 < koop487> oh didn't even notice
17:40 < koop487> took so long i though everything went right
17:40 < koop487> thanks man
17:51 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 245 seconds]
18:04 -!- GoldHatCarls [42829386@gateway/web/freenode/ip.66.130.147.134] has joined #bitcoin-core-dev
18:06 -!- GoldHatCarls [42829386@gateway/web/freenode/ip.66.130.147.134] has quit [Client Quit]
18:26 -!- koop487 [b89935bc@gateway/web/freenode/ip.184.153.53.188] has quit [Quit: Page closed]
19:17 -!- bitbee [~bitbee@unaffiliated/cryptocat] has quit [Quit: Leaving.]
19:23 -!- bitbee [~bitbee@unaffiliated/cryptocat] has joined #bitcoin-core-dev
19:52 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
19:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
20:20 -!- gkrizek [~gkrizek@ip98-164-15-79.ks.ks.cox.net] has quit [Quit: gkrizek]
20:54 -!- v8c9X [~v8C16x3R@178.138.35.113] has quit [Read error: Connection reset by peer]
21:13 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
21:26 -!- skyikot [~skyikot@gateway/tor-sasl/skyikot] has quit [Remote host closed the connection]
21:29 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
21:30 -!- gkrizek [62a40f4f@gateway/web/freenode/ip.98.164.15.79] has joined #bitcoin-core-dev
21:35 -!- gkrizek [62a40f4f@gateway/web/freenode/ip.98.164.15.79] has quit [Ping timeout: 256 seconds]
21:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
21:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 245 seconds]
22:07 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Quit: ZNC 1.7.0+deb0+xenial1 - https://znc.in]
22:09 -!- achow101 [~achow101@unaffiliated/achow101] has joined #bitcoin-core-dev
22:15 -!- v8c9X [~v8C16x3R@178.138.35.113] has joined #bitcoin-core-dev
22:59 -!- TheHoliestRoger [~TheHolies@unaffiliated/theholiestroger] has quit [Quit: Find me in #TheHolyRoger or https://theholyroger.com]
23:02 -!- TheHoliestRoger [~TheHolies@unaffiliated/theholiestroger] has joined #bitcoin-core-dev
23:25 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 246 seconds]
23:26 -!- flowctrl [~flowctrl@S0106602ad07279e4.cn.shawcable.net] has joined #bitcoin-core-dev
23:29 < flowctrl> Hello! I downloaded a macos binary, bitcoin-0.17.1-osx.dmg, from bitcoin.org. In the image, there is a file that produces a 'permission denied' error message when I try to copy it to any location. The file is: /Volumes/Bitcoin-Core/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
23:30 < flowctrl> I'm using MacOS Mojave 10.14.3
23:31 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
23:31 < flowctrl> Does anyone have some advice? Is the QT library just incompatible with the latest osx?
23:41 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
23:47 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
23:58 < luke-jr> flowctrl: this is the development channel; try #bitcoin for support
23:58 < flowctrl> That's where I tried first; someone recommended I check here.
--- Log closed Sun Feb 24 00:00:58 2019