KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2437 blocks

[mikefallen]

can someone point to the place that will show me how to block connections from my node
edit : specific connections

if your using linux just block the traffic from the ip using iptables

[sorry2xs]

no I'm using OS X 

[os2sam]

This can not be taken seriously if transactions are ignored, which is what the system is built to produce.  Really nothing can be done?  All is already lost?

My understanding the discussions are focused on 1mg blocks...  When it should be on 26k blocks.

Transactions are processed on a supply and demand model.  As transaction revenue becomes a larger percentage then more of them will be processed.  If we increase the block size when the demand is low then we are just subsidizing this bad behavior and will get more of it.  The system isn't broken it should be allowed to work.

[dmwardjr]

Transactions are processed on a supply and demand model.  As transaction revenue becomes a larger percentage then more of them will be processed.  If we increase the block size when the demand is low then we are just subsidizing this bad behavior and will get more of it.  The system isn't broken it should be allowed to work.

+1

[wolfen]

Kano seems to be healthier for s7 miners. Other pools (pps) seem to crash the s7 hard when they go down, ddos, etc. Too expensive for that baloney.

Hats off to the devs.

[sorry2xs]

and like clock work a payout

[kano]

and like clock work a payout

If we do keep growing (I'll repeat ... 'IF' ...) and get to an expected 2 or more payouts per day, I might switch to simply doing one payout per day around the same time, combining any due (and maybe delay it e.g. an hour if there's another due an hour later etc)

That will also help a bit with the smaller miners getting pushed below the dust limit due to more payouts

--

Payout 387968 sent (a little while ago)
2236d7a9f47035b3b7cb2317b377c43274f6025dd0dbfafbb7c1b271a8a77bf3
but not confirmed yet

I did double the (low ) fee this time - lets see if anyone else confirms it this time (other than us and solo.ckpool)

[o_solo_miner]

and like clock work a payout

If we do keep growing (I'll repeat ... 'IF' ...) and get to an expected 2 or more payouts per day, I might switch to simply doing one payout per day around the same time, combining any due (and maybe delay it e.g. an hour if there's another due an hour later etc)
That will also help a bit with the smaller miners getting pushed below the dust limit due to more payouts

I would vote for it.
I am a verry smal miner.... and I switched it back on for the SPV discusion going on!

[kano]

Payout confirmed

[edonkey]

dmwardjr, did you get an answer to your "invalids" question? Because I'm seeing something similar since moving to Kano.

Basically, my best performing S7 unit that has the highest hash and fewest HW errors has higher rejects since moving to Kano. The other two S7s (with worst hash and higher HW errors) are nominal.

Maybe I'm OCD about this, but since receiving my S7s I've kept a spreadsheet with performance snapshot numbers including hash rate, HW errors, DiffA, and DiffR over time. This allows me to reduce performance numbers to the form DiffA and DiffR per second for a given configuration and pool. I have a complete record of performance for every pool I've been on.

In general the stats for Kano's pool over a few days is similar to other low latency pools that I've tried. But this one "high performing" S7 has a 26% higher DiffR per second value than the previous pool I was on (Slush), where the other "lower performing" S7s have had around a 16-20% reduction in DiffR per second.

Correspondingly, this "high performance" unit has been granted a lower difficulty (3.98K) than the other two (5K+). On all the other pools the best performing unit had higher or equal difficulty than the other two.

Note that all three units are deployed at a data center with very reliable and consistent cooling, power, and high network performance. They are behind a firewall so all of them will appear to be from the same IP address, in case that's relevant.

While this is not having a huge impact on earnings, it's a bit odd that the unit that was my best performer on all other pools is now my worst one, seemingly due to an increase in rejects.

Any thoughts as to what might cause this?

Other than this minor anomalous behavior, I'm very happy with the move to Kano. I was at wits end because the big pools are behaving badly (SPV mining, empty blocks, etc.) and run by people who seem to be lacking in both character and technical competence. And Slush's pool, which I've really liked in the past, seems to be underperforming well outside of statistical reason. Also, it's hard to buy their explanation for the slew of orphans they had, especially since they continue to have a disproportionate orphan problem.

Anyway, thanks Kano for providing a great pool! Now if we can just get enough like minded miners over here so that the pool can go from an alternative to a major player...

[kano]

dmwardjr, did you get an answer to your "invalids" question? Because I'm seeing something similar since moving to Kano.

Um? Where?

Basically, my best performing S7 unit that has the highest hash and fewest HW errors has higher rejects since moving to Kano. The other two S7s (with worst hash and higher HW errors) are nominal.
...

Anomalous?

There was a stale reduction change on the last ckpool restart which, checking the web site was 3 days ago.
So if it was before that, then yes there may have been a slightly higher stale issue.
It was caused by my slightly different ckpool setup that resulted in sometimes sending a "don't clean" work block change followed by a "clean" work change.

[dmwardjr]

dmwardjr, did you get an answer to your "invalids" question? Because I'm seeing something similar since moving to Kano.

Um? Where?

Basically, my best performing S7 unit that has the highest hash and fewest HW errors has higher rejects since moving to Kano. The other two S7s (with worst hash and higher HW errors) are nominal.
...

Anomalous?

There was a stale reduction change on the last ckpool restart which, checking the web site was 3 days ago.
So if it was before that, then yes there may have been a slightly higher stale issue.
It was caused by my slightly different ckpool setup that resulted in sometimes sending a "don't clean" work block change followed by a "clean" work change.

I had a post up earlier with two screenshots that was up only about 35 to 45 minutes.  I said I would take it down after an answer.  He answered shortly after I took it down.

[edonkey]

dmwardjr, did you get an answer to your "invalids" question? Because I'm seeing something similar since moving to Kano.

Um? Where?

Basically, my best performing S7 unit that has the highest hash and fewest HW errors has higher rejects since moving to Kano. The other two S7s (with worst hash and higher HW errors) are nominal.
...

Anomalous?

There was a stale reduction change on the last ckpool restart which, checking the web site was 3 days ago.
So if it was before that, then yes there may have been a slightly higher stale issue.
It was caused by my slightly different ckpool setup that resulted in sometimes sending a "don't clean" work block change followed by a "clean" work change.

Thanks for the info Kano. Sounds like a good explanation. The timing makes sense.

I'll snapshot my stats and do a soft reset to clear the decks.

[e46btc]

Payout 387968 sent (a little while ago)
2236d7a9f47035b3b7cb2317b377c43274f6025dd0dbfafbb7c1b271a8a77bf3
but not confirmed yet

Kano, just for information - is this ok that Status field in Account->Payout tab is empty and not updated after each payment?  This is not a problem really as payments are regular, but it might be good idea to fix it? Some users I guess not able to track payouts on forum because of limited time but it will be quite convenient to login into your account and to check what is paid and what still not..

[clgrissom3]

Wow! Payout 388017 received about 30 minutes ago and it has 3 confirmations already.  Thanks Kano!

[kano]

Payout 388017 sent
9d24b3570e35ba200a155ccc87943ab6eeea3d67e811448efae126a4e1aa1947
and confirmed

--

Payout 387968 sent (a little while ago)
2236d7a9f47035b3b7cb2317b377c43274f6025dd0dbfafbb7c1b271a8a77bf3
but not confirmed yet

Kano, just for information - is this ok that Status field in Account->Payout tab is empty and not updated after each payment?  This is not a problem really as payments are regular, but it might be good idea to fix it? Some users I guess not able to track payouts on forum because of limited time but it will be quite convenient to login into your account and to check what is paid and what still not..

Yep, not written the code to do it yet
(I've mentioned that a few times here, but that would require reading back quite a bit)

Also, your wallet will show the transactions for all that I've sent.
That will be all that have Matured but the current one.
The current Matured one will be when I send it (and say it here) and it will show up in your wallet then.

... and you can find it by clicking on the block link, then clicking on the block hash shown there, then the 1st block payout address, click on that.

[clgrissom3]

Sounds like you could simply remove Status as a column header and solve the question.  It's not a feature that's needed anyway 

[e46btc]

Kano, for sure I know how to check if I got paid Thank you  
But I just talking about kind of convenience.  No probs if still not implemented.
I've started mining of kano.is pool just a few days ago and I do not know if it worked before present moment.
To be honest I haven't read all 300 pages sorry for this

[clgrissom3]

Haha!  I'm pretty sure I have not read through all 300 pages either.  But I will say this thread can be an interesting and fun read at times...

[hurricandave]