Quote from: eminer001 on April 06, 2018, 09:52:42 AM

Quote from: moppidoo on April 06, 2018, 06:38:57 AM

Quote from: eminer001 on April 06, 2018, 05:13:52 AM

Quote from: Bob-Bit on April 05, 2018, 07:07:13 PM

Quote from: eminer001 on April 05, 2018, 04:41:19 PM

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" . I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end, maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.

I understand your frustration, but you should just deselect Zergpool yourself from your list if they have crossed a line for you. I don't think it should just be removed from Awesome miner. Some people may only be using it for a couple algorithms, (and they may be ones you don't even use) but those people may really want it as an option. I'd like to see MORE pools added (Blazepool, and Yiimp pool for starters) Even if you hate a pool and never want to use it, it will help you to have it in the list because other people who do have it selected will switch to that pool, leaving less miners at the pool that you DO prefer, and also, everybodys miners won't all go to the same place at the same time if there are more pools available.

They are at 6k miners from below 1k miners just because of us, AM miners that selected zergpool from AM settings.
ZergPool should be aware that as easy it was to skyrocket to 6k they can go back to below 1k if zergpool is removed from AM.
Miners simply had no option because X17 is one of the most popular algos from all pools.
AM's performance and credibility relies on pool's statistics that if they send for 6 hours statistics for X17 that are 10 times higher than any other pool, than AM did nothing to prevent it and is the one that could be blamed also.
Mining works as a synergy between Awesome Miner and and pools like zergpool. If the pools send statistics that are 10 times higher for 6 hours, than AM's credibility is affected because its lack of protection and users will try to use any other mining software that offers them stability and reliability. For 6 hours, 4500 miners had no protection from AM and mined on a fork and pool administrators did nothing for 6 hours as you can see from everybody's graphs.

don't know how it's all AM's fault and all those extra 5k miners are all AM users....but if you think it's ZergPool that was reporting false data, you were pretty wrong, first XVG forked due to the attack, and major pool shuts down to implement the fork etc. and difficulty reported by WTM also coincides with the btc/mh reported by the active pools. Low difficulty, high profit...there's nothing ppl can do with things out of their control. Sorry if the Zerg hasn't been polite in their discord channels, but maybe the other way round not everyone is tolerant being accused of scammers, hash stealers ... etc.

BTW, I don't use any of the online services except NH pretty much as a failover protection only. So I haven't been zerged....point being...if you care about profits so much, you should really be choosing the pools carefully.

Also, don't assume the pools are making profit over this. Did you see MPH's announcement on MUSIC now? as well as other occassions that chainsplit happens at both HashRefinery, Ahashpool...that they displayed good gestures that they still paid for the orphaned blocks that were mined on the wrong chain...As someone who might predict, dear you would not appreciate it at all since you believe that they made so much money off you by all means through your accusations against them all the time. But TBH, they are not obliged to compensate you when sh*ts like that happens...None of the pool ops, SW devs other than XVG team for example, are responsible for attacks on the XVG network in the past days, and yet, would XVG team compensate you? not at all!

***
Back to topic regarding the solution however, you can simply support my suggestion that the implementation of rules based on profit (globally/individuallly) can be actuated. If I can set miners to profit switch when profit falls below certain threshold, who says I can't do it the other way round? when it got absurdly high that I can disable a pool until the coin's stat return to what I deemed "normal".

Support my proposition, this is not the smartest workaround, but it does what you asked...a safeguard that you could define the threshold values yourself and hopefully works while you are sleeping.

What do you think ?
When all the other 4 pools have no issue, and when zergpool has this issue for 6 hours making 4500 miners loose all for 6 hours, it's something from bad management of the pool, right ?
Also AM should implement a protection against this type of behavior from pools, right ?

Once I get the current development release done and released as v4.7 I will start investigating how Awesome Miner can be improved to detect more of these pool related issues.

I agree that Awesome Miner should be able to analyze and find pools that are reporting unrealistic numbers in terms of profitability. Please keep in mind that when you mine on Zergpool and similar, Awesome Miner may not have full insight in the coin details of what you are actually mining. The profit information is however always known.