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).