Author

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

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Why cant I cut or copy from paint and paste here?
No, that's not the question.
I'm on the shifts page.
The names to the left appear really random and multi-national. Are they randomly generated to help identify the shift?
Shifts appear to be around 45 minutes so I guess that if you're mining for more than that, you're 'in' for that shift.
The 'your diff' column says 60/63 but I'm mining at diff 80.
What's the 'inv diff'. It's either 0 or 80 as I read it. Why the difference?
Why to the right is the PPS%? It's either 0 or if I scroll down it jumps to 19 or so%. Why does this matter.

If you want to make mountains out of molehills I can help.
To expand on the reply already given Smiley

The characters to the left of the shift name are a base 32 encoding of (the number of seconds since 2-Jan-2014) / 16
The name on the right is an incrementing a-z name for each consecutive shift.

The "Your Diff" is the total share Difficulty you submitted in that shift
The "Inv Diff" is the total rejected share Difficulty you submitted in that shift

The PPS% is how much each share has been rewarded compared to 100% PPS
Shifts above the red line may be rewarded again (they are expected, on average, when pool luck is 100%, to be rewarded 5 times)
Shifts below the red line will not be rewarded again and their final PPS% value won't increase.
The BTC marker shows each block found and thus the PPS% will change (go up) at that point, reading down the page.
When a difficulty change occurs, you will notice that the shift PPS% is also affected.
Shifts (as of recently) also end on the network block before a difficulty change.

tl;dr of the shift name follows:
The shift 'code' makes for a small but readable code that (as you may notice) increases with each shift
However, the first 5 characters are not guaranteed to be unique, since more than one shift could start/end within 16 seconds, so I added a single character 'a' to 'z' on the end, since it's not possible to have 26 shifts end in 16 seconds.
Thus I had a small and simple to read (currently 5+1 character) code rather than a long number
Then I had the idea of instead using a name for each letter since it was more interesting Smiley
You will notice that the a-z character added on the end is always sequential, so for any sequence of 26 shifts, that's unique, so it's easy to identify a shift by name (e.g. kosaki) without having to remember the full 5 character code and not confuse which one, if you refer to the approximate time also. A shift a-z name can usually only occur at most twice a day.
legendary
Activity: 1726
Merit: 1018
I remember when ck's signature read to the effect 'only ignoring luke jr.'
That's when I tried to figure out who's who or what around here and I came to the conclusion that jr. guy was some sort of a jesus freak who also happened to 'pick up' on ck's early open source? miner and bend it to his liking. This is my current understanding.

To the point, jesus freaks aren't supposed to steal and cheat. This too is my current understanding.
And he's still the only person on my ignore list. Unfortunately in that time the landscape has changed so much and so many people have moved on and newcomers replaced them that the reason for the argument is not known by many of the current people in the bitcoin world - most people think it's a simple matter of "why don't you just make up and be friends?". But search enough and the history on the internet doesn't lie about where source code came from, who wrote it first, what claims were made, and how ridiculous he was, is and will continue to be. Then one can understand why that is not a solution. The biggest continuing problem is I try to remain out of the arguments, but in this world if you don't defend yourself, then people just end up believing the person who shouts loudest and longest and silence is assumed as guilt through being unable to defend oneself. Kano enjoys such fights and I have him to thank for defending when the trolling resurfaces (as it often does). I have no time for them...

My observation, for what it is worth, is that actually Kano trolls the eligius thread.  My further observation is that it is readily apparent why nobody can get along with Luke Jr because he posts like someone who is mentally incapable of understanding that other people have valid points of view that differ from his own.  He speaks from the assumption that he is already 100% correct. I have always found wizkid to be reasonable although to the most recent issue, why he wouldn't think that it was worthwhile to prevent people throwing away their hashrate if they incorrectly enter an address I do not know.  Maybe just because Kano showed up to troll about it.  I can understand taking a position just because someone who bugged me tried to force me to take another.  Also just for the record @kano, no I don't think you are simply a troll and I find you a pretty reasonable voice in general but there is no doubt that your posts in the eligius thread are trolling in nature, as I said, just an observation.  You seem to have an axe to grind and every so often you stop by there to grind it.

I have been mining on eligius for a couple years, I have also mined here in the past, and have mined on bitminter for over a year (and most of the other smaller pools at some point).  Organofcorti made a recommendation to me a long time ago which I have tried to follow as to spreading hashrate on multiple pools to decrease variance, and I have always tried to support smaller pools to help reduce centralization.  I did move half of my eligius hashrate back over here after this latest little dust up though.  I thought Luke's "lol" response to someone mining with more then a Petahash on a misconfigured address was more over the top a-hole than even he usually manages.  But wizkid gave a reasonable response in that he would work with the miner if they asked to make sure they were compensated.  Even so, luck there has been horrible lately so I was contemplating moving anyway.
hero member
Activity: 777
Merit: 1003
Why cant I cut or copy from paint and paste here?
No, that's not the question.
I'm on the shifts page.
The names to the left appear really random and multi-national. Are they randomly generated to help identify the shift?
Shifts appear to be around 45 minutes so I guess that if you're mining for more than that, you're 'in' for that shift.
The 'your diff' column says 60/63 but I'm mining at diff 80.
What's the 'inv diff'. It's either 0 or 80 as I read it. Why the difference?
Why to the right is the PPS%? It's either 0 or if I scroll down it jumps to 19 or so%. Why does this matter.

If you want to make mountains out of molehills I can help.

The names are not random, they are alphabetical: akatsuki, belldandy, charlotte
Yes, they are used to identify the shift. Kano said they are female anime character names.

You don't need to be mining the whole shift to be "in", all shares submitted are counted and will be rewarded as long as they are within 500% of the next block found.

I'm not sure about how to explain the "your diff" and "inv diff", I'll let someone else answer those.

PPS% is the PPS equivalent for what we have been credited so far for that shift. Notice the ones that are 19.87% have rewards 1, meaning that those shifts have been counted in 1 block so far, then scroll down and see 39.69% have rewards 2, they have been counted in two blocks.
full member
Activity: 223
Merit: 100
Why cant I cut or copy from paint and paste here?
No, that's not the question.
I'm on the shifts page.
The names to the left appear really random and multi-national. Are they randomly generated to help identify the shift?
Shifts appear to be around 45 minutes so I guess that if you're mining for more than that, you're 'in' for that shift.
The 'your diff' column says 60/63 but I'm mining at diff 80.
What's the 'inv diff'. It's either 0 or 80 as I read it. Why the difference?
Why to the right is the PPS%? It's either 0 or if I scroll down it jumps to 19 or so%. Why does this matter.

If you want to make mountains out of molehills I can help.
sr. member
Activity: 266
Merit: 250
Love this quote:

The biggest continuing problem is I try to remain out of the arguments, but in this world if you don't defend yourself, then people just end up believing the person who shouts loudest and longest and silence is assumed as guilt through being unable to defend oneself..... I have no time for them...

The same could be said for a few other forum members on BCT I think  Wink
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
...
I noticed it was down on the website. It said the last share was submitted 4 days ago by worker 3. I will leave it a few days and try reinstalling the update. Is there anything i can show you or give to you if it happens again to diagnose the fault? If so i'm happy to help.
Well at this point I can only suggest running it without the update - since I'd expect it to have the same problem.

Note that unless you can reproduce the problem over a specific time range, you may find that switching between versions will have the expected random effect of "who knows when the problem will happen again"

One thing to look at with my cgminer version would be the stats output - e.g. temperature and usb errors.
The usb errors in the S3 aren't true usb errors, but rather show problems talking to the fpga that runs the chips.
If you have another computer you could periodically (every 5 minutes?) run and log an API summary+devs+estats and look for a pattern in that leading up to when it happens.

