Pages:
Author

Topic: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC - page 32. (Read 217698 times)

full member
Activity: 235
Merit: 100
So what exactly causes a coin switch on this pool?  Is it the profitability of the coin, the difficulty, how much hash you can bring to the coin, or how much hash everyone can bring to a coin to flash mine it, or how easy it is to exchange for confirmations?  I see daily profitability, and then inside I have coin profitability on the algorythm  selection.  Just trying to figure out why I mine some coins and not others even though the coins I normally mine are higher up on the profit list.

Thanks in advance.
newbie
Activity: 53
Merit: 0
http://www.zpool.ca/explorer/RADS?txid=9cb9fe3d2edd6a8f123e3e240aa7d791b85ff5526defa7a50867f132777a0a58
http://www.zpool.ca/explorer/RADS?txid=0dbef3ebefb3d5cb40806f02dcfe3bf152b2e34bf24e01598580f8a1c79f77ff

It is not done Payouts by a wallet.


?
Radium 1.4.3 is a mandatory hard fork update. The hard fork will occur at block 619480, or around August 10th 2016.

Looks like I compiled it from the old git, I've re-compiled the proper one but having issues and I'm on my way out to camp until Aug 22. It might have to wait to get fixed until then.

OK

I will wait.

Paying at the future expecting it and being got.
legendary
Activity: 3570
Merit: 1126
http://www.zpool.ca/explorer/RADS?txid=9cb9fe3d2edd6a8f123e3e240aa7d791b85ff5526defa7a50867f132777a0a58
http://www.zpool.ca/explorer/RADS?txid=0dbef3ebefb3d5cb40806f02dcfe3bf152b2e34bf24e01598580f8a1c79f77ff

It is not done Payouts by a wallet.


?
Radium 1.4.3 is a mandatory hard fork update. The hard fork will occur at block 619480, or around August 10th 2016.

Looks like I compiled it from the old git, I've re-compiled the proper one but having issues and I'm on my way out to camp until Aug 22. It might have to wait to get fixed until then.
newbie
Activity: 53
Merit: 0
hero member
Activity: 1092
Merit: 552
Retired IRCX God
I'm interested in trying an S9 on zpool. Searches of this thread and discussions in the S9 thread indicates that there could be problems with S9s on zpool, or with mining alts in general.

Aarons6 suggested using a proxy. Someone else indicated that explicitly setting the difficulty might be needed.


It's not alts in general, I've mined several of them solo and currently run about 25% of the network hash power on NeosCoins using S9s.
The diff setting of a miner (most specifically any using cgminer or any of it's forks) does nothing more than halt submissions of anything lower than that number.
Miners run hashes at 1 diff. Setting 4,000 diff (for example) will still run the rig at 1 diff, but only tun in shares that equal a solve for 4k or better. Diff settings have zero effect on a rig crashing (unless you set the rig to a 200m diff and halt time outs, in which case it might burn up  Tongue).
legendary
Activity: 1150
Merit: 1004
I'm interested in trying an S9 on zpool. Searches of this thread and discussions in the S9 thread indicates that there could be problems with S9s on zpool, or with mining alts in general.

Aarons6 suggested using a proxy. Someone else indicated that explicitly setting the difficulty might be needed.

If anyone is reliably mining on zpool with reasonable rejects using an S9, can you tell me what you did to get it to work?

Thanks in advance.
legendary
Activity: 1797
Merit: 1028
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
I 100% agree.   Somehow I think its linked to that "garbage string" they seem to send to stratum (from what i've read)....

I wonder if someone compiles a fresh cgminer for them if it would fix the problem.

The strange thing is it seems to increase in severity with hashrate.

My S3's rarely saw downtime, and it was always happening on any pool anyways.
Ive heard of the S5's having issues staying connected on the pool
And worse with S7 Etc...

I wonder whats so different between your stratum and kano....

ive had good luck with the java stratum proxy..
https://github.com/Stratehm/stratum-proxy

setting the proxy to use ES  then NOT enable ES on the s7.
also setting a diff helps a lot..



WHAT DIFF WOULD YOU SUGGEST FOR 1-4GH/s? --

I stopped mining with my S5 units because they kept crashing on ZPOOL.  I was afraid that they were being damaged.  They hung-up, requiring a reboot, instead of rolling over to another pool.

My payments went from 1-1.5 DASH a day, to practically nothing.  I suspected I was being paid BTC percentages applied to DASH coin, my prefered payment coin.

There are a couple spare RasPi units lying around, I may work on the proxy set-up.  I've never bothered to set difference values for minning before.       --scryptr


you can try starting at 2000.. just make sure you pick a number that isnt a power of two.. bitmains cgminer fork hates that for some reason and it bugs out..

so no, 1024, 2048, 4096 etc..


edit, i just noticed you said 1-4GH/s and not TH/s heh.. i read s5 and thought maybe you meant for that.. or did you??


YES, I HAVE S5 UNITS, WRONG UNIT LABEL--

So I corrected it.  Quotes may be off, preserving my mistake for a digital  eternity.       --scryptr
legendary
Activity: 1736
Merit: 1006
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
I 100% agree.   Somehow I think its linked to that "garbage string" they seem to send to stratum (from what i've read)....

I wonder if someone compiles a fresh cgminer for them if it would fix the problem.

The strange thing is it seems to increase in severity with hashrate.

My S3's rarely saw downtime, and it was always happening on any pool anyways.
Ive heard of the S5's having issues staying connected on the pool
And worse with S7 Etc...

I wonder whats so different between your stratum and kano....

ive had good luck with the java stratum proxy..
https://github.com/Stratehm/stratum-proxy

setting the proxy to use ES  then NOT enable ES on the s7.
also setting a diff helps a lot..



WHAT DIFF WOULD YOU SUGGEST FOR 1-4GH/s? --

I stopped mining with my S5 units because they kept crashing on ZPOOL.  I was afraid that they were being damaged.  They hung-up, requiring a reboot, instead of rolling over to another pool.

My payments went from 1-1.5 DASH a day, to practically nothing.  I suspected I was being paid BTC percentages applied to DASH coin, my prefered payment coin.

There are a couple spare RasPi units lying around, I may work on the proxy set-up.  I've never bothered to set difference values for minning before.       --scryptr


you can try starting at 2000.. just make sure you pick a number that isnt a power of two.. bitmains cgminer fork hates that for some reason and it bugs out..

so no, 1024, 2048, 4096 etc..


edit, i just noticed you said 1-4GH/s and not TH/s heh.. i read s5 and thought maybe you meant for that.. or did you??



legendary
Activity: 1736
Merit: 1006
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool

For mine it was the 6-20 times the server died per day.

the pool has been pretty stable for me.



i did make a crude sh script to reboot cgminer every 6 hours and if the hash speed dropped down for more then 5 minutes.. that did help a bit.

legendary
Activity: 1797
Merit: 1028
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
I 100% agree.   Somehow I think its linked to that "garbage string" they seem to send to stratum (from what i've read)....

I wonder if someone compiles a fresh cgminer for them if it would fix the problem.

The strange thing is it seems to increase in severity with hashrate.

My S3's rarely saw downtime, and it was always happening on any pool anyways.
Ive heard of the S5's having issues staying connected on the pool
And worse with S7 Etc...

I wonder whats so different between your stratum and kano....

ive had good luck with the java stratum proxy..
https://github.com/Stratehm/stratum-proxy

setting the proxy to use ES  then NOT enable ES on the s7.
also setting a diff helps a lot..



WHAT DIFF WOULD YOU SUGGEST FOR 1-4TH/s? (EDIT - WRONG UNIT)--

I stopped mining with my S5 units because they kept crashing on ZPOOL.  I was afraid that they were being damaged.  They hung-up, requiring a reboot, instead of rolling over to another pool.

My payments went from 1-1.5 DASH a day, to practically nothing.  I suspected I was being paid BTC percentages applied to DASH coin, my prefered payment coin.

There are a couple spare RasPi units lying around, I may work on the proxy set-up.  I've never bothered to set difference values for minning before.       --scryptr
legendary
Activity: 3570
Merit: 1126
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool

For mine it was the 6-20 times the server died per day.

Right, and now there are no interruptions on the server side... none. nada.
hero member
Activity: 1092
Merit: 552
Retired IRCX God
I wonder whats so different between your stratum and kano....

Round about the difference between Windows and Fedora.  Grin
hero member
Activity: 1092
Merit: 552
Retired IRCX God
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool

For mine it was the 6-20 times the server died per day.
legendary
Activity: 1736
Merit: 1006
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
I 100% agree.   Somehow I think its linked to that "garbage string" they seem to send to stratum (from what i've read)....

I wonder if someone compiles a fresh cgminer for them if it would fix the problem.

The strange thing is it seems to increase in severity with hashrate.

My S3's rarely saw downtime, and it was always happening on any pool anyways.
Ive heard of the S5's having issues staying connected on the pool
And worse with S7 Etc...

I wonder whats so different between your stratum and kano....

ive had good luck with the java stratum proxy..
https://github.com/Stratehm/stratum-proxy

setting the proxy to use ES  then NOT enable ES on the s7.
also setting a diff helps a lot..

legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
I 100% agree.   Somehow I think its linked to that "garbage string" they seem to send to stratum (from what i've read)....

I wonder if someone compiles a fresh cgminer for them if it would fix the problem.

The strange thing is it seems to increase in severity with hashrate.

My S3's rarely saw downtime, and it was always happening on any pool anyways.
Ive heard of the S5's having issues staying connected on the pool
And worse with S7 Etc...

I wonder whats so different between your stratum and kano....
legendary
Activity: 3570
Merit: 1126

FWIW my spondoolies are a-ok on your pool but my antminers are getting KILLED, like every 4-6 hours they just die and I have to reboot them.

That's the main reason I quit using my S9s on zpool   Sad
While this comotion was going on I decided to try and point an S7 back at zpool.   Started online for ~5 min before being kicked into retard mode where I can't even log into it.
Nicehash is working flawlessly.... so the issue is still pretty prevalent.

I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?

FWIW my spondoolies are a-ok on your pool but my antminers are getting KILLED, like every 4-6 hours they just die and I have to reboot them.

That's the main reason I quit using my S9s on zpool   Sad
While this comotion was going on I decided to try and point an S7 back at zpool.   Started online for ~5 min before being kicked into retard mode where I can't even log into it.
Nicehash is working flawlessly.... so the issue is still pretty prevalent.
hero member
Activity: 1092
Merit: 552
Retired IRCX God

FWIW my spondoolies are a-ok on your pool but my antminers are getting KILLED, like every 4-6 hours they just die and I have to reboot them.

That's the main reason I quit using my S9s on zpool   Sad
full member
Activity: 125
Merit: 100
anyone having issues connecting to sha256 port ? keep getting a null error

I've noticed a drop in the # of miners but it doesn't appear to be a problem on the system. I'm not sure if it's provider related but I didn't get any alerts from them.

I'm got some patching to do on that server tonight so I'll let you know when it's restarted to see if there is any change...

FWIW my spondoolies are a-ok on your pool but my antminers are getting KILLED, like every 4-6 hours they just die and I have to reboot them.

and all yours are using sha256.mine.zpool.ca?

Yes, all of my miners on your pool are using sha256.mine.zpool.ca
legendary
Activity: 3570
Merit: 1126
anyone having issues connecting to sha256 port ? keep getting a null error

I've noticed a drop in the # of miners but it doesn't appear to be a problem on the system. I'm not sure if it's provider related but I didn't get any alerts from them.

I'm got some patching to do on that server tonight so I'll let you know when it's restarted to see if there is any change...

FWIW my spondoolies are a-ok on your pool but my antminers are getting KILLED, like every 4-6 hours they just die and I have to reboot them.

and all yours are using sha256.mine.zpool.ca?
Pages:
Jump to: