It's the minimum difficulty shares of work that will be sent to workers.
So the difficuly is ~158B. If I raise the mindiff in ckpool is there any benfit towards increasing the likelihood of mining a block? Why is the mindiff set to 1 is that only for the purpose of payment for shared pools? Sorry if I am lost on this. If I'm not mistaken, ckpool adjusts difficulty per user hashrate. There's probably a description on solo.ckpool.org or kano.is (the two most prominent pools I know of using ckpool backend). |
|
|
|
What do the values for mindiff (in ckpool.conf) mean? "mindiff": 1 -> if I set that to ten does that mean 10 zeros min prepending the hash?
Is there any feedback or insight on manipulating mindiff - is there any benefit for a small pool?
Thanks,
It's the minimum difficulty shares of work that will be sent to workers. |
|
|
|
|
Is there anything built into notifier to notify a remotely running ckpool of block changes? or would I have to set up the remote machine to execute notifier locally via ssh? Also, if notifier runs once from a local bitcoind, will ckpool grab work from all listed bitcoinds? And what happens if notifier runs between block changes? anything catastrophic or just gets new work more often?
|
|
|
|
|
@thedreamer is your red line average above 250 TH/s?
|
|
|
|
If mining w/ ckpool via -A does found block get awarded to address in bitcoin.conf or ckpool.conf
And - can everyone stop mining for ten minutes so I can test my rig.
Thanks!
I believe ckpool.conf, but you can just make them both the same to be certain. |
|
|
|
Here's something interesting...this morning I sent a little BTC to nicehash to refill the tank a bit and it's been sitting at 0 confirmations all day along with 5 other transactions in my wallet. The interesting part is nicehash has given me access to my BTC even though the transaction is still at Transaction pending 0 confirmations. I've never seen anyone do that before...it's like NH want's me to use that BTC bad!
That is interesting! NH usually won't allow me to use my BTC deposits until 2 confirmations. Maybe they're feeling the sting of all these backed-up transactions? I sent some to NH this morning, it took a couple of hours to hit 2 confs. Longer than usual but not really a big deal. However, of the last 3 payments Kano sent only one of them has any confirmations. The other two are still either "unverified" or 0 confirmations in my wallet. I'll just agree with Phil that this is a good sign for network difficulty dropping... (That being said, good thing I don't try to buy coffee in the morning with BTC!  ) Interestingly enough, coffee.foldapp (spend BTC at Starbucks) has always been 0-conf for me in the past, but I haven't used it since RBF came out. |
|
|
|
Yep, my NH rental kicked down to the red area at 3am for 4 hours.
I cancelled it and resubmitted it. The new rental has also been stuck for 4 hours.
WBF1, thanks for the 2048 diff tip. That fixed the stuck NH rental on kano after restarting the rental.
Kano, I wonder why this changed? The difficulty on the workers management page? AAAHHH!
Anyone have issues connecting NiceHash rental to Kano pool today? Tried stratum 80, 81, and 3333 still no luck
I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page. After that, you probably need to restart your rental. I saw reference to changing worker diff but thought it needs to be done at NH side which is greyed out. That works. Thanks! from what I can tell, the diff setting on NH shows 127 => 2048 which means diff can start at 127 as long as it increases to 2048 after some time. problem might have occurred if workers disconnected from the pool, pool started difficulty extremely low (below 127) and never tried to increase it because no work was being done. Just one of those weird hiccups that can happen. also possible something happened pool side that reset min diff settings for workers, but kano or ck would have to confirm that. all is good now though. just make sure any nh workers have a min diff in the pool settings of 2048. The minimum pool diff is set to 42. Previously if you set a worker diff in the web site and then set it back to zero it would stick to the worker diffThat has been changed now and setting it back to zero will set it back to default and allow it to get as low as the pool allows - during a ramp up or ramp down of hashrate it might now be dropping diff to lower levels. Presumably if the lowest diff you can have is 127 on NH you will have to set it to 127 or higher for rentals with them now, but I'd suggest a sensible much higher value as you've done. Use hashrate in TH / 1.4 for the worker diff. Also, with using badhash there's no idea what random hardware will be mining, and various old bitmain firmware has issues with power of 2 diff values, so rather than 2048 I might suggest 2052. Thanks for this tip kano! |
|
|
|
|
Is teaming up allowed?
If so, anyone want to team up?
|
|
|
|
|
Maintenance complete as of 2016-02-29 @ 12:49 PM EST
|
|
|
|
Yep, my NH rental kicked down to the red area at 3am for 4 hours.
I cancelled it and resubmitted it. The new rental has also been stuck for 4 hours.
WBF1, thanks for the 2048 diff tip. That fixed the stuck NH rental on kano after restarting the rental.
Kano, I wonder why this changed? The difficulty on the workers management page? AAAHHH!
Anyone have issues connecting NiceHash rental to Kano pool today? Tried stratum 80, 81, and 3333 still no luck
I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page. After that, you probably need to restart your rental. I saw reference to changing worker diff but thought it needs to be done at NH side which is greyed out. That works. Thanks! from what I can tell, the diff setting on NH shows 127 => 2048 which means diff can start at 127 as long as it increases to 2048 after some time. problem might have occurred if workers disconnected from the pool, pool started difficulty extremely low (below 127) and never tried to increase it because no work was being done. Just one of those weird hiccups that can happen. also possible something happened pool side that reset min diff settings for workers, but kano or ck would have to confirm that. all is good now though. just make sure any nh workers have a min diff in the pool settings of 2048. |
|
|
|
Anyone have issues connecting NiceHash rental to Kano pool today? Tried stratum 80, 81, and 3333 still no luck
I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page. After that, you probably need to restart your rental. |
|
|
|
Looks like all my rentals died while I was asleep and never came back. Woke up and saw we'd had some dropouts/restart while I was sleeping, but usually everything bounces back once things get back to normal. This time only my S3 had managed to reconnect and was hashing.
After doing a little research, the problem was that since I had my diff at the pool set for all workers to 0, the minimum starting pool diff on the rentals was 1042, which is below the minimum on NH. Once I set my minimum diff on the workers page at the pool to 2084 they all came back to life.
Anyone else notice this? I've never had this become an issue before. Any dropouts in pool connectivity have reconnected pretty quickly once the pool restart completed or connectivity issues were resolved. Maybe NH recently updated their minimum pool difficulty setting?
happened to me too. Maybe they changed the min diff |
|
|
|
How many people get blocks on kano from rentals?
I have, but I still think NH/WH withhold blocks.   I wonder about that too, but wouldn't that mean mean blocks are getting solved elsewhere? Would have to check if increased nicehash rentals correlates to increase of blocks solved at some other specific pool. It's not like the hash provider pays out the solved block... |
|
|
|
And right behind the beautiful Kano CKPool double blocks at 964K+ each the next pool pulls an empty block at 0.22K...what the hell! Grrr  SPV mining. Annoying, but it's a natural outcome of the way bitcoin works. It's also a calculated risk for the mining pools... No, it's not a natural outcome, it's purely the results of pools being coded by shit quality coders. Luke-Jr started with empty blocks coz his pool code is so shitty and he got so many orphans. Bitmain and F2Pool continued the idea to generate the empty blocks even before verifying they are fully valid. What do they gain? Eligius - NOTHING - they are slower than us. Their pool code sux. SPV - a few hundred milliseconds - our block processing time is ALMOST NEVER over 1 second - it's usually around 300ms or less. The only natural side of it is the fact that when you let shitty programmers near code, they produce crap to overcome their lack of ability. I guess what i meant is that folks would naturally find hackish shortcuts to overcome local shortcomings rather than rolling up their sleeves and getting their hands dirty. |
|
|
|
And right behind the beautiful Kano CKPool double blocks at 964K+ each the next pool pulls an empty block at 0.22K...what the hell! Grrr SPV mining. Annoying, but it's a natural outcome of the way bitcoin works. It's also a calculated risk for the mining pools... |
|
|
|
Dear CKPool Kano, Good day to you CK Pool Kano Admin, I want to seek help from any of CKPool Kano Mining company regarding my problem, I was trying to find email address where I can contact CK Pool Kano but I can't find one. So I am trying my luck to post my problem here, that somebody might help me from concerned people here. So here is my problem; I encountered big trouble happened Feb. 18 with my bitcoin transaction using https://blockchain.info/, I sent 1 BTC to this address 15awcsvGd2xyVwab5eq1RSGfzG8ESY9Vf5 , but there was an error for unknown reason that the transaction fee was accidentally 1 bitcoin and I only noticed this after sending my bitcoin to the said address above. I want to ask support how if possible to recover my 1 BTC that was deducted as transaction fee. Please refer to my transaction below indicating 1 BTC transaction fee : https://blockchain.info/address/15awcsvGd2xyVwab5eq1RSGfzG8ESY9Vf5My transaction was relayed by Kano CKPool at Height #399022 https://blockchain.info/block-index/1070568I wish I could refund back my loss 1 BTC and return to my wallet address : 1JmFmpbKq7S36J7w2zpXPhJHFFj9Zc4Gbr I really appreciate your big help if I anyone can help me recover back my 1 BTC transaction fee by mistake. Hoping that a good heart from CK Kano company could read my message. Thank you and best regards, Manuel de Leon i'm sure kano will reply as well, but that fee was split between all miners here, which is currently 880 people. Refunding your fee would be the same as stealing from all 880 of us now. Like d57heinz I feel bad for you, but it's unlikely youll get any refund. |
|
|
|
Hi
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
Short answer is PPLNS is better than PPS because PPS is capped. For example, if you mine at a pool with 5% fee, paying PPS, the most you will ever make compared to expected payout is 95%... even if thepool hits a string of blocks at 50% dificulty (which means the pool income is roughly 200% expected income but you only get 95%). Works the other way too where a string of 200% difficulty blocks has the pool at roughly 50% expected income but you get 95%. PPS will always have higher fee to make up for variance. In the above scenario, on PPLNS, you get 200% of expected income when the pool hits a string of fast blocks at 50% difficulty and 50% expected income when with a string of 200% blocks. BUT PPLNS smooths out this variance using a window of size N to look backwards and see what portion of the payout you get. The only time work isever unpaid is when work on one block goes over 500% (because N here is 5d where d is difficulty). This hasn't happened very often. And like phillipma1957 said, you have to look at it over a longer time span. At time spans of 7 days or more, this pool is over 100%. |
|
|
|
|
2016-02-26 @ 7:00 PM EST: Doing some maintenance for the next few hrs. Expect intermittent connection.
|
|
|
|
|
Well it's Friday here now. Bumped up to 500 TH on my rental. Maybe we can make it block Friday... Do eggs for breakfast count as chicken sacrifice?
|
|
|
|
|
Show Posts