I did get someone with hundreds of S3s to test it and they are still using it, so I would have expected some response if it was failing after a period of time, thus I'd expect it to not be a cgminer issue.
member
Activity: 70
Merit: 10
Time is the one thing you can't run from
Has anybody had issues with Kano's s3 update? The day i moved my 2x s3's here i updated them with Kano's update. I bought anther s3 whilst mining here and it came with an earlier version of the update perhaps. I know it looked different to what i had with my other 2. I left it with that update. Saturday i noticed my hash rate was down a lot. I checked the miners and the most recent one wasn't hashing. There were no values in the status area. I rebooted it and stayed the same. unplugged it for a bit and powered on it was still the same. I did a factory reset through the web GUI and it started hashing again. So I put the latest update on the same as my other 2 and it hashed for a while so i thought problem was solved. I discovered yesterday it had died again sometime after the update. I have factory reset it again and is hashing happily again for the last 2 hours. Any good advice out there?

Noticed over the weekend that my 2 S3s (both /K software versions) started acting strange also but everything seems to be going well this morning. Just glanced at them now and both keep showing less than 10GH/s in the GH/S(5s) box, even though the pool stats show what I should be submitting.

It was, however, enough to plant the S7 seed in my head again...
One cause can be if the time jumps forward - the web/API elapsed will show that.
My update also checks if the time jumps forward more than 70 days and will kill and restart cgminer - that will also come into effect if it has been mining for 70 days.

If the time jumped forward a lot but less than 70 days it would show a low hash rate.
The pool of course will know the corrected hash rate based on the proper time.

The "Share Rate" on the Workers page can also help see that it's working ok - it shows the hash rate for the given short interval "«Elapsed"
It resets every network block, thus shows the shares submitted since then converted directly to a hash rate.
Note also, the "Share Rate" for my antminer cgminer versions will have high variance since I set the internal work difficulty as high as possible to match the pool work difficulty (but of course less than or equal to the pool difficulty)


I noticed it was down on the website. It said the last share was submitted 4 days ago by worker 3. I will leave it a few days and try reinstalling the update. Is there anything i can show you or give to you if it happens again to diagnose the fault? If so i'm happy to help.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Smiley

Payout 379604 sent
6905173afd98442c00f2a1db6fc69f3ce3b6fdf5a2305e419b8beac9935c964c
and confirmed
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I remember when ck's signature read to the effect 'only ignoring luke jr.'
That's when I tried to figure out who's who or what around here and I came to the conclusion that jr. guy was some sort of a jesus freak who also happened to 'pick up' on ck's early open source? miner and bend it to his liking. This is my current understanding.

To the point, jesus freaks aren't supposed to steal and cheat. This too is my current understanding.
And he's still the only person on my ignore list. Unfortunately in that time the landscape has changed so much and so many people have moved on and newcomers replaced them that the reason for the argument is not known by many of the current people in the bitcoin world - most people think it's a simple matter of "why don't you just make up and be friends?". But search enough and the history on the internet doesn't lie about where source code came from, who wrote it first, what claims were made, and how ridiculous he was, is and will continue to be. Then one can understand why that is not a solution. The biggest continuing problem is I try to remain out of the arguments, but in this world if you don't defend yourself, then people just end up believing the person who shouts loudest and longest and silence is assumed as guilt through being unable to defend oneself. Kano enjoys such fights and I have him to thank for defending when the trolling resurfaces (as it often does). I have no time for them...
full member
Activity: 223
Merit: 100
Heh Eligius are liars and thieves Smiley
No idea why anyone would mine there.

2 posts deleted from their thread:

What is this?

#15 (Unknown users) 183.02 Th/s 460225024 1.257%
LOL, that's people mining with an invalid address I think.

= donations.
scam
If you have a way to track these users down, you're welcome to share it.

On my pool we don't keep users connected with invalid connection details so we can steal their mining power = BTC.
Invalid address miners are not allowed to mine.

...
And as others have mentioned, it's not like rejecting the connections is going to benefit anybody.
...
Although you may think it wise to mine with a single account and no backup, most miners have realised for MANY years that is a foolish thing to do.

