ProfMac,
Correct. The evidence suggests that someone with an ASIC/serverfarm has kicked the difficulty up at least twice, once on 4-08 at block 14112, where diff jumped from 4096.032 to 16384.25, and again on 5-06 at block 18144 where diff jumped from 8948.631 to it's present 35794.675.
What this new group proposes to do by forking the blockchain is to form a pool that gives them the advantage in mining and leaves the rest of us with our fly unzipped and nowhere to go.
Thanks for the lead.
At block 16128, on 2013-05-03 22:20:02, a new difficulty of 8,196 was begun.
1 day later, at block 17108 2013-05-04 22:20:08
That is 980 blocks / day, or about 4X what it should be.
In the 30 days or so since block 16128, there should be 7,200 blocks mined to bring us to about block 23,328.
The blockchain is behind 4,997 blocks.
I can't get a genrate from #bitcoin-otc right now.
----
There are two things I don't know:
a. How fast can you generate blocks with 1.2 GH/s at difficulty 8,196
b. Can you spoof the time to the miner.
The thing you can do if there is a rogue and hostile ASIC is to simply generate a block with a timestamp each 10 minutes, starting with
block 16129, on 2013-05-03 22:30:00. Include all the transactions that are valid on your fork, and simply invalidate all of the pirates mined blocks. Keep the blocks paced at the 10 minute rate, and when you get to 18,332 you have done a takeover. The date will be far in the past, and some transactions will appear to be in the future to the block-chain.
Then, you mine a block for each transaction that needs to be confirmed.
When you are caught up, the rate is low and karma is restored.