[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[icey]

Here's a painful eventuality for someone:

Code:

[2015-04-30 09:26:05] Possible block solve diff 47477499325.899284 !
[2015-04-30 09:26:05] SUBMIT BLOCK RETURNED: high-hash
[2015-04-30 09:26:05] Submitted, but rejected block 354334

Note that my ckpool code figures it may as well submit blocks that look very close to the diff in case there's a rounding error, but alas that really didn't meet the target which is currently 47610564513

So close...

Oh wow, 0.3% away.

How close does a hash need to be to network diff for the pool to submit it?

Ouch so close..

Best for me so far, nowhere near.. "bestshare": 2757206198.6944957}

[1714529949]

1714529949

[ezeminer]

*Gulp* Gonna take a chance renting hash.

[icey]

Good luck to you sir, its a gamble but fun nevertheless

[-ck]

nice/westhash:
some problems getting workers to connect because(got 10ths rented):
104.200.24.180:3333   Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000

Pool's starting diff is 1000 and it can work at any diff whatsoever from 1 up to virtually infinity. This is not my problem, take it up at their end.

[jonnybravo0311]

nice/westhash:
some problems getting workers to connect because(got 10ths rented):
104.200.24.180:3333   Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000

Pool's starting diff is 1000 and it can work at any diff whatsoever from 1 up to virtually infinity. This is not my problem, take it up at their end.

problem is when your rent order is not filled atall and waits price to drop.
meanwhile pool starts dropping diff to 4.
when price drops and you get, lets say 100ths hash instantly , its a problem when u have starting diff att 4 when big hashes hits.. so it disconnects.

Doesn't nice/westhash work by using your gear only if a rental meets a certain criteria?  I'm confused why it would drop the difficulty down to say 4... and then suddenly hammer that with 100TH/s.  Also, why don't you just set the difficulty yourself?

Code:

cgminer -o stratum+tcp://stratum.westhash.com:3334 -u YOUR_BITCOIN_ADDRESS -p p=0.01;d=1024

Wouldn't that solve your problem?

[jonnybravo0311]

nice/westhash:
some problems getting workers to connect because(got 10ths rented):
104.200.24.180:3333   Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000

Pool's starting diff is 1000 and it can work at any diff whatsoever from 1 up to virtually infinity. This is not my problem, take it up at their end.

problem is when your rent order is not filled atall and waits price to drop.
meanwhile pool starts dropping diff to 4.
when price drops and you get, lets say 100ths hash instantly , its a problem when u have starting diff att 4 when big hashes hits.. so it disconnects.

Doesn't nice/westhash work by using your gear only if a rental meets a certain criteria?  I'm confused why it would drop the difficulty down to say 4... and then suddenly hammer that with 100TH/s.  Also, why don't you just set the difficulty yourself?

Code:

cgminer -o stratum+tcp://stratum.westhash.com:3334 -u YOUR_BITCOIN_ADDRESS -p p=0.01;d=1024

Wouldn't that solve your problem?

no, when im the one who rents from nice/westhash to mine here
happens rarely, but its annoying --->Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000
do we these days really need so low diff as under 128 values?

Then that's on west/nicehash to fix.  ckpool will automatically detect the hash rate and set the difficulty appropriately.  If for some reason the rentals initially connect at some low hash rate, then the pool would properly set the diff low.  The pool itself sets the starting diff to 1042 when you first connect and authorize.  I don't know the specifics of how west/nicehash move the rentals, but if you're experiencing this kind of behavior, then it's something they're doing on their end.  I know for a fact that when I point my own gear here it behaves appropriately.

[cisahasa]

nice/westhash:
some problems getting workers to connect because(got 10ths rented):
104.200.24.180:3333   Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000

Pool's starting diff is 1000 and it can work at any diff whatsoever from 1 up to virtually infinity. This is not my problem, take it up at their end.

problem is when your rent order is not filled atall and waits price to drop.
meanwhile pool starts dropping diff to 4.
when price drops and you get, lets say 100ths hash instantly , its a problem when u have starting diff att 4 when big hashes hits.. so it disconnects.

