Quote from: lordgunshaw on February 19, 2018, 02:20:09 PM

Quote from: jefffree on February 19, 2018, 07:18:57 AM

Hello developers! I suggest publishing the essence of the problem so that everyone can suggest a solution. And you could use these ideas. I'm a very bad specialist, but I suggest. It is necessary to stop mining on all pools and stop transactions on the network, then you need to fix the error in the database and put on all the pools a new version of the database in the mode read-only. And wait some time.
May be anybody suggest one better.

Dear Community.

It has been a real tough couple of days for everyone, we have not stopped trying to work out what went wrong.

Please cease all operations while we continue to work on the cause and fix.

We have taken all of your advice ondoard and we will update you officially once we have a rock solid POA.

Our priorities are to ensure the value fo your work to date, preservation of the existing blockchain and returning normal service ASAP.

We know this is not good news but our official release date of June 2018 is still well within our reach we just new a few more days to formulate our approach.

Please bare with us.

okey! no problem! work and share results!