Calculation courtesy of organofcorti - thanks!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2233. (Read 5352633 times)
November 13, 2014, 09:12:22 AM
Added CDF in case anyone wants it and understands it
Calculation courtesy of organofcorti - thanks!
Calculation courtesy of organofcorti - thanks!
November 13, 2014, 04:12:01 AM
Its really convenient to be able to check confirmations without logging in too.
November 13, 2014, 02:37:38 AM
Just added a public Pool->Blocks menu so non-members can see the awesomeness of our past luck on the web site without having to login 
November 13, 2014, 12:05:33 AM
Hi Kano,
Just wanted to let you know something about "REGISTERING."
The first time I registered under the user name "Proud Clown" [with a space], my rigs never did want to connect to your pool with Proud Clown_worker1 in my S3's.
When I went back in and created another account with the user name "ProudClown" [no space], my rigs connected just fine with ProudClown_worker1 in my S3's.
When registering, it never told me I could not use a space. I was quite happy at first because it appeared that I could WHEN REGISTERING. However, when I entered my worker name with a space in my worker box in "miner configuration" it would not connect. It was dead every time.
So, when you have the time [which I know that is limited at the moment] you might want to look into making it where people cannot register with a user name with a space in it.
Proud Clown
I'd guess you missed putting quotes around it like "Proud Clown_worker1" for cgminer?Just wanted to let you know something about "REGISTERING."
The first time I registered under the user name "Proud Clown" [with a space], my rigs never did want to connect to your pool with Proud Clown_worker1 in my S3's.
When I went back in and created another account with the user name "ProudClown" [no space], my rigs connected just fine with ProudClown_worker1 in my S3's.
When registering, it never told me I could not use a space. I was quite happy at first because it appeared that I could WHEN REGISTERING. However, when I entered my worker name with a space in my worker box in "miner configuration" it would not connect. It was dead every time.
So, when you have the time [which I know that is limited at the moment] you might want to look into making it where people cannot register with a user name with a space in it.
Proud Clown
I've registered a username on my home test pool with a space and it works ok for me - so that's probably the reason.
Yeah the home pool is the same thing - it's where I test changes also before they go live - so far I'm 1.85% of a block on my home pool since I started writing ckdb
Though that keeps going down ... since I don't mine much there ... diff rises make it go down each time - I think it was above 2% once.
November 12, 2014, 07:22:11 PM
This is tempting!
November 12, 2014, 07:12:40 PM
Another block
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
dodo dood dood dood another one bites the dust, and another one down and another one down, another one bites the dust......
having an issue with a new long tube that came in today. I have it running at www.mmpool.org but can't get it to run here. using minera will post a screen shot after supper.
The original ignores some of the pool settings and thus if the pool doesn't match the tube settings, it wont work.
That's why ckolivas has extra tube solo pool instances, the extra hacked to match the tube.
ckdb doesn't yet support multiple ckpools talking to it.
no worries then I will move some other miners around to you.
November 12, 2014, 06:40:46 PM
Another block
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
dodo dood dood dood another one bites the dust, and another one down and another one down, another one bites the dust......
having an issue with a new long tube that came in today. I have it running at www.mmpool.org but can't get it to run here. using minera will post a screen shot after supper.
The original ignores some of the pool settings and thus if the pool doesn't match the tube settings, it wont work.
That's why ckolivas has extra tube solo pool instances, the extra hacked to match the tube.
ckdb doesn't yet support multiple ckpools talking to it.
November 12, 2014, 06:30:26 PM
Another block
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
dodo dood dood dood another one bites the dust, and another one down and another one down, another one bites the dust......
having an issue with a new long tube that came in today. I have it running at www.mmpool.org but can't get it to run here. using minera will post a screen shot after supper.
November 12, 2014, 06:00:12 PM
Another block
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
74% diff
https://blockchain.info/block-index/491090/00000000000000000dc85348919480f04044764491d60dd5cf0f290ab6d40205
dodo dood dood dood another one bites the dust, and another one down and another one down, another one bites the dust......
November 12, 2014, 05:50:53 PM
Would it be better to run it in passthru proxy or standalone? I've used it as standalone for some other pools before. It worked pretty well. Way easier than having 40 smaller miners opening their own connections.
I leave that for ckolivas to reply later since he'll get the technical reasons right November 12, 2014, 05:46:51 PM
November 12, 2014, 09:10:47 AM
Would it be better to run it in passthru proxy or standalone? I've used it as standalone for some other pools before. It worked pretty well. Way easier than having 40 smaller miners opening their own connections.
November 12, 2014, 09:07:25 AM
Payout 329574 sent and just confirmed.
Though the proxy is running on the same server so the added latency is almost nothing.
If you run in passthrough mode each worker you have will be a worker on the pool and ckproxy will use the minimum resources.
It combines all the miners on a single tcp/ip connection, but they are still all treated as separate workers.
However there's no ckproxy logging of the workers in passthrough mode.
Thanks - you didn't have to do that - but it's appreciated.
I'm still going to see if I can mess with pointing everything to a local instance of Ckpool in proxy mode and see if that makes things smoother.
That's actually how the extra ports (80, 81, 443 and 8080) work.I'm still going to see if I can mess with pointing everything to a local instance of Ckpool in proxy mode and see if that makes things smoother.
Though the proxy is running on the same server so the added latency is almost nothing.
If you run in passthrough mode each worker you have will be a worker on the pool and ckproxy will use the minimum resources.
It combines all the miners on a single tcp/ip connection, but they are still all treated as separate workers.
However there's no ckproxy logging of the workers in passthrough mode.
November 12, 2014, 08:56:58 AM
Im getting spoiled by this pool. Thank you for another payment. Now lets find another block.
November 12, 2014, 08:48:50 AM
Thanks - you didn't have to do that - but it's appreciated.
I'm still going to see if I can mess with pointing everything to a local instance of Ckpool in proxy mode and see if that makes things smoother.
I'm still going to see if I can mess with pointing everything to a local instance of Ckpool in proxy mode and see if that makes things smoother.
November 12, 2014, 03:23:48 AM
We'll wait for you to get the payments section sorted out, then start buggin you for multi-colored, slick, fancy, charts of all kinds of useless data.
November 12, 2014, 02:16:43 AM
... and ... another one.
17% diff.
Awaiting confirm ...
Edit: forgot to add - yep it confirmed.
17% diff.
Awaiting confirm ...
Edit: forgot to add - yep it confirmed.
Holy cow - I found a block. That's a pretty cool feeling. And it was from a Black Arrow Prospero X-3, I guess proving that 1TH miners still can find blocks.
I presume you must be fls then
I've added into this payout all your dust from before and gave you ~half my mining payout even though I'm only mining a fraction of you, so it's not much.
Your dust had added up to 1792satoshi and ~half mine was another (tiny) 0.0063BTC (so only worth a couple of dollars - oh well)
But I have to keep at least something mining so I can put a small fee in each payout
Congrats on finding the block, yep even the smaller miners can find a block once in a while!
though you're not that small any more ...
I'll add the dust into other's normal payouts (if they've gone above dust mining) once I've sorted out the mining/payments web pages
Still not done yet sorry - but not much left in the way to delay getting it done.
Edit: anyone looking at the payout payment on blockchain and is curious about the 2 extra small inputs, they are dust/change from previous payouts.
The last address on all payouts, except the first payout, is the dust/change address I create each payout.
November 11, 2014, 08:59:28 PM
Thanks Kano! This is without a doubt the most transparent pool I've ever mined at.
Don't forget for now luckiest (or very well coded) either way I will take it. Thanks again for providing us a very good pool to point our hash at.
November 11, 2014, 07:07:55 PM
Thanks Kano! This is without a doubt the most transparent pool I've ever mined at.
November 11, 2014, 05:58:04 PM
3 payouts done since I last posted (on the previous page)
1 last night and 2 this morning.
the 3rd payment hasn't confirmed yet.
329441, 329468 and 329482
And yep as everyone already knows - another low % block overnight
Edit: last payout now confirmed
Edit2: I should add, anyone wanting to see the specific generations and payouts you can see them all here
(unless I change the main generation address in the future)
https://blockchain.info/address/1KzFJddTvK9TQWsmWFKYJ9fRx9QeSATyrT
... since I do the payouts directly from the generation transaction,
since that ensures there's one payout per block, any missed will be obvious and no way to accidentally double pay.
Edit3: the double spend warning at the top is coz blockchain is stupid
It's caused by the fact our 2nd block was an orphan and blockchain decides that the existence of an orphan (even though we didn't even try to spend it) is a double spend ... morons.
1 last night and 2 this morning.
the 3rd payment hasn't confirmed yet.
329441, 329468 and 329482
And yep as everyone already knows - another low % block overnight
Edit: last payout now confirmed
Edit2: I should add, anyone wanting to see the specific generations and payouts you can see them all here
(unless I change the main generation address in the future)
https://blockchain.info/address/1KzFJddTvK9TQWsmWFKYJ9fRx9QeSATyrT
... since I do the payouts directly from the generation transaction,
since that ensures there's one payout per block, any missed will be obvious and no way to accidentally double pay.
Edit3: the double spend warning at the top is coz blockchain is stupid
It's caused by the fact our 2nd block was an orphan and blockchain decides that the existence of an orphan (even though we didn't even try to spend it) is a double spend ... morons.
Jump to: