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

[bronder]

Kano,

I appreciate you keeping us informed as to the plan for B-Day, hopefully it's a non-event and it should be at least for us.

[firetreeactual]

I'm all clear on payments as well. Reminds me of the brouhaha around the last two halvings... 

[philipma1957]

I'm all clear on payments as well. Reminds me of the brouhaha around the last two halvings... 

hope so.

Oh my avalon 741 comes on tues  just in time for the new era.

[OneInchWonder]

With the fork going happen and if a good size of the speed drops off the network to mine BCC with about 8 days till difficulty adjustment.

How do you see it playing out?
Longer wait times and tell blocks are found and slow down transactions and confirmations.

[kano]

With the fork going happen and if a good size of the speed drops off the network to mine BCC with about 8 days till difficulty adjustment.

How do you see it playing out?
Longer wait times and tell blocks are found and slow down transactions and confirmations.

Well that all simply depends on how much hash rate goes to the fork, and that's anyone's guess.

It will of course mean average slower blocks until the next diff change, but once the next diff change gets here, that will mean a diff drop also.

I doubt we'll see 20% of the network switch to the fork, but doing the calculations with 20%:

e.g. if it was 20% then that would mean 1/0.8 or 25% longer blocks i.e. expected avg 12.5 mins per block.
we are at the moment 666 blocks in this diff change i.e. 1350 to go so ~1/3 done, ~2/3 to go
2/3 would expect to be 9.375 days, but with the extra 25% that would be 11.7 days so about 2.3 extra days - so even 20% is not that big a change.
The diff drop for 20% would be about 13.3% - i.e. about 2/3 of the 20%

The next diff change, after this up coming one, will also be a little slower, since the first 1/3 of this diff change was at the higher hash rate, so that should be the other 1/3 of the 20% for the whole next diff change, but since it would already have dropped 13.3% ... that 1/3 would mean roughly about another 6.2% diff drop next diff change.

... all that also presuming no hash rate rise

[kano]

Last payout (478295) confirmed - in time
The power of 42,000 satoshis

Edit: also there were a few failovers from 16:18 to 16:28 UTC from one of the US stratum nodes.
You'll see a drop on the shift graph for that shift.
I'm guessing there was network trouble but got no notifications (to wake me up) since in each case they were immediate failovers and failbacks.
My monitoring needs to lose the connection (which it didn't, so it wasn't a full failover of everyone) or it needs to fail another network test, which didn't happen either.
So must have been very short each time.

[philipma1957]

Okay is it now August 1? and if so has anything started?

first new block

https://blockchain.info/blocks


https://blockchain.info/block-height/478479

[kano]

Okay is it now August 1? and if so has anything started?

first new block

https://blockchain.info/blocks


https://blockchain.info/block-height/478479

Well you'd have to look for rejected blocks in your bitcoin debug.log
Give it a while
Also the network hash rate will probably drop a bit - but that won't be obvious for a while either.
The pools list at btc.com may or may not show the split correctly ... who knows how they come up with the numbers there
I sent them the details for KanoPool a while ago and they've still done nothing to fix that ...

Edit: blockchair.com was supposed to have a browser at fork time ... but that clearly didn't happen

[Tamerz]

Well you'd have to look for rejected blocks in your bitcoin debug.log

Would that be these?

Code:

warning='20 of last 100 blocks have unexpected version'

[kano]

Well you'd have to look for rejected blocks in your bitcoin debug.log

Would that be these?

Code:

warning='20 of last 100 blocks have unexpected version'

No, they're just the different block version numbers - for segwit2x 0x20000012 or other guff with other numbers
The expected block version at the moment is 0x20000002

I've seen messages saying
"invalid block=" and "is marked invalid"
a bit over a week ago for a block with the hash "0000000000000000013ee4a86822d37a061732e04ee5f41fb77168f193363d1b" at 477115

So I'm guessing the message might be similar - but I'm not sure and have never checked the code to see what other such messages there are.

