[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[ballexplorer]

I would like to ask the following question: Would the tifficultly increase in BTC mining if in the future with nuclear computer or quantum computer is minted?

[1713519845]

1713519845

[1713519845]

1713519845

[1713519845]

1713519845

[1713519845]

1713519845

[cashen]

Looking for some input

I have multiple Baikals and I'm wanting to update the pool and The only way I have been able to do it so the algo switches as well is to have the pool and algo setup in the miner using the webUI.

Is there a faster way of doing it? This will be very time consuming with 30+ machines.


I thought about using MRR and have it setup in the miners for each algo.

then create a coin in AM "MRR-QUARK"

then when I want to mine a specific pool I would make "MRR-QUARK" the most profitable and then go to MRR and change it to the pool I want.

[patrike]

Awesome Miner version 4.4.2

- Excavator 1.4 supported as both Managed Miner and Managed Profit Miner. Please note that automatic download isn't supported.
- Performance improvements when performing opertions on many Antminers over SSH, for example setting default pools or configuring the API access.
- Antminer diagnostics, where the cgminer/bmminer configuration of the Antminer can be displayed
- The Managed profit switcher can be configured to detect pool failures and move on to the next pool
- Added support for a total of three modes for profit statistics from pools like zpool, Hash Refinery and AHashpool: Current, 24h average estimate, 24h average actual.
- Notification actions can specify a custom Webhook POST body
- New notification variable to get the Notification ID
- The system notifications can be disabled with a new setting
- Claymore Dual Ethereum Miner 11.0, including the new dual mining algorithms
- Minor corrections

Awesome Miner cannot automatically download the Excavator mining software because of the Nicehash end user license agreement where redistribution of their software isn't allowed. The Excavator mining software needs to be downloaded manually from:
https://github.com/nicehash/excavator/releases
The Excavator software can be downloaded and extracted to any path. To use it from the profit switcher, edit the Profit profile and enable it in the list of software, then click the configure button to specify the path.

The new profit switching feature to detect pools that doesn't give any accepted share can be enabled in the Options dialog, Profit switching section. To see if any pools are listed as a failed, right click on the miner and select View Details to view the profit calculations per pool and also if any of these pools have failed to give accepted shares.

Please note that the pool is listed as failed per miner - it's not global to all miners. The reason is that if a single miner is unstable and doesn't produce any accepted shares, it will not ban the pool for all the other miners. If it's a pool problem, it will be detected for each individual miner about the same time anyway, and each miner will mark the pool as failed.

There are now three modes for profit statistics: Current, 24h average estimate, 24h average actual - configurable in Options dialog, Statistics section. Please note that all of these numbers are still taken directly from the pools, so it's still the responsibility of the pool to provide as accurate numbers as possible.

[sergw]

Hi, question regarding switching mining pools:

I have several Antminer S9 ASICs in awesomeminer, I configured 2 pools: antpool and BTC.com, i configured API access on S9, when i try to switch pools it disables 1st pool, then switches 2nd and 3rd pools, as result miner not working because 1st pool - disabled, anybody faces similar issues?

[Mercutio999]

Now i have upgraded, my custom Phoenix miner doesn't connect to the interface. Can anyone help please?

[patrike]

Hi, question regarding switching mining pools:

I have several Antminer S9 ASICs in awesomeminer, I configured 2 pools: antpool and BTC.com, i configured API access on S9, when i try to switch pools it disables 1st pool, then switches 2nd and 3rd pools, as result miner not working because 1st pool - disabled, anybody faces similar issues?

The existing pool show be removed after a few seconds and be replaced by the two new pools. What's the pool status of the two new pools, are they enabled and working?

[patrike]

Now i have upgraded, my custom Phoenix miner doesn't connect to the interface. Can anyone help please?

I just downloaded the Phoenix miner and made sure I started it with the flag -cdmport 3333 to have the API enabled. From Awesome Miner I added it as an External Miner of type Claymore Ethereum and then I was able to see the monitoring information.

Can you send me the API report for this miner you had?

[patrike]

Hi

Could phoenix miner be added for profit management as it's faster than claymore and uses a lot of the same cli arguments from claymore and has a compatible API

https://bitcointalk.org/index.php?topic=2647654.0

Thanks

I'll second this

third it .
me to it is faster then Claymore ETH Miner just tested it by about 2 MH or was for me .

I think patrike indeed said a while back he was looking at a way to add any custom miner with full stats or what we need to run it in AM and Other OC options that AM can use but that's gonna take some time it's more involved to add. if I understood him wrong ,then I'm being it up again or hint, hint it will make life a lot easier but only if i misunderstood....if there needs to be a one time add on fee i will be then glad to pay for it or any thing to make AM more Universals then it all ready is . .. or Improve it , there is always room for improvement .

Thanks for the suggestions on this.

Until it's officially supported, it can be added as a user defined Managed Software. This is what I tried:
1) Via Options dialog, Managed Software, add a new software called "Phoenix Miner"
2) Set it as API compatible with Claymore Ethereum and use API port 3333
3) You can disable the algorithms not supported but no further configuration is required in this dialog
4) Add a new Managed Miner and set software to the new "Phoenix Miner". Point the path to the location of the Phoenix miner exe-file.
5) All command line parameters needs to be manually specified in the Command Line section of the Managed Miner, and it's important to specify API port like "-cdmport 3333". Example command line:
-pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 -cdmport 3333

