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

[xuy]

I hope it's like Y2K issue
Also hope BTC will keep its value and increase more value.

Re: payouts, I'll keep processing them for another day at least (30th) and then decide again if it's useful to put them on hold for a few days.
i.e. 478076 and 478087 will be processed as per normal.

Again, I don't really think it matters, since the issues with the fork are not going to lose anyone their BTC, which is really all that matters.
If any websites decide that they won't accept your BTC, well that simply means that you shouldn't use such a web site ... it is just BTC no matter what melodramas people want to create about it.
The fork should have no effect on BTC transactions, only a possible small reduction in global hash rate of whatever Bitmain might move to their fork ... which should probably mean a difficulty drop for the next 2 diff changes

[kano]

Rockou

Yes that was the email address you got in every email from the pool

No don't post email addresses on public forums

[Rockou]

Rockou

Yes that was the email address you got in every email from the pool

No don't post email addresses on public forums

I'm so sorry Mr Kano, but I'm new in this so, it will not happen again... And thank you so much

[kano]

There'll be a DB restart in about 30mins - as per the web site says also.

NO mining will be affected.

Minor update to the code, mainly a fix for the "«Elapsed" not resetting.

I also updated the web code yesterday to give you an error on the User->Setting page if you forget to enter the password(s)
Before it used to just return with the old values and no warning, now it gives you a red error message at the top.

All went as planned.
DB restart was from 9:31:59 to 9:40:18 UTC a bit under about 8.5 minutes.
I set it to reload twice the shift history, that is usually loads, so the workers page can show further back in time, for some who needed that

[kano]

Block! by blockmines
2 Payouts

Heh - the luck for the month now shows exactly 100.00%

Edit: oh that was the uncorrected (estimate) value that gave 100.00% - oh well it's corrected to 99.95% - close enough

[philipma1957]

Block! by blockmines
2 Payouts

Nice keep them coming

[clgrissom3]

Block by MariaCRdeV with 53.37TH/s!  Welcome to the Acclaim Board with your 1st Kano block!  

This is our 2nd of BLOCK SUNDAY!

It's a nice fat one!

[clgrissom3]

Block by schmokeandapancake!

This is our 3rd of BLOCK SUNDAY!

[smutboy420]

schmokeandapancak… for another block

[overcon]

I'm not Kano, but I'll give you the assurance that your Core wallet is the safest place to be right now...or ever, for that matter.

Excellent, thanks!

[kano]

Payout Information

So the payout handling for B-Day (yeah I think that name is an appropriate play on D-Day) will be as follows:

I'm queueing up 478254 and 478261 right now to go out as soon as they Mature - as per normal.

The 'expected' Maturity times at the moment are: ~3:50am (478254) and ~5:00am UTC (478261)
That gives a bit over 19 hours to confirm them before 1-Aug 0:20 UTC

Currently we expect to average ~13hrs per block so there's a reasonably high probability they will both be confirmed before B-Day
If not, well I don't REALLY think it matters, but we'll see anyway

478295, on the other hand is expected to Mature at ~10:40am UTC, and with the ~13hrs before it's average 'expected to be confirmed', that lands it close to B-Day arrival time.

So, I'll hold back sending out the payment for 478295 (and any blocks found after 478295) until tomorrow.

--

Again, I don't see why there should be any problems at all with Bitcoin on B-Day, but considering the melodrama going around, it's not really that big a deal to add a short delay to just a few payouts.

... and anyone who is really concerned can also have me hold their 'unqueued' payouts until they are no longer concerned as per the web site says.

--

Edit: I also set 42,000 sat in each one as a txn fee - about $1 - to see if that makes others confirm them also.
The Bitcoin transaction rate really has dropped recently - often block aren't full - so there's probably a higher chance of it getting into another pool's block if there's some tiny fee in it.
Anyway - we'll see if that makes any difference for those 2 payouts.

