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

[voodooman]

The mining code is ckpool.
For this update I've just done a few changes as mentioned above (and rolled forward to the current ckpool git ... that failed)

Seems the node code can't handle a pool version update It may need a complete restart of everything.
I'll do some node<->pool testing and work out what's up with that - I was more concerned about block code, and I tested that thoroughly - didn't expect a network protocol problem.
Weird, coz some of the nodes are current code also. As I said ... more work to do

Everything else is my KanoDB
That's the name for the updated closed source version - so no one has any wrong ideas about who wrote almost all of it
The CKDB in the public ckpool git (that I got thrown out of) works fine for a single pool and can handle a few hundred PH - but has no support at all.

A few pools use it: Ver's bitcoin.com did (no idea if they still do) BitClub does, so does LinuxJounal
There's 1 other I know of but I wont mention their names since:
 they removed my copyright off the web site and replaced it with their own copyright ... scumbags

Mine on

Nice. Thanks for the input :-)

I can't understand why some people are not having esteem for a programmer who build some serious cool code
and share it with the rest of the world for free.

So good luck the node<->pool testings.

[bit2255]

Hey Kano-san, Do you think it is time to update the title in the forum to [80+ PH]?

The average Pool rate has been above 80 for a little while.

Mine on!!

[kano]

Hi kano,
Im still new in this mining world.

Is it still okay if I havent received the payments for two days ago?
Anw, the payment for today's block has been received, I still wonder why did the payment for yesterday's and two days ago's block still not arrived since it has matured.

Thank you

PM me your username and I'll check.

The rewards page will show all the rewards you've got.
The payouts page will show all the payouts sent (or due to be sent), but also show all the dust not sent (with a red *) and comments at the top and bottom about that.
No dust is sent yet (as it says) - but it will be a while yet before that happens.

Of course, if you are mining to an address, and not to an account, then you wont be able to see any of that.
You'd have to PM your address your mining to, so I can check.

[kano]

Hey Kano-san, Do you think it is time to update the title in the forum to [80+ PH]?

The average Pool rate has been above 80 for a little while.

Mine on!!

I know why the pool hash rate goes up and down
OK I've set it to 80PH now.

Once it's colder and many mining datacentres around the world are no longer in summer, I'll consider put the thread title up more.
Also, of course, if someone points another 5PH or more at the pool I'd put it up more

[kano]

...

hi kano, nah, it's okay.
i've crosschecked it, and turned out that the transaction is still not confirmed.
guess i have to wait longer before it confirmed because of the low transaction fee.

anyway,thank you kano, all time best pool.

