Topic: ckpool.org CLOSED - page 166. (Read 162894 times)

yeah I started this rental and was at derp of .33  I moved it to .37

Excellent, thanks and good luck.

Remember to the other miners, on the very first block of the pool, it is effectively like a proportional pool so you can "hop" on and game it to get more reward if it's a lucky block than you otherwise could get on an established running pool.

 

cool I am going to increase rental  I want my derp to go up

Yes that's correct so I should explicitly say: DERP is your expected reward if a block is found now.

okay  so derp = my money due

and
my herp/ pool herp = derp

so I am renting right now   so my derp should rise  and my derp went from .33 to .35

From post #1...

"SPLNS calculation is done on the fly and updated every minute based as a product of HERP DERP.
Herp stands for Hash Extracted Rate Product - where each share is worth sqrt(MIN(share diff, network_diff) / work_diff) * work_diff / 2
Derp stands for Difficulty Extrapolated Reward Payment - where the reward equals the user's herp divided by the pool's herp.
The pool's Herp is simply added until it reaches 5 * network difficulty. After that it is biased every minute by scaling existing herp down to add the latest minute's herp and all users' herp is adjusted by the same scale the pool's was."

P.s. Landy1264 - thank you. Like I said informative little pool here.

http://ckpool.org/users/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje


{
 "hashrate1m": "61.8T",
 "hashrate5m": "57.8T",
 "hashrate1hr": "47.6T",
 "hashrate1d": "5.67T",
 "hashrate7d": "2.26T",
 "lastshare": 1492808725,
 "workers": 1,
 "shares": 429389621,
 "bestshare": 340,875,420.0220159,
 "lns": 429389621.1,
 "luck": 1.03,
 "herp": 443064194.229417,
 "derp": 0.33836364,
 "worker": [
  {
   "hashrate1m": "61.8T",
   "hashrate5m": "57.8T",
   "hashrate1hr": "47.6T",
   "hashrate1d": "5.67T",
   "hashrate7d": "2.26T",
   "lastshare": 1492808725,
   "shares": 429389621,
   "bestshare": 340875420.0220159,
   "lns": 429389621.1,
   "luck": 1.03,
   "herp": 443064194.229417,
   "workername": "1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje.1"
  }
 ]
}

so  

what is derp?
what is herp?

I have 429,389,621  shares/

  Where do I find  the grand total of the pools shares?

http://ckpool.org/pool/pool.status

{"runtime": 61503, "lastupdate": 1492808908, "Users": 22, "Workers": 58, "Idle": 9, "Disconnected": 3}
{"hashrate1m": "315T", "hashrate5m": "323T", "hashrate15m": "322T", "hashrate1hr": "315T", "hashrate6hr": "285T", "hashrate1d": "265T", "hashrate7d": "103T"}
{"SPS1m": 12.1, "SPS5m": 12.2, "SPS15m": 12.2, "SPS1h": 12.1}
{"diff": 3.4, "accepted": 18156822714, "rejected": 46384868, "lns": 18156822717.3, "herp": 18140917911.71134, "reward": 14.01909947}


18,156,822,714   is this all the pools shares?


     429,389,621/18,156,822,714 = 0.02365  / 14.0 = .3311  which is close to my derp number

Put your adress after this -> http://ckpool.org/users/

DERP only by user not by worker!

But I had 150T running for a while.  I miss my DERP!! 

Me neither - that's OK. With my measly little ASIC generating...

"hashrate1m": "17.3G",
 "hashrate5m": "16.1G",
 "hashrate1hr": "16.5G",
 "hashrate1d": "14.1G",
 "hashrate7d": "3.97G",
 "lastshare": 1492805664,
 "shares": 645345,
 "bestshare": 838263.0,
 "lns": 645345.1,
 "luck": 1.04,
 "herp": 668007.6800807626

I'm just lookin' to collect me up some dust - when one of those PentaHash contributors, hits a block for the pool!

Thank you, -ck; for all your work. This pool's fun & informative.