Doesn't nice/westhash work by using your gear only if a rental meets a certain criteria?  I'm confused why it would drop the difficulty down to say 4... and then suddenly hammer that with 100TH/s.  Also, why don't you just set the difficulty yourself?

Code:

cgminer -o stratum+tcp://stratum.westhash.com:3334 -u YOUR_BITCOIN_ADDRESS -p p=0.01;d=1024

Wouldn't that solve your problem?

no, when im the one who rents from nice/westhash to mine here
happens rarely, but its annoying --->Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000
do we these days really need so low diff as under 128 values?

Then that's on west/nicehash to fix.  ckpool will automatically detect the hash rate and set the difficulty appropriately.  If for some reason the rentals initially connect at some low hash rate, then the pool would properly set the diff low.  The pool itself sets the starting diff to 1042 when you first connect and authorize.  I don't know the specifics of how west/nicehash move the rentals, but if you're experiencing this kind of behavior, then it's something they're doing on their end.  I know for a fact that when I point my own gear here it behaves appropriately.

edit:

no, when im the one who rents from nice/westhash to mine here
happens rarely, but its annoying --->Disconnected. Pool difficulty too low.   Speed TH/s 0.6519   Current diff 4.0000
problems is related somehow because nice/westhash keeps connection to pool alive but submits no shares when price target not reached. i think nice/westhash dont care this problem atall..

so, do we these days really need so low diff as under 128 values? especially when targetting 47G.


current, OK: 104.200.24.180:3333   OK.   Miners 0    Speed TH/s 0.0000 Current diff 1000.0000
sometimes: 104.200.24.180:3333   OK.   Miners 0    Speed TH/s 0.0000 Current diff 4.0000

[Gws24]

nevermind

[os2sam]

  Speed TH/s 0.6519   Current diff 4.0000

This pools is setting 651.9Ghs to diff 4?  I find that hard to believe.

[jonnybravo0311]

  Speed TH/s 0.6519   Current diff 4.0000

This pools is setting 651.9Ghs to diff 4?  I find that hard to believe.

I think that's the problem from the nice/westhash side... it would appear that they are somehow keeping an authorized open connection with the pool, and vardiff is continuously lowering until it hits 4... then when the hash rate climbs, nice/westhash determines that the difficulty of 4 is too low for the hash rate and disconnects.

I know for a fact that ckpool properly addresses difficulty.  I've got 5 U2 sticks solo mining here and they get a difficulty of 7, so 651GH/s would definitely not see a diff of 4.

It's an issue on the nice/westhash side.

[os2sam]

  Speed TH/s 0.6519   Current diff 4.0000

This pools is setting 651.9Ghs to diff 4?  I find that hard to believe.

I think that's the problem from the nice/westhash side... it would appear that they are somehow keeping an authorized open connection with the pool, and vardiff is continuously lowering until it hits 4... then when the hash rate climbs, nice/westhash determines that the difficulty of 4 is too low for the hash rate and disconnects.

I know for a fact that ckpool properly addresses difficulty.  I've got 5 U2 sticks solo mining here and they get a difficulty of 7, so 651GH/s would definitely not see a diff of 4.

It's an issue on the nice/westhash side.

By the same token it wouldn't bother me if my Block Erupters got set to diff 128 or even higher.  But then someone would have a problem with that too, I'm sure.

[jonnybravo0311]

  Speed TH/s 0.6519   Current diff 4.0000

This pools is setting 651.9Ghs to diff 4?  I find that hard to believe.

I think that's the problem from the nice/westhash side... it would appear that they are somehow keeping an authorized open connection with the pool, and vardiff is continuously lowering until it hits 4... then when the hash rate climbs, nice/westhash determines that the difficulty of 4 is too low for the hash rate and disconnects.

I know for a fact that ckpool properly addresses difficulty.  I've got 5 U2 sticks solo mining here and they get a difficulty of 7, so 651GH/s would definitely not see a diff of 4.

It's an issue on the nice/westhash side.

By the same token it wouldn't bother me if my Block Erupters got set to diff 128 or even higher.  But then someone would have a problem with that too, I'm sure.

I'm right there with you.  I wouldn't care if the minimum diff was 128 or 512 or whatever.  None of it means squat anyway on this pool.

[cisahasa]

 Speed TH/s 0.6519   Current diff 4.0000

This pools is setting 651.9Ghs to diff 4?  I find that hard to believe.

I think that's the problem from the nice/westhash side... it would appear that they are somehow keeping an authorized open connection with the pool, and vardiff is continuously lowering until it hits 4... then when the hash rate climbs, nice/westhash determines that the difficulty of 4 is too low for the hash rate and disconnects.

I know for a fact that ckpool properly addresses difficulty.  I've got 5 U2 sticks solo mining here and they get a difficulty of 7, so 651GH/s would definitely not see a diff of 4.

It's an issue on the nice/westhash side.

you got the point, thats the question
that keeps me thinking is it possible to attack ck pool with low diff shares, not so useful(and expensive with 2pths) at these days , but still..

[philipma1957]

Has anyone hit renting with nice or west hash?  I have spent quit a bit of coin attempting it.  not 40 or 50 maybe 10 btc

 Curious to know how many of the  41 blocks have been hit by nice-west hash rentals.

For instance  727miner used MRR

[cisahasa]

Has anyone hit renting with nice or west hash?  I have spent quit a bit of coin attempting it.  not 40 or 50 maybe 10 btc

 Curious to know how many of the  41 blocks have been hit by nice-west hash rentals.

For instance  727miner used MRR

not me, but ppc blocks i got plenty using nice/west

[Gws24]

no luck renting on nicehash but then again also no luck renting on mrr since my block in september last year.

[thedreamer]

Has anyone hit renting with nice or west hash?  I have spent quit a bit of coin attempting it.  not 40 or 50 maybe 10 btc

 Curious to know how many of the  41 blocks have been hit by nice-west hash rentals.

For instance  727miner used MRR

I threw 3 BTC over the past 2 weeks on and off from westhash about 0.0097avg, no wins.

[-ck]

that keeps me thinking is it possible to attack ck pool with low diff shares, not so useful(and expensive with 2pths) at these days , but still..

Why do you think it would let you continue mining at the low diff? As soon as the hashrate climbed it would just keep bumping your diff up and ckpool has the fastest adapting diff algorithm in use of any pool software. ckpool also happens to be absurdly scalable (which was the whole point of the design when I started writing it) so it could likely handle 100k clients. There are much more effective ways to "attack" a pool, like any server, though there's really nothing to gain by attacking this one, just downtime.

[itod]

Has anyone hit renting with nice or west hash?  I have spent quit a bit of coin attempting it.  not 40 or 50 maybe 10 btc

 Curious to know how many of the  41 blocks have been hit by nice-west hash rentals.

For instance  727miner used MRR

I threw 3 BTC over the past 2 weeks on and off from westhash about 0.0097avg, no wins.

Does anyone have a calculation how many TH should one rent for a day to have an equal chance (50%/50%) hitting or not hitting a block?

[-ck]

I think that's the problem from the nice/westhash side... it would appear that they are somehow keeping an authorized open connection with the pool, and vardiff is continuously lowering until it hits 4... then when the hash rate climbs, nice/westhash determines that the difficulty of 4 is too low for the hash rate and disconnects.

I know for a fact that ckpool properly addresses difficulty.  I've got 5 U2 sticks solo mining here and they get a difficulty of 7, so 651GH/s would definitely not see a diff of 4.

It's an issue on the nice/westhash side.

Indeed this is not a problem with ckpool applying some kind of restriction on mining. I do have quite a few miners mining with 2GH or less, despite what you see here and the feedback of shares is helpful to them. If nice/westhash want to have an arbitrary lower limit on diff they support they should use the "suggest diff" method that is in the original stratum specification so that the pool knows what the mining client wants.