Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.
no, nothing I could do. he was pressuring me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.
I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.
Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.
You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".
It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.
Now, a day after the launch you STILL haven't got your coin under control moron.
