Gold collapsing. Bitcoin UP.

[cypherdoc]

ok, finally achieved smackdown by resorting to the SW math. the time i've spent studying & understanding SW has paid huge dividends:

 

[solex]

A good illustration of why expending energy on /r/bitcoin is so frustrating

Massive parts of the thread deleted
https://unreddit.com/r/Bitcoin/comments/37vg8y/is_the_blockstream_company_the_reason_why_4_core/crqcg3f

 

[rocks]

I had a recent reddit conversation with Adam about that tweet where he said that he has not changed his mind on the 2MB HF, but claimed SF segwit is "safer" & "quicker"

Well both the SW and 2MB options are out in the market now and they can compete for adoption based on user preferences.

What Adam seems to not understand is he can not dictate user preferences or coerce/force them to be what he wants. The market will choose what the market wants the right path to be. If Bitcoin works the way we think it should, no amount of FUD, censorship, VC money, etc can force the market to take a different path, it may delay it but that is all.

 

[sickpig]

No easy fixes.

• Patch the source code to glibc and recompile is the most straightforward (easiest if your Linux distribution is source-based)
  
• Disable DNS resolution entirely.
• Wait for your Linux distribution to provide an update

Debian and ubuntu have already released an updated version of the libc6 package to fix the problem:

eglibc (2.19-0ubuntu6.7) trusty-security; urgency=medium

* SECURITY UPDATE: glibc getaddrinfo stack-based buffer overflow
- debian/patches/any/CVE-2015-7547-pre1.diff: fix memory leak in
resolv/nss_dns/dns-host.c.
- debian/patches/any/CVE-2015-7547-pre2.diff: fix memory leak in
include/resolv.h, resolv/gethnamaddr.c, resolv/nss_dns/dns-canon.c,
resolv/nss_dns/dns-host.c, resolv/nss_dns/dns-network.c,
resolv/res_query.c, resolv/res_send.c.
- debian/patches/any/CVE-2015-7547.diff: fix buffer handling in
resolv/nss_dns/dns-host.c, resolv/res_query.c, resolv/res_send.c.
- CVE-2015-7547

so just apt-get update && apt-get upgrade and you will be safe from this particular security problem.

 

[Norway]

Classic friendly Antpool is taking a dive in hashrate. I don't like this development.
https://blockchain.info/pools?timespan=24hrs

 

[bluemoon]

@Norway: I've noticed the hashrate shares vary a lot over fairly short time periods. Last Thursday F2Pool had a 38% share over 24 hours: https://bitco.in/forum/threads/gold-collapsing-bitcoin-up.16/page-327#post-11804

Why this happens I don't know, but I guess short term variation is nothing to worry about.

 

[cypherdoc]

Classic friendly Antpool is taking a dive in hashrate. I don't like this development.
https://blockchain.info/pools?timespan=24hrs

Back to normal

 

[Zarathustra]

Bitcoin up - Altcoin market cap down with the first Antpool Classic block mined.

 

[cypherdoc]

Debian and ubuntu have already released an updated version of the libc6 package to fix the problem:



so just apt-get update && apt-get upgrade and you will be safe from this particular security problem.

Do we need a sudo reboot?

 

[sickpig]

@cypherdoc

not necessary.

just restart your bitcoind and any services exposed to the internet.

 

[cypherdoc]

Bitcoin up - Altcoin market cap down with the first Antpool Classic block mined.

[doublepost=1455707497][/doublepost]Thank you Tim Cook

https://www.apple.com/customer-letter/

 

[sgbett]

Do we need a sudo reboot?

I run my nodes in an opsworks stack. Only the blockchain is on persistent storage. I restart them and they automatically rebuild the entire OS with latest updates and download and compile bitcoin.

Any other suckers with money to burn https://github.com/sgbett/cryptonet-opsworks

 

[freetrader]

https://www.reddit.com/r/btc/comments/467oat/sudden_appearance_of_bitcoinj_nodes/

It's high time to patch any of your machines that might be vulnerable to the recent libc bug.

I noticed the strange dip across Core+Classic nodes on http://nodecounter.com/#nodes_1mb_vs_2mb myself, and also had those bitcoinj nodes connecting to me (fortunately after I had already patched).

 

[Justus Ranvier]

@cypherdoc

not necessary.

Technically true, but a machine reboot after as glibc update is the safest way to make sure you didn't miss something.

 

[sickpig]

it seems that Eligius is still performing validation less (*) mining:

(*) as long as they at least check block version validation less mining is not bad per se.

 

[Richy_T]

@Norway: I've noticed the hashrate shares vary a lot over fairly short time periods. Last Thursday F2Pool had a 38% share over 24 hours: https://bitco.in/forum/threads/gold-collapsing-bitcoin-up.16/page-327#post-11804

Why this happens I don't know, but I guess short term variation is nothing to worry about.

Displayed Hashrate is calculated based on blocks found, not measured directly. Blocks found is random with statistical variance.

 

[theZerg]

You might remember that we had a bit of a pop in the BTC price when BU became a thing. We were joking about it; I didn't take the possible causality seriously. But now we have another pop for classic... this market wants to rise but is being restrained by worries that Bitcoin will be hamstrung by the Core client.

 

[Inca]

@theZerg: i agree.

Anyone else sickened by how artificial the markets are? Last week there were no buyers and suddenly the FTSE is being heavily bought back up to a 6 handle. Transparent action by the central banks who in attempting to reel in this hyper credit cycle have now become the very problem which is preventing makets from fair and true pricing. We have exchanged private banks rigging the markets for central banks doing the same with legal impunity.

 

[cypherdoc]

You might remember that we had a bit of a pop in the BTC price when BU became a thing. We were joking about it; I didn't take the possible causality seriously. But now we have another pop for classic... this market wants to rise but is being restrained by worries that Bitcoin will be hamstrung by the Core client.

there's been 3 pops since the bottom. yours, @Peter R's, and now Classic's.

it IS telling.

 

[theZerg]

after all my work, I should've grabbed some leverage...