▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!10 FLUX PA's!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂

[JaredKaragen]

MAn, I picked the wrong time to take a few days away from forums.


Most info people have been requesting is in my batch link in my signature;  how to normalize, etc... but looks like its all sorted now.


Still working on updates for my batch.

Ill probably integrate the core/clock modifications to the batch I see in the posts above me.

Will add some more convolution, but that's all right.

Right now I'm trying to get my "All batches in one" to work properly.   Lots to figure out still.

[1715112842]

1715112842

[1715112842]

1715112842

[1715112842]

1715112842

[cashen]

Crackfoo,

Can you talk / explain Hashtap a little bit. I really like the idea but but i'm not sure who would use it at it's current price structure. It appears to be 2x the current algo 24 hour estimate.

for people to actually use it would it have to be less than current estimate?

like somewhere between 90%-95% of 24 hr est.

[crackfoo]

Crackfoo,

Can you talk / explain Hashtap a little bit. I really like the idea but but i'm not sure who would use it at it's current price structure. It appears to be 2x the current algo 24 hour estimate.

for people to actually use it would it have to be less than current estimate?

like somewhere between 90%-95% of 24 hr est.

Remember it's the miners multipool. No miner will want to give their hash away at a price less than what they can be by mining coins so the price will most always be slightly higher than mining would make. Keep in mind there is no order fees or work restart penelties  or order cancel fees like you get by using Nicehash.

[Jaerin]

hmq1725 Is reporting low hash rates again.  It's actually affecting the pay %.

It was fine after the first time we reported it, but it's happening again now.

Its off by 1000

I'm mining at 15.5 Mh/s but it's reporting 68 kh/s.

It's not just a reporting/cosmetic issue because the payouts reflect the performance.  I was getting larger payments for each Espers block found but now the payouts are as small as the reported hash rate (same ratio).

I'm seeing the same thing.  I think I'm disabling hmq1725 for now.   Not sure why the pool hashrate is so low compared to what local miners are saying.

[crackfoo]

hmq1725 Is reporting low hash rates again.  It's actually affecting the pay %.

It was fine after the first time we reported it, but it's happening again now.

Its off by 1000

I'm mining at 15.5 Mh/s but it's reporting 68 kh/s.

It's not just a reporting/cosmetic issue because the payouts reflect the performance.  I was getting larger payments for each Espers block found but now the payouts are as small as the reported hash rate (same ratio).

I'm seeing the same thing.  I think I'm disabling hmq1725 for now.   Not sure why the pool hashrate is so low compared to what local miners are saying.

Technically your paid by the share and the hashrate is simply something that's calculated from that. Once I'm back I'll check and see with the yiimp dev to see about changing the hashrate calculation. It's not going to change anything in regards to your connection, just a GUI fix.

[Jaerin]

hmq1725 Is reporting low hash rates again.  It's actually affecting the pay %.

It was fine after the first time we reported it, but it's happening again now.

Its off by 1000

I'm mining at 15.5 Mh/s but it's reporting 68 kh/s.

It's not just a reporting/cosmetic issue because the payouts reflect the performance.  I was getting larger payments for each Espers block found but now the payouts are as small as the reported hash rate (same ratio).

I'm seeing the same thing.  I think I'm disabling hmq1725 for now.   Not sure why the pool hashrate is so low compared to what local miners are saying.

Technically your paid by the share and the hashrate is simply something that's calculated from that. Once I'm back I'll check and see with the yiimp dev to see about changing the hashrate calculation. It's not going to change anything in regards to your connection, just a GUI fix.

But the earnings of everything reporting on the site seems to indicate that it's not paying out what the site is reporting it should.  All graphs look flat, the hashrates of the workers are showing significantly lower than what is being reported locally.  Are you saying that we should see similar earnings to what we've seen in the past few days if we keep mining hmq1725?  I trust you, but it's very hard to judge if our miners are actually effective when the tools to measure the performance on the pool show otherwise.

I do see that I was getting shares of a few Esper mined, but again it seems near impossible to know what returns that we can expect from it when the graphs are all showing either flat or decreasing earnings.