One simple way on linux to see all block messages other than the standard expected ones is:
grep 000000000 debug.log | grep -v "new best="

[huynhdat1989]

Dear kano,
Do you support mining Bitcoin Cash? We use the same asic miner to mine?

Regards,

[mousehouse]

Wow, nearly 40 hours without finding any blocks

Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move?

[kano]

Dear kano,
Do you support mining Bitcoin Cash? We use the same asic miner to mine?

Regards,

It's an alt-coin - which I tend to completely stay clear of.

Unless it becomes what I consider 'valid', I'd not setup a pool, in my usual disinterest in being involved in scams, which it clearly currently is

Setting up a pool is simple enough, but it also depends on how reliable the bitcoind is, since if it's crashing or causing problems, that's a royal PITA coz it can mean wasted mining for everyone pointed at the pool when such things happen.
That's not something new, it happens all over the place, but you find that others pools don't tell you about it, or tell you what's going on ... ... ... ... ...

However, Core bitcoind is currently pretty reliable as a fast work generator, with minor changes and since I run a few on the main node, it's been a long time since there's been anything that could matter.

[kano]

Wow, nearly 40 hours without finding any blocks

Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move?

Try pinging any in the thread title to find the closest one to you.
i.e. de, sg, jp, nl, and nya.kano.is

[mousehouse]

Wow, nearly 40 hours without finding any blocks

Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move?

Try pinging any in the thread title to find the closest one to you.
i.e. de, sg, jp, nl, and nya.kano.is

Thx, works great! Two new miners on your pool

[kano]

Wow, nearly 40 hours without finding any blocks

Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move?

Try pinging any in the thread title to find the closest one to you.
i.e. de, sg, jp, nl, and nya.kano.is

Thx, works great! Two new miners on your pool

Your welcome and cool, more miners

[Biffa]

Okay is it now August 1? and if so has anything started?

first new block

https://blockchain.info/blocks


https://blockchain.info/block-height/478479

The BIP148 split was a no-sho it seems, everyone had already moved to BIP91

The Bitcash hard fork happens around 12:20 UTC today. Thats when there should be some ripples.

[kano]

For those interested
This might actually be working - it now shows no BCH blocks ... correctly ... 5 mins before the 'fork'
https://blockchair.com/bitcoin-cash/blocks

That might well show reasonably quickly (hours) how much hash rate has gone from Bitcoin.

or https://www.btcforkmonitor.info/

[Apprentice]

I'm all clear on payments as well. Reminds me of the brouhaha around the last two halvings... 

hope so.

Oh my avalon 741 comes on tues  just in time for the new era.

Waiting too for 2 S9s to ship in August! 

[d57heinz]

If anyone wants me to hold their payouts - they can request it (but send an email from your pool account email address to the address you get pool messages from)
However, the held payouts will sit in your dust fund until I do the dust processing code, some time in the future, in a galaxy far far away.

Also, tell me ASAP, coz once I've created the payout for any block, which is before it matures, I'd have to redo the payout from scratch to change anything, and of course once it's matured, the transaction is out on the bitcoin network, so I certainly wont be trying to double spend it, to change it.

It's not an on, off, on, off, on, off thing I will be doing, just a once off thing now you can request over the next few days, then later request it back on again.

Edit: OK added a link to here, on the web site also.

Why don't you save yourself from all this hassle and just setup a payout like most all pools do. I know it's not from lack of coding ability.  Set a small withdrawal fee and that's that.  You've been talking about this for cpl years. I'd say either get it done or just say that's going to be donation to the pool.  When someone tells me it's gonna get done some time in future in a galaxy far far away basically says to me it's never getting done. You need to take a stand get it done and stop leading on the little miners that could actually be receiving a payout from other pools.  Granted it may be less but if you never pay the other pools look much better.   How about a roadmap of some sort please and thank you.

Ps. Hell of ya have to use code from mpos. That'll save loads of time

Best Regards
Doug