Author

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

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Something strange going on at the pool, it is resetting the stats and shares everyone a block is found on the network.  It is also screwing up the miners and they are starting to roll over. Huh
I have absolutely no idea what you mean?
legendary
Activity: 980
Merit: 1001
aka "whocares"
Something strange going on at the pool, it is resetting the stats and shares everytime a block is found on the network.  It is also screwing up the miners and they are starting to roll over. Huh

Edited to correct the dumb ass autocorrection on phone
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Meh, more shit from linode - DE node lost connection again for 2 minutes from 04:31 UTC to 04:33 UTC
(and also between the DE node and another linode I have that monitors everything)

I'm guessing I'm gonna need to find someone not as shitty as linode soon (for the nodes) ...
newbie
Activity: 59
Merit: 0
Block!  Whew!  n200ug hits his 4th block with kano.is!

Here for the long run & looking forward to see CK at 50pt +
legendary
Activity: 1274
Merit: 1000
Great, thanks for the explanations, makes sense.  I guess in my year here this was the soonest I had looked at the webpage after a block solve!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Why is the diff and diff % on this block reported with a tilde (~), is it approximate?  And if so, how come?  I don't see/haven't seen any other blocks like that.
It has always been like that when a block is first found.

The web page header calculations for the current block (Shares/Invalids) are not always 100% accurate.
They are simple counters that gets reset when a new block is confirmed by ckpool (ckpool sends 2 messages per block to ckdb) and since shares can come in from before and after the block during the time frame between the 2 messages, it's simplest to just ignore the problem and know it's not 100% exact Smiley
CKDB generates a block record for each message, then later when the 'workinfo' of the block is aged (meaning it cannot get any more valid or invalid shares for the work that generated the block) then ckdb redoes the block stats calculation and creates a new block record that says it has been redone.
The web page displays ~ until it gets the updated (corrected) stats.
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Why is the diff and diff % on this block reported with a tilde (~), is it approximate?  And if so, how come?  I don't see/haven't seen any other blocks like that.

What cavaliersrus said  Cheesy

Every block we hit starts out with the ~tilde in front of the Diff and Diff% until the software is happy that we have the block for sure and it has time to set up the reward & payment page.  It usually takes between 2-4 confirms to to clear it out.
hero member
Activity: 735
Merit: 500
★YoBit.Net★ 350+ Coins Exchange & Dice
the ~ means its not on the reported page till 3-4 confirmations
legendary
Activity: 1274
Merit: 1000
Why is the diff and diff % on this block reported with a tilde (~), is it approximate?  And if so, how come?  I don't see/haven't seen any other blocks like that.
hero member
Activity: 735
Merit: 500
★YoBit.Net★ 350+ Coins Exchange & Dice
right when i was getting ready to say hey kano kick the server or something to find a block here we go finding another block
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block!  Whew!  n200ug hits his 4th block with kano.is!
legendary
Activity: 4382
Merit: 9330
'The right to privacy matters'

I have 5 avalon6's I would like to try the  command  could you show exactly how to write it?

just add "--suggest-diff XXX" in the "more options" box in the cgminer configuration page in the advanced settings.... XXX would be the stratum difficulty you want the miners to work at, in my case it was "--suggest-diff 27857"


--suggest-diff 10000

will be first try.


So far it appears to work.

great, I'm glad to hear it works, I used this post by CK about "Suggestion for how to choose a pool difficulty for miners" https://bitcointalksearch.org/topic/suggestion-for-how-to-choose-a-pool-difficulty-for-miners-274023 to calculate my number.

I have four running at 13.1 th and diff was auto at 11500

I dropped to 10000.

Fifth Avalon 6 comes on weds

So I will bump to 12000

legendary
Activity: 4382
Merit: 9330
'The right to privacy matters'

I have 5 avalon6's I would like to try the  command  could you show exactly how to write it?

just add "--suggest-diff XXX" in the "more options" box in the cgminer configuration page in the advanced settings.... XXX would be the stratum difficulty you want the miners to work at, in my case it was "--suggest-diff 27857"


--suggest-diff 10000

will be first try.


So far it appears to work.
legendary
Activity: 4382
Merit: 9330
'The right to privacy matters'
why not create a different worker for each miner?

wouldn't that allow you to see which ones might be having an issue/offline. which would also let your use the auto-diff from the pool instead of using the manual diff.

i like having separate workers for each miner as it lets me see/track the changes in shares/hash rate of each as i fine tune/tweak each miners frequency. Slowly tweaking the frequency up/down to find the optimal hash/stability.
ie one of my s7s only likes stock frequency the other likes more power and still wanting more.

it's not possible....Avalon miners use a centralized controller and all the miners are connected to the same controller via proprietary cables, you can set only a single worker in each controller. I have 1 controller with 11 Avalon 6 Miners, so it's one 39 TH worker for all my Avalon 6 machines.

I have 5 avalon6's I would like to try the  command  could you show exactly how to write it?
sr. member
Activity: 266
Merit: 250
why not create a different worker for each miner?

wouldn't that allow you to see which ones might be having an issue/offline. which would also let your use the auto-diff from the pool instead of using the manual diff.

i like having separate workers for each miner as it lets me see/track the changes in shares/hash rate of each as i fine tune/tweak each miners frequency. Slowly tweaking the frequency up/down to find the optimal hash/stability.
ie one of my s7s only likes stock frequency the other likes more power and still wanting more.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Sigh, lost DE there for less than a minute (13:48:38 UTC)
DE itself didn't lose connection with the main pool, just almost anyone connected to DE lost connection and may have failed over.
Linode again Tongue
All's ok again now.
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.
...
Yeah I meant it the other way around.
You, the stats pro Smiley, used 10x and I guessed right about (the same) appropriate value when I commented in that thread.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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
-ck (of course) wrote the code in ckpool that sets your diff Smiley
The target is 18 SPM
full member
Activity: 214
Merit: 100
1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ
I wonder how many other pools were still looking for the 1st block when we found the 2nd of the back to back blocks.
Jump to: