Sorry) I didn't want to offend you)
You didn't actually offend. I don't take offense easily. You amused, honestly.
Actually, I'm checking your code for bugs sometimes.
Cool. I know of at least one minor "bug" hiding in the path finding, which makes the work curve slightly inaccurate, directly. I don't consider it a huge deal, since we already know the work curve is a best-guess approximation anyway. It is not really a significantly exploitable problem, it just makes one coin slightly more likely to be grabbed. (hint hint ;-))
Have you spotted any others?
I still think 196000 was too early (we had only one hour before the fork).
You're probably not wrong, but again it only would've mattered if both forks ran, and someone transacted on the wrong fork. This is a risk with any fork, anyway! I stand by my decision to move to 198000 (despite the setback in the end) but I think we would've been fine at either fork point. All well, it is all just ancient history now.
Current situation is not a problem at all. We just need new builds)
It is only a problem because C-Cex and explorer are "stuck." I've contacted C-Cex to revert, and will revert the explorer at my first available opportunity. (I'll still send out the 10k prize coins, once c-cex is safely "unstuck." If we find ourselves crawling toward the next fork point, I may run a similar promotional initiative again to help move things along.)
I'm quite busy for the next 24-48 hours with other obligations, so our next attempt at a fork will not be immediately coordinated unless someone else wants to handle it and commit the changes sooner. (I should at least be able to find some time to merge a PR and sneak in a Gitian run or two.)