If one pool/account is rejected or fails when mining, cgminer (used by the vast majority of BTC miners on the planet) switches over to the secondary or later accounts it has been provided with.

If someone is dropping money on the street, it isn't the job of whoever finds it to hunt them down even if it is possible.
...
Well ... a few years ago a guy walking through a centre about 30m ahead of me dropped a small amount of paper.

When I got to it I noticed it contained cash.
I picked it up and it included over $100 ...

Though you may consider that a bad thing to do, I chased after him and gave it to him.
He hadn't even realised he'd dropped it.

And wizpants final comment Smiley
...
The accusations of stealing based on a well established policy are a bit absurd, and honestly I don't want to hear it.
...
I'm not going to implement valid address/worker name checking in the pool software.  It's not worth the time and effort when there are plenty of other things I can dedicate my time to.
Well established policy of stealing Smiley

Well ... it is a fee free pool ... where no one makes the expected payout ... for years ... they gotta get paid somehow for all their costs running the pool right?

I remember when ck's signature read to the effect 'only ignoring luke jr.'
That's when I tried to figure out who's who or what around here and I came to the conclusion that jr. guy was some sort of a jesus freak who also happened to 'pick up' on ck's early open source? miner and bend it to his liking. This is my current understanding.

To the point, jesus freaks aren't supposed to steal and cheat. This too is my current understanding.

full member
Activity: 223
Merit: 100
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Any idea's on what the minimum hash rate might be in order to get a fair share of the pie and not end up in the dust bin?
I know that 1GH will only create dust. So I wonder about the guys running 10GH or less and if they're getting paid.

Also, is any plan in place to add up the dust until it's no longer dust and qualify for a payout, or should I go dust myself off?

Riding the coattails of giants
Well a dust payout is < 10,000 satoshi (0.00010000 BTC or very roughly currently < 3 US cents)

Your Reward per payout will depend on the pool hash rate of course, since that also decides the expected average hashes per 5Nd payout, and you are rewarded your % of the 5Nd times the miner reward.

For the last payout my Reward numbers were:
Code:
Block   Block UTC     Miner Reward  N Diff    N Range        Pool N Avg  Your %  Your N Diff  Your N Avg  Your BTC
379604  19/Oct 11:49  24.84179216   304.453G  198hr 32m 59s  1.83PHs     0.07%   219.053M     1.32THs     0.01787361
So Avg 1.32TH was 0.07% was 0.0178BTC
So for that payout, roughly (1320GHs * 0.00010000 / 0.01787361) ~7.4GHs was around the dust reward mark.

Yes, I've still not done the dust accumulation code.
But no, your dust isn't lost, it's still there on your Rewards page, just not paid yet of course.
The code yet to be done requires I differentiate correctly between paid rewards and unpaid rewards - and record that on the payments.
legendary
Activity: 1274
Merit: 1000
Any idea's on what the minimum hash rate might be in order to get a fair share of the pie and not end up in the dust bin?
I know that 1GH will only create dust. So I wonder about the guys running 10GH or less and if they're getting paid.

Also, is any plan in place to add up the dust until it's no longer dust and qualify for a payout, or should I go dust myself off?

Riding the coattails of giants

Right now (based on pool size) I think you need more than 10 or 11 GH/s to see a payout that is more than the dust threshold (10,000 satoshi).

Yes, Kano has posted in this thread that at some point he will add code to sweep up the dust as part of the payout.  You can look back a few pages and find the most recent response.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Has anybody had issues with Kano's s3 update? The day i moved my 2x s3's here i updated them with Kano's update. I bought anther s3 whilst mining here and it came with an earlier version of the update perhaps. I know it looked different to what i had with my other 2. I left it with that update. Saturday i noticed my hash rate was down a lot. I checked the miners and the most recent one wasn't hashing. There were no values in the status area. I rebooted it and stayed the same. unplugged it for a bit and powered on it was still the same. I did a factory reset through the web GUI and it started hashing again. So I put the latest update on the same as my other 2 and it hashed for a while so i thought problem was solved. I discovered yesterday it had died again sometime after the update. I have factory reset it again and is hashing happily again for the last 2 hours. Any good advice out there?