Now it should be possible to start the miner and get monitoring information. I did however notice that the Pools tab is empty with this setup, but I will implement support for that in the next release.

For general information on the Managed Software feature, please see:
http://www.awesomeminer.com/help/managedsoftware.aspx

[kipper01]

Hi

Could phoenix miner be added for profit management as it's faster than claymore and uses a lot of the same cli arguments from claymore and has a compatible API

https://bitcointalk.org/index.php?topic=2647654.0

Thanks

I'll second this

third it .
me to it is faster then Claymore ETH Miner just tested it by about 2 MH or was for me .

I think patrike indeed said a while back he was looking at a way to add any custom miner with full stats or what we need to run it in AM and Other OC options that AM can use but that's gonna take some time it's more involved to add. if I understood him wrong ,then I'm being it up again or hint, hint it will make life a lot easier but only if i misunderstood....if there needs to be a one time add on fee i will be then glad to pay for it or any thing to make AM more Universals then it all ready is . .. or Improve it , there is always room for improvement .

Thanks for the suggestions on this.

Until it's officially supported, it can be added as a user defined Managed Software. This is what I tried:
1) Via Options dialog, Managed Software, add a new software called "Phoenix Miner"
2) Set it as API compatible with Claymore Ethereum and use API port 3333
3) You can disable the algorithms not supported but no further configuration is required in this dialog
4) Add a new Managed Miner and set software to the new "Phoenix Miner". Point the path to the location of the Phoenix miner exe-file.
5) All command line parameters needs to be manually specified in the Command Line section of the Managed Miner, and it's important to specify API port like "-cdmport 3333". Example command line:
-pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 -cdmport 3333

Now it should be possible to start the miner and get monitoring information. I did however notice that the Pools tab is empty with this setup, but I will implement support for that in the next release.

For general information on the Managed Software feature, please see:
http://www.awesomeminer.com/help/managedsoftware.aspx

Thanks for this.

[eminer001]

Here is a small update about what's in the pipeline and the plan is to include it in a new release within the next 24 hours.

* Claymore 11.0 with the new dual mining algorithms
* Excavator 1.4.3 supported as Managed Miner and Managed Profit Miner
* A new profit switching feature where the profit switcher looks at the accepted shares of the mining to try to figure out if the current pool is failing. If there are no accepted shares for 8 minutes (configurable), the pool will be ignored by the profit switcher for 5 hours (configurable). The feature will be disabled by default.

Please note that if the pool is reporting that the shares are accepted, but still fail in some other way (payouts not as good as expected, shares not counted although reported as accepted, ...) it will be impossible for Awesome Miner to detect. Awesome Miner will not be able to solve all pool issues, but hopefully help a bit.

The release will contain more than the items above, but I think these three items are the most requested and discussed right now. Thanks for all feedback.

I can also point out that Bminer probably will be the next mining software for me to explore.

Thanks for the improvements.

The problem was that accepted shares that was reported by ccminer was between 19000 and 53000 and the method you described won't work, because accepted shares on pool's reports was zero, see this : https://www.dropbox.com/s/4obw9jkx0s8l84g/Screenshot%202018-02-09%2011.53.34.png?dl=0
 
