I've have to wonder if we've reached the point where there *needs* to be more than one developer on this project.
@artos, it's obvious you still have shit going on in your life that keeps you from addressing issues with this coin. We're now into the third day of a situation where the difficulty is pegged... and will only rise. Your response: it's being monitored. There is nothing to monitor. We need a fix. It's a simple fix. It's a fix that's been posted here. It's a fix that's been committed via GitHub... it's a matter of merging code. It simply couldn't be any easier.
There are a lot of us that have a great deal of money invested in SBC and we're left thinking 'am I an idiot for thinking this guy will stick with the project... after having abandoned it already?'
Dude, what the hell can we do to help? This thing is dying here and YOU are responsible.
Had I merged your code, the blockchain would have been forked instantly, 1800 blocks in the past. Does that sound like an acceptable solution? The actual fix is an extremely simple one, and has been ready for days. I've been monitoring block generation trends so that I could set a reasonable point for the next fork to occur at. Hardforks are a delicate art, and screwing this part up would surely be the final nail in the coffin. Why are you all suggesting that we rush into it? Is 3 days of low mining rewards worth jeopardizing the coin over? I've gathered enough data, and the fork will occur at block
317,000.