Quote from: pereira4 on July 07, 2015, 09:01:20 PM

Quote from: SebastianJu on July 07, 2015, 12:00:27 PM

Quote from: turvarya on July 07, 2015, 11:13:06 AM

Quote from: Amitabh S on July 07, 2015, 10:57:20 AM

Quote from: turvarya on July 07, 2015, 10:16:21 AM

Quote from: Bonio on July 07, 2015, 10:00:33 AM

Why is this taking so long to resolve?

Surely it is in the mining pools interest to fall into line? Or is there something more sinister going on?

Re stress testing I suppose it needs to be done isnt bitcoin still classed as beta or am I missing the point?

It actually was resolved pretty fast. (6 blocks ~ 1h)

I guess the news at the top of the forum, is just a reminder that you should update your client.
Theoretically this could happen again(I highlty doubt it, since pools/miners already lost money) and the only prevention is to use a up-to-date client(or connect to an up-to-date node)

It is clearly not resolved. Look at the forum header and you will see. Things are not "back to normal" if you have to wait for ~30 confirmation on many clients. This is ongoing as of now until the above warning is removed.

Sorry, for the misinformation. Seems like there was another split according to: https://bitcoin.org/en/alert/2015-07-04-spv-mining
So, miners are stupid enough to still lose money. Sorry, I assumed, they were smarter.

So this happened twice now in a row? Oo

When what is said is correct in this thread then couldnt that be used to attack bitcoin and lower the price of bitcoin? I mean presenting wrong hashes to these pools and letting them create a fork? I guess there is some failsaife built in as to which pools they watch but most probably they watch small ones too and someone could decide that he could earn some coins by shorting them with leverage and then starting the next fork?

Further proof that we aren't ready for mass adoption. Glad I always stuck with Core, but feel really bad for anyone affected by this. 30 confirmations is a ton of time. I hope no one lost money somehow with this if you can lose money in this situation (some transaction getting stuck or something, or being precessed into the other blockchain). This sounds pretty messy to me.

Still. Im impressed that happened 2 times in a couple days. And the first time on the worldwide known independence day in america? Im not into conspiracy theories but the randomness is interesting at least. Nothing for years and then, at this day. Oo