[JaredKaragen]

fwiw;  yesterday on a larger machine only got one payout, when its normally 2-3 a day.

Profitability was down for ~22 hours or so give or take.

[cashen]

There is something going on. My scrypt miners have been acting funny all day. It's pool side. Just look at the pool hashrate and look at the sharp drops.

[icolsuineg]

crackfoo, had the same issue with equihash - both machines start spinning nicely, then suddenly we mine Komodo, finish it, probably pool switches to other coin and the interface rejects (red line and percentage) jump up to 95% rejects on whatever else we start mining. It disappeared with Zen, now I see Zen is back again. Is it possible that we have an issue with it?



Whatever the interface shows, that's about 7.3 kS that gives me abount the same percentage from the total hashpower. I just pointed one miner at the equihash again and I will report if it's the same.

EDIT - so far so good, couple of Komodos and still no rejects.

There is something going on. My scrypt miners have been acting funny all day. It's pool side. Just look at the pool hashrate and look at the sharp drops.

https://i.imgur.com/WlQXYDC.png

During payouts?

[icolsuineg]

Just happened:

See how hashrate dropped, despite me having 6% of the hashpower. I think it happens right after we finish one coin and switch to another (and that is not Komodo and Zcl, I guess)

[Jaerin]

The height of the red rejects is on a different scale than the rest of the graph.   I've noticed that even 1 or 2 rejected shares will create a very large spike on the graph even though it is only a couple rejected shares.

Still something that should be investigated if possible

[shotgun1969]

you guys have to realize   somewhere somehow some graphing dev is sitting back lhao.

[JaredKaragen]

The height of the red rejects is on a different scale than the rest of the graph.   I've noticed that even 1 or 2 rejected shares will create a very large spike on the graph even though it is only a couple rejected shares.

Still something that should be investigated if possible

It's simple.  Hashrate makes the graph 0-2gh let's say.   the rejects are a flat 0-100 scale.  I think the vertical scale is staying matched with the hashrate display instead of its own 0-100%.

[Storx]

for multi-algo,

SET PASS format for equihash is in ksol correct? so if the miner reports 4242sols, i place it in the SET PASS line as 4.242 correct? just trying to fine tune some errors i may have made... noticed that i have been mining non-stop equihash all day since adding it to my multi-algo switcher batch

[guytechie]

for multi-algo,

SET PASS format for equihash is in ksol correct? so if the miner reports 4242sols, i place it in the SET PASS line as 4.242 correct? just trying to fine tune some errors i may have made... noticed that i have been mining non-stop equihash all day since adding it to my multi-algo switcher batch

That seems right to me, but might want to round it to less digits if it doesn't seem to work right.  Maybe to 4.24 or 4.2

[icolsuineg]

The height of the red rejects is on a different scale than the rest of the graph.   I've noticed that even 1 or 2 rejected shares will create a very large spike on the graph even though it is only a couple rejected shares.

And there is the number in the right corner

90.6%

[guytechie]

hmq1725 Is working fine again.  Seeing the hasrate back (and the share % is back up).

So when it was defective, the pool only saw hashrates in the kh/s range (60-100 kh/s) and I was getting only around 0.1- 0.2% of the shares.  Also, finding blocks took forever.

Now, I see 13.7MH/s (still not the full 15.5 MH/s as I'm seeing on my miner) but my share is now in the 2.6% area and blocks found much faster.

I don't think it's just a graphing problem.

[guytechie]

BTW, is there a condition where the pool will ignore the difficulty?  Equihash is always set to 127 no matter what I put in the password.

[cashen]

As stated yesterday, something is going on with scrypt. Maybe its a coin the pool doesnt like. There is no way I should have 16% reject shares. my machines show solid 504MH each. The pool isnt even showing each worker.

[AK74XXX]

Hey, what happened to MonetaryUnit (MUE)

It disappeared from everywhere at one moment, but looks like alive unseen: blocks are being found, transactions confirmed, balances updated... but unpaid. WTF, plz?