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

[crackfoo]

Hey, what happened to MonetaryUnit (MUE)

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

How about you follow the mue thread? Coins are being swapped. When they are, things will resume.

[1713444535]

1713444535

[1713444535]

1713444535

[AK74XXX]

Oh. sry, I'm new to bitcointalks, don't know where to search first

Btw, couldn't find the answer: is there a way to make so-called "NiceHash/1.0.0" miner (bought hashpower) to connect w/xnsub? If I got the idea correctly, in some cases that could reduce NiceHash switching charges.

[Storx]

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect

[cashen]

I moved all my scrypt until pool issues get resolved.

[guytechie]

hmq1725 reporting low hash rate again.

[Storx]

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

[Storx]

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect

I have managed to fix the issue i posted earlier on equihash with a band aid tell server side figures out connection issues... i added --eexit 3 to the miner, which moves on to the next algo if it fails to reconnect after 3 trys

[JaredKaragen]

problem with doing that and leaving equihash in the password string is the pool still can try and switch you to it;  when its not connecting....  unless the stratum not connecting only happens after its been mining equihash for a bit..... then it could be a viable solution.

[guytechie]

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

What is a good difficulty to set to for 6.8 Mh/s?

Also, how would you modify Nemosminer 2.0.4 PowerShell script to incorporate that just for hmq1725?

[crackfoo]

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

I just bumped the starting diff to 64 from 8.

[guytechie]

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

I just bumped the starting diff to 64 from 8.

Thanks.  I think that helped, but will wait to see if it stays that way.

[cashen]

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

I just bumped the starting diff to 64 from 8.

Speaking of difficulty. Nicehash will not allow zpool as a pool due to low diff. Might be an opportunity for you.

[gruntbull]

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect
https://farm5.staticflickr.com/4265/35529090375_5f8fe62ac8_z_d.jpg

Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.

I think I will do the same, take it out of my multi-algo until it is resolved.

[crackfoo]

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect

Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.

I think I will do the same, take it out of my multi-algo until it is resolved.

where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.

[crackfoo]

where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.

Rejects at pool
Share above target   0.0000 MSol/s   0.0000 MSol/s
Stale share   0.0000 MSol/s   0.0001 MSol/s
Duplicate share   0.0000 MSol/s   0.0000 MSol/s
Invalid nTime   0.0000 MSol/s   0.0000 MSol/s
Invalid worker   0.0000 MSol/s   0.0000 MSol/s
Other   0.0000 MSol/s   0.0000 MSol/s

[crackfoo]

where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.

Rejects at pool
Share above target   0.0000 MSol/s   0.0000 MSol/s
Stale share   0.0000 MSol/s   0.0001 MSol/s
Duplicate share   0.0000 MSol/s   0.0000 MSol/s
Invalid nTime   0.0000 MSol/s   0.0000 MSol/s
Invalid worker   0.0000 MSol/s   0.0000 MSol/s
Other   0.0000 MSol/s   0.0000 MSol/s

a/some stale shares but nothing I'd be concerned about.

[crackfoo]

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

I just bumped the starting diff to 64 from 8.

Speaking of difficulty. Nicehash will not allow zpool as a pool due to low diff. Might be an opportunity for you.

What algo??? AFAIK NH doesn't offer hmq1725.

[Storx]

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect

Storx, I am getting similar issues - equihash either has disconnets or HIGH (90%) reject rate (stock settings 82% power NO OC on 6x1080tis). On my 2 card test rig I have no issues with it.

I think I will do the same, take it out of my multi-algo until it is resolved.

where are you seeing your rejects? on your miner? If it's the pool, disregard it, it's not able to calculate rejects properly. I've been running 200Ksol for a couple hours now and no reported rejects miner side, but my stats showed some.

The miner is loosing connection to the server at random intervals and seems to reject reconnects for long periods of time. I can assure you its not my internet or miners, because its happening within seconds of one another on ALL my rigs and half are located at a different location on a completely different ISP service.

Just today monitoring my 1 rig i left on equihash.. i noticed that it seems to disconnect right around the peaks of the day when the miner count spikes high from everyone switching... and if you do manage to not get disconnected.. the miner will report a ton of errors for a few minutes tell things settle down.. its like a 50/50 on the disconnect vs error phase occurring..
 

[minerx117]

don't pay any attention to the graphs they are rubbish... just monitor the miner console..

Nemo

[AceIsAngry79]

Do anny know how to setupp Yellowjacket 2.2 GH/s USB ASIC Miner (Nanofury) whit BFGMiner to work whit Zpool?

https://www.amazon.ca/Yellowjacket-2-2-ASIC-Miner-Nanofury/dp/B00I21R4HG


I have tryd sha256.mine.zpool.ca:3333  but BGFminer says "All the pools are dead".

Sorry for my bad english.

SINCERELY

Benny