Quote from: BitcoinNewsMagazine on January 16, 2016, 08:42:47 PM

Quote from: Westin Landon Cox on January 16, 2016, 08:27:25 PM

Quote from: franky1 on January 16, 2016, 08:17:21 PM

Keccak is SHA3..
which will totally kill off ASICs of todays current design.. and would cause the system to take weeks to solve one block because the difficulty is soo high, by the time that 2016 blocks are solved (years) to then downgrade difficulty, would be too late...

Yes, it will kill off today's ASICS. But I disagree about the difficulty. Obviously the hardfork would not only change the PoW but initialize the difficulty to a reasonable value for that PoW.

The github pull request by luke-jr that everyone is concerned about was closed by jtoomin. No longer a concern your ASICS are safe. luke-jr seems to be a bit of a loose cannon:) As I read the repositories they are trying to make the implementation as simple as possible with just a 2 MB patch to gain support from the pools. Since a client is not even available yet that support remains to be seen.

I don't have any ASICS. I agree that Bitcoin Classic won't merge Luke Jr.'s PR. But don't worry. There's a proposal for Bitcoin FU (Forking Uninhibited) that will hard fork away from SHA2 the same time Bitcoin Classic forks away from 1MB.

https://bitcointalk.org/index.php?topic=1330447.0

Everyone will get what the Bitcoin they want and we can finally put all this drama behind us.