Quote from: binaryclock on March 27, 2014, 08:38:08 PM

Quote from: BlitzCoinDev on March 27, 2014, 08:31:24 PM

Quote from: chango on March 27, 2014, 08:15:04 PM

Quote from: ocminer on March 27, 2014, 08:07:40 PM

Quote from: BlitzCoinDev on March 27, 2014, 07:31:27 PM

Quote from: chango on March 27, 2014, 07:22:43 PM

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.

Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.

You know, if you didn't present yourself as an amateur that didn't even show up for your second launch, dedicatedpool would of been on board. You scared away all the good pools, then the scampools hopped on over the hype.

Nice job creating another shitcoin.

+11111