Author

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

full member
Activity: 226
Merit: 103
hello guys

one question, i'd like to set the stratum difficulty manually on my miners to 20 shares per minute as suggested in https://bitcointalksearch.org/topic/suggestion-for-how-to-choose-a-pool-difficulty-for-miners-274023


Hello,
I do not think there is interest for you  to increase the pace, unless you have a very high hashrate.
If everyone does that, it will increase the traffic kano servers and it can have more disadvantages than advantages.

I think the best thing is to let kano team fix the steady rhythm. He must surely calculate the best compromise between the possibility of its servers, your hash rate and latency.

It is interesting to reduce the rate if your internet connection is slow or if you have to pay the amount of data.
newbie
Activity: 45
Merit: 0
hello guys

one question, i'd like to set the stratum difficulty manually on my miners to 20 shares per minute as suggested in https://bitcointalksearch.org/topic/suggestion-for-how-to-choose-a-pool-difficulty-for-miners-274023

i did this on my Avalon6 controller without problems using the "--suggest-diff" command on the cgminer "more options" field available in the Avalon6 controller interface.

however i got a few Antminer s7, s4 and s5 that do not offer any field to enter any extra cgminer commands, anybody know how do i set the stratum difficulty manually on Antminers?

thanks in advance for any information

You can set it directly on the pool for each worker, under "Worker-> Management"
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Part of the internet lost contact with the pool again (myself included) - was an asia-pacific issue again since DE was ok.
Outage was around 2 minutes this time at 11:33 UTC
We dropped from 23PH down to 20PH so I guess that means about 3PH were connected through whatever part of the internet lost connection with the pool data centre.
All is OK again.
zOU
hero member
Activity: 728
Merit: 500
★ these are stars ★
Sweet !

I can't wait to get my S5 and add it to my current miners on the pool ! (2xS3+, 6 compac Gekkoscience sticks, 5xU3)
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Last 3 payouts sent as each reached +101 finally all just confirmed now.

Payout 398566
c42d88d83148bd223f10ea1b37951cf6414fad734e00a3642ef01e8d0364bacd

Payout 398569
dde23dc18baa5f7c43e91d71bcd6d12dbc52accf796cf695a81e1c85d75e612f

Payout 398586
fd2dfe2d1c8cd9b2e1e0675232407e1e9aa21637b8bd27c57a0ff519896dec90
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Hi i've mined 4 or 5 days without btc adress set  how can i withdraw my BTC

-Login
-Account tab -> Settings

"To change your payout address, enter a new address and your password
BTC Address:"

-Input BTC address.

I've input the adress how can i withdraw them all rewards?

I have a lot of rewards that were not sent and i want to withdraw them because are my BTC

I think Kano does this manually whenever it happens, as long as it is over the dust threshold  Grin...send him a PM and he will take care of you...

Ok it is over
Check your PM txn sent
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...
Not picking on you - it's something I've read lots of times.

But ... ok ... I do need to add something else also for the 32-bit miner failure ... ok that hits the top of the todo list ... ... once I finish this I'm working on.

I envisioned this as an automated screening test that would be applied to all user accounts, and wouldn't have to be tied to just the known modes of failure. Let me know if anything in the post is unclear and I'll lend a hand.

To my knowledge no one has automated a similar test yet but it's pretty simple. Keeping track of the difficulty, user account and pool difficulty of every submitted share might be a PITA though.

Yeah no trouble understanding what you did - as I mentioned in your thread, it's obvious ... but yeah the thought never even crossed my mind Cheesy
That's why I posted in here twice about it.
First time was ... yeah I keep basic block/diff stats per user.
Second time was ... OH! That's what he means ... OK that's a good idea!

My solution is very simple, log all shares individually above a certain difficulty.
I already store a LARGE amount of data in the permanent database and in ram ... a few (10s 100s whatever) thousand more records is no big deal and ckpool already has the numbers in each share record it sends to ckdb.

I do already have simple full block/submit statistics for miners that even shows on the Acclaim web page ... if you're me, but for none else Smiley
https://bitbucket.org/ckolivas/ckpool/src/abe0aef095c63b1ce263e3b90d7dc2ff7ce9bc9f/pool/page_userinfo.php?at=master&fileviewer=file-view-default#page_userinfo.php-18
donator
Activity: 2058
Merit: 1007
Poor impulse control.
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...
Not picking on you - it's something I've read lots of times.

But ... ok ... I do need to add something else also for the 32-bit miner failure ... ok that hits the top of the todo list ... ... once I finish this I'm working on.

I envisioned this as an automated screening test that would be applied to all user accounts, and wouldn't have to be tied to just the known modes of failure. Let me know if anything in the post is unclear and I'll lend a hand.

To my knowledge no one has automated a similar test yet but it's pretty simple. Keeping track of the difficulty, user account and pool difficulty of every submitted share might be a PITA though.
donator
Activity: 2058
Merit: 1007
Poor impulse control.
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...

That is some interesting stuff.  Why would someone do that here?  Would it be to benefit from faster block change notifications? Harm the reputation of the pool?

