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

[overcon]

It's possible with Awesomeminer to put backup ?
Because i manage pool with it not directly by web interface.

EDIt:
Just add the pool on the pool page for each miner

You confirm is useful when the first is offline.
how can i check if i lost something because first was offline ? there is a stat which mean that ?


EDIT2:
I have some doubt if the profit is very good if a minimum luck is not here....
For example, with my hashrate 27.3TH/s, i earn an average of 0.0046 by block found. (it's the stable earning after 3 days of running)
If i estimate with expected block for september, i found :
31 * 0.0046 = 0.1426

On nicehash, for the same Hashrate, i have 0.2597 for the month, minus  4% = 0.2493.
To have the same earning on Kano, it need 54 blocks found for the month.
Everything is calculated in BTC, and the BTC/USD exchange will not affect that.

My simulation is wrong ?

How do you know we will not get 5 blocks today, 5 tomorrow, 4 the next day, none the next day, 2 the next day, 6 the next day?

You can guess all you want, but historically, the pool usually meets its historical numbers. But you can take a sure thing over a better thing if you like. No one forces you to mine at a pool, remember that. I think maybe, if you had mined here for 8 months and you found it was lower than what you would get at another pool, then maybe you'd have a reason to leave? But without putting in the time, you can crunch numbers all you want to justify your actions, still doesn't make them correct

[ordimans]

I did same calcul with old months, and it's same, where it's finish.
So maybe i forgot one thing in my simulation...

[overcon]

I did same calcul with old months, and it's same, where it's finish.
So maybe i forgot one thing in my simulation...

Maybe, who knows. I'm by far an expert. But I do well here and that works for me.

[philipma1957]

Hello guys, I know this is not the best place to post this problem, but as I know you are the best and smartest guys over here please help me with this if you are able:

I've been mining in kano since six months I think and from yesterday I realized my TH/S dropped a lot and I went to check my miners and I found this:

I have an Antminer S9 and it got in the chain #8 GH/S(RT) = 0.00000

I've seen in the forum some problems about that and says it is a board problem.

My antminer is out of warranty, and I am not able to send back to bitmain to get a repair ticket because it is almost impossible to send it from my country. So please help me guys Sad I'm really worry about that Sad

Here is a picture of what I'm telling you:

You need to post a screenshot of the full page for seeing all chips. but it looks like you have a problem with 1 hashing board; should send to bitmain for repair or purchase a hashing board and replace it at your own risk.

I also highly recommend to have a 2nd and 3rd mining address for backup (not just the 1st one).

It's possible with Awesomeminer to put backup ?
Because i manage pool with it not directly by web interface.

EDIt:
Just add the pool on the pool page for each miner

You confirm is useful when the first is offline.
how can i check if i lost something because first was offline ? there is a stat which mean that ?


EDIT2:
I have some doubt if the profit is very good if a minimum luck is not here....
For example, with my hashrate 27.3TH/s, i earn an average of 0.0046 by block found. (it's the stable earning after 3 days of running)
If i estimate with expected block for september, i found :
31 * 0.0046 = 0.1426

On nicehash, for the same Hashrate, i have 0.2597 for the month, minus  4% = 0.2493.
To have the same earning on Kano, it need 54 blocks found for the month.
Everything is calculated in BTC, and the BTC/USD exchange will not affect that.

My simulation is wrong ?

so wrong

it will take me  a few hours to explain why it is wrong



Block Statistics

Description   Time   Mean Diff%   MeanTx%   CDF[Erl]   Luck%   ?PPPS%

Last 5 Blocks   4.4days   163.90%   108.40%   0.9110   61.01%   65.54%
Last 10 Blocks   6.5days   119.82%   107.57%   0.7560   83.46%   88.97%     based on this luck  you would be correct.


Last 25 Blocks   12.6days   89.55%   110.10%   0.3176   111.66%   121.84%
Last 50 Blocks   27.2days   96.91%   116.61%   0.4312   103.19%   119.24%  based on this luck you would be wrong
Last 100 Blocks   8.1wks   103.53%   113.04%   0.6489   96.59%   108.20%
Last 250 Blocks   17.7wks   100.20%   116.95%   0.5209   99.80%   115.67%
Last 500 Blocks   42.2wks   99.77%   113.41%   0.4856   100.23%   112.65%
Last 1000 Blocks   63.0wks   100.90%   108.50%   0.6162   99.10%   106.56%
All - Last 2120 Blocks   156.4wks   97.09%   104.56%   0.0893   102.99%   106.73%


Monthly Statistics

UTC Month   Pool Avg   Blocks   Expected   Mean Diff%   MeanTx%   CDF[Erl]   Luck%   PPPS%


2017 September…   80.56PHs   33   30.52   92.50%   112.28%   0.3506   108.11%   120.29%    you are wrong for this month


2017 August   81.45PHs   48   58.46   121.79%   115.84%   0.9278   82.11%   94.26%
2017 July   76.79PHs   62   60.52   97.61%   110.04%   0.4416   102.44%   111.71%     ----------- you are wrong for this month
2017 June   74.80PHs   72   65.61   91.13%   122.31%   0.2308   109.73%   133.00% -------------- you are wrong for this month
2017 May   60.72PHs   71   68.06   95.86%   120.05%   0.3767   104.32%   124.10% -------------- you are wrong for this month
2017 April   34.94PHs   61   41.36   67.81%   111.07%   0.0025   147.47%   162.33%
2017 March   27.11PHs   33   37.83   114.64%   113.14%   0.8052   87.23%   97.81%
2017 February   21.21PHs   34   26.71   78.57%   109.46%   0.0978   127.28%   138.07%---- wrong
2017 January   22.65PHs   40   41.37   103.43%   105.58%   0.6053   96.68%   101.16% --- wrong
2016 December   28.63PHs   41   58.65   143.04%   105.24%   0.9936   69.91%   72.91%
2016 November   33.55PHs   70   76.09   108.69%   104.59%   0.7725   92.00%   95.36%
2016 October   32.43PHs   82   79.69   97.19%   104.01%   0.4128   102.90%   106.06% ---- wrong

[wmabern]

That new difficulty SUCKS peas! 

[Mikestang]

I wish I could find my post from last year when I wondered aloud when diff would cross the 1 trillion mark, certainly happened sooner than expected.

[NomadGroup]

That new difficulty SUCKS peas! 

It does!  Let's hope that the price will jump up to 5k pretty quick to make up for that 20% jump! 

[NotFuzzyWarm]

That new difficulty SUCKS peas!  

It does!  Let's hope that the price will jump up to 5k pretty quick to make up for that 20% jump!  

And/or the BTC network sees it as an over-correction and compensates.... What's the average Block time look like since the diff rise?
Wonder what the control loop's PID values and constants are?

[philipma1957]

That new difficulty SUCKS peas!  

It does!  Let's hope that the price will jump up to 5k pretty quick to make up for that 20% jump!  

And/or the BTC network sees it as an over-correction and compensates.... What's the average Block time look like since the diff rise?
Wonder what the control loop's PID values and constants are?

There is huge drop in hash with a big shift to BCC

viabtc has

 BTC at  6995 ph
 BCC at  2171 ph



please note gray line as it is actual btc hash rate now

[gecox22]

Hello guys, I know this is not the best place to post this problem, but as I know you are the best and smartest guys over here please help me with this if you are able:

I've been mining in kano since six months I think and from yesterday I realized my TH/S dropped a lot and I went to check my miners and I found this:

I have an Antminer S9 and it got in the chain #8 GH/S(RT) = 0.00000

I've seen in the forum some problems about that and says it is a board problem.

My antminer is out of warranty, and I am not able to send back to bitmain to get a repair ticket because it is almost impossible to send it from my country. So please guys, help me. I'm really sad about that

Here is a picture of what I'm telling you:

I guess I  don't see the problem besides the pools are dead on 2 and 3 which you should add another of one of kano's nodes.

As for the Proxy just uses the imagine link instead of the image like the URL we will have to click on the image but at least we can see it. And yea you can buy a board and replace it your self. It is really easy. If that is the issue.

[TheYankeesWin!]

That new difficulty SUCKS peas!  

It does!  Let's hope that the price will jump up to 5k pretty quick to make up for that 20% jump!  

And/or the BTC network sees it as an over-correction and compensates.... What's the average Block time look like since the diff rise?
Wonder what the control loop's PID values and constants are?

There is huge drop in hash with a big shift to BCC

viabtc has

 BTC at  6995 ph
 BCC at  2171 ph



please note gray line as it is actual btc hash rate now

wow 7000 ph is a big drop lets hope for it to stay at 7ph

[philipma1957]

our 1,103 diff is a 7,898 ph  hash rate

we would drop  to   about 1000 diff if we stay at 7000ph. hash rate




All of this is due to the BTC   vs BCC/BCH   issue  and of course the Chinese Gov flexing their muscle.

[clgrissom3]

Block by cobramining!

This is our 1st of BLOCK TUESDAY!

A nice 14+ block and a payout!

[philipma1957]

And  our diff is dropping  as I type.

the gray line  is way down.  due to pressure from  BCC/BCH

Get used to big swings until BCC/BCH  fades away.

[dzimmerm56]

The difficulty changed yesterday, the profit have decreased a lot since two week agos with some S9

People!  Keep your sanity and watch your long term profits...If you constantly watch daily and weekly profits, you will go nuts!  There is just too much variance in this venture for short term happiness.

Right on! Mine on!.

The flip side are things you should watch or do daily.
1) Your miners health, keep a miner stats page up and refresh it to confirm you are maintaining health of all miners.
2) The availability of miners and power supplies to buy.
3) Backup your bitcoin Core wallet daily.