How come I have no DERP??

 "hashrate1m": "34.2T",
 "hashrate5m": "35.8T",
 "hashrate1hr": "37.3T",
 "hashrate1d": "39.9T",
 "hashrate7d": "18.1T",
 "lastshare": 1492803208,
 "shares": 3275849805,
 "bestshare": 4087264624.971183,
 "lns": 3275849805.1,
 "luck": 1.0,
 "herp": 3286045206.756059

Restarts complete. All looking okay for now.

This change should make it unnecessary to have the per worker stats pages any more so I will be removing them on the next update.

Just an update about what's planned and happening with this pool.

I'm expecting a reasonably large hasher to come online within a month or so; the presence of such an interested party contributed significantly to me being interested in starting this pool in the first place.

The stats as they are currently displayed are awkward, I acknowledge, and some of the values displayed are unnecessarily showing lots of significant digits. This will be trimmed in the future to make it easier to read.

The pool LNS and HERP values will eventually converge once the pool reaches 5xN; the only time they will change after that is temporarily after a diff change until they converge again.

The current displayed "diff" with the pool is off by a factor of 10. It shows 0.15% diff when in fact it's 1.5% diff. This will be rectified on a future restart.

User stats show only the overall user statistics at the moment. The solo pool also shows per-worker stats on the same page which would allow a full summary of all user and worker stats in one convenient place, if somewhat crowded. I plan to port that change from solo to this pool.

I am toying with the idea of a most rudimentary GUI summary of the user stats in the near future just to make life easier for miners. I don't know what form this will take but an outsider has offered to help.

Further nodes: At this stage it would be hard to justify setting up an EU based node to mine to with the pool and it would be a less satisfactory mode of communication since the coinbase would need to be shared to another pool meaning delays there anyway. This means there would not be much advantage to miners local to that area since there would be the delays of communicating with the main pool anyway. At most I could provide a DE passthrough which would slightly decrease latency for miners who have a very slow communication with the main pool but overall it may not actually be a real world advantage counting the latency between the node and the main pool so I'm against it for now. Passthrough nodes tend not to have perfect 24/7 connectivity in the real world either which is why solo has them as two virtually separate pools that simply collate their statistics - that cannot be done with this pool.

Because of coinbase generation of payouts, there are potential issues with the coinbase getting very large if the number of users on this pool ends up growing dramatically. This could start slowing down communication to miners and worse, make the pool incompatible with some mining hardware that has limits on coinbase size. If we reach this size, I will rework the payout mechanism to limit the number of users paid with each block found and interleave users' payouts between blocks found. This would mean miners would not necessarily get a payout with every block found (but they'd be rewarded the same overall), but this change would only come about if the pool ends up getting large enough and blocks would be coming more frequently by then. The smallest miners would be the ones whose payouts would end up getting interleaved as this would then give them a better reward/transaction fee ratio. If it gets to this, the pending payouts would become part of the user statistics.

No more disadvantage than rentals have overall. Their cost is always more than their expected return. However given the pool is still very small, if it's lucky then you could be lucky and earn a much better return.

Rentals are a disadvantage in most cases (due to cost vs return), even more so in a pool this small.

Added 80+TH for a few hours to test out my older version of ckproxy.

Just means your miner has switched to a new diff too early on the instructions from the pool. In 30 seconds it would go away.

First time i've seen this...

[2017-04-19 19:01:51] Accepted 099a6d7d Diff 6.82K/4000 AMU 0 pool 1
[2017-04-19 19:01:55] Rejected 01799c3a Diff 174/76 AMU 0 pool 1 (Above target)

What does (Above target) indicate?

No restrictions. As the front page says; all ASICs are welcome. If your stats are showing your luck converging to 1, I wouldn't worry, but I haven't had mathematical proof that the luck estimate is spot on yet.


No, there's a disadvantage. I highly recommend multiple workers use different worker names but the same username. The reason is each payout will end up being a transaction in its own right, and spending rewards will end up requiring more transaction fees. Additionally if you have multiple small miners (eg. usb stick), you may never get over the dust threshold if you split them up. I should add this to the faq... but there haven't been hardly any questions yet so there aren't any frequently asked questions  

Added the first FAQs to the top post in anticipation of them being frequently asked.

Just http://ckpool.org/workers/YOUR ADDRESS