Topic: [ANN] GamerholicCoin (GHC) [SHA-256] - Fair launch! - I WIN FOR A LIVING - page 9. (Read 80329 times)

All he did is advice, the fault is from the beginning of 2 forks.

Bro, this is my fault. I went to 'I Got Spots' to get advice on a recommended fix to the forking issue plus some apparent code discrepancies. He was not here to compete or disrespect anyone or direct anything towards any of his projects. I take 100% of the blame in this instance. I only was wanting to give Mr. Sengbe a sound recommendation is all. However I see that now the dev is back and would really like to speak with him. Not here to cause trouble but I also lost some coins in this mess and would like some answers myself. But 'I got Spots' was not here to break up or disturb this community nor am I. Please accept my apology on that. I am seeking some answers from Bryce.  

~S                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              

What's the problem Bryce, the coin didn't get enough noobs for the miners to dump on?

Just make another one!!!!


https://twitter.com/_Valar_Dohaeris/status/499871717091979264

You're certainly right about that, though not for the reason that you think.

Remember I was asked to come here and look fora solution...this coin is so far below my radar that it's laughable. Look at the open source code yourself then. You'll see exactly what I see  

I don't need to FUD to be successful lol, I could literally do nothing for the rest of my life and be just fine

static const int64_t nTargetTimespan = 16 * 60;  // 1 min

unsigned int nTargetSpacing = 2 * 60; // 2 minutes

If you can't figure out why I chose those two to post (among many, many problems), then I have no more reason to try to help you guys. I'm done giving this garbage free thread bumps to the first page. Best of luck, even though I know exactly how this will end  

+1, Jyap.   iGotSpots is making it increasingly obvious that he's only trying to FUD the competition in order to drive his own business.

My analysis was very accurate. Coin is still not broken, even with 8 second blocks. No forks, but the dev bailed. Pretty accurate assessment. What you have in this shit pile is an (advertised) 60 second block time with many, many problems that haven't even come up yet. I'm not posting every error because I'll just be called a FUDster. I've always watched out for the majority and just tell it like it is, which is why I have the reputation of being an asshole

Believe me or don't. Doesn't matter, really, but everyone eventually sees that I do know what I'm talking about

Yea it's totally the community's fault you can't make a working coin using the parameters mentioned in OP

Only put money into this coin that you are ok losing

Did you put this much work into your 'findings' ?
Is it hard to go back and pull it up to show us?
I am honestly interested in this and no one seems to give a shit to point it out.

What coin was this based on, and why do you consider it crap?
I am guessing this is a clone of an old coin still in use today that isn't LTC or BTC. From what I can tell, but hey, I don't run a clone mill.

The network is now fine.  Wallets are staking. Pools are mining. No orphans are being created.

The emission schedule kicked in and the hashrate dropped as predicted when speculators left the network.

That there are those who continue to ignore the reality of what happened for their own gain is not something I can control.

That's BitcoinTalk.  This is the last coin we launch here and the last client we will accept from here.

this guy has been around forever and i trust him. ive done very well buying and mining coins and his word is gold

wow man, that's your update? that's a big "fuck you" to this community. I wasn't expecting much from the dev's follow up post but it was certainly more than this.

The Github in the OP...

Defensive much? Can you link to your findings so that we may see?

Ok think I'm just FUD?

Target Block Time isn't even correct. You guys should look at what you mine before you set up you r rigs or call one of the few people here that can help you a liar.

The code is possibly the worst I've ever seen on here. And I've been around a while

Best of luck, though?

We know what happened.  Gamerholic knows what happened.

Forum posturing isn't my thing. 

Carry on.

I think this coin should be passed over to proper, trusted and dedicated dev.
Having one of the main pools on a fork shows a lack of commitment from the dev and/or the team.
Pools are the "heartbeat" of a coin, that should be closely monitored and taken care of if an issue arises.

Also, the differences between the reality and what the OP claims are another sign of a dev that can't be trusted.

Otherwise, that coin has a lot of potential ! I'll be watching it.

HAHAHAHAHAHAHAHAHAHAH



ANOTHER BRYCE COIN THAT WAS EITHER A SCAM OR A TOTAL CLUSTERFUCK OR BOTH!

What did I tell you about that charlatan?


The party is over Bryce, by now I guess people that still have at least a few neurons in their brains understand that they should stay away from your coins.


Maybe a few more scams or clusterfucks and even the few fools left believing your bullshit will no longer follow BAGTECH coins.


Gamerholic, I'm sorry for what happened, you are a legit company and your projects outside of this coin are clearly very good.
Too bad you didn't know who you were working with.

Haha, you are a direct competitor to Blocktech.  Nice try.

still waiting