[dzimmerm56]

Looks like someone overdid it on the difficulty increase. I see a 35 minute and counting block time.
I am guessing automatic calculators are picking what coin to mine based on difficulty and bitcoin just set itself to lose a bit of hash rate.
This could cause a sea saw effect when the diff drops , then rises, and drops and rises ......
Hang onto your seats for the roller coaster ride!

[dzimmerm56]

I see canaan is getting organized with an authorized reseller. I am guessing they are buying the pallets and then selling singles.
Go to canaan's home page for the straight news and links.
Not going to put links in here as too many folks put up links that are scams, better you go to canaan's website your self and follow the info there.

[jungleb0y]

I was watching the block get put together I guess on https://tradeblock.com/bitcoin/ the lat one was like 56 minutes and then it released it or whatever it does and then you see each mining pool start to get the blocks average 5-6 blocks found for that hour of collecting transactions.

Is that how it always worked or was it one block every 10 minutes? I guess either way it works out to a block every 10 minutes if they collect data for an hour and release 6 blocks huh.

If that's how it works collecting and the releasing a group of blocks you could just shut everything off on the pool and then 10 minutes before the blocks come out open them up again and shut down after the blocks have been found?

Kano just needs to make a script that can interface with the miners to remotely shut them off and start them  

I'm just talking like a man with a paper ass, I know think you can find a block in between that time but it looks like the majority of blocks lately have come in groups.

Just sayin

[kano]

Block! by moecarrimNEW
(13.9BTC)

[kano]

Block finding is purely random - you don't build up to finding a block.

It's random in exactly the same way as rolling an un-weighted dice is random
(though the block hash is pseudo-random coz it's a mathematical calculation with enough complexity to consider it random)

You double sha256-hash an 80 bytes value, check it's pseudo-random result and see if it's less than a value calculation of the network difficulty.
If it is, then it's a block.
So yep there is absolutely no history effect on finding blocks, and you can NEVER say when the next block will be found by any pool or even the whole network.

The block length distribution is a poisson distribution.
https://en.wikipedia.org/wiki/Poisson_distribution
Meaning you expect them to average at 100% difficulty, but the length between blocks can be 1 hash or infinite hashes (never)

The CDF table also explains that - it's not just for the pool, it's for all of Bitcoin.

Code:

 0.39346934028737   50.000%  1 in 1.6
 0.63212055882856  100.000%  1 in 2.7
 0.86466471676339  200.000%  1 in 7.4
 0.95021293163214  300.000%  1 in 20.1
 0.98168436111127  400.000%  1 in 54.6
 0.99326205300091  500.000%  1 in 148.4
 0.99752124782333  600.000%  1 in 403.4
 0.99908811803445  700.000%  1 in 1096.6
 0.99966453737210  800.000%  1 in 2981.0
 0.99987659019591  900.000%  1 in 8103.1

So using that table also for all Bitcoin network blocks, and assuming blocks are expected to average 10 minutes in length,
you can see that since 10 minutes would mean 144 blocks a day, then it would average, over time, a 50 minute block about every day -
this comes from "500.000% 1 in 148.4" i.e. "500%" of 10 minutes = 50 minutes, and "1 in 148.4" is a little over a day's expected number of blocks: 144.
(144 = 6 per hour times 24)

The most important part to understand is that it's an expected average, nothing more.
So when we say the network blocks should average once every 10 minutes, it doesn't mean they will be every 10 minutes.
Some will be a few seconds, some 50 minutes, some half an hour, some 1 minute etc etc etc
But the long term average of all those is expected to be 10 minutes.

Lastly, most if not all Difficulty graphs are interpreted incorrectly by most people who view them.
You cannot give an accurate estimate of the network hash rate from the graph.
Yep, you can't.
Why? Coz the time used to estimate/update the network difficulty is 2016 blocks, and even that is not very accurate.
The network hash rate changes every minute, every hour, every day, but a day's worth of block data is far from accurate enough to estimate the network hash rate.
As I implied, even ~14 days worth of data (2016 blocks) isn't very accurate, but it's necessary to be used to reduce the effect of a large hash rate drop.