Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2245. (Read 5352229 times)

Multiple/Regional front end servers already works.

Currently the back end is a single server and I'm not sure how long until I get to changing that.
Things keep popping up that need to be done for the pool (and of course irl )

Distributing the back end is high on the todo list though.

Well, not sure if this answers your question exactly, but ...

Your accepted shares (A:) in cgminer should match the accepted shares at the pool.
The rejected shares (R:) in cgminer represents the invalid % on the pool.
Of course you'd have to have restarted cgminer when we found a block to get an exact match, but the delta-numbers should of course match.

Any other share counts in cgminer (Stale, HW:) are not sent to the pool so they wont count in the pool total.


Though, there is a secondary issue of course.
The issue of if the pool is reporting all users correctly.
e.g. I could set my hash rate (or the hash rate of a user I created that no one knows it's me) to be double what it is so that I get paid twice as much.
The only way to know if this might be the case would be if long term the pool block count vs. the pool total hash rate was low.
Though, if there was block withholding that would show up the same.
Unfortunately with a small pool (where this would have the biggest effect) the block count is pretty low so it would take quite a while to be able to tell.


Also note that I show the 5 minute hash rate in the top left and the pool stats, so it varies a bit more.
The worker stats shows the 5 minute stat until you've been connected for an hour then it switches to the 1 hour stat.


And of course, anyone curious about how it all works, the source code is in git.
I run the exact C code in there with only one change to stratifier.c and ckpool.c, the 0.9% fee and where it's paid.
The web is slightly changed to show the different payout info vs what git says - otherwise it's all the same.

I think you will find that is the expected performance increase associated with the CKPool software 

Is there a way to tell if a pool is skimming?  I'm just curious, because I've noticed a 5-8% increase in pool side hashing with this pool compared to where I was earlier. It's probably within anticipated variance, but still curious.

Oh and since you asked, (and while I'm whining about web-side bugs):


I can login to the website on my phone (repeatedly, compulsively, all day long, on the bus, in line at the mini mart, and oblivious to speeding vehicles while crossing the street), but clicking on menus does not work, the clicks are totally ignored.  Tried using the iPhone's built in Mobile Safari browser as well as Chrome for IOS [emoticon face=frowney] Same problem with both browsers on the iPad Mini too [double frownie-face].

Oh, and one other thing!  (This is more of a feature request than a bug report, but...)

Instead of telling me "You're lost!" when I type kano.is into my browser, could you correct that to say:


You might even add:


{insert wry, winking smiley here}

thanks, in advance...

-dave

Wow

    => Pool Hashrate: 226.86THs <=

Shaa... Weet.

Hey Kano, how come my payout isn't shown on the Account / Payments page?  You gonna make me start keeping my own records?  The IRS won't take "Kano never implemented that" for an answer, ya know.  Especially when the price goes TTM Real Soon Now!

thanks,

-dave, now all in, and pretty much constantly leaning on the refresh button all day at work while I should be ...er, working :-)

I've got a server on the west coast I can put this on ... as long as it's mostly pnp.

M

Do you have an ETA in which the software would allow regional servers to allow a more global system, even if not shared with other pool operators?

--->>>  We just past 200Th...  Lets get this up to 1Ph...

Heh - that's the same "quick and dirty" I use on the workers page
That of course is only correct if you have been mining at the same rate as the current block rate for one whole N in PPLNS when we find a block
(that's actually what that cryptic comment on the bottom of the workers page means )

I'll look into it for the address pages.

Been chasing around server suppliers ... now waiting on the new server to be configured up.

That "concept" is in the design - not implemented yet.
Basically as mentioned in the ckpool code thread, have a concept of pool siblings.
This will tie in to the multi backend code ... whenever I get to doing that.

In reality, in mining, there's no real "sharing" of work as such.
In this case it would just be the sharing of the block payout based on the amount of work done - so sharing the information about how much work is done, to share the block reward.
But that also requires trust.
Of course each pool will validate the work done by the other pool, so that will be one of the differences between absolute trust (multiple backends) and the sibling concept.
Basically, one pool would present it's hashes to another pool as a single user (for verification) and the other pool would payout that proportion of the hashes.
.. and the reverse for both.

This, of course, is simply a way of reducing variance.

Looks like we're past 180TH now

Any chance of dropping in % of shares or something like that in the mining by address data at http://www.kano.is/address.php?a= or http://www.kano.is/worker.php?a= ??
It'd be a nice quick and dirty look at what percentage of a block you might get.

Now after saying that, I'll go look at user stats page for registered users

That's awesome.  Can't wait to see how this pays out.

Just added ~50t to the pool.

-- Would be interesting if this could be connected to another pool to help the speed up process until mature with users - EG: piggy back on P2Pool, or allow several operators of this software to share a workload.

-- I'd be willing to put these in US-East, US-West, Singapore, AMS, Ireland so there was a 'close' version to the miners.

I'm bringin' my other 2TH over tonight, so I'll be all-in for the next block.

The trail of tears on the Slush statistics page has become just too painful to bear...

-dave

Good idea!

Done.

https://bitbucket.org/ckolivas/ckpool

Thanks.

I was gonna suggest CloudFlare too.  They protect the sites of security researchers/publishers when they start getting attacked by the organized criminal botnet operators...  but I dunno how CloudFlare's ip-hopping solutions would work with a stratum pool...

-dave

Where are the servers located? - I'd be interested in helping out with this and getting you some horsepower to operate on.  PM me.

Also, are you planning on releasing this software to the public?

Just moved my 5T over.  Thought I'd see what we can do.

You could also put it behind cloudflare. That would help in terms of preventing some DDoS. If you need other options hit me up, I got a background in cloud architecture I can help. I am using the pool myself right now, would be nice to see it grow

Check out the Azure stuff mate, pricing is good and services are rock solid. I run all my stuff on there.