Bugfixes on lolminer compatibility:
1. Miner supports all c29 variants (29,d,m) and c31
2. Miner uses this format of algo support. I think it is done internally in AM and not via miner properties-command line arg. Adding support to do this via the deafult/user defined command line args would help
--coin
--coin sets the coin you want to mine, e.g. BEAM,AION,BTG,...
...
3. Hashrates are not properly parsed in decimal from the api. The api gives proper 1.2 as values, but is parsed and displayed as 1 in am.
Thanks for the details! There were a number of hardcoded mappings for Lolminer as it had a bit special concept for specifying algorithms - as it's typically the coin name you specify. I will change this to be more flexible where you can use the standard algorithm configuration for Lolminer as well.
I will also correct the hashrate reporting.
Hey, this still has some hardcoded mapping. MWC coin runs with --coin MWC instead of the standard algorithm overrides.
Algo : C29D : MWC-C29D
Rest of the C29M, C31, C32 work fine
Can you please double check if you manually added "--coin MWC" or "MWC" somewhere like below?
1) In the Properties of your pool, command line.
2) Options dialog, Managed Software section, lolMiner algorithm mapping.
When looking at how lolMiner is started by Awesome Miner, there are no hard coded coins. If I'm wrong - please let me know.
MWC is mined with C31 and C29D algos.
For lolminer, AM doesnt have builtin algo mapping for C29D algo, so adding custom mapping as MWC-C29D.
Then starting the miner with no parameters in diagnostics shows, miner started with --coin MWC instead of the custom mapped --coin MWC-C29D
Each time a new algo is added, AM need to be updated from your side...
Can you pls make it more dynamic in the coin properties.
Miner supports the common -a configuration like any other miner, the AM is still using the old --coin hard mappings.
Suggestion:
1. Make -c [ --coin ] dynamic
List of supported coin presets:
Preset Coin Algorithm
AION Aion Equihash 210/9
AUTO144_5 Equihash Pool Selection Equihash 144/5
AUTO192_7 Equihash Pool Selection Equihash 192/7
BEAM BEAM BeamHash III
BTCZ BitcoinZ Equihash 144/5
BTG Bitcoin Gold Equihash 144/5
CTXC Cortex Ai Cuckaroo 30 CTXC
EXCC Exchange Coin Equihash 144/5 (EXCC)
GRIN-C29M Grin CuckarooM 29
GRIN-C32 Grin Cuckatoo 32
MWC-C29D MimbleWimbleCoin CuckarooD 29
MWC-C31 MimbleWimbleCoin Cuckatoo 31
XSG Snowgem Equihash 144/5
YEC YCash Equihash 192/7
ZCL Zclassic Equihash 192/7
ZEL Zel Cash ZelHash
ZER Zero Equihash 192/7
[OR] 2. Switch to -a [ --algo ]
List of supported algorithms:
Parameter Algorithm Fee % Needs / Supports --pers
BEAM-I BeamHash I 1.0 true
BEAM-II BeamHash II 1.0 false
BEAM-III BeamHash III 1.0 false
C29AE Cuckoo 29 2.0 false
C29D CuckarooD 29 2.0 false
C29M CuckarooM 29 2.0 false
C30CTX Cuckaroo 30 CTXC 2.5 false
C31 Cuckatoo 31 2.0 false
C32 Cuckatoo 32 2.0 false
CR29-32 Cuckaroo 29-32 1.0 false
CR29-40 Cuckaroo 29-40 1.0 false
CR29-48 Cuckaroo 29-48 2.0 false
EQUI144_5 Equihash 144/5 1.0 true
EQUI192_7 Equihash 192/7 1.0 true
EQUI210_9 Equihash 210/9 1.0 false
ZEL ZelHash 1.0 true
Thanks for the feedback. Using the algorithm-approach is probably the best way forward, as these are fully configurable for you as well. I will look into this.