One Eth
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 384. (Read 703143 times)
March 28, 2018, 04:42:42 AM
March 28, 2018, 04:39:18 AM
Hello everybody!
Tell me please how can I turn on the dual miner
I can not understand what I'm not doing rightfully tell me where it is not what to prescribe!
Tell me please how can I turn on the dual miner
I can not understand what I'm not doing rightfully tell me where it is not what to prescribe!
March 28, 2018, 02:53:10 AM
And in conjunction, I would like to offer my part of the contribution, a manual switch rule to avoid long interval mining on short profit spikes via API, a crude workaround, but it works a treat and avoids potential double digit profit loss is important priority in current bear market
https://bitcointalksearch.org/topic/awesome-miner-api-plugin-profit-spike-fake-profit-guard-need-diy-3210119
All credits goes to Patrike for providing Awesome Miner Software and @soothaa for the inspiration from his Coin Updater Plugin.
https://bitcointalksearch.org/topic/awesome-miner-api-plugin-profit-spike-fake-profit-guard-need-diy-3210119
All credits goes to Patrike for providing Awesome Miner Software and @soothaa for the inspiration from his Coin Updater Plugin.
March 28, 2018, 02:47:50 AM
Patrike,
Anyway we can do some brainstorming together on a way to improve the Profit Switching mode of the software?
If i understand NemoMiner, basically its logging the 24hr est, 24hr actual, and Current est, then its doing a calculation to figure out a running offset.. then applying it to smooth out the outlier spikes in profit that result in poor actual pay.
Example:
x17:
Current: 0.01523 *which is based on current sharerate and exchange price
24hr Est: 0.01853 *which is a projection of the next 24hrs based on the current exchange rate
24hr Actual: 0.01544 *which is based on actual payouts from past 24hrs of exchanged coins
Trust:
(3/26/2018 0500EST 24hr Est:) - (3/27/2018 0500EST 24hr actual) = Trust 24hr Offset
Example:
(0.01853)-(0.01544)=0.00309 Difference of 16.7%
So on the profit switching list,
it will compare the current price with a running offset to determine if its worth switching to, because if the current est... greater than the 16.7% current offset, than its more likely it will actually payout more.
Then the next day lets say the new next 24hr trust offset is 17.0%, it does an averaging
16.7 and 17.0 for an average running offset of 16.85% and so far as time of the software collects data.
One thing i noticed on nemo's is if the offset places the coin below the 24hr actual, it defaults to 24hr actual price on the list for profit switching.
Basically, the trust offset in nemo miner is just saying hey, this is the expected amount of drop in value on this algo after all the peeps switch over to catch the spikes in high current payout and its actually exchanged for payout to peeps. The part i dont know how it does it is how it is taking into account current prices to this trust offset to mix those values into the calculations, thus why i suggest some brainstorming by the masses to figure out a good way of doing this.
Thanks for your feedback. I'm very much open for a discussion on this topic.Anyway we can do some brainstorming together on a way to improve the Profit Switching mode of the software?
If i understand NemoMiner, basically its logging the 24hr est, 24hr actual, and Current est, then its doing a calculation to figure out a running offset.. then applying it to smooth out the outlier spikes in profit that result in poor actual pay.
Example:
x17:
Current: 0.01523 *which is based on current sharerate and exchange price
24hr Est: 0.01853 *which is a projection of the next 24hrs based on the current exchange rate
24hr Actual: 0.01544 *which is based on actual payouts from past 24hrs of exchanged coins
Trust:
(3/26/2018 0500EST 24hr Est:) - (3/27/2018 0500EST 24hr actual) = Trust 24hr Offset
Example:
(0.01853)-(0.01544)=0.00309 Difference of 16.7%
So on the profit switching list,
it will compare the current price with a running offset to determine if its worth switching to, because if the current est... greater than the 16.7% current offset, than its more likely it will actually payout more.
Then the next day lets say the new next 24hr trust offset is 17.0%, it does an averaging
16.7 and 17.0 for an average running offset of 16.85% and so far as time of the software collects data.
One thing i noticed on nemo's is if the offset places the coin below the 24hr actual, it defaults to 24hr actual price on the list for profit switching.
Basically, the trust offset in nemo miner is just saying hey, this is the expected amount of drop in value on this algo after all the peeps switch over to catch the spikes in high current payout and its actually exchanged for payout to peeps. The part i dont know how it does it is how it is taking into account current prices to this trust offset to mix those values into the calculations, thus why i suggest some brainstorming by the masses to figure out a good way of doing this.
Awesome Miner already have access to these numbers, so making some adjustments to the profit switcher should be possible. Please give me a little more time to investigate before I get back with a longer response.
What I had in mind since before was that the Awesome Miner cloud could help out here to build this statistics trend, so you don't have to run Awesome Miner for a longer period of time to build the trust-level. It could be provided for you.
That's great! Yes, somewhere to store the historic data (exchange rate, difficulty evolution, daily actual earnings) and making switching decisions on such data would be tremendously helpful providing fairly reliable and intelligent feature to AM. Personally I'm in the process trying to automate and build my earnings record database...this would be part of the crucial data needed for a better switching algorithm IMHO (currently there isn't an algorithm, but more like a rule). Would love to see more awesome users input and collaborate with Patrike making AM absolutely awesome!
March 27, 2018, 11:29:32 PM
Patrike,
Anyway we can do some brainstorming together on a way to improve the Profit Switching mode of the software?
If i understand NemoMiner, basically its logging the 24hr est, 24hr actual, and Current est, then its doing a calculation to figure out a running offset.. then applying it to smooth out the outlier spikes in profit that result in poor actual pay.
Example:
x17:
Current: 0.01523 *which is based on current sharerate and exchange price
24hr Est: 0.01853 *which is a projection of the next 24hrs based on the current exchange rate
24hr Actual: 0.01544 *which is based on actual payouts from past 24hrs of exchanged coins
Trust:
(3/26/2018 0500EST 24hr Est:) - (3/27/2018 0500EST 24hr actual) = Trust 24hr Offset
Example:
(0.01853)-(0.01544)=0.00309 Difference of 16.7%
So on the profit switching list,
it will compare the current price with a running offset to determine if its worth switching to, because if the current est... greater than the 16.7% current offset, than its more likely it will actually payout more.
Then the next day lets say the new next 24hr trust offset is 17.0%, it does an averaging
16.7 and 17.0 for an average running offset of 16.85% and so far as time of the software collects data.
One thing i noticed on nemo's is if the offset places the coin below the 24hr actual, it defaults to 24hr actual price on the list for profit switching.
Basically, the trust offset in nemo miner is just saying hey, this is the expected amount of drop in value on this algo after all the peeps switch over to catch the spikes in high current payout and its actually exchanged for payout to peeps. The part i dont know how it does it is how it is taking into account current prices to this trust offset to mix those values into the calculations, thus why i suggest some brainstorming by the masses to figure out a good way of doing this.
Thanks for your feedback. I'm very much open for a discussion on this topic.Anyway we can do some brainstorming together on a way to improve the Profit Switching mode of the software?
If i understand NemoMiner, basically its logging the 24hr est, 24hr actual, and Current est, then its doing a calculation to figure out a running offset.. then applying it to smooth out the outlier spikes in profit that result in poor actual pay.
Example:
x17:
Current: 0.01523 *which is based on current sharerate and exchange price
24hr Est: 0.01853 *which is a projection of the next 24hrs based on the current exchange rate
24hr Actual: 0.01544 *which is based on actual payouts from past 24hrs of exchanged coins
Trust:
(3/26/2018 0500EST 24hr Est:) - (3/27/2018 0500EST 24hr actual) = Trust 24hr Offset
Example:
(0.01853)-(0.01544)=0.00309 Difference of 16.7%
So on the profit switching list,
it will compare the current price with a running offset to determine if its worth switching to, because if the current est... greater than the 16.7% current offset, than its more likely it will actually payout more.
Then the next day lets say the new next 24hr trust offset is 17.0%, it does an averaging
16.7 and 17.0 for an average running offset of 16.85% and so far as time of the software collects data.
One thing i noticed on nemo's is if the offset places the coin below the 24hr actual, it defaults to 24hr actual price on the list for profit switching.
Basically, the trust offset in nemo miner is just saying hey, this is the expected amount of drop in value on this algo after all the peeps switch over to catch the spikes in high current payout and its actually exchanged for payout to peeps. The part i dont know how it does it is how it is taking into account current prices to this trust offset to mix those values into the calculations, thus why i suggest some brainstorming by the masses to figure out a good way of doing this.
Awesome Miner already have access to these numbers, so making some adjustments to the profit switcher should be possible. Please give me a little more time to investigate before I get back with a longer response.
What I had in mind since before was that the Awesome Miner cloud could help out here to build this statistics trend, so you don't have to run Awesome Miner for a longer period of time to build the trust-level. It could be provided for you.
I've tested and used for several days Nemos Miner 3 and I do think that:
1) Nemos Miner has a lot more miners (10 ccminer forks for various miners and cuda versions to maximize hashrate+ high prfitability RVN x16r mining) and to select the best miner for each algo it will benchmark them all and use the best one with highest hash-rate (for 300 seconds and bench-marking is done in in mining mode, so earnings are nt lost, and important is that mining begins after benchmark is complete, and this is very useful when compared to AM that doesn't have this feature).
2) Nemos Miner has a better algorithm switching implementation using BrainPlus and EarningTracker with past statistics
Patrike, I recommend you to check their sourcecode and statistics files from /statistics folder to improve performance.
I started on the same pool both Awesome MIner and Nemos Miner and after 48 hours Nemos miner had a better real BTC payout than AM (never trust inflated statistics, always compare real BTC payments).
How you managed to get v3.0, ive only seen as high as 2.5.2 on his gethub
I am here to stick with AM, but for now im only using it mainly as a monitor for my rigs, this is a feature that nemo doesnt have currently that AM does, i just hope we can improve AM and make it way better so everyone comes to AM to help build up this community, i feel this software has far more potential.
Future things that would help AM is the ability to run it on Linux, this is something that 3 other common miners are already transitioning into, NemoMiner, MultipoolMiner, and WatchdogMiner are all partnering up with HiveOS to run on linux.... I think if a linux version of the remote awesome miner would be the first step in the right direction, still use the main program off windows, but allow the rigs to be on linux and communicate
March 27, 2018, 11:02:00 PM
Small bug: when I change cpuminer-opt to use cpuminer-avx2.exe, AM doesn't read the hash rate for blake2s or yescrypt.
Worked fine when left as the default sse2 miner.
Happens in 4.6.2 w/ cpuminer-opt 3.8.4.1
Worked fine when left as the default sse2 miner.
Happens in 4.6.2 w/ cpuminer-opt 3.8.4.1
March 27, 2018, 10:46:02 PM
Hi,
tried the suggestion to use the remote service, but still, Awesome miner is unable to see my rigs under DTSM miner 0.5.8, with or without telemtry option...
Anyone did manage to add them as external miners ? I can see them with the remote agent, but if i laucnh DTSM with AM it will crash, where if i let them run by themself no issues...
It seems there is a bug with Awesome miner and DTSM...
tried the suggestion to use the remote service, but still, Awesome miner is unable to see my rigs under DTSM miner 0.5.8, with or without telemtry option...
Anyone did manage to add them as external miners ? I can see them with the remote agent, but if i laucnh DTSM with AM it will crash, where if i let them run by themself no issues...
It seems there is a bug with Awesome miner and DTSM...
Right-click the miner, and select Diagnostics... post the result here.
March 27, 2018, 07:34:11 PM
Could anyone explain to me how to setup awesome miner with Zpool? I've tried to check Select BTC Payout option in Profit Switching, add c=BTC parameter in the password filed in Online Services fo Zpool (all algos), add c=BTC to command-line and to the Zpool template. Pool also show me right version of my miner and Extra c=BTC is correct. But payouts only in SYS coins. Of course I added BTC wallet address to the Zpool filed and the address is correct. What I'm doing wrong? How to make awesomeminer to work with Zpool correctly?
Anybody here
Also if your wallet on zpool is already identified as non BTC even if it is a valid BTC address, you'd best to go to zPool thread and post a correction request there, crackfoo is usually quite prompt with that sort of requests... kinda happens quite often (see for yourself in the pools thread)
Thank you too!
March 27, 2018, 07:26:36 PM
Could anyone explain to me how to setup awesome miner with Zpool? I've tried to check Select BTC Payout option in Profit Switching, add c=BTC parameter in the password filed in Online Services fo Zpool (all algos), add c=BTC to command-line and to the Zpool template. Pool also show me right version of my miner and Extra c=BTC is correct. But payouts only in SYS coins. Of course I added BTC wallet address to the Zpool filed and the address is correct. What I'm doing wrong? How to make awesomeminer to work with Zpool correctly?
Anybody here
Please use the Diagnostics button in the toolbar to see if "c=BTC" is passed to the mining software when started by Awesome Miner. If passed correctly, the problem is at zpool. If not passed correctly, please share the complete diagnostics output with me and I will investigate.
Thank you!
March 27, 2018, 04:03:19 PM
Patrike,
Anyway we can do some brainstorming together on a way to improve the Profit Switching mode of the software?
If i understand NemoMiner, basically its logging the 24hr est, 24hr actual, and Current est, then its doing a calculation to figure out a running offset.. then applying it to smooth out the outlier spikes in profit that result in poor actual pay.
Example:
x17:
Current: 0.01523 *which is based on current sharerate and exchange price
24hr Est: 0.01853 *which is a projection of the next 24hrs based on the current exchange rate
24hr Actual: 0.01544 *which is based on actual payouts from past 24hrs of exchanged coins
Trust:
(3/26/2018 0500EST 24hr Est:) - (3/27/2018 0500EST 24hr actual) = Trust 24hr Offset
Example:
(0.01853)-(0.01544)=0.00309 Difference of 16.7%
So on the profit switching list,
it will compare the current price with a running offset to determine if its worth switching to, because if the current est... greater than the 16.7% current offset, than its more likely it will actually payout more.
Then the next day lets say the new next 24hr trust offset is 17.0%, it does an averaging
16.7 and 17.0 for an average running offset of 16.85% and so far as time of the software collects data.
One thing i noticed on nemo's is if the offset places the coin below the 24hr actual, it defaults to 24hr actual price on the list for profit switching.
Basically, the trust offset in nemo miner is just saying hey, this is the expected amount of drop in value on this algo after all the peeps switch over to catch the spikes in high current payout and its actually exchanged for payout to peeps. The part i dont know how it does it is how it is taking into account current prices to this trust offset to mix those values into the calculations, thus why i suggest some brainstorming by the masses to figure out a good way of doing this.
Thanks for your feedback. I'm very much open for a discussion on this topic.Anyway we can do some brainstorming together on a way to improve the Profit Switching mode of the software?
If i understand NemoMiner, basically its logging the 24hr est, 24hr actual, and Current est, then its doing a calculation to figure out a running offset.. then applying it to smooth out the outlier spikes in profit that result in poor actual pay.
Example:
x17:
Current: 0.01523 *which is based on current sharerate and exchange price
24hr Est: 0.01853 *which is a projection of the next 24hrs based on the current exchange rate
24hr Actual: 0.01544 *which is based on actual payouts from past 24hrs of exchanged coins
Trust:
(3/26/2018 0500EST 24hr Est:) - (3/27/2018 0500EST 24hr actual) = Trust 24hr Offset
Example:
(0.01853)-(0.01544)=0.00309 Difference of 16.7%
So on the profit switching list,
it will compare the current price with a running offset to determine if its worth switching to, because if the current est... greater than the 16.7% current offset, than its more likely it will actually payout more.
Then the next day lets say the new next 24hr trust offset is 17.0%, it does an averaging
16.7 and 17.0 for an average running offset of 16.85% and so far as time of the software collects data.
One thing i noticed on nemo's is if the offset places the coin below the 24hr actual, it defaults to 24hr actual price on the list for profit switching.
Basically, the trust offset in nemo miner is just saying hey, this is the expected amount of drop in value on this algo after all the peeps switch over to catch the spikes in high current payout and its actually exchanged for payout to peeps. The part i dont know how it does it is how it is taking into account current prices to this trust offset to mix those values into the calculations, thus why i suggest some brainstorming by the masses to figure out a good way of doing this.
Awesome Miner already have access to these numbers, so making some adjustments to the profit switcher should be possible. Please give me a little more time to investigate before I get back with a longer response.
What I had in mind since before was that the Awesome Miner cloud could help out here to build this statistics trend, so you don't have to run Awesome Miner for a longer period of time to build the trust-level. It could be provided for you.
I've tested and used for several days Nemos Miner 3 and I do think that:
1) Nemos Miner has a lot more miners (10 ccminer forks for various miners and cuda versions to maximize hashrate+ high prfitability RVN x16r mining) and to select the best miner for each algo it will benchmark them all and use the best one with highest hash-rate (for 300 seconds and bench-marking is done in in mining mode, so earnings are nt lost, and important is that mining begins after benchmark is complete, and this is very useful when compared to AM that doesn't have this feature).
2) Nemos Miner has a better algorithm switching implementation using BrainPlus and EarningTracker with past statistics
Patrike, I recommend you to check their sourcecode and statistics files from /statistics folder to improve performance.
I started on the same pool both Awesome MIner and Nemos Miner and after 48 hours Nemos miner had a better real BTC payout than AM (never trust inflated statistics, always compare real BTC payments).
March 27, 2018, 03:51:34 PM
Anayone seen this bug ?
dual mining ether + blakes2
One coin + blake2s listed as 0.42 €
Other cains same algo + blake s2 listed as 0.03 €
should not second algo be same with all coins ?
See attached image..
http://www.bla-bla.net/blakes2.png
dual mining ether + blakes2
One coin + blake2s listed as 0.42 €
Other cains same algo + blake s2 listed as 0.03 €
should not second algo be same with all coins ?
See attached image..
http://www.bla-bla.net/blakes2.png
March 27, 2018, 12:58:16 PM
Hi,
tried the suggestion to use the remote service, but still, Awesome miner is unable to see my rigs under DTSM miner 0.5.8, with or without telemtry option...
Anyone did manage to add them as external miners ? I can see them with the remote agent, but if i laucnh DTSM with AM it will crash, where if i let them run by themself no issues...
It seems there is a bug with Awesome miner and DTSM...
tried the suggestion to use the remote service, but still, Awesome miner is unable to see my rigs under DTSM miner 0.5.8, with or without telemtry option...
Anyone did manage to add them as external miners ? I can see them with the remote agent, but if i laucnh DTSM with AM it will crash, where if i let them run by themself no issues...
It seems there is a bug with Awesome miner and DTSM...
March 27, 2018, 10:27:56 AM
I've got a new rig and for some reason I'm not able to benchmark anything with Excavator (the new version). I keep getting the error:
Thanks for reporting this issue. A correction will soon be made available.Thanks for the quick fix. I saw this note in the Excavator 1.5.0 alpha release notes today:
Code:
From version 1.5.0a further excavator supports only NiceHash stratum servers. Stratum servers are available at:
nhmp.LOCATION.nicehash.com (LOCATION: eu, usa, hk, jp, in, br).
nhmp.LOCATION.nicehash.com (LOCATION: eu, usa, hk, jp, in, br).
https://github.com/nicehash/excavator/releases/tag/v1.5.0a
I'm guessing that without some hostfile changes to fake out the DNS lookup we'll not be able to use excavator with other pools anymore.
March 27, 2018, 10:16:44 AM
Couple small bugs I've noticed. On my CPU miner after todays update it's showing $0 profitability, and in the cpu tab it says hashrate of 0 for the processors, but the mining program is showing the hashrate and accepted shares, and that all looks normal from that end. Also, since a couple updates ago when my Baikal miners are mining on Zergpool they list the profit as $0, now the weird thing with that is that probably 75% of the time if I look at the list it will have the profit for my GPU rig, my CPU rig (well, not anymore since todays update), and one Baikal I have set to only mine at Nicehash. The other 3 Baikals don't show the profit (Just show 0) BUT, if you subtract what IS listed from the total at the top right, you can figure out the profit for the 3 Baikals showing the 0s, so somewhere Awesome Miner IS receiving the profit amounts, just they aren't being displayed on the individual miners profiles. I've been doing the math in my head, but obviously it would be better to not have to do that constantly. Thank you for all the hard work! Looking forward to the profit switching optimization that is being discussed. Have a great day, and again, thank you!
March 27, 2018, 08:47:33 AM
Hi Patrike,
can you implement Raven miner so X16r algo can be minable, please?
Same for some new algos which you have added in the excelent AWM 4.6.1, please
Thank you a lot.
can you implement Raven miner so X16r algo can be minable, please?
Same for some new algos which you have added in the excelent AWM 4.6.1, please
Thank you a lot.
Try this without having to wait:
http://www.awesomeminer.com/help/managedsoftware.aspx
get software here:
https://bitcointalksearch.org/topic/--2752467
March 27, 2018, 08:28:20 AM
Hi Patrike,
can you implement Raven miner so X16r algo can be minable, please?
Same for some new algos which you have added in the excelent AWM 4.6.1, please
Thank you a lot.
can you implement Raven miner so X16r algo can be minable, please?
Same for some new algos which you have added in the excelent AWM 4.6.1, please
Thank you a lot.
March 27, 2018, 07:48:17 AM
Patrike,
Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
Awesome Miner is not doing anything for this scenario and simply assuming that zpool will go for BTC if nothing is specified explicitly. Awesome Miner do not specify payout coin at all, so this must be investigated from a zpool point of view.Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
The zpool instructions have always been a bit unclear on this.
Quote
-o stratum+tcp://
You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk
Awesome Miner is setting the Bitcoin wallet address the user specified. I interpret that you can specify any coin for payout, but that specifying like that is "at your own risk". For that reason, Awesome Miner is not specifying this "c=" parameter. In the past zpool always went for Bitcoin payouts in that scenario.
You can still configure Awesome Miner to add this parameter if you want (via Options dialog, Online Services, modify the zpool entries and add command line "-p c=ABC" or similar).
Further reading on zpool instructions:
Quote
c= doesn't always work
This is yet another reason why Awesome Miner isn't trying to set this parameter at all.Can you please make this option more visible or even required? 99% of the time having the proper c=BTC set (or whatever symbol is for the wallet their using) will choose BTC. As it is now.... it's 50/50 with nothing set.
Could anyone explain to me how to setup awesome miner with Zpool? I've tried to check Select BTC Payout option in Profit Switching, add c=BTC parameter in the password filed in Online Services fo Zpool (all algos), add c=BTC to command-line and to the Zpool template. Pool also show me right version of my miner and Extra c=BTC is correct. But payouts only in SYS coins. Of course I added BTC wallet address to the Zpool filed and the address is correct. What I'm doing wrong? How to make awesomeminer to work with Zpool correctly?
Anybody here
Also if your wallet on zpool is already identified as non BTC even if it is a valid BTC address, you'd best to go to zPool thread and post a correction request there, crackfoo is usually quite prompt with that sort of requests... kinda happens quite often (see for yourself in the pools thread)
March 27, 2018, 06:33:50 AM
Patrike,
Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
Awesome Miner is not doing anything for this scenario and simply assuming that zpool will go for BTC if nothing is specified explicitly. Awesome Miner do not specify payout coin at all, so this must be investigated from a zpool point of view.Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
The zpool instructions have always been a bit unclear on this.
Quote
-o stratum+tcp://
You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk
Awesome Miner is setting the Bitcoin wallet address the user specified. I interpret that you can specify any coin for payout, but that specifying like that is "at your own risk". For that reason, Awesome Miner is not specifying this "c=" parameter. In the past zpool always went for Bitcoin payouts in that scenario.
You can still configure Awesome Miner to add this parameter if you want (via Options dialog, Online Services, modify the zpool entries and add command line "-p c=ABC" or similar).
Further reading on zpool instructions:
Quote
c= doesn't always work
This is yet another reason why Awesome Miner isn't trying to set this parameter at all.Can you please make this option more visible or even required? 99% of the time having the proper c=BTC set (or whatever symbol is for the wallet their using) will choose BTC. As it is now.... it's 50/50 with nothing set.
Could anyone explain to me how to setup awesome miner with Zpool? I've tried to check Select BTC Payout option in Profit Switching, add c=BTC parameter in the password filed in Online Services fo Zpool (all algos), add c=BTC to command-line and to the Zpool template. Pool also show me right version of my miner and Extra c=BTC is correct. But payouts only in SYS coins. Of course I added BTC wallet address to the Zpool filed and the address is correct. What I'm doing wrong? How to make awesomeminer to work with Zpool correctly?
Anybody here
Please use the Diagnostics button in the toolbar to see if "c=BTC" is passed to the mining software when started by Awesome Miner. If passed correctly, the problem is at zpool. If not passed correctly, please share the complete diagnostics output with me and I will investigate.
March 27, 2018, 06:08:15 AM
Patrike,
Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
Awesome Miner is not doing anything for this scenario and simply assuming that zpool will go for BTC if nothing is specified explicitly. Awesome Miner do not specify payout coin at all, so this must be investigated from a zpool point of view.Can you check out the code in Awesome Miner for a bug.
Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.
The zpool instructions have always been a bit unclear on this.
Quote
-o stratum+tcp://
You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk
Awesome Miner is setting the Bitcoin wallet address the user specified. I interpret that you can specify any coin for payout, but that specifying like that is "at your own risk". For that reason, Awesome Miner is not specifying this "c=" parameter. In the past zpool always went for Bitcoin payouts in that scenario.
You can still configure Awesome Miner to add this parameter if you want (via Options dialog, Online Services, modify the zpool entries and add command line "-p c=ABC" or similar).
Further reading on zpool instructions:
Quote
c= doesn't always work
This is yet another reason why Awesome Miner isn't trying to set this parameter at all.Can you please make this option more visible or even required? 99% of the time having the proper c=BTC set (or whatever symbol is for the wallet their using) will choose BTC. As it is now.... it's 50/50 with nothing set.
Could anyone explain to me how to setup awesome miner with Zpool? I've tried to check Select BTC Payout option in Profit Switching, add c=BTC parameter in the password filed in Online Services fo Zpool (all algos), add c=BTC to command-line and to the Zpool template. Pool also show me right version of my miner and Extra c=BTC is correct. But payouts only in SYS coins. Of course I added BTC wallet address to the Zpool filed and the address is correct. What I'm doing wrong? How to make awesomeminer to work with Zpool correctly?
Anybody here
March 27, 2018, 05:57:41 AM
This is a minor update.
Awesome Miner version 4.6.2
- Added more images for popular coins
- Improved sorting and scrolling during updates of the Coins and Online Services lists.
- XMRig miner 2.5.2
- CpuMiner-Opt 3.8.4.1
- Correction to benchmarking of Excavator miner
Awesome Miner version 4.6.2
- Added more images for popular coins
- Improved sorting and scrolling during updates of the Coins and Online Services lists.
- XMRig miner 2.5.2
- CpuMiner-Opt 3.8.4.1
- Correction to benchmarking of Excavator miner
Jump to: