Pages:
Author

Topic: 🔥🔥🔥Blazepool on FIRE🔥180+ coins🔥well established🔥multi-algo switching pool - page 4. (Read 20749 times)

newbie
Activity: 85
Merit: 0
@Jaerun  Several users did report on the difference of displayed hashrate.  The pool calculates the hashrate to display by the shares submitted and it's done just like all other algo.  We suspect a bug somewhere with the display of the rate only; your shares and payouts are not affected; this is confirmed by users' posting on the discord verifying the payout matches their hashrates.  We are still searching for that display bug though; would be great if anyone can give us a pointer to it too.  Will keep you guys posted.

Yesterday the 24 actual profitability for Lyra2Rev2 was around .00700.  The current estimate jumped from .004 to .185.  I left my rig mining Lyra2Rev2 for 10 hours on BlazePool.  The expected profit during that time (based on the 24 actual) was .00128 btc (440*.007*10/24), or .128 mBTC/hr.  Instead I made .000619 -- .0619 mBtc/hr -- a little more than half what was expected.  The remainder of the day I left my rig on NiceHash, Lyra2Rev2.  In 13 hours I made .00174 -- 133 mBTC/hr.  

Either your display bug is showing half my mining rate and double the estimated return, or only half of my rate is being counted for some reason.  In any event, I wont be mining Lyra on BlazePool until that is fixed.

-J

Well, some estimations doesn´t look so accurate:
Code:
Miner                Algorithm       Speed mBTC/Day BTC/Day USD/Day BTC/GH/Day
-----                ---------       ----- -------- ------- ------- ----------
ccminerx16s          HMQ1725    14.13 MH/s    3.171 0.00317  23.463    0.22435
ccminerAlexis78      Hsr        36.40 MH/s    0.859 0.00086   6.358    0.02360
enemyzealot1.10      X16r       35.97 MH/s    0.743 0.00074   5.497    0.02065
ccminerx16s          Hsr        31.07 MH/s    0.733 0.00073   5.426    0.02360
ccminerTpruvot       Lyra2z      6.38 MH/s    0.714 0.00071   5.282    0.11194
enemyzealot1.10      Phi        64.22 MH/s    0.626 0.00063   4.629    0.00974
ccminerAlexis78      Lyra2RE2  130.77 MH/s    0.625 0.00063   4.627    0.00478
ccminerTpruvot       Phi        60.87 MH/s    0.593 0.00059   4.388    0.00974
ccminerAlexis78      Keccakc     2.40 GH/s    0.587 0.00059   4.344    0.00024
enemyzealot1.10      Bitcore    58.04 MH/s    0.518 0.00052   3.835    0.00893
ccminerAlexis78      C11        52.45 MH/s    0.423 0.00042   3.132    0.00807
ccminerTpruvotskunk  Skunk      98.43 MH/s    0.406 0.00041   3.007    0.00413
ccminerAlexis78      X17        33.69 MH/s    0.384 0.00038   2.841    0.01139
ccminerKlausT        NeoScrypt   2.50 MH/s    0.377 0.00038   2.787    0.15068
ccminerAlexis78      Skein       1.72 GH/s    0.374 0.00037   2.767    0.00022
ccminerSphash        Skein       1.70 GH/s    0.369 0.00037   2.732    0.00022
ccminerAlexis78xevan Xevan      10.36 MH/s    0.346 0.00035   2.557    0.03334
enemyzealot1.10      X16s       32.72 MH/s    0.316 0.00032   2.342    0.00967
enemyzealot1.10      Tribus    206.81 MH/s    0.252 0.00025   1.864    0.00122
ccminerKlausT        Yescrypt   35.64 KH/s    0.246 0.00025   1.817    6.89040
ccminerAlexis78      Nist5     145.80 MH/s    0.029 0.00003   0.214    0.00020

Just taken a minute ago, for my average of 0.00053 BTC/day these values look like doubled (Ignore that ridiculous HMQ peak).
Since Im using Nemosminer, i could add Pricepenaltyfactor again, just as on my previous pool

EDIT: 5 minutes later...
Code:
Miner                Algorithm       Speed mBTC/Day BTC/Day USD/Day BTC/GH/Day
-----                ---------       ----- -------- ------- ------- ----------
ccminerAlexis78      Lyra2RE2  130.77 MH/s    1.275 0.00128   9.459    0.00975
ccminerAlexis78xevan Xevan      10.36 MH/s    0.969 0.00097   7.185    0.09346
enemyzealot1.10      X16r       35.38 MH/s    0.731 0.00073   5.419    0.02065
ccminerTpruvot       Lyra2z      6.38 MH/s    0.639 0.00064   4.743    0.10028
enemyzealot1.10      Bitcore    58.04 MH/s    0.518 0.00052   3.845    0.00893
ccminerTpruvotskunk  Skunk      98.43 MH/s    0.510 0.00051   3.781    0.00518
ccminerx16s          HMQ1725    14.13 MH/s    0.509 0.00051   3.777    0.03603
ccminerKlausT        NeoScrypt   2.50 MH/s    0.499 0.00050   3.700    0.19953
ccminerAlexis78      Keccakc     2.40 GH/s    0.496 0.00050   3.677    0.00021
ccminerAlexis78      Hsr        36.40 MH/s    0.414 0.00041   3.074    0.01139
ccminerAlexis78      X17        33.69 MH/s    0.400 0.00040   2.967    0.01187
ccminerx16s          Hsr        31.07 MH/s    0.354 0.00035   2.624    0.01139
enemyzealot1.10      Phi        64.22 MH/s    0.346 0.00035   2.565    0.00539
ccminerAlexis78      Skein       1.72 GH/s    0.340 0.00034   2.521    0.00020
ccminerSphash        Skein       1.70 GH/s    0.336 0.00034   2.490    0.00020
ccminerAlexis78      C11        52.45 MH/s    0.333 0.00033   2.473    0.00636
ccminerTpruvot       Phi        60.87 MH/s    0.328 0.00033   2.432    0.00539
enemyzealot1.10      X16s       32.72 MH/s    0.316 0.00032   2.348    0.00967
enemyzealot1.10      Tribus    206.81 MH/s    0.274 0.00027   2.035    0.00133
ccminerKlausT        Yescrypt   35.64 KH/s    0.256 0.00026   1.898    7.17750
ccminerAlexis78      Nist5     145.80 MH/s    0.019 0.00002   0.139    0.00013

Is my nemos wrong, or is pool stats?
newbie
Activity: 16
Merit: 0
@Jaerun  Several users did report on the difference of displayed hashrate.  The pool calculates the hashrate to display by the shares submitted and it's done just like all other algo.  We suspect a bug somewhere with the display of the rate only; your shares and payouts are not affected; this is confirmed by users' posting on the discord verifying the payout matches their hashrates.  We are still searching for that display bug though; would be great if anyone can give us a pointer to it too.  Will keep you guys posted.

Yesterday the 24 actual profitability for Lyra2Rev2 was around .00700.  The current estimate jumped from .004 to .185.  I left my rig mining Lyra2Rev2 for 10 hours on BlazePool.  The expected profit during that time (based on the 24 actual) was .00128 btc (440*.007*10/24), or .128 mBTC/hr.  Instead I made .000619 -- .0619 mBtc/hr -- a little more than half what was expected.  The remainder of the day I left my rig on NiceHash, Lyra2Rev2.  In 13 hours I made .00174 -- 133 mBTC/hr.  

Either your display bug is showing half my mining rate and double the estimated return, or only half of my rate is being counted for some reason.  In any event, I wont be mining Lyra on BlazePool until that is fixed.

-J
newbie
Activity: 85
Merit: 0
@BlazePool
Thanks for your analisis, that was my first 12h on Blazepool, so ill keep it going.
Looking the graphics and api, I have some questions.

https://screenshotscdn.firefoxusercontent.com/images/ff8e913e-c772-47b6-b6ca-8588ad6a64f1.png

Code:
currency	"BTC"
unsold 0.00033522309104886
balance 0.00024886
total_unpaid 0.00058408
total_paid 0
total_earned 0.00058408


On graphic: There is the "inmature" line, displayed in gray
It lowers as balance increases, that means this are the estimate to get in BTC before it gets exchanged. Once it get exchanged, this value decrease as its transfered to "Balance"

The satoshis i see on earnings are the estimate value of the coins mined that need to mature and then exchanged, they are the first step as "inmature", then when that coins mature they become part of "in process", awaiting to be exchanged.

So the steps Would be:
Inmature --> In process --> Balance
Inmature on graphic are the "Inmature" itself + "In process", called as "Unsold" on API

Unpaid = Inmature + In process + balance
If balance reach the treshold (0.003BTC) it will transfered to our wallets on next payout time... and the rest is well known...

Well my confusion is  the inmature, in process and unsold terms.
tell me if my interpretation is ok.

EDIT: The Revenue looks like an estimate based on last 24h?
newbie
Activity: 129
Merit: 0
@Jaerun  Several users did report on the difference of displayed hashrate.  The pool calculates the hashrate to display by the shares submitted and it's done just like all other algo.  We suspect a bug somewhere with the display of the rate only; your shares and payouts are not affected; this is confirmed by users' posting on the discord verifying the payout matches their hashrates.  We are still searching for that display bug though; would be great if anyone can give us a pointer to it too.  Will keep you guys posted.

@MaxiMan  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.  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.

@Supercoiner111  Many users ask for this option and we've talked about it many times within the team.  I just started a discord channel on to find out more from users or would be users, please join our discussion.

Blazepool
newbie
Activity: 85
Merit: 0
I started mining on Blazepool, im using Nemosminer with Normal Estimate settings (No 24h, no plus), ActMiner 5%, Interval Set to 120s.
However, the switching rate is more frequent than Zergpoll or Zpool on "plus" mode

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"

Is this good? Or should i lower the switching rates?
newbie
Activity: 16
Merit: 0
I ran Lyra2v2 for several hours today.  Looking back on it, BlazePool is only picking up about half of my hashrate -- my mine says I run at 440, but BlazePool is reporting 220ish.  Any ideas?  I run the Alexis78 CCMiner for Lyra2v2, and have not noticed this issue on other pools.
newbie
Activity: 129
Merit: 0
Hello all,

Pool webpage down at the moment.  All api calls and stratum activities remain healthy.  Will keep posting updates here.

Webpage online.

Blazepool
full member
Activity: 490
Merit: 100
I can't wait till you add LTC payouts that would be great!
newbie
Activity: 129
Merit: 0
@Sergunqa   Zealot/Enemy will work with Blazepool just like any miner with proper .bat settings.  It is highly recommended that you use one of the multi-algo switcher apps in the market stated on the first post of the thread or compatible ones and choose 6 - 7 algos, using a switch interval of 5 minutes for switching to work for you.  Profitability is likely not to be good for you by using a single algo miner on Blazepool.  The pool is designed to provide best profitability when switching is used.  You may also visit us at our discord, many users can share their experience with you on much better profits when switching is implemented correctly with Blazepool.

@somaton  Thank you for paying attention to the Blazepool.  The vardiff feature of a stratum does not affect your profitability because it is based on both # of shares submitted along with the share's diff.  A sensible auto-diff is one that balances the count of shares submitted with the share's diff, NOT one that makes the miner's rig submit shares at too low a diff and too high a speed.

Blazepool
jr. member
Activity: 212
Merit: 6
with so high auto-difficulty for x16r (64! Shocked), there is much more better pools with more sensible auto-diff or at least with possibility to manually ajust it.
newbie
Activity: 3
Merit: 0
Question to the administrator. I am currently working on Zealot/Enemy (NVIDIA GPU miner) and "xxxxx pool". Interested in your pool. Can I work with Zealot/Enemy (NVIDIA GPU miner) on your pool or I need to download another miner?. If so, what? thank you!
newbie
Activity: 129
Merit: 0
Hello all

Working on a web front-end issue now.  Stratums are unaffected.

Done.

Blazepool
newbie
Activity: 68
Merit: 0
You have the wrong address. Try copying and pasting.  That will always happen if the address is not correct
newbie
Activity: 51
Merit: 0
When I check my wallet on the website I can't find anything
Just got the page "Come back~~! Mine more . Play less :p", as if I haven't any account.

Am I alone ?

Edit : everything is back
newbie
Activity: 11
Merit: 0
@mafaz   Nemosminer is a good one, stable enough for running without issues for weeks.  I've also done well with hashauger.   Awesome miner for when you have 5 or more rigs you need to maintain.  As for lyra2v2, it's been profitable over the past couple of days for us, slightly above average.

I have some rigs running on Nemos to w/o any issue,  I never heard about Hash Auger,  lets say we wanna make a comparison which one you like the most nemos or hash, my nemos are runing with small mods in order to make them fit my needs also im using the monitor script they made with some small mods I pretty much dont even look to the rigs anymore.

By the way from time to time I test old places like MPH nicehash etc I moved 1 rig to MPH the past week when most of equihash was high, after 3 days I quit because the incoming was to low, same type of machine same period of time blaze was better.
newbie
Activity: 129
Merit: 0
@mafaz   Nemosminer is a good one, stable enough for running without issues for weeks.  I've also done well with hashauger.   Awesome miner for when you have 5 or more rigs you need to maintain.  As for lyra2v2, it's been profitable over the past couple of days for us, slightly above average.
newbie
Activity: 48
Merit: 0
@mafaz For some miners, you can switch it within the corresponding "bin" folder for the algo.  If you like finer control of the actual miner app that we do recommend using more advanced versions of miner instead of the blazepoolminer since it was designed with beginners in mind. 

which miner would you recommend? nemos or awesome miner?
and why is blazepool myning lyra2v2 when noone is mining it? is their some fault at reporting profits or what?
newbie
Activity: 129
Merit: 0
@mafaz For some miners, you can switch it within the corresponding "bin" folder for the algo.  If you like finer control of the actual miner app that we do recommend using more advanced versions of miner instead of the blazepoolminer since it was designed with beginners in mind. 

@Seetth Thank you for reporting back.  Our web wiz fixed it after the bug reports from various users of the pool.   = )  Enjoy.
newbie
Activity: 11
Merit: 0
Workers monitor is working, I just got a mail as soon I put one of my rigs under maintenance.
Pages:
Jump to: