5 ms·
Now 4 blocks in: https://cash.coin.dance/blocks#blockDetails https://cash.coin.dance/blocks#blockDetails
by bsmith 9y ago
Now 4 blocks in: https://cash.coin.dance/blocks#blockDetails https://cash.coin.dance/blocks#blockDetails
- mathieutd 9y agoThat's surprisingly fast. Much more hashing power than anticipated is backing the fork.
- tlrobinson 9y agoWasn't the fork scheduled to happen ~7 hours ago? Why did the first block take so long if the hashrate is high enough to produce 4 blocks in the subsequent half hour?
- zorked 9y agoThe new chain inherited the difficulty from the previous chain. Now that the network realized there isn't as much hash rate the difficulty has been reduced and a more normal rate of block creation restored. Edit: that didn't happen yet, I stand corrected
- simias 9y agoThat didn't have time to trigger. Difficulty didn't change.
- LyndsySimon 9y agoMy understanding is that it will take much longer than that for the BCC chain difficulty to significantly adjust.
- eco 9y ago2016 blocks from what I understand. That's 14 days at 10 minute blocktimes.
- simias 9y agoThe last common block was #478558 mined at 3:16:14 PM UTC The first BCC fork block was mined at 8:12:41 PM, almost 5 hours later. The 2nd one was mined at 8:33:06 PM, 20 minutes later. And then an other one not 5 minutes later. Meanwhile the difficulty remained constant at 860221984436.2223 Clearly there's been a sudden surge in the hash rate.
- RustyRussell 9y agoNo, the first block in the fork needed to be > 1MB. But it also changed the format, so they dropped all pending transactions from the mempool. ViaBTC did mine the first bcash block, but it was rejected because it was too small! Someone had to figure out the problem and stuff a block so it could make progress.