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.

There are tons of possibilities, here are three:

1. Proper seednodes
Use dnsseed.yourcoinname.org to resolve to (at least) 6 or more nodes running the "correct" chain of the coin. The "wallets" then connect to this nodes and use them as the preffered blocksource.

2. Higher diff right from the start instead of incredible 0.00000123 diff

3. Post "addnode=" right from the start, not the pool nodes as they will sync up later on, YOUR nodes.

I believe the "dev" doesn't had enough pocket money to afford some VPS's for the seed nodes, so he fully relied on the pools, which then were all on separate forks. Yes, a relaunch for sure deletes or resets the wallets of the users, since there were multiple forks this would be the fairest possibility. This way simply one pool was chosen to be on "the right" chain and thats it.

Note that there is no really "right" chain in a fork.. Here we had the problem that there were even 4-5 forks, all different chains. So who decides which is the right/wrong fork ?

However, the coins idea is not bad even though the dev stole the idea from someone else and postponed the launch 2 times which should make my alarm bells ring like it did for dedicatedpool already, they were right, I was wrong - shit happens. It just pisses me off that retard-dev takes absolutely no repsonsibility for his shit and instead blames others for his incompetence, his failure(s).