I opened www.zpool.ca/api/walletEx?address=WALLET_ADDRESS and the miner's array are not uniquely identified by AM with ID fields from miner's array (you leave it empty) and also accepted field from each miner remained to zero even if AM was mining for 3 hours.  

So from my point of view you are not reading and you are not using the real values from the pools that are the most important, because only the registered hash-rate on the pool's side is that transforms to payments.  

The implementation is simple and will fix a lot of issues all caused by the fact that you read what miners are reporting (that many times miner lie and report misleading values to hide the developer / or hacker's stealing fee) instead of reading values recorded from the pool that many times, with many miners are lower.

I also think that you should use total_earned field from /api/walletEx?address= and add checks like :
1) if value decreased it means you were mining an orphaned fork - this happened last week, and was reported on this forum and also we saw that on all pools 8 hours of income vanished because all MA users with 24 hours statistics were mining on ahashpool orphaned CRC coin . Also AM could cause 51% attack and soft fork that means all AM users will loose all the money on that branch (I hope you know what I am talking about).
2) if the value increases you have the difference and you will have to show a new column for each miner with pool's earnings reports the statistics with income per unit of time (make the difference between 2 requests from the pool in seconds and if the reports are not identical (because pools refresh statistics every few minutes) divide the income to the number of seconds and you have real income from the pool in $.
3) Add in rules triggers and actions (a very useful part of AM, congrats for that, btw) new items based on the accepted and total_earned fields from pool's statistics (all you need is some associative arrays to store values for each pool. New rules will be much better than flawed "accepted" rules we have now.

Am users will compare values from the pool with values from the statistics and will notice that :
1) the miner is stealing and reporting inflated hash rates that is a practice these days and you are ignoring it;
2) a specific pool is stealing or is not functioning correctly for any reason (errors, restart, ddos).
3) AM users will really appreciate you because they feel you are on their side, because they have together millions of dollars on your hands and you have a huge responsibility to protect their inestment

So, do you understand, Patrike ?

Do you understand ?

[Zaffor]

Installed new version of AM and added excavator. Benchmark runs fine but when I start the rig on multipool hub it seems to show several algos in blue with speeds all 0.00000

What did I do wrong?

[sharknakedo]

Same issue here. Upgraded remote agent, pointed to 1.4.3a, etc., same issue with multiple algos all showing zero hash rate.

[narousberg]

Hi Patrike
please add in your system this wonderful multipool service: d3pool.eu
Its realy good pool with low fees.

[cashen]

Mine stops. Picture below.

[patrike]

Installed new version of AM and added excavator. Benchmark runs fine but when I start the rig on multipool hub it seems to show several algos in blue with speeds all 0.00000

What did I do wrong?

I just learned that Excavator and Mining Pool Hub doesn't work together. After doing more research, it looks like the Excavator miner is explicitly blocking connections to Mining Pool Hub because of some disagreements between Nicehash and Mining Pool Hub.

I will have to implement something in Awesome Miner that prevents the profit switcher from selecting the combination of Excavator and MPH. For the moment, please disable one of them.

[patrike]

Mine stops. Picture below.

Please make sure you select "Excavator (latest)". By the look of the command line, it looks like it was prepared for the old Excavator miner

[patrike]

Here is a small update about what's in the pipeline and the plan is to include it in a new release within the next 24 hours.

* Claymore 11.0 with the new dual mining algorithms
* Excavator 1.4.3 supported as Managed Miner and Managed Profit Miner
* A new profit switching feature where the profit switcher looks at the accepted shares of the mining to try to figure out if the current pool is failing. If there are no accepted shares for 8 minutes (configurable), the pool will be ignored by the profit switcher for 5 hours (configurable). The feature will be disabled by default.

Please note that if the pool is reporting that the shares are accepted, but still fail in some other way (payouts not as good as expected, shares not counted although reported as accepted, ...) it will be impossible for Awesome Miner to detect. Awesome Miner will not be able to solve all pool issues, but hopefully help a bit.

The release will contain more than the items above, but I think these three items are the most requested and discussed right now. Thanks for all feedback.