Noticed over the weekend that my 2 S3s (both /K software versions) started acting strange also but everything seems to be going well this morning. Just glanced at them now and both keep showing less than 10GH/s in the GH/S(5s) box, even though the pool stats show what I should be submitting.

It was, however, enough to plant the S7 seed in my head again...
One cause can be if the time jumps forward - the web/API elapsed will show that.
My update also checks if the time jumps forward more than 70 days and will kill and restart cgminer - that will also come into effect if it has been mining for 70 days.

If the time jumped forward a lot but less than 70 days it would show a low hash rate.
The pool of course will know the corrected hash rate based on the proper time.

The "Share Rate" on the Workers page can also help see that it's working ok - it shows the hash rate for the given short interval "«Elapsed"
It resets every network block, thus shows the shares submitted since then converted directly to a hash rate.
Note also, the "Share Rate" for my antminer cgminer versions will have high variance since I set the internal work difficulty as high as possible to match the pool work difficulty (but of course less than or equal to the pool difficulty)
newbie
Activity: 49
Merit: 0
no problem with my 32 S3's noticied
full member
Activity: 223
Merit: 100
Any idea's on what the minimum hash rate might be in order to get a fair share of the pie and not end up in the dust bin?
I know that 1GH will only create dust. So I wonder about the guys running 10GH or less and if they're getting paid.

Also, is any plan in place to add up the dust until it's no longer dust and qualify for a payout, or should I go dust myself off?

Riding the coattails of giants
newbie
Activity: 16
Merit: 0
Has anybody had issues with Kano's s3 update? The day i moved my 2x s3's here i updated them with Kano's update. I bought anther s3 whilst mining here and it came with an earlier version of the update perhaps. I know it looked different to what i had with my other 2. I left it with that update. Saturday i noticed my hash rate was down a lot. I checked the miners and the most recent one wasn't hashing. There were no values in the status area. I rebooted it and stayed the same. unplugged it for a bit and powered on it was still the same. I did a factory reset through the web GUI and it started hashing again. So I put the latest update on the same as my other 2 and it hashed for a while so i thought problem was solved. I discovered yesterday it had died again sometime after the update. I have factory reset it again and is hashing happily again for the last 2 hours. Any good advice out there?

Noticed over the weekend that my 2 S3s (both /K software versions) started acting strange also but everything seems to be going well this morning. Just glanced at them now and both keep showing less than 10GH/s in the GH/S(5s) box, even though the pool stats show what I should be submitting.

It was, however, enough to plant the S7 seed in my head again...
member
Activity: 70
Merit: 10
Time is the one thing you can't run from
Has anybody had issues with Kano's s3 update? The day i moved my 2x s3's here i updated them with Kano's update. I bought anther s3 whilst mining here and it came with an earlier version of the update perhaps. I know it looked different to what i had with my other 2. I left it with that update. Saturday i noticed my hash rate was down a lot. I checked the miners and the most recent one wasn't hashing. There were no values in the status area. I rebooted it and stayed the same. unplugged it for a bit and powered on it was still the same. I did a factory reset through the web GUI and it started hashing again. So I put the latest update on the same as my other 2 and it hashed for a while so i thought problem was solved. I discovered yesterday it had died again sometime after the update. I have factory reset it again and is hashing happily again for the last 2 hours. Any good advice out there?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
As mentioned before the payout is generated either 13min or the next confirm after the block (whichever is longer) which in this case it was 30min to the next block.
Same for the block stats correction.

But the block stats at the top and in the workers pages reset immediately.
sr. member
Activity: 331
Merit: 250
Happy to be in the Kano team! Grin

Stats are resetting after we find a block?

Yes, they reset after a block.
Jump to: