Thought he said at that time he would keep his reduced hashrate stable at that GH/s rate?
Now he confessed he was keeping it somehow 'balanced' to the other miners hashrate.
I never said that. I promised to keep hashrate low enough to don't inflate block times into extremely high values. And I did this by readjusting our algorithms especially for NLG.
Dear Guldencoin community, I adjusted our algorithms long time ago to don't cause pain to your users and merchants (to prevent 180-560-minute gaps between block). I recommended you DIGI readjustment algorithm back in September as the best to handle coin-switching pools, but you decided to go with DGW3 instead and only now you're correcting this mistake. I have always been trying to find a way to coexist with altcoins and help any way I can while still doing my job as pool operator.
But if you want us to shut down the pool or stop mining at all, then it's not going to happen. Coin-switch pools exist, and CM is not the only one, and you just need to learn to live in this world. You won't close all coin-switching pools which exist. In fact, you brought more coin-switching pools on yourself by writing in our thread. CM was the only coin-switching pool mining NLG for a very long time. Only after you started writing in our thread - which is also read by other pool operators - the other coin-switching pools discovered NLG and started mining it.
This is the world we are all living in. There are coin-switching pools and you are a very little brother to LTC in the meaning that you use the same mining algorithm but you have only 1.2% of LTC mining power. There will always be big pools or mining farms which will be able to control 50% of your hashrate and there will be many of them. This is the fate of small scrypt coins and you need either to change or to learn to live with it.
I am trying to make your life easier any way I can while still doing my job as coin-switch pool operator (which is important disclaimer). Limiting our hashrate to don't cause multi-hour block gaps is what I understand something which solved the biggest problem for your users and merchants - and also reduced our share in your mining power from 85% in September to ~50%. This is something we did voluntarily after your developers contacted me and informed me about your problem.
But mining 50% of new coins is not really a problem in my understanding. Before you object - I know that you read "mining 50% of coins is bad" repeated hundreds times like a mantra - please read my explanation with understanding. It's not mining 50% of coins what is bad, it's someone being able to mine 50% of coins. And there are dozen of pools or mining farms who have enough hashpower to do this - and all of them are in a position to harm NLG if they wanted. CM is only one of them, but it's the only one visible because it shows its hashrate on your blockchain. But showing it doesn't make CM any bigger threat than the other dozen - it only makes it more visible.
Please let me quote two posts in which I explained this. Please read it entirely and with understanding before you reply, because only then we can have a constructive discussion. Thank you!I contacted you as well. I have the PM's if you need a refresher. Our block gaps were caused by our broken algo, and as a direct result of your pool's influence in that algo. So you "helped" by reducing the problems you caused. The block times weren't the concern though.
It was the concern for the other developer who contacted me first with the issue. I addressed this issue and helped to solve this problem.
I have your PM and I answered it immediately. I just checked it. Your concern was also "When CleverMining hops on NLG, we see difficulty swings and periods of no blocks found". I addressed this issue and solved this problem for your community.
It was the fact that directly after telling us you would reduce mining power, and dropping down to 20% of the block mining in a given day, you went up to 90% of the blocks in a day, and then back down to around 50% for the last few months.
I promised to drop our hashrate to solve inflated block times problem and I did exactly that. Our NLG mining share in September was 85% mined blocks, then 65% in October, then 55% in Nov, 51% in Dec, and 53% in Jan. These numbers are coming from your own mining stats at
http://nlgstats.iblogger.org/historical_mining_stats.html. You see, I did what I promised, I decreased our NLG hashrate and I kept that promise and never increased it back again.
So is asking that you not take 50% of the blocks in a given day, a common concern in the crypto community regardless of the coin, a unreasonable request? Help me wrap my head around that, because no, I don't understand that.
As you write about "50% ... common concern in the crypto community regardless of the coin" I assume you are taking about 51% attack.
Then you probably lack understanding of 50% issue/attack. It really doesn't matter if someone mines 50% blocks or even mines 80% blocks or doesn't mine at all. The coin has the same problem even if someone doesn't mine it at all, but has enough hashpower to mine 51% blocks. Anyone who has enough hashpower can jump into your coin at any time and execute a 51% attack. It doesn't matter if they were mining 51% blocks before the attack or if they didn't mine your coin at all. And with 14 GH/s network hashrate there are at least dozen entities (mining farms and pools) which have enough hashpower to take 51% of your network. An entity which mines 51% but doesn't attack is better than entity that doesn't mine but plan to attack. Your problem isn't with CM. Your problem is with having a coin which uses the same mining algorithm (scrypt) as another coin which has 85x higher network hashrate (Litecoin). I can't help you with that (some coins solved this by switching algorithms to non-scrypt, but that made them even more niche coins, other solved this by implementing AuxPoW and becoming merge-mined coins, other decided that they didn't care that much and accepted the fact of being little brother to LTC). What I can do is to promise that you will never face a 51% attack from CleverMining. This is much more than you get from the other dozen entities which control over 14 GH/s of scrypt mining power. You don't even need to believe me to believe that we won't attack - as we don't hoard NLG, we don't have coins to double-spend and 51% attack is useful only for double spending.
Another issue which you might have is that we sell blocks which we mine. But this is simply a market mechanism and this is our business model. What you would like us to do is to cease operations and close the pool. This is not going to happen. I can cooperate to don't inflate your block gaps to several hours - which would cause inconvenience for users and merchants and would kill the coin in the long term - but I won't let my users down and I don't close the pool. Coin-switching pools are reality and you need to learn to live with that. I've done as much as I could to limit inconvenience caused by CM to your users and I expected only a little bit of friendliness in return (and I got it from other NLG developers).
I'm sorry you're a power hungry, greedy multi-pool op who doesn't give a shit about anything besides his bottom line.
If I were, then I would probably like to show you my "power" - after you started offending me and shitting in my thread - by removing all limits which are limiting amount of hashpower sent to NLG. This wouldn't inflate your block times to 560 minutes as before because of your improved algorithm, but it would inflate them to 120~180 minutes which is high enough to cause painful inconveniences to users and merchants. I won't do this. I am friendly and I won't hurt intentionally entire community because of one of their members.
Truth of the matter is that you continued to mine NLG on a side fork. Your failure to identify the issue, or even plan for it, was a nice little bonus to the whole changeover. I won't apologize for my enthusiasm with that.
This only shows how hostile you are, while I have been cooperative and friendly.
Also, by the way of your "whole changeover", I would like to remind you, that I was recommending you DigiShield algorithm when you were brainstorming what to use instead of KGW back in September. I told your developers that coins with DigiShield readjustment behave the best with coin-switching pools and that it will be better for NLG to adapt it. I did this because I wanted to help. I really prefer thriving coins than coins with problems. You went with DGW3 despite my advice and you saw only little improvement (which would be zero improvement if I didn't decrease our hashrate). Now you finally switched to Digi readjustment, which is something I recommended from the start for the good of your coin. This is another example of me being helpful, caring and cooperative. You try to paint me as a villain but the truth is I really did everything I could to help your coin. Perhaps you didn't use my advice on readjustment algorithm out of suspicion that I try to sell you something which was good only for me, but I was recommending something which was good for the coin (and in effect, also good for me, because CleverMining can profit only from healthy coins). I wish you could learn to recognize a friendly pool operator and learn to work together peacefully, because coin-switching pools won't disappear - instead of sending only hate my way despite my efforts to cooperate and help.
Again, thank you so much for working so hard to cooperate with our coin. You're right... I'm completely wrong for being upset about half of the coins mined daily going to be sold on markets, and not going to users who will actually use the coins.
These coins don't disappear. If the coins are sold on markets, then it means that someone else bought them. So the coins still go to users who will actually use the coins. Nothing changes here.
I already came to the conclusion of DIGI before we knew who you were on the chain. Your suggestion, at the time, was just another in a long line of suggestions.
If you came to that conclusion at the time you now claim you did, then well, you were not successful in implementing it. I recommended DIGI to another NLG developer in a PM sent on Sep 14th and I recommended it to you personally in a PM sent on Sep 16th. One week later you announced switching to DGW3. Then you finally implemented DIGI with the beginning of Feb, four months later. You can't blame me for you being unable to implement good solutions for four months.
If you were trying to help, where were you in the 5 months of discussing how to mitigate your pool's influence on the coin?
Actually exactly 5 months ago I recommended you the solution which you failed to implement then and finally implemented only 4 days ago.
No, not 51% attack. Owning 50%+ of the network, as in centralization of mining.
I repeat: There is no difference wether we actually mine 50% or don't mine but control hashpower which is able to dominate your mining network. It's just the fact that somewhere there exists a hashpower which could take over your network - this is the problem. There are dozen of entities with this amount of hashpower, CM being only one of them, and you can't do anything about it. Wether we mine 50% blocks or 0%
changes only perception, but doesn't solve the problem. Mining 50% blocks makes only the problem more visible to you. Not mining makes it less visible to you - and that's the only change. Us stopping mining won't change the problem - there still will be dozen of different entities each controlling enough hashpower to dominate your network at any time.
If you find a solution to this - and somehow prevent the other dozen entities to be able to control your network, then I'm ready to discuss what more CM can do for you. Until this happens,
I refuse to decrease my users profit only to change your perception of the problem, but don't solve any real problem. Your coin is as much vulnerable with someone mining 50% or not mining but being able to mine. Think of it like 10 people accidentally holding copies of keys to your home. You are vulnerable, because if they decided to, they can go in and out whenever they please (as: attack the coin). 9 of these people are holding their keys in their pockets (are not mining) and you don't see them. 1 of these people have his copy in plain sight (is mining) and it annoys you. You really should be worried that 10 copies of the key exist, not that you can see 1 of them. The thing is that you can't take these keys back and these people cannot give them back even if they wanted. There are dozen of entities with high enough hashpower to dominate your network and they won't disappear. Me hiding my key in a pocket won't solve your problem. And I won't throw my key away (where key being controlling enough amount of hashrate) as it would require shutting the pool down.
So again: I'm helping any way I can while running our pool at the same time. I reduced your max block time 20-fold. I recommended you the best readjustment algorithm four months before you finally decided to use it. But I won't stop mining NLG at all only for you to feel better, because it wouldn't solve any real problem.
Your idea of "cooperation with coin-switch pool" is the pool to stop mining at all. This is not cooperation and this is not going to happen. This is not coexistence. You would like us to stop existing at all. I can agree to solutions which decrease inconvenience to your users a lot (decreasing maximum block times from 580 minutes to 30 minutes) and don't decrease profitability of my users in a significant way, but I won't implement solutions which really don't improve NLG in any way (other than make you feel better) but decrease our users profitability.