I'm pretty sure I saw the word "unintentional" in there somewhere.
That's to do with possible detection of a specific "unintentional" problem.
However, if someone has $100k (or more) worth of "unintentional" miners, do you expect people would just throw them away if there was no real fix for them ... ... ...

In the post, "Intentional block withholding" just means the max sized share changes to match difficulty, which can only be done on purpose. Any other problems that causes valid blocks to not be returned to the pool -- even a network problem -- is "unintentional".

I meant "intentional" as an intentional attack against a pool (which could be extremely hard to detect) rather than someone with known faulty equipment that they can't repair wanting to mine and not caring who they affected.

So yes, Kano is right -- people can be intentionally acting like dicks and still be "unintentionally" block withholding. As soon as someone comes up with better terminology to describe the differences, I'll be the first to use it.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...

That is some interesting stuff.  Why would someone do that here?  Would it be to benefit from faster block change notifications? Harm the reputation of the pool?

I'm pretty sure I saw the word "unintentional" in there somewhere.
That's to do with possible detection of a specific "unintentional" problem.
However, if someone has $100k (or more) worth of "unintentional" miners, do you expect people would just throw them away if there was no real fix for them ... ... ...
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...

That is some interesting stuff.  Why would someone do that here?  Would it be to benefit from faster block change notifications? Harm the reputation of the pool?
There are a number of reasons to withhold blocks.
1) If you rent out your gear, you will always be paid even if you withhold.The rental company will also be paid no matter what.
(fuck-you-hash doesn't give a shit about checking for this even though they get 6% of the rental cost - they know they get paid no matter what - they don't care)

2) If you rent out your gear, withholding will reduce the next diff change, so make your gear worth a little bit more each time you manage to withhold a block - again same story for the rental company ... and fuck-you-hash

3) Trying to kill off a competitor. Depending upon the pool payout method, the loss may be small.
PPS - withholding loss (per block) for the miner is zero (pool operator loses all the loss - pool miners lose nothing)
Eligius - withholding loss (per block) for the miner is very small (pool operator loses nothing - pool miners lose all the loss)
PPLNS - withholding loss (per block) for the miner is dependent upon the miner size vs the pool size (pool operator loses pool fees - pool miners lose the difference between the withholder loss and the block reward)
legendary
Activity: 3586
Merit: 1099
Think for yourself
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...

That is some interesting stuff.  Why would someone do that here?  Would it be to benefit from faster block change notifications? Harm the reputation of the pool?

I'm pretty sure I saw the word "unintentional" in there somewhere.
hero member
Activity: 615
Merit: 500
Kano, thoughts on this on block withholding?  http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...

That is some interesting stuff.  Why would someone do that here?  Would it be to benefit from faster block change notifications? Harm the reputation of the pool?
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...
But ... ok ... I do need to add something else also for the 32-bit miner failure ... ok that hits the top of the todo list ... ... once I finish this I'm working on.
legendary
Activity: 952
Merit: 1003
But hey, it brings large miner to the pool so increases the chance to find a block even though is reduces payout for the smaller miners (like me).

Reduces the individual payout but increases the frequency of payouts.  Don't forget that little detail Smiley
Yes - but more importantly to make it clear - it has NO negative effect on total reward for smaller miners.

Of course if you are in the dust mining league, yep you end up with more of your reward being dust and thus a much longer wait until you ever get it.

 Cool
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
But hey, it brings large miner to the pool so increases the chance to find a block even though is reduces payout for the smaller miners (like me).

Reduces the individual payout but increases the frequency of payouts.  Don't forget that little detail Smiley
Yes - but more importantly to make it clear - it has NO negative effect on total reward for smaller miners.

Of course if you are in the dust mining league, yep you end up with more of your reward being dust and thus a much longer wait until you ever get it.
legendary
Activity: 3586
Merit: 1099
Think for yourself
But hey, it brings large miner to the pool so increases the chance to find a block even though is reduces payout for the smaller miners (like me).

Reduces the individual payout but increases the frequency of payouts.  Don't forget that little detail Smiley
zOU
hero member
Activity: 728
Merit: 500
★ these are stars ★
300Ghs

300Ghs is pretty easy to have (not profitable though)
250Ths is not that easy but more profitable (if recent HW and/or cheap power)

I wish the giveaway would be for 300Ghs to 2.5Ths to favor the smaller miners.

After all, who would want an Avallon6 when you already have 250Ths ?
But hey, it brings large miner to the pool so increases the chance to find a block even though is reduces payout for the smaller miners (like me).


Anyway.... back to my movie :p
sr. member
Activity: 441
Merit: 250
What about the giveaway of the 5 Avalon 6 miners ? Is it already finished ? Do you need to be a miner to be eligible to win it ?

There have been 2 Avalon6's given away so far...3 more to go in March, April, and May.  Yes, you have to mine here to be eligible...here is a quote from page 1 of this thread:

Quote
Your 'Workers'->'Shift Graph' must show an average of 300GHs or more - and less than 250THs - on the red average line - for the sum of all your miners.

Okay, so I'll never be eligible for this promotion. Unless you buy the really latest miners your profits are way too low, and if you profit Sad...
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Heh he picked the same number I said on the slush thread - 10 blocks.
Yes the pool already has information about that ...
Jump to: