<soapbox>OK, one last time I'm going to try to compel you to do this, then I'll shut up and get off my soapbox
The network is taking on average 4.53 hours per confirmation right now. Yes, I know the math given the current diff and net hashrate says it should be around 100 minutes but it's not, check the block explorer:
March 5 total of 6 blocks were found, average 4 hours per block
March 6 total of 5 blocks were found, average 4.80 hours per block
March 7 total of 7 blocks were found, average 3.43 hours per block
March 8 total of 4 blocks were found, average 6.0 hours per block
Network average of the past four days is 4.53 hours per blockBEN requires 120 confirmations for mined blocks. At this rate that is
22 days to confirm a newly mined block of BEN's. My pool, which is the *only* pool actually mining BEN right now, has not made a payout in two days.
BEN requires 6 confirmations for transactions.
That's 27.18 hours to send someone BEN. For God's sake, Fedex is faster.BEN is 1986 blocks away from the next diff adjustment.
That is 374.85 days. Yes, over a YEAR before BEN difficulty adjusts back to "normal," assuming the network hashrate does not drop any lower. Problem is, by then, BEN will be way behind schedule on blocks, so it will adjust way too low. Undoubtedly, this will cause many more miners to jump on, BEN will probably end up getting ahead of itself again, and we'll be back at the same problem we are right now. Likely, it won't be quite this severe, but it's going to happen again.
This coin HAS TO FORK. It cannot fix itself.Prayer had a good idea a few posts back. It has been roughly 60,000 minutes since the network launched, we are currently at block 24223, so that gives BEN around 2.5 minutes average block time since launch. I agree with his recommendation:
Fork at block 24250 or so, adjust to have 2.5 minute block times
Diff adjustments every 60 blocks (2.5 hours)
Diff adjusts based on average block time over the past 60 blocks, rather than average block time since network was launched (which is pretty much what it does now)
</soapbox>