Used to mine Litecoin on ASIC. Frankly, the yield per day did not exceed 12 $, and taking into account the cost of electricity - 8 $, not thick!
Now I'm thinking about the mastenodes, i've been watching the news about them for a while now. I'm trying to choose from three: GoByte, Zest and LUX.
Still, I'm looking towards the first coin - it's too tempting to hear the latest news about the decline in the cost of the transaction and the increase in profits for the owners of masternodes, which is not the case with other coins - they promise 70% of the award against 30% to the miners. It sounds attractive, and GoByte is not just another scam project - they've already collected the funds and the product is working. Guys, I need you help! Which coin would you prefer from these three and why?
Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 14. (Read 289466 times)
I haven't seen a new version released for a while, should we just be downloading the master from github as I see changed have been made.
Thanks!
Thanks!
Is there any way to manually choose what algos to be mined from each pool?
I tried to tweek some files inside the config folder but even though I deleted some algos from the list under the pool's name, it kept loading those algos when I start Nemos.
Maybe it's taking the list in a dynamic way when it connects to each pool. Does anyone in which file is this coded? I could try manually change the code in order to read the pool-algos file.
I tried to tweek some files inside the config folder but even though I deleted some algos from the list under the pool's name, it kept loading those algos when I start Nemos.
Maybe it's taking the list in a dynamic way when it connects to each pool. Does anyone in which file is this coded? I could try manually change the code in order to read the pool-algos file.
any news about linux version?
ccminerx16r-x16s
Shame those just cause errors and reboots on 6*1080ti rigs
something about memory, before ccminer throws a wobbly, and if not manually terminated will crash sys
Tried latest, and then master, same issue.
Works fine when those are deleted from the list.
Shame those just cause errors and reboots on 6*1080ti rigs
something about memory, before ccminer throws a wobbly, and if not manually terminated will crash sys
Tried latest, and then master, same issue.
Works fine when those are deleted from the list.
- ETHlargement tool --> supposed to boosts ETH mining
Just run it, doesn't need to be built into miner
Any chance that you'll add support for these?
- ETHlargement tool --> supposed to boost ETH mining
- DelosMiner --> performs very good on Phi, Skunk, and some more
- ETHlargement tool --> supposed to boost ETH mining
- DelosMiner --> performs very good on Phi, Skunk, and some more
@MaxiMan Thanks for trying Blazepool. Switching more with the current estimates is as expected and is the mechanism that will net you more profit on average in the long run on Blazepool. You'll notice from your log that for larger algos like x17 or x16r, your rig usually stays on the algo for 10 to 20 minutes, this is the correct behavior as the diff dip on these algo lasts longer. Whereas for algos like tribus and neoscrypt it usually exits after the first round.
Blazepool
Blazepool
This month i decided to jump to Blazepool, they recommend use the Normal Estimates, just in my first 12 Hours i got a lot of switching!
Interval set to 120s, ActMinerGain 5%
It is fine on this pool? or should i make lower switching rates? Like inc Intervals...etc
Interval set to 120s, ActMinerGain 5%
Code:
"date","algo","wallet","username","Stratum"
"01/06/2018 12:05:45 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 12:10:28 a.m.","Keccakc","","nemo","stratum+tcp://keccakc.mine.blazepool.com:5134"
"01/06/2018 12:21:28 a.m.","X17","","nemo","stratum+tcp://x17.mine.blazepool.com:3737"
"01/06/2018 12:24:08 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 12:41:33 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 12:58:48 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 01:01:28 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 01:06:12 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 01:19:17 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 01:46:59 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 01:49:39 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 02:11:07 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 02:17:57 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 02:24:45 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 02:27:26 a.m.","NeoScrypt","","nemo","stratum+tcp://neoscrypt.mine.blazepool.com:4233"
"01/06/2018 02:28:13 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 02:30:58 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 02:51:20 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 02:54:01 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 03:05:03 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 03:09:51 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 03:29:21 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 03:34:05 a.m.","Xevan","","nemo","stratum+tcp://xevan.mine.blazepool.com:3739"
"01/06/2018 03:47:16 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 03:54:17 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 03:59:26 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 04:00:59 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 04:06:09 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 04:10:53 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 04:13:34 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 04:24:33 a.m.","Keccakc","","nemo","stratum+tcp://keccakc.mine.blazepool.com:5134"
"01/06/2018 04:28:32 a.m.","X17","","nemo","stratum+tcp://x17.mine.blazepool.com:3737"
"01/06/2018 04:37:26 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 04:38:03 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 04:44:52 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 04:47:32 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 05:00:38 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 05:01:16 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 05:20:36 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 05:23:18 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 05:34:16 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 05:45:16 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 05:54:10 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 05:57:10 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 06:06:04 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 06:12:52 a.m.","Xevan","","nemo","stratum+tcp://xevan.mine.blazepool.com:3739"
"01/06/2018 06:21:46 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 06:41:08 a.m.","Xevan","","nemo","stratum+tcp://xevan.mine.blazepool.com:3739"
"01/06/2018 06:41:45 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 06:48:33 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 06:53:17 a.m.","X17","","nemo","stratum+tcp://x17.mine.blazepool.com:3737"
"01/06/2018 07:08:28 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 07:15:17 a.m.","Keccakc","","nemo","stratum+tcp://keccakc.mine.blazepool.com:5134"
"01/06/2018 07:24:10 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 07:28:55 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 07:40:05 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 07:40:42 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 07:45:26 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 07:58:31 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 08:03:15 a.m.","X17","","nemo","stratum+tcp://x17.mine.blazepool.com:3737"
"01/06/2018 08:12:12 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 08:14:52 a.m.","Keccakc","","nemo","stratum+tcp://keccakc.mine.blazepool.com:5134"
"01/06/2018 08:19:36 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 08:24:20 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 08:33:14 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 08:42:07 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 09:03:34 a.m.","Xevan","","nemo","stratum+tcp://xevan.mine.blazepool.com:3739"
"01/06/2018 09:04:11 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 09:15:13 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 09:19:57 a.m.","X17","","nemo","stratum+tcp://x17.mine.blazepool.com:3737"
"01/06/2018 09:33:02 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 09:41:55 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 09:44:36 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 09:47:16 a.m.","Lyra2z","","nemo","stratum+tcp://lyra2z.mine.blazepool.com:4553"
"01/06/2018 10:02:26 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 10:09:15 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 10:26:34 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 10:33:22 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 10:38:05 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 10:59:32 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 11:02:13 a.m.","Tribus","","nemo","stratum+tcp://tribus.mine.blazepool.com:8533"
"01/06/2018 11:02:50 a.m.","X17","","nemo","stratum+tcp://x17.mine.blazepool.com:3737"
"01/06/2018 11:18:00 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 11:37:22 a.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 11:37:59 a.m.","Lyra2RE2","","nemo","stratum+tcp://lyra2v2.mine.blazepool.com:4533"
"01/06/2018 11:40:40 a.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 11:55:51 a.m.","Skein","","nemo","stratum+tcp://skein.mine.blazepool.com:4933"
"01/06/2018 12:00:33 p.m.","HMQ1725","","nemo","stratum+tcp://hmq1725.mine.blazepool.com:3747"
"01/06/2018 12:01:10 p.m.","X16r","","nemo","stratum+tcp://x16r.mine.blazepool.com:3636"
"01/06/2018 12:14:14 p.m.","NeoScrypt","","nemo","stratum+tcp://neoscrypt.mine.blazepool.com:4233"
"01/06/2018 12:16:54 p.m.","C11","","nemo","stratum+tcp://c11.mine.blazepool.com:3573"
It is fine on this pool? or should i make lower switching rates? Like inc Intervals...etc
Making some tests in last 3 days:
blazepool is better than ahashpool
nicehash is better than blazepool ...
Maybe its up to per day stats because I use 1 rig mining for 24h.
blazepool is better than ahashpool
nicehash is better than blazepool ...
Maybe its up to per day stats because I use 1 rig mining for 24h.
The difference with nicehash is you get the balance instantly as you mine, while other pools need to mature and exchange the mined coin blocks
Also i doubt nicehash better it doenst have the newer profitable algos.
Making some tests in last 3 days:
blazepool is better than ahashpool
nicehash is better than blazepool ...
Maybe its up to per day stats because I use 1 rig mining for 24h.
blazepool is better than ahashpool
nicehash is better than blazepool ...
Maybe its up to per day stats because I use 1 rig mining for 24h.
I have to add that the GPU monitor stops running after several hours, it just closes without apparent reason.
This happens to me too. I tried to make the .bat restart itself if the monitor closes with Windows Task Scheduler, but I can't seem to make it work properly.
I have to add that the GPU monitor stops running after several hours, it just closes without apparent reason.
Im having serious issues when this message appears on log
The other day it stopped of contact with the pool and keep retrying, until i restarted the miner, more than 12 hours lost
https://screenshotscdn.firefoxusercontent.com/images/c3dd058c-031a-4195-abb4-4bc8cfa8261a.png
Im using Zergpool, this started from last week, i kept miners updated.
Code:
Finding available TCP Port
[color=red]PS>ErrorTerminación(New-Object): "Excepción al llamar a ".ctor" con los argumentos "2": "No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión 127.0.0.1:4068""[/color]
Miners API Port: 4068
Starting Brains for Plus...
Starting Earnings Tracker...
Starting Cycle
Loading BTC rate from 'api.coinbase.com'..
Loading pool stats..
Computing pool stats..
Loading miners..
Comparing miners and pools..
Starting miner
The other day it stopped of contact with the pool and keep retrying, until i restarted the miner, more than 12 hours lost
Code:
--------------------------------------------------------------------------------
Stats ' Lyra2z ' -> 5.84 MH after 1611 sec
Sleeping 120
Starting Cycle
Stats ' Lyra2z ' -> 5.84 MH after 1732 sec
Loading BTC rate from 'api.coinbase.com'..
Loading pool stats..
PS>ErrorTerminación(Invoke-RestMethod): "La operación sobrepasó el tiempo de espera."
Computing pool stats..
[color=red]Error contacting pool, retrying..[/color]
Starting Cycle
Stats ' Lyra2z ' -> 5.84 MH after 1772 sec
Loading BTC rate from 'api.coinbase.com'..
Loading pool stats..
Computing pool stats..
Loading miners..
Comparing miners and pools..
Idle: 9
https://screenshotscdn.firefoxusercontent.com/images/c3dd058c-031a-4195-abb4-4bc8cfa8261a.png
Im using Zergpool, this started from last week, i kept miners updated.
After several hours 3.1 borks - all miners "fail" to start. after reboot it all works again
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
I have the same issue but not with "all" miners. It's just some miners failing. I don't know if it's always the same miner but DSTM (for zcash) was surely one that failed to start after hours of mining.
By the way I have made my "HashRate" files inside the "Stats" folder read-only. Sometimes I run two instances of the miner for two different groups of cards, but if I don't have the files in read-only weird things happen when for example there are two instances of CCminers running.
I would highly advise you to use two copies of NemosMiner in two different base directories if you're trying to run them simultaneously (i.e. C:\NemosMiner and C:\NemosMiner2). You'll run into all sorts of weirdness otherwise, with conflicting config files, pool stats, miner stats. Given you likely want to tune the miners to the distinct groups of cards (assuming they are different hardware), this would allow you more flexibility.
After several hours 3.1 borks - all miners "fail" to start. after reboot it all works again
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
I have the same issue but not with "all" miners. It's just some miners failing. I don't know if it's always the same miner but DSTM (for zcash) was surely one that failed to start after hours of mining.
By the way I have made my "HashRate" files inside the "Stats" folder read-only. Sometimes I run two instances of the miner for two different groups of cards, but if I don't have the files in read-only weird things happen when for example there are two instances of CCminers running.
After several hours 3.1 borks - all miners "fail" to start. after reboot it all works again
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
Monitoring - Remote adjustments
Hello all, I'm currently using HiveOS because it's easier to manage remotely. I can change waller ang algo and view monitoring.
However I'm missing the auto algo switching.
If i wish to use nemosminer, will i be able to control / monitor this remotely and if yes how?
Hello all, I'm currently using HiveOS because it's easier to manage remotely. I can change waller ang algo and view monitoring.
However I'm missing the auto algo switching.
If i wish to use nemosminer, will i be able to control / monitor this remotely and if yes how?
The updated version of emosminer 1.3.0 improves the performance of skins. Nemosminer v1.4.1 has support for sib.
any recent comparison with ahashpool ?
Jump to: