Thats a fucking scampool lol, mined coins balance was 57.000 sat, after it went unpaid balance 42,000 satoshi.
Mega scam pool, guys go mine on Suprnova, or Multipool.Us
Topic: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC - page 21. (Read 217685 times)
August 28, 2016, 03:33:15 AM
August 28, 2016, 03:12:49 AM
@zpool
you will ad cryptonight algo soon to this pool? maybe moreno?
you will ad cryptonight algo soon to this pool? maybe moreno?
I can really only add what Epsylon3 develops. I don't have the brain function to understand how to code new algo and such. ^_^
but cryptonight isnt a new algo. this algo exist already. but its only a improve from my side
August 27, 2016, 07:08:54 PM
Hashrate is more stabile but reduced to 230 MH/s. On other Pools I get a rate about 360 MH/s. Seems for Titans zpool is not working
Are there any other titan user who can present their settings?
Can you tell or guesstimate how often you see your shares being submitted?
Any more feedback? I'd really like to get this working nicely for Titan users. Scrypt algo could use a real boost in hash and its the Titans that can deliver it.
August 27, 2016, 07:06:28 PM
crackfoo, FYI looks like Epsylon3 made some changes to his yiimp frontend
so now if you have wallet page open (top Wallet tab is active),
and click on an algo in Pool Status - everything goes to that algo page (top Pool tab activates itself).
for me that's long awaited fix, maybe you could implement the same behavior
thx
so now if you have wallet page open (top Wallet tab is active),
and click on an algo in Pool Status - everything goes to that algo page (top Pool tab activates itself).
for me that's long awaited fix, maybe you could implement the same behavior
thx
hrmm I'll see. I did just merge his recent changes but I've been busy with my 9-5 last week and must have missed one.
August 27, 2016, 07:05:29 PM
@zpool
you will ad cryptonight algo soon to this pool? maybe moreno?
you will ad cryptonight algo soon to this pool? maybe moreno?
I can really only add what Epsylon3 develops. I don't have the brain function to understand how to code new algo and such. ^_^
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
August 27, 2016, 04:34:13 PM
are you all really paying that good for cpuing mining argon2 according to pool picker:
Argon2
ZPOOL
0.01121198
BTC/MHs
I parked one of MY PC here to find out:)..if it does il boot up two more pc one is a 4 core and one is a 8 core , they are turned off most of the time used mostly for gaming for when i feel like running two or three accounts in wow .
Argon2
ZPOOL
0.01121198
BTC/MHs
I parked one of MY PC here to find out:)..if it does il boot up two more pc one is a 4 core and one is a 8 core , they are turned off most of the time used mostly for gaming for when i feel like running two or three accounts in wow .
My 20 core machine gets about 0.17% share..... so... remember with your 8 core machine, you are seeing only a few kh/s....... 1/100 to 1/1000 of a Mh....
August 27, 2016, 01:14:42 PM
are you all really paying that good for cpuing mining argon2 according to pool picker:
Argon2
ZPOOL
0.01121198
BTC/MHs
I parked one of MY PC here to find out:)..if it does il boot up two more pc one is a 4 core and one is a 8 core , they are turned off most of the time used mostly for gaming for when i feel like running two or three accounts in wow .
Argon2
ZPOOL
0.01121198
BTC/MHs
I parked one of MY PC here to find out:)..if it does il boot up two more pc one is a 4 core and one is a 8 core , they are turned off most of the time used mostly for gaming for when i feel like running two or three accounts in wow .
August 27, 2016, 01:06:50 PM
@edonkey
Perhaps switch to ckproxy (instead of java and/or node) and set a min diff and start diff?
Perhaps switch to ckproxy (instead of java and/or node) and set a min diff and start diff?
Thanks for the suggestion. But I can set the minimum difficulty with the Stratehm stratum-proxy, so I'm not sure what ckproxy will give me (other than being an awesome lightweight proxy).
Also, I'm on an RPi. So I would probably have to build ckproxy. Not a problem, but probably more work than getting Stratehm running.
August 27, 2016, 11:29:04 AM
@edonkey
Perhaps switch to ckproxy (instead of java and/or node) and set a min diff and start diff?
Perhaps switch to ckproxy (instead of java and/or node) and set a min diff and start diff?
August 27, 2016, 10:06:33 AM
@zpool
you will ad cryptonight algo soon to this pool? maybe moreno?
you will ad cryptonight algo soon to this pool? maybe moreno?
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
August 27, 2016, 09:31:21 AM
Batch V1.07b is posted.
Fail-safe batch V0.1.0 posted for those of you whom have issues with the batch starting many instances of ccminer at once.
Of course, algos I am not currently running are commented out and removed from the password string.
See the link in my signature for the new batch files.
I am interested in feedback on the new method for selecting specific GPU(s) for mining in the batch and any issues you guys may have.
I've been rather poor paying medical bills etc, and thus have let the internet lapse at my house for a few weeks and haven't had time/ability to really do a hardcore test of 1.0.7b thus the beta designation. But quadruple checking the code, and running the batch with timed-out network connections is an 80% test.
All the new web addressing is covered and up to the new specs in both versions I posted today.
Happy saturday! I get to fix more audio equipment (working on my 3rd mixer in two days now) and do a few shows in SF this weekend.
Fail-safe batch V0.1.0 posted for those of you whom have issues with the batch starting many instances of ccminer at once.
Of course, algos I am not currently running are commented out and removed from the password string.
See the link in my signature for the new batch files.
I am interested in feedback on the new method for selecting specific GPU(s) for mining in the batch and any issues you guys may have.
I've been rather poor paying medical bills etc, and thus have let the internet lapse at my house for a few weeks and haven't had time/ability to really do a hardcore test of 1.0.7b thus the beta designation. But quadruple checking the code, and running the batch with timed-out network connections is an 80% test.
All the new web addressing is covered and up to the new specs in both versions I posted today.
Happy saturday! I get to fix more audio equipment (working on my 3rd mixer in two days now) and do a few shows in SF this weekend.
August 26, 2016, 04:47:14 PM
...It then gets set to 211 on kano...
...I've got around 24.7 THs...According to the logs, 211 was set as the initial diff after the zpool disconnect and failing over to kano:
Code:
2016-08-25 23:03:15,975 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool zpool in 15.0 seconds.
2016-08-25 23:03:16,015 INFO [192.168.80.101-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.101 subscribed. 1 connections active on pool Kano.
2016-08-25 23:03:16,020 INFO [192.168.80.102-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.102 subscribed. 2 connections active on pool Kano.
2016-08-25 23:03:16,227 WARN [192.168.80.102-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.102. methodName: mining.multi_version, id: 56912, params: [1]
2016-08-25 23:03:16,234 WARN [192.168.80.101-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.101. methodName: mining.multi_version, id: 60712, params: [1]
2016-08-25 23:03:21,962 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 211.0 on pool Kano.
2016-08-25 23:03:21,967 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:16,015 INFO [192.168.80.101-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.101 subscribed. 1 connections active on pool Kano.
2016-08-25 23:03:16,020 INFO [192.168.80.102-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.102 subscribed. 2 connections active on pool Kano.
2016-08-25 23:03:16,227 WARN [192.168.80.102-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.102. methodName: mining.multi_version, id: 56912, params: [1]
2016-08-25 23:03:16,234 WARN [192.168.80.101-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.101. methodName: mining.multi_version, id: 60712, params: [1]
2016-08-25 23:03:21,962 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 211.0 on pool Kano.
2016-08-25 23:03:21,967 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
Moments later kano's pool starts rejecting shares at that diff:
Code:
2016-08-25 23:03:31,438 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool zpool for 30 seconds.
2016-08-25 23:03:31,447 WARN [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool zpool is UP.
2016-08-25 23:03:31,527 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 64.0 on pool zpool.
2016-08-25 23:03:31,530 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool zpool.
2016-08-25 23:03:35,710 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:37,584 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:38,646 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool zpool.
2016-08-25 23:03:38,824 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:46,273 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 211.0) from [email protected] on Kano. Booo !!!!. Error: JsonRpcError [_code=null, message=null, traceback=null]
2016-08-25 23:03:31,447 WARN [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool zpool is UP.
2016-08-25 23:03:31,527 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 64.0 on pool zpool.
2016-08-25 23:03:31,530 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool zpool.
2016-08-25 23:03:35,710 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:37,584 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:38,646 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool zpool.
2016-08-25 23:03:38,824 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from [email protected] on Kano. Yeah !!!!
2016-08-25 23:03:46,273 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 211.0) from [email protected] on Kano. Booo !!!!. Error: JsonRpcError [_code=null, message=null, traceback=null]
In around a minute from the disconnect event, the proxy determined that zpool was stable and pointed back at it, so kano's pool never got an opportunity to ramp up. Zpool set the diff back to 64 (ouch) and it starts getting rejects due to "Invalid job id" errors:
Code:
2016-08-25 23:04:01,448 WARN [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Pool zpool is STABLE.
2016-08-25 23:04:01,450 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool Kano to pool zpool.
2016-08-25 23:04:01,452 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Close connection 192.168.80.101 since the on-the-fly extranonce change is not supported.
2016-08-25 23:04:01,458 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.80.101 closed. 1 connections active on pool Kano. Cause: Change extranonce not supported.
2016-08-25 23:04:01,460 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Close connection 192.168.80.102 since the on-the-fly extranonce change is not supported.
2016-08-25 23:04:01,464 INFO [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.80.101:49375.
2016-08-25 23:04:01,471 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.80.102 closed. 0 connections active on pool Kano. Cause: Change extranonce not supported.
2016-08-25 23:04:01,477 INFO [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.80.102:53840.
2016-08-25 23:04:01,517 INFO [192.168.80.101-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.101 subscribed. 1 connections active on pool zpool.
2016-08-25 23:04:01,521 INFO [192.168.80.102-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.102 subscribed. 2 connections active on pool zpool.
2016-08-25 23:04:03,276 WARN [192.168.80.102-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.102. methodName: mining.multi_version, id: 57067, params: [1]
2016-08-25 23:04:03,278 WARN [192.168.80.101-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.101. methodName: mining.multi_version, id: 60886, params: [1]
2016-08-25 23:04:06,562 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 64.0) from [email protected] on zpool. Booo !!!!. Error: JsonRpcError [_code=21, message=Invalid job id, traceback=null]
2016-08-25 23:04:01,450 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool Kano to pool zpool.
2016-08-25 23:04:01,452 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Close connection 192.168.80.101 since the on-the-fly extranonce change is not supported.
2016-08-25 23:04:01,458 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.80.101 closed. 1 connections active on pool Kano. Cause: Change extranonce not supported.
2016-08-25 23:04:01,460 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Close connection 192.168.80.102 since the on-the-fly extranonce change is not supported.
2016-08-25 23:04:01,464 INFO [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.80.101:49375.
2016-08-25 23:04:01,471 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.80.102 closed. 0 connections active on pool Kano. Cause: Change extranonce not supported.
2016-08-25 23:04:01,477 INFO [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.80.102:53840.
2016-08-25 23:04:01,517 INFO [192.168.80.101-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.101 subscribed. 1 connections active on pool zpool.
2016-08-25 23:04:01,521 INFO [192.168.80.102-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.102 subscribed. 2 connections active on pool zpool.
2016-08-25 23:04:03,276 WARN [192.168.80.102-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.102. methodName: mining.multi_version, id: 57067, params: [1]
2016-08-25 23:04:03,278 WARN [192.168.80.101-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.101. methodName: mining.multi_version, id: 60886, params: [1]
2016-08-25 23:04:06,562 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 64.0) from [email protected] on zpool. Booo !!!!. Error: JsonRpcError [_code=21, message=Invalid job id, traceback=null]
Zpool started accepting shares after setting a diff of 128. Took about 8 minutes to ramp up to the full difficulty (lower than before the disconnect because one blade had fallen over at some point during the above thrashing).
Note that I've changed both zpool and kano to have a minimum difficulty of 13722. Hopefully this will help with stability moving forward.
August 26, 2016, 03:28:20 PM
CrackFoo, sorry I'm newbe in zpool, what is "cleared" status mean on any coin that I already mine.. It's decrease my total earn drastically... So sad see my total earn decrease time by time even I mine in so profitable algorithm I'm just getting loss compare to the cost to get the coin... Thanks for the response...
August 26, 2016, 02:23:47 PM
...It then gets set to 211 on kano...
...I've got around 24.7 THs... August 26, 2016, 12:35:22 PM
sha is set to a starting diff of 64, so I'm going to jack that up to 2000 as the majority of miners are above that anyway and I'm not going to use a x2 number as I think someone said bitmains get a bit funky when they're on a x2 diff?
This should make it a bit easier on re-connecting miners with high hashrates, so they don't have to spit out so many shares at diff 64 before the diff starts to change.
This should make it a bit easier on re-connecting miners with high hashrates, so they don't have to spit out so many shares at diff 64 before the diff starts to change.
Thank you, that 64 min diff was killing me.
August 26, 2016, 10:06:43 AM
Looks like my problem started happening at 23:03:15 Pacific time last night.
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
sha is set to a starting diff of 64, so I'm going to jack that up to 2000 as the majority of miners are above that anyway and I'm not going to use a x2 number as I think someone said bitmains get a bit funky when they're on a x2 diff?
This should make it a bit easier on re-connecting miners with high hashrates, so they don't have to spit out so many shares at diff 64 before the diff starts to change.
Thanks. That sounds like a good change.
But I'm probably still going to set a minimum difficulty, just in case. I did some searching and the recommendation is around 1 per 1.8 GHs for an average of 25 shares per minute. I've got around 24.7 THs, so that works out to a minimum difficulty of around 13722. I guess I'll try that.
August 26, 2016, 10:00:28 AM
Looks like my problem started happening at 23:03:15 Pacific time last night.
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
sha is set to a starting diff of 64, so I'm going to jack that up to 2000 as the majority of miners are above that anyway and I'm not going to use a x2 number as I think someone said bitmains get a bit funky when they're on a x2 diff?
This should make it a bit easier on re-connecting miners with high hashrates, so they don't have to spit out so many shares at diff 64 before the diff starts to change.
August 26, 2016, 09:56:54 AM
I have some s5 miners on this pool
I find they slowly drop hash through the day and need rebooting.
On CK pool they were stable.
Is there any way of stabilising the hash rate? I have tried a few settings for the difficulty but they all slowly drop.
I find they slowly drop hash through the day and need rebooting.
On CK pool they were stable.
Is there any way of stabilising the hash rate? I have tried a few settings for the difficulty but they all slowly drop.
have you tried using the stratum-proxie thing-a-majig that someone mentioned a little while ago?
everything "Java" on this pc (win10) falls flat.
August 26, 2016, 09:52:11 AM
Looks like my problem started happening at 23:03:15 Pacific time last night.
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
August 26, 2016, 09:24:38 AM
I jumped back on the pool yesterday lured by the increased profitability.
It was great until one of my S9 blades fell over again sometime over night. I woke up to the middle blade displaying all x's.
I think it happened around 11 PM Pacific time. At least the graph shows a drop off sometime around then. I'll check the logs to see if I can find an event.
This never happened on Kano.is, where I've mined since June. This is the second time that I've mined on zpool, and the second time that a blade fell over. I've restarted and pointed back at Kano and the middle blade is back and working fine.
I am using the Stratehm stratum-proxy. Doesn't seem to matter.
I have not specified a minimum difficulty. Last time this happened I think I noticed the difficulty being very low (64).
Maybe there's a Bitmain firmware problem that causes a blade to look disconnected if it runs at too low a difficulty and floods the controller with shares. Just a guess. Since Bitmain hasn't released their S9 source, no one can look at it.
Any suggestions for getting my S9s to be stable on zpool would be appreciated.
It was great until one of my S9 blades fell over again sometime over night. I woke up to the middle blade displaying all x's.
I think it happened around 11 PM Pacific time. At least the graph shows a drop off sometime around then. I'll check the logs to see if I can find an event.
This never happened on Kano.is, where I've mined since June. This is the second time that I've mined on zpool, and the second time that a blade fell over. I've restarted and pointed back at Kano and the middle blade is back and working fine.
I am using the Stratehm stratum-proxy. Doesn't seem to matter.
I have not specified a minimum difficulty. Last time this happened I think I noticed the difficulty being very low (64).
Maybe there's a Bitmain firmware problem that causes a blade to look disconnected if it runs at too low a difficulty and floods the controller with shares. Just a guess. Since Bitmain hasn't released their S9 source, no one can look at it.
Any suggestions for getting my S9s to be stable on zpool would be appreciated.
Jump to: