🔥🔥🔥Blazepool on FIRE🔥180+ coins🔥well established🔥multi-algo switching pool

[Blazepool]

Hello all,

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

Webpage online.

Blazepool

[1714468931]

1714468931

[1714468931]

1714468931

[1714468931]

1714468931

[1714468931]

1714468931

[Jaerun]

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.

[MaxiMan]

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?

[Blazepool]

@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

[MaxiMan]

@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?

[Mr Zeus]

Can you add PapelCoin to mining pool?

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

[Jaerun]

@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

[MaxiMan]

@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?

[Blazepool]

@Jaerun We've had a long discussion over at the discord about the lyra2v2 reporting.  There are conflicting cases presented and we are looking into what's actually happening.  The symptoms differs between different ccminer versions is what we observed.  We do not have the root cause yet and will update as we find more.

@MaxiMan  Are you using the current estimates like we suggested?  If you are, then the current estimates shooting to higher values than your daily average is the normal scenario.  After all we are shooting for those low diff algos at that particular moment in time.  The actual payout from the pool should be taken as the only valid metric to evaluate a benchmark.

Blazepool

[MaxiMan]

Im using Normal estimate values from pool, however im getting many peaks that causes constant switching, as my interval is set to 2 minutes
dont you find too short time switching algos?

Another question: Should i set my miner to mine all possible algos? Or set the best ones?

@Blazepool It is possible to make zoom into the graphic? I want to see my balance at exact point in time so i can track my incomes better, also the points are not constant, it changes. for example i point my mouse on the graphic and show my balance for 4:31pm ~ 4:46
but after some time i cant point my balance at that exact time now it is 4:35 ~ 4:50... This points should be constant on the graph
I want to see my balance every HH:00 ~ HH:15 ~ HH:30 ~ HH:45

[Blazepool]

@MaxiMan  I would think that the switching time is okay as long as you see some algo running 10 - 15 minute sessions as those are the ones that needs the longer time.  As for algos, we always recommend 6-7 profitable ones based on your benchmark.  As for zooming on graphs, don't think it'll be easy but will talk to the team about it. 

Blazepool

[NetfetMiningCompany]

I have a hard time believing that TImetravel is getting me 64 bucks a day. Whats going on with the reporting? Your pool is screwing with my profit manager with the crazy reports. HMQ, TT, and Lyra all had problems. Just going to have to ignore the pool for now. I have no idea whats actually going on here.

[jcorbijn]

What's going on with the X16R algoritm? Since 3 days my income dropped by 30%. Matching my miner log and the income graph from your site I noticed that everytime I was mining X16R the immature income would stay flat. This morning I removed X16R from my switching list and income has increased again to somewhat normal lower level income.

[Blazepool]

@NetfetMiningCompany  Good question here.  Would need to know if you are seeing TimeTravel on top for a long time or only for short durations.  If you are using the current estimate, it is possible for the profitability to spike for short durations and that's a perfect time to mine the coin.  But if the said super high profitability stays up top for a long period of time, then it is more likely that a glitch occurred during the benchmarking process which resulted in incorrect stats stored.

@jcorbijn  Yes, the pool has had 3 days of below average performance; mostly due to the significant drop of overall market.  The x16r has been working fine, i believe it's just co-incidence with the below-average days. 

Blazepool

[NetfetMiningCompany]

Awesome Miner is pretty good with benches, but I will redo it and report back to see what it did.

[Blazepool]

Hello everyone,

Pool has been very stable... market not so... so are many problems with exchanges everywhere.  Just a reminder to users that you might want to run benches to to update your algo listing, things have been very dynamic in the past few weeks.


@NetfetMiningCompany  Thanks for running the benches. 



Blazepool

[MaynardVII]

https://bitcointalk.org/index.php?topic=3572424.msg36430518#msg36430518

MM.Hash supports blazepool for auto-algo profit switching. It also has Nicehash integration, as well as auto-coin switching built in simultaneously for pools that support it. It is a newer mining program I worked hard to design.

Windows and Linux version is available.

[natan069]

What list of ALGOS you guys using with Blazepool and Nvidia?

[natan069]

What list of ALGOS you guys using with Blazepool and Nvidia?

And a UPDATE on the Blazepool miner would be nice too! please 

[cs@blazepool]

Cool... @natan069
Indeed we are just revising our blazepool miner and please be aware an update will possibly coming soon in days....
please stay tuned~~