Post
Topic
Board Announcements (Altcoins)
Re: Re
by
HR
on 04/09/2014, 07:57:15 UTC
Interesting stuff ... but with 50% of Groestl that is still only half of one algorithm, i.e. 10% of the network. So not a huge issue.

There are some big hitters soaking up the rewards for the less popular algos (ie. not scrypt or Sha) and some of those are solomining ... be interesting to see how it works out in a few days after everything has calmed down.

The issue isn't a 51% attack issue, it's a monopolization issue, or unfair competition if you will. His pool has an unfair advantage that basically eliminates other competing Groestl pools.




Hi HR!

I saw your message, but I'm not quite sure what course of action you are proposing.


Well, I wasn't really proposing anything as it was that I was simply documenting what I was seeing, but now that you've asked . . .

Your pool ( http://cryptohunger.com:81/ ) has an unfair advantage that makes other Groestl pools uncompetitive with you. We all know that is not fair, and no-one would argue that it is.

It's simple common sense: who would mine on any other pool when they could get a higher hashrate (and payout) on your pool with the same equipment? (All other things being equal and baring things like hidden fees, questionable payouts, and other similar issues that can cause a user to distrust - only distrust would cause someone to forego a more profitable opportunity, until the larger community steps in to enforce equal opportunity and general fairness that is.)

So you attract all mining to your pool and you make good money yourself. Sounds like a good capitalist proposition, but the problem is that your unfair advantage eliminates competition (other pools) and capitalism places a higher priority on competition than it does with one entity's individual desires to get rich at others' expense.

Therefore, the obvious proposal would be to correct the problem, and that would be done by addressing the unfair advantage, either by making it possible for other pools to use your optimized kernel, or by discontinuing its use on your pool (which would be easily verifiable).