If you mean the last block we found - 479731 - yep I haven't sent that payout yet.
It's gotta wait for the 101 confirms before I can spend it, so that's when I send out the payout - when it matures
(and it says on the blocks page when it's matured - after the + counter gets to 101)

If you mean any before that - let me know, coz they've all already confirmed, the last one was 479656 that confirmed 38 blocks ago.

[clgrissom3]

New Diff...

[2017-08-09 07:06:54] Network diff set to 860G
[2017-08-09 07:10:33] Stratum from pool 0 detected new block
[2017-08-09 07:15:39] Stratum from pool 0 detected new block
[2017-08-09 07:20:04] Stratum from pool 0 detected new block
[2017-08-09 07:20:20] Stratum from pool 0 detected new block
[2017-08-09 07:34:21] Stratum from pool 0 detected new block
[2017-08-09 07:43:46] Stratum from pool 0 detected new block
[2017-08-09 07:46:29] Stratum from pool 0 detected new block
[2017-08-09 07:54:46] Stratum from pool 0 detected new block
[2017-08-09 08:06:04] Stratum from pool 0 detected new block
[2017-08-09 08:08:35] Network diff set to 923G

[kano]

7.3% - well not as bad as it could have been, without the fork it would have been noticeably higher.

[tbonetony]

New Diff...

[2017-08-09 07:06:54] Network diff set to 860G
[2017-08-09 07:10:33] Stratum from pool 0 detected new block
[2017-08-09 07:15:39] Stratum from pool 0 detected new block
[2017-08-09 07:20:04] Stratum from pool 0 detected new block
[2017-08-09 07:20:20] Stratum from pool 0 detected new block
[2017-08-09 07:34:21] Stratum from pool 0 detected new block
[2017-08-09 07:43:46] Stratum from pool 0 detected new block
[2017-08-09 07:46:29] Stratum from pool 0 detected new block
[2017-08-09 07:54:46] Stratum from pool 0 detected new block
[2017-08-09 08:06:04] Stratum from pool 0 detected new block
[2017-08-09 08:08:35] Network diff set to 923G

every 1% increase these days constitutes many jaw dropping G's

[smutboy420]

block by bobsyouruncle

[tbonetony]

block by bobsyouruncle

No my uncle is rob

[clgrissom3]

block by bobsyouruncle

This is our 2nd of BLOCK WEDNESDAY!

[kano]

Oh well, maybe we do gotta hate diff increases after all

Someone got a share that was 99.2% of a block (about half an hour ago) but that would have been a block yesterday before the diff change

[2017-08-09 22:16:48.830+00] Share (479859) ok Diff 99.2% (915655346740/923233068448.9) aurora-ii Pool 193716723162.0 194G 20.98%

[tbonetony]

Oh well, maybe we do gotta hate diff increases after all

Someone got a share that was 99.2% of a block (about half an hour ago) but that would have been a block yesterday before the diff change

[2017-08-09 22:16:48.830+00] Share (479859) ok Diff 99.2% (915655346740/923233068448.9) aurora-ii Pool 193716723162.0 194G 20.98%

This is why log sometimes hurts people's feelings

[DarKSm0ke]

Block by cobramining!

Nice increase of Hashrate, let's reach 100 PH and celebrate!

[kano]

Block! by gmb with ~30Ths

That one was also pretty awse coz it's not completely full (63 second network block) but I watched the payout for 479844 go out about 1 minute 41 seconds before the block was found and bang, a block with the payout in it, and it didn't even waste any block space at all (not even free space)

[MEARK]

Block! by gmb with ~30Ths

That one was also pretty awse coz it's not completely full (63 second network block) but I watched the payout for 479844 go out about 1 minute 41 seconds before the block was found and bang, a block with the payout in it, and it didn't even waste any block space at all (not even free space)

Possibly dumb question about block finding... I've been mining in Kano for about a month now, watching this message board like a hawk and learning a lot along the way.

I am looking forward to getting on the Acclaim Board some day.  How does one "find" a block... is it the miner who solves the last calculation or fills the last space in a given block?  I can clearly see the big miners with PH power find more blocks.  With just ~17 TH to my name, will I ever "find" one... is this a factor of luck?  Am I even using the right terminology?

OK that was actually 3 questions.    

Thanks in advance!

[VRobb]

Hi MEARK, many of us here are still waiting/hoping to make the acclaim board, including me!  Indeed you need to solve a block to get there.  Good luck to you, since if you get on the board we all get PAID!!  
Cheers

[kano]

Block! by gmb with ~30Ths

That one was also pretty awse coz it's not completely full (63 second network block) but I watched the payout for 479844 go out about 1 minute 41 seconds before the block was found and bang, a block with the payout in it, and it didn't even waste any block space at all (not even free space)

Possibly dumb question about block finding... I've been mining in Kano for about a month now, watching this message board like a hawk and learning a lot along the way.

I am looking forward to getting on the Acclaim Board some day.  How does one "find" a block... is it the miner who solves the last calculation or fills the last space in a given block?  I can clearly see the big miners with PH power find more blocks.  With just ~17 TH to my name, will I ever "find" one... is this a factor of luck?  Am I even using the right terminology?

OK that was actually 3 questions.    

Thanks in advance!

There's no build up to finding a block.

A block is simply found by one single hash if it gives the low enough value to be a block.
That block was:
 000000000000000000b6a5fb2524fb754860e9a3321695b51ccc566ee163d36a

Which is the double sha256 hash of the 80 byte block header which is:
 Version + Previous Block Hash + Merkle Root + Block 'Time' + Network Difficulty + Nonce

So:

Code:

Network difficulty is currently:
 0x180130e0
Which equates to:
 0130e0 x 2 ^ ((0x18 - 3) * 8)
=
 0130e0 x 2 ^ (21 * 8)
now 2 ^ (21 * 8) = (21 * 8) / 4 zeros = 42 zeros
so the Network difficuilty is:
 00000000000000000130e0000000000000000000000000000000000000000000
i.e. vs our block:
 000000000000000000b6a5fb2524fb754860e9a3321695b51ccc566ee163d36a
thus our block is less than the network difficulty value, thus it was block

The chance of finding a block is purely random statistics.
Imagine you roll a dice, if you dont have a weighted dice and you can't affect the result of the roll, the chance of rolling a 6 is one in six.

Bitcoin mining is the same idea.
You are feeding numbers into hashing hardware, at a given THs rate

1 THs = 10^12 hashes per second

Network difficulty is currently 0x180130e0 (as mentioned above) but that also comes out as 923233068448.9053
I'll round it to 9.2x10^11

That number represents a ratio vs a 1 difficulty share.
A 1 difficulty share is randomly found, on average, once every 2^32 hashes
So the current difficulty says we should find a block, on average, once every 9.2x10^11 x 2^32 hashes = 3.9x10^21 hashes
Yep that's a pretty big number

That also currently represents '100%' on the blocks page.

So if your miner does ~17THs then you'd expect to expend (3.9x10^21) / (17*10^12) seconds, on average, to find a block at the current difficulty
Which is about 233million seconds or about 7.4 years
But since difficulty changes, there no point in saying that silly large number, it's better to simply say that at the current difficulty, your 17THs has a 1 in 2699.7 chance of finding a block in 1 day, which makes sense and is correct to actually say that.

Of course it's random and you could find it today, or you could never find it.
Them's the breaks

I also have a web page that does these sort of calculations for you:
http://tradebtc.net/bitcalc.php

[icon73]

Meanwhile, whoever the retard was who coded the changes for BitCH, unbelievable how stupid he was.
He clearly had no idea about the fact that people run Bitcoin wallets, duh! and Bitcoin will exist for way longer than that scam.
His wallet screws up or overrides the Bitcoin wallet by default, and uses all the Bitcoin ports, folders and even the same node list lookup.
This all means that they're using the place on the internet (and on your computer) that Bitcoin uses and causing issues doing so.
Every altcoin knows not to use the Bitcoin settings/ports and channels ... except for this retard.

i.e. someone running a BitCH node connecting to a Bitcoin node ... duh how stupid is that ... and the cause is that the guy who coded it didn't bother to use their own ports.
I guess it required him to know what he was doing and spend 30 seconds changing them

I agree, there isn't a good reason to mine BCH for the moment, but as things change, it may become time to rethink.  The most interesting part of your post what the part I quoted above.  I am surprised you are taking this position with "BitCH".  It seems apparent to me... that the "retard" who coded BCH used the same ports, and the same node list lookup... on PURPOSE.  I don't think that the folks who created BCH plan for it to be an altcoin.  I think they plan for it to replace BTC.  Maybe when the Blockstream zombies fail to turn on the 2x part of Segwit2x, or who knows why or when.  I realize that my opinion is not unique and there is a ton of this going around on some of the reddit pages.   But any way you slice that pie, I think it is unlikely that they made a mistake or didn't know what they were doing.  I think it was cold and calculated.  That doesn't mean what they did was good or right, but I believe it was with purpose, and not because he was retarded. 

Obviously Kano, my understanding of life the universe and everything BTC pales in comparison to yours, but at minimum something to consider.

[kano]

Yes I do realise the 'retard' did it on purpose and knew it would cause problems for bitcoiners, but in the assumption that BCH would replace BTC.

But that's even worse than doing it by mistake ...

BCH was claimed to have been created to over come the problem of the UASF.
Once that problem was removed, BCH should have disappeared.
Since it didn't disappear, it means that Bitmain and ViaBTC purposely caused problems for Bitcoin, when they could have simply avoided them with a few lines of code change.
Yes I do know it's only a few lines of code change, I've done it before for testing purposes.

So, what's better?
1) Calling him a 'retard' for making a mistake (not the case) or
2) Lynching him up for risking screwing around with everyone's Bitcoin wallet who runs BCH ...

I worded it as 1), but since it really is 2), when and where's the hanging?