< andytoshi> whew, 1000 bt2 buy wall at 0.25
< andytoshi> oops, wrong channel, sorry
< midnightmagic> Could I request that whoever is in charge of updating bitcoin.org and bitcoincore.org put up statements that I can point to when complaining to Twitter about impersonating accounts? Do these statements already exist?
< meshcollider> Yeah surely there's something we can do about this ... :(
< achow101> midnightmagic: what kind of statements?
< achow101> is the second bullet of https://bitcoincore.org/en/2017/08/18/btc1-misleading-statements/ enough?
< midnightmagic> achow101: Probably getting the blue checkmark at this point would probably be a good idea, if it's at all possible.
< achow101> midnightmagic: yeah.. what's the process for that?
< midnightmagic> Not a clue, I've never gotten a blue checkmark. https://support.twitter.com/articles/20174631 ?
< achow101> Whoever controls the bitcoincoreorg account is going to need to do that. I guess that's probably btcdrak
< midnightmagic> :-/
< jonasschnelli> BlueMatt: is removing the 40attempts-use-also-peers-with-missing-relevant-services unproblematic? https://github.com/bitcoin/bitcoin/pull/11456/files#diff-9a82240fe7dfe86564178691cc57f2f1L1829
< jonasschnelli> I guess you hardly find a useful peer with that logic...
< gmaxwell> justanotheruser: peers without witness are not longer outbound useful at all.
< gmaxwell> er jonasschnelli
< gmaxwell> we'll never fetch blocks from them anymore.
< bitcoin-git> [bitcoin] fanquake opened pull request #11460: [depends] mac_alias 2.0.6, ds_store 1.1.2 (master...update-mac-alias) https://github.com/bitcoin/bitcoin/pull/11460
< sipa> gmaxwell: but with NODE_LIMITED we may still try to connect to a limited node if no NETWORK nodes are available (and we need history)
< jonasschnelli> sipa: but the current NODE_NETWORK implementation has this finger-printing prevention and will never serve <288...
< jonasschnelli> (as also recommended by the BIP)
< sipa> jonasschnelli: ?
< sipa> jonasschnelli: oh, you mean LIMITED will not serve further back, sure
< sipa> but connecting to a LIMITED is still far better than not connecting to anything at all
< sipa> at the very least to learn about more peer
< fanquake> Hey cfields, could you ping me if your online sometime this arvo
< gmaxwell> sipa: perhaps but the mechenism we used for segwit might not really be the best one for that.
< MarcoFalke> Seems we can create issues and tag them with "hacktoberfest" to get other people fix it... :3
< MarcoFalke> https://github.com/search?q=label:hacktoberfest+state:open+type:issue
< MarcoFalke> Just created one to see what happens.
< fanquake> Do we have to give away free shirts
< MarcoFalke> Not that I am aware of
< fanquake> MarcoFalke was just being sarcastic :p
< MarcoFalke> heh, there might be some leftover shirts from sf to give away
< gmaxwell> BlueMatt: this is a ppa user:
< gmaxwell> 02:06:47 < someone235> Hi, after installing bitcoin-qt on Ubuntu 16.04 I get this error: "bitcoin-qt: error while loading shared libraries: libzmq.so.3: cannot open shared object file: No such file or directory". Someone knows how to fix it?
< meshcollider> MarcoFalke: I'm a poor student, I'll claim one if there is ;)
< meshcollider> gmaxwell: that sounds like a dependency issue, I'm not 100% sure but you could try `apt-get purge libzmq3` and then reinstall
< Sentineo> gmaxwell: libzmq was not in ppa before iirc, could it be that the dependency was left out of the package?
< MarcoFalke> A fresh install works fine with the dependencies: "Selecting previously unselected package libzmq5:amd64."
< BlueMatt> gmaxwell: strange...ppa magics deps, dunno how they got the package to install without its dep
< Bullpay> anyone care to help me out with a small issue? 2017-10-07T21:15:28.711Z] info: Header Service: we have not received a response to getHeaders from the network, retrying.
< Bullpay> [2017-10-07T21:15:14.699Z] info: Connected to peer:, network: livenet, version: 70015, subversion: /Satoshi:0.15.99/, status: ready, port: 8333, best height: 288324
< Bullpay> bitcore-node keeps saying it cant get a response / retrying any ideas why?
< Bullpay> this is a p2p setup bitcore-node over bitcoind
< Bullpay> or if there is anyone here that can get me an insightAPI/UI system up and running over bitcoind full node I will pay you in BTC!
< meshcollider> Bullpay: not the right channel sorry, try #bitcoin or the bitcoin stackexchange?
< Bullpay> opps you are right
< meshcollider> BlueMatt: maybe it had already been installed or thought it had because of something else, but the install was broken