█▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC

[Mario241077]

I just lost money mining quark over you guys!! My payout was in MUE it's clear that without me you guys have 50 to 60% less hashpower and I made half of I was expecting!!

Exchange rates seems to be really bad

I don't know I will not mine quark here anymore not worth

I've been mining quark and qubit for a long time and have always come away with more BTC.

Not sure how you go about it but as with any algo, if you're renting, you can't just set an order and guarantee you'll make $.

show 400 UNB, that's wrong!? check it please crackfoo

but realy is, Unbreakable (sha256)   50 UNB   6.241 M   46 459   3m ago   Immature (1)

Mining 42 coins at 420.7 Th/s * with 223 miners (sha256)
Unbreakable (sha256)   400 UNB   6.241 M   46 459   67 secs   395.9 Th/s   0.0078

changed, thanks

[jkminkov]

ANyone else having issues with the nvidia driver crashing and causing a major hit in hashrates?

I have little experience, v. 368.39, 750ti seems to work well, if it crashed I have to drop intensity, and unlike amd I don't get 50% of hashrate after a crash.

you can check for driver crash when you start/stop miner a few times.

[bensam1231]

Yeah, 5 out of 7 Lyra2v2 coins are dead. Keeping track of payouts from the pool, I could've made more mining Vert or Mona from a normal pool. I'll wait another 12, but definitely pretty certain they're tanking pool efficiency.

Actual pool rate multiplied by my hashrate definitely does not give me my payouts as well. My payouts were about 20% lower then that. The 'actual' payout still was below mining coins direct as well.

[bensam1231]

Yeah, 5 out of 7 Lyra2v2 coins are dead. Keeping track of payouts from the pool, I could've made more mining Vert or Mona from a normal pool. I'll wait another 12, but definitely pretty certain they're tanking pool efficiency.

Actual pool rate multiplied by my hashrate definitely does not give me my payouts as well. My payouts were about 20% lower then that. The 'actual' payout still was below mining coins direct as well.

i assure you, any yaamp pool and its op do everything possible to maximize their (pool/op) profits  
sometimes (well actually most of the time) it doesn't mean any good profits for miners,
and that's pretty obvious if you carefully look at the pool payouts scheme

If you're eluding to them skimming off the top, they could still make more by removing five out of seven dead Lyra2v2 coins..

[crackfoo]

Yeah, 5 out of 7 Lyra2v2 coins are dead. Keeping track of payouts from the pool, I could've made more mining Vert or Mona from a normal pool. I'll wait another 12, but definitely pretty certain they're tanking pool efficiency.

Actual pool rate multiplied by my hashrate definitely does not give me my payouts as well. My payouts were about 20% lower then that. The 'actual' payout still was below mining coins direct as well.

i assure you, any yaamp pool and its op do everything possible to maximize their (pool/op) profits  
sometimes (well actually most of the time) it doesn't mean any good profits for miners,
and that's pretty obvious if you carefully look at the pool payouts scheme

If you're eluding to them skimming off the top, they could still make more by removing five out of seven dead Lyra2v2 coins..

If they're on exchanges, they are no dead and no worthless. Most of the time it is mona and vtc being mined and very little hash is put on the others. And for the merged mined coins who cares? If you want, I'll see if I can have your account donate any earnings from them to the pool.

[JaredKaragen]

I have again started pointed a S7 at zpool.   It is consistently reconnecting but, is not getting kicked off needing a hard-reset like it was before.

I do see the results of the disconnects (pool hashrate drops massively is one clue) and my miner hashrate resets then climbs back up.

So it seems as whatever garbage that was keeping the miner from reconnecting or getting hung waiting to reconnect... is no longer happening.   My only issues now are the normal power issues associated with living out of the city in the country.

The lyra2 port seems to waver greatly on my hashrate it is seeing.   Its very odd.... So sometimes I get a full reward (~25Mh) and sometimes a partial reward (~13Mh)...  I am wondering if I force a diff that this will change my hashrate consistency....  telling me that the diff is going just a little too high for the speed of the coins its mining.

[bensam1231]

Yeah, 5 out of 7 Lyra2v2 coins are dead. Keeping track of payouts from the pool, I could've made more mining Vert or Mona from a normal pool. I'll wait another 12, but definitely pretty certain they're tanking pool efficiency.

Actual pool rate multiplied by my hashrate definitely does not give me my payouts as well. My payouts were about 20% lower then that. The 'actual' payout still was below mining coins direct as well.

i assure you, any yaamp pool and its op do everything possible to maximize their (pool/op) profits  
sometimes (well actually most of the time) it doesn't mean any good profits for miners,
and that's pretty obvious if you carefully look at the pool payouts scheme

If you're eluding to them skimming off the top, they could still make more by removing five out of seven dead Lyra2v2 coins..

If they're on exchanges, they are no dead and no worthless. Most of the time it is mona and vtc being mined and very little hash is put on the others. And for the merged mined coins who cares? If you want, I'll see if I can have your account donate any earnings from them to the pool.

Considering they don't have any volume and almost zero sell orders, they're pretty dead. Still also missing about 20% of my income even though my hashrate was relatively stable. '24 hour Actual' my ass

Going to back to a normal pool.

[JaredKaragen]

Here's another useful cut and paste.    I was able to kick my live mining machine from P2 into P0, no interruptions.

I am thinking of building this command into my batch every time it re-launches the miner apps to make sure P-state is zero.

Code:

Run this in cmd in admin mode:
c:\progra~1\nvidia~1\NVSMI\
nvidia-smi -q -d SUPPORTED_CLOCKS | more
(that's a pipe before more)

Take the top number for memory, something like 3505 (GTX970), and the first number for graphics, something like 1531. Again in admin mode, enter your numbers in this format:

nvidia-smi -ac 3505,1531

You're card's memory will now run in compute mode (P0).

nvidia-smi.exe -ac 3505,1443  For my ASUS GTX 980.

"nvidia-smi.exe -acp UNRESTRICTED" removes the admin requirements. 

Ive also noticed X11evo is a power-hungry algo.  One machine used to sit at 80-84*C when running only X11EVO.  Now Running Lyra2 full-time and it sits @65*C...

[BryanC]

Strange - we have opposite problems! My lyra2v2 hash rate is spot on - on Zpool, the average over the course of the day is pretty damn close to what my rig sees. For my S7-LN, right at 20% of my hash rate is rolling over to the next pool on the list (and only 10% of that is recognized in the other pool, so I'm effectively losing 10% of my hash rate). This is without #xnsub - if I append it, my rate never goes about 800-900 Gh/s.

In looking at my hash rate graph against the pool's, and my dropouts line up fairly precisely with the pool's. How can that be expected behavior?

I have again started pointed a S7 at zpool.   It is consistently reconnecting but, is not getting kicked off needing a hard-reset like it was before.

I do see the results of the disconnects (pool hashrate drops massively is one clue) and my miner hashrate resets then climbs back up.

So it seems as whatever garbage that was keeping the miner from reconnecting or getting hung waiting to reconnect... is no longer happening.   My only issues now are the normal power issues associated with living out of the city in the country.

The lyra2 port seems to waver greatly on my hashrate it is seeing.   Its very odd.... So sometimes I get a full reward (~25Mh) and sometimes a partial reward (~13Mh)...  I am wondering if I force a diff that this will change my hashrate consistency....  telling me that the diff is going just a little too high for the speed of the coins its mining.

[JaredKaragen]

In looking at my hash rate graph against the pool's, and my dropouts line up fairly precisely with the pool's. How can that be expected behavior?

Im running a late batch 6 600M model of S7.  So, its 4.2Th on a good day.  I have it backed off to 30% fan speed and 3.2Th.

This is my password string: Henry.S7-1,c=BTC,sha256=3000

My next change will be in another 24 hours where ill bump the diff up by 1K to 4000.    My issues is faster coins need a lower diff cause of my internet connection.. I tend to get stale shares and they don't count.... When the share spacing is great, I dont get shares for some time and my delta hashrate at the pool drops.   Finding the point where it drops off, and then backing it back off a bit, seems to do the trick....

PRoblem is it needs to stay online long enough to be sure its trimmed properly.  What a bugger that is so far....

[crackfoo]

I have again started pointed a S7 at zpool.   It is consistently reconnecting but, is not getting kicked off needing a hard-reset like it was before.

I do see the results of the disconnects (pool hashrate drops massively is one clue) and my miner hashrate resets then climbs back up.

So it seems as whatever garbage that was keeping the miner from reconnecting or getting hung waiting to reconnect... is no longer happening.   My only issues now are the normal power issues associated with living out of the city in the country.

The lyra2 port seems to waver greatly on my hashrate it is seeing.   Its very odd.... So sometimes I get a full reward (~25Mh) and sometimes a partial reward (~13Mh)...  I am wondering if I force a diff that this will change my hashrate consistency....  telling me that the diff is going just a little too high for the speed of the coins its mining.

This is good to hear. We've made changes to the lowest level socket connections which seems to cut out a lot of connection problems. Mainly problems were coming from miners disconnecting from the stratum server when we were in the middle of handing out jobs for one of the coins that were being mined. We now have 5s socket timeouts. Which is way more than enough time. The majority os sockets are established successfully in 1ms or less so even 5 is a lot and I may fiddle with that a bit more. So the stratum isn't resetting so much as it is closing failed sockets before it hangs the whole stratum like it was doing.

I hoped it would help with all the problems but there there is still problems when I enabled AUX coins so I've dropped them all on sha again and just left DOGE on scrypt. the other algos don't seem to have problems with them probably because there are no ASIC's on them aside from X11, which may eventually see problems once there are more providers of ASIC's building crappy devices etc...

[JaredKaragen]

This is good to hear. We've made changes to the lowest level socket connections which seems to cut out a lot of connection problems. Mainly problems were coming from miners disconnecting from the stratum server when we were in the middle of handing out jobs for one of the coins that were being mined. We now have 5s socket timeouts.

I hoped it would help with all the problems but there there is still problems when I enabled AUX coins so I've dropped them all on sha again and just left DOGE on scrypt. the other algos don't seem to have problems with them.

I can see how the server would get kinda pissed and lock up/reset from being overloaded with open sockets....

I have stability, so I am in for the long haul with that S7.   I refuse to let people lowball me on nicehash since they can't change the profitability flag to be something other than what it is which is broken on >S3 models.

It was amazing watching people immideately pay almost half for the same sized order;  then in the next day watch diff on the altcoins all rise and drop their value per hashrate because they arent pointing it at BTC as much as they were......   The ripple of the halving's second signs...

[crackfoo]

This is good to hear. We've made changes to the lowest level socket connections which seems to cut out a lot of connection problems. Mainly problems were coming from miners disconnecting from the stratum server when we were in the middle of handing out jobs for one of the coins that were being mined. We now have 5s socket timeouts.

I hoped it would help with all the problems but there there is still problems when I enabled AUX coins so I've dropped them all on sha again and just left DOGE on scrypt. the other algos don't seem to have problems with them.

I can see how the server would get kinda pissed and lock up/reset from being overloaded with open sockets....

I have stability, so I am in for the long haul with that S7.   I refuse to let people lowball me on nicehash since they can't change the profitability flag to be something other than what it is which is broken on >S3 models.

It was amazing watching people immideately pay almost half for the same sized order;  then in the next day watch diff on the altcoins all rise and drop their value per hashrate because they arent pointing it at BTC as much as they were......   The ripple of the halving's second signs...

I have a good feeling that there will be a stable python port of the stratum servers available eventually which I'll put putting in BTC to help push the dev along to get it done. It's a tricky project so I hope it makes it to finish.

[JaredKaragen]

I have a good feeling that there will be a stable python port of the stratum servers available eventually which I'll put putting in BTC to help push the dev along to get it done. It's a tricky project so I hope it makes it to finish.

I myself ponder why altcoin devs on the SHA port don't add a way to have merge mine support with BTC.  That way we can mine BTC, and send all lesser hashes to altcoins.   Would be a win-win for long-term miner support and for the miners as well.

We can only hope for someone to unify the coding so it happens and its easy to add to different coins.

[Megaquake]

I have a good feeling that there will be a stable python port of the stratum servers available eventually which I'll put putting in BTC to help push the dev along to get it done. It's a tricky project so I hope it makes it to finish.

I myself ponder why altcoin devs on the SHA port don't add a way to have merge mine support with BTC.  That way we can mine BTC, and send all lesser hashes to altcoins.   Would be a win-win for long-term miner support and for the miners as well.

We can only hope for someone to unify the coding so it happens and its easy to add to different coins.

There are many SHA256d  that are merged mining capability, I don't know if the code messes up BTC mining but it causes more orphaned BTC blocks

[jkminkov]

use stratum proxy for sha256, you can add more pools and your miners will get work all the time, no more hits with pool connection resets.

[BaalMcKloud]

someone is using a botnet for neoscrypt...

Code:

Version			Count	Donators	Extranonce	Percent	Hashrate*	Reject
cpuminer-multi/1.2-dev	9929	0		9917		34.94%	8.5 Mh/s	0%

[Megaquake]

someone is using a botnet for neoscrypt...

Code:

Version			Count	Donators	Extranonce	Percent	Hashrate*	Reject
cpuminer-multi/1.2-dev	9929	0		9917		34.94%	8.5 Mh/s	0%

Yes indeed wow!

[pallas]

someone is using a botnet for neoscrypt...

Code:

Version			Count	Donators	Extranonce	Percent	Hashrate*	Reject
cpuminer-multi/1.2-dev	9929	0		9917		34.94%	8.5 Mh/s	0%

Yes indeed wow!

it's been like that forever.
low hashrate and tons of miners.
those are CPUs for sure.

[bensam1231]

someone is using a botnet for neoscrypt...

Code:

Version			Count	Donators	Extranonce	Percent	Hashrate*	Reject
cpuminer-multi/1.2-dev	9929	0		9917		34.94%	8.5 Mh/s	0%

Yes indeed wow!

it's been like that forever.
low hashrate and tons of miners.
those are CPUs for sure.

Yaamp had the samething. It's a blob that moves around and it looks like it's still growing.