I can also point out that Bminer probably will be the next mining software for me to explore.

Thanks for the improvements.

The problem was that accepted shares that was reported by ccminer was between 19000 and 53000 and the method you described won't work, because accepted shares on pool's reports was zero, see this : https://www.dropbox.com/s/4obw9jkx0s8l84g/Screenshot%202018-02-09%2011.53.34.png?dl=0
 
I opened www.zpool.ca/api/walletEx?address=WALLET_ADDRESS and the miner's array are not uniquely identified by AM with ID fields from miner's array (you leave it empty) and also accepted field from each miner remained to zero even if AM was mining for 3 hours.  

So from my point of view you are not reading and you are not using the real values from the pools that are the most important, because only the registered hash-rate on the pool's side is that transforms to payments.  

The implementation is simple and will fix a lot of issues all caused by the fact that you read what miners are reporting (that many times miner lie and report misleading values to hide the developer / or hacker's stealing fee) instead of reading values recorded from the pool that many times, with many miners are lower.

I also think that you should use total_earned field from /api/walletEx?address= and add checks like :
1) if value decreased it means you were mining an orphaned fork - this happened last week, and was reported on this forum and also we saw that on all pools 8 hours of income vanished because all MA users with 24 hours statistics were mining on ahashpool orphaned CRC coin . Also AM could cause 51% attack and soft fork that means all AM users will loose all the money on that branch (I hope you know what I am talking about).
2) if the value increases you have the difference and you will have to show a new column for each miner with pool's earnings reports the statistics with income per unit of time (make the difference between 2 requests from the pool in seconds and if the reports are not identical (because pools refresh statistics every few minutes) divide the income to the number of seconds and you have real income from the pool in $.
3) Add in rules triggers and actions (a very useful part of AM, congrats for that, btw) new items based on the accepted and total_earned fields from pool's statistics (all you need is some associative arrays to store values for each pool. New rules will be much better than flawed "accepted" rules we have now.

Am users will compare values from the pool with values from the statistics and will notice that :
1) the miner is stealing and reporting inflated hash rates that is a practice these days and you are ignoring it;
2) a specific pool is stealing or is not functioning correctly for any reason (errors, restart, ddos).
3) AM users will really appreciate you because they feel you are on their side, because they have together millions of dollars on your hands and you have a huge responsibility to protect their inestment

So, do you understand, Patrike ?

Do you understand ?

Yes - I see your point.

[patrike]

Hi Patrike
please add in your system this wonderful multipool service: d3pool.eu
Its realy good pool with low fees.

Thanks for the suggestion. I will try to find a good solution for supporting yiimp-based pools like this one in general, so any of these pools can be supported.

[Zaffor]

Installed new version of AM and added excavator. Benchmark runs fine but when I start the rig on multipool hub it seems to show several algos in blue with speeds all 0.00000

What did I do wrong?

I just learned that Excavator and Mining Pool Hub doesn't work together. After doing more research, it looks like the Excavator miner is explicitly blocking connections to Mining Pool Hub because of some disagreements between Nicehash and Mining Pool Hub.

I will have to implement something in Awesome Miner that prevents the profit switcher from selecting the combination of Excavator and MPH. For the moment, please disable one of them.

Thanks for the prompt response

Shame, Excavator is a good miner for Neo and a few others and I was going to try out Multipoolhub to see if it was any better than ahashpool. Will reconfigure Awesome to go back to KlausT and DSTM for npw.

[patrike]

Installed new version of AM and added excavator. Benchmark runs fine but when I start the rig on multipool hub it seems to show several algos in blue with speeds all 0.00000

What did I do wrong?

I just learned that Excavator and Mining Pool Hub doesn't work together. After doing more research, it looks like the Excavator miner is explicitly blocking connections to Mining Pool Hub because of some disagreements between Nicehash and Mining Pool Hub.

I will have to implement something in Awesome Miner that prevents the profit switcher from selecting the combination of Excavator and MPH. For the moment, please disable one of them.

Thanks for the prompt response

Shame, Excavator is a good miner for Neo and a few others and I was going to try out Multipoolhub to see if it was any better than ahashpool. Will reconfigure Awesome to go back to KlausT and DSTM for npw.

I’m exploring if there are other solutions around this.