[clgrissom3]

Sounds like a plan!  I agree with you, I think it will not amount to anything when it's all over.

[kano]

Having some intermittent communication issues between the main server and the web server.
If you get a web error, just retry it and it should be ok.

[kano]

...
Edit: I also set 42,000 sat in each one as a txn fee - about $1 - to see if that makes others confirm them also.
The Bitcoin transaction rate really has dropped recently - often block aren't full - so there's probably a higher chance of it getting into another pool's block if there's some tiny fee in it.
Anyway - we'll see if that makes any difference for those 2 payouts.

Well that worked
478,360 BTCC confirmed the payout for 478254

478261 payout will be sent out (the same) after the next network block (when it matures)

Edit: and again

478,363 BTC.TOP confirmed the payout for 478261

... those $1 fees work well ... at the moment ...

[matscol]

feels funny to get payout alerts without a corresponding block alert 

when the first one came in i had to double-check to make sure the script was running properly.

[kano]

Payout Information

So the payout handling for B-Day (yeah I think that name is an appropriate play on D-Day) will be as follows:

I'm queueing up 478254 and 478261 right now to go out as soon as they Mature - as per normal.

The 'expected' Maturity times at the moment are: ~3:50am (478254) and ~5:00am UTC (478261)
That gives a bit over 19 hours to confirm them before 1-Aug 0:20 UTC

Currently we expect to average ~13hrs per block so there's a reasonably high probability they will both be confirmed before B-Day
If not, well I don't REALLY think it matters, but we'll see anyway

478295, on the other hand is expected to Mature at ~10:40am UTC, and with the ~13hrs before it's average 'expected to be confirmed', that lands it close to B-Day arrival time.

So, I'll hold back sending out the payment for 478295 (and any blocks found after 478295) until tomorrow.

--

Again, I don't see why there should be any problems at all with Bitcoin on B-Day, but considering the melodrama going around, it's not really that big a deal to add a short delay to just a few payouts.

... and anyone who is really concerned can also have me hold their 'unqueued' payouts until they are no longer concerned as per the web site says.

--

Edit: I also set 42,000 sat in each one as a txn fee - about $1 - to see if that makes others confirm them also.
The Bitcoin transaction rate really has dropped recently - often block aren't full - so there's probably a higher chance of it getting into another pool's block if there's some tiny fee in it.
Anyway - we'll see if that makes any difference for those 2 payouts.

Full quote since it's about what I said, and I'm changing it a bit:

I'll also send out 478295 in a few hours (when it matures) with the same $1 (42,000 sat) fee since it should get confirmed reasonably quickly.
Of course, best if we confirm it ... i.e. find a block ... but either way, it 'should' be confirmed well before B-Day.

[clgrissom3]

Thanks Kano!

[philipma1957]

It is 9:01AM EST time.

It looks to me that all blocks are mature and that they have been paid.


All go here for me and all have confirms

https://blockchain.info/address/16yLHLoeyuCLPMXkVpC3gyrRYvwRGwjKJr

[overcon]

My core wallet has a incoming transaction from Kano.is at 7/31/17 @ 04:04 and it shows a light grey and says:

Status: 0/unconfirmed, not in memory pool
Date: 7/31/2017 04:04
From: unknown
To: 1Q14j1KRDRcpUUb2rQYUh5WMLaynPfyP7S (own address, label: KANO.IS)
Credit: 0.00599468 BTC
Net amount: +0.00599468 BTC
Transaction ID: 5f6688c178cd5cba2c98056f9091da43e0b6b7ac3ecda023ab7f21b4b0773d4f
Transaction total size: 28234 bytes
Output index: 496


Never seen that, new normal?

[kano]

Just means the last payout (that's not confirmed yet) actually got out past the pool bitcoind.
When it's a zero fee transaction, few others will accept it or pass it on.
It's not zero fee (42,000 sat) so it gets out further on the net.