Another day has passed, and the freelance developer has made some good progress on the issue.
Many people wanted to add new features and hard fork once those are done, but enough people posted that they just want the problem fixed as fast as possible. We are just going to fix things immediately without adding new features.
We will plan a hard fork adding new features later. This will allow us to test the new features properly and make sure we are adding the right features.
We got some excellent feedback on which features people want next (atomic swap and multi-algo) and we can start working on those once this problem is solved.
Someone also suggested a regular schedule for hard forks (because we will always be adding new features) and I really like this idea.
I also have contacted multipool.us and they are willing to work with us to get people on their chain.
https://www.multipool.us/dashboard/pool/trcSince we are trying to get everyone on that fork you should keep your rewards, but nothing is guaranteed at this time.
We are going to force everyone to use Sentinel, and if you have installed the watchdog branch of the github you will eventually need to revert to the master branch. The checkpoints are nice, but my changes like the protocol bump will cause you issues in the long run.
Don’t bother updating right now. Might as well stay on whatever you are using to save time until we release the new code etc.
If you want to try to get on the multipool chain clearbanned first then sometimes a reindex works, but other times a whole new download of the blockchain is required.
If you can get on that chain and stay on it for a bit you will get some good rewards while you are on there, but you will regularly have to fix the blockchain.
If you have a peer that is sending tons of data to another peer you might as well block that peer for a day. This will stop the bandwidth use since it is just sending error data anyways.
Thanks again for your patience!
We will get this problem cured over the next couple of days!