I checked the page you rewards, but it does not say anything
They are mining with 3X S7
about 14 terash
PM me your username and I'll look up what's happening.They are mining with 3X S7
about 14 terash
... and ... block!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1833. (Read 5352140 times)
January 14, 2016, 02:26:18 AM
... and ... block!
January 14, 2016, 02:25:59 AM
Block 393256 !!!
January 14, 2016, 02:15:13 AM
I checked the page you rewards, but it does not say anything
They are mining with 3X S7
about 14 terash
They are mining with 3X S7
about 14 terash
January 14, 2016, 01:58:58 AM
kano hello, I do not know if my configuration in your pool and correct,
it is possible that in one day and 54 minutes, I did not receive any payment?
I ask because I've never understood how your pool kano.is
it is possible that in one day and 54 minutes, I did not receive any payment?
I ask because I've never understood how your pool kano.is
Are you mining? How much? Did you check the rewards page? Do you have more than dust? Need more info.
January 14, 2016, 01:51:00 AM
kano hello, I do not know if my configuration in your pool and correct,
it is possible that in one day and 54 minutes, I did not receive any payment?
I ask because I've never understood how your pool kano.is
it is possible that in one day and 54 minutes, I did not receive any payment?
I ask because I've never understood how your pool kano.is
January 13, 2016, 11:20:09 PM
Kano, what is this?
Дaтa: 13.01.2016 13:25
Кpeдит: 0.00010000 BTC
Чиcтaя cyммa: +0.00010000 BTC
ID - 08691d30f3a15697576f34e0702c0d721f92ff83770511f64edd36c6cc692dcd
https://bitcointalksearch.org/topic/m.13540136 Дaтa: 13.01.2016 13:25
Кpeдит: 0.00010000 BTC
Чиcтaя cyммa: +0.00010000 BTC
ID - 08691d30f3a15697576f34e0702c0d721f92ff83770511f64edd36c6cc692dcd
January 13, 2016, 11:17:04 PM
Kano, what is this?
Дaтa: 13.01.2016 13:25
Кpeдит: 0.00010000 BTC
Чиcтaя cyммa: +0.00010000 BTC
ID - 08691d30f3a15697576f34e0702c0d721f92ff83770511f64edd36c6cc692dcd
Дaтa: 13.01.2016 13:25
Кpeдит: 0.00010000 BTC
Чиcтaя cyммa: +0.00010000 BTC
ID - 08691d30f3a15697576f34e0702c0d721f92ff83770511f64edd36c6cc692dcd
January 13, 2016, 11:07:44 PM
Kano, will you and your pool support "Bitcoin Classic"? What is your opinion about it?
I support Bitcoin.Every time someone (Gavin
) comes along with a "OMG great new version of Bitcoin everyone switch over now!" I'll ignore it until I have to take notice of it ...--
Payout 393122 sent (3hrs ago)
fcc8bf3f21492444c1fe2ced02441ad65bab4e52180ea6c5fedcd82a77d0657e
and finally just confirmed
January 13, 2016, 10:42:52 PM
Kano, will you and your pool support "Bitcoin Classic"? What is your opinion about it?
January 13, 2016, 10:31:16 PM
Everything's spiffy here. All five dwarfs are digging like crazy...no bumps. Mahalo!
January 13, 2016, 10:24:37 PM
...
Before that, I'm now going to do a ckdb restart in about 20 minutes.
Will happen shortly after the next shift completes and is processed.
... and the usual reminder about a ckdb restart, no miners are affected by it at all.
Only the web site stats are unavailable.
This is a small update to support a small change in ckpool, to provide me with some more useful data about connections and I'll enable it on the workers page with a minor web change a bit later also.
CKDB Restart completed.Before that, I'm now going to do a ckdb restart in about 20 minutes.
Will happen shortly after the next shift completes and is processed.
... and the usual reminder about a ckdb restart, no miners are affected by it at all.
Only the web site stats are unavailable.
This is a small update to support a small change in ckpool, to provide me with some more useful data about connections and I'll enable it on the workers page with a minor web change a bit later also.
Took a little over 9 minutes this time:
[2016-01-14 14:00:59.058+11] Listener received terminate message, terminating ckdb
[2016-01-14 14:10:10.668+11] reload queue completed 0m 13.617s
January 13, 2016, 09:44:37 PM
Thank you for the updates. Much appreciated.
I remember now when you mentioned "once a day."
That payment was so fast after the 101 confirmations, I just assumed it was "automated."
I remember now when you mentioned "once a day."
That payment was so fast after the 101 confirmations, I just assumed it was "automated."
January 13, 2016, 09:30:24 PM
... and on the subject of changes ...
There's been some important changes on the ckpool local <->remote node code by -ck so there'll be a set of updates with those in about 18 hours.
I'll post again tomorrow morning (it's early afternoon here now) an hour before I do that with ckpool on all the nodes.
Before that, I'm now going to do a ckdb restart in about 20 minutes.
Will happen shortly after the next shift completes and is processed.
... and the usual reminder about a ckdb restart, no miners are affected by it at all.
Only the web site stats are unavailable.
This is a small update to support a small change in ckpool, to provide me with some more useful data about connections and I'll enable it on the workers page with a minor web change a bit later also.
There's been some important changes on the ckpool local <->remote node code by -ck so there'll be a set of updates with those in about 18 hours.
I'll post again tomorrow morning (it's early afternoon here now) an hour before I do that with ckpool on all the nodes.
Before that, I'm now going to do a ckdb restart in about 20 minutes.
Will happen shortly after the next shift completes and is processed.
... and the usual reminder about a ckdb restart, no miners are affected by it at all.
Only the web site stats are unavailable.
This is a small update to support a small change in ckpool, to provide me with some more useful data about connections and I'll enable it on the workers page with a minor web change a bit later also.
January 13, 2016, 09:19:41 PM
Hi Kano,
Was that our first "automated" payment?
Heh, no, there never will be completely "automated" payments.Was that our first "automated" payment?
The first (very simple) change I made a few weeks ago was being able to process them before they confirm.
So usually there's only a few minutes delay (unless I'm asleep) between +101 and sending the payout since I set it up (randomly) in advance.
The changes the other day were to do with how I get the actual payout data from the server.
I simplified that process greatly and secured it a little more also.
These steps do of course lead to the next one: one payout per day, but that may still be a week or more before I get to working on that.
January 13, 2016, 09:14:03 PM
Your thinking of the 5Nd the wrong way.
I am going to see if I can come up with a better way to explain this to people...
Edit: Maybe this will help?
Current difficulty = 113354299801
That means that 1Nd = 113354299801
5Nd = 113354299801 x 5 = 566771499005
That means that when a block is found the last 566771499005 shares are paid.
So for every one of those 566771499005 shares that you submitted you are paid for.
You are paid for the ratio of your shares to the 566771499005 that are paid.
The 5Nd is not a time, but a number of shares...
I'm a completely noob about technical knowledge of the bitcoin protocol, but now i understand this 5Nd thing thanks to you.
Really helpful explanation.
Kano should put this on the website, under his explanation. its a good "practical example".
January 13, 2016, 08:33:58 PM
Since I have mined since the start of the pool, I have a reward in every block.
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt
Awesome, so the pool hash rate at block 23 was 1.31PH. As I type this the pool hash rate is 9.9PH, 7.56 times larger.
The network difficulty at block 23 was 39,603,666,252. As I type this the network difficulty is 113,354,299,801, 2.86 times larger.
Is there a non-linear increase in how hard it is to find a share higher than value X? If not, then it looks like the first streak was much more impressive.
January 13, 2016, 08:10:51 PM
Hi Kano,
Was that our first "automated" payment?
Was that our first "automated" payment?
January 13, 2016, 07:21:32 PM
I see what's going you here. You people are trying to get me to do math.
Well even I cheated I just copy pasted my Rewards page rather than writing some code/sql to generate it for them all
January 13, 2016, 07:04:31 PM
Why bother? I'm sure most ppl don't care for past random ratios.
January 13, 2016, 06:56:14 PM
Since I have mined since the start of the pool, I have a reward in every block.
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt
Thus I also have the Pool hash rate shown for every (valid) block on the Rewards page
Comma separated, lf (not crlf)
Block,Block UTC,Miner Reward,N Diff,N Range,Pool N Avg
http://kano.is/kblocks.txt
Awesome, so the pool hash rate at block 23 was 1.31PH. As I type this the pool hash rate is 9.9PH, 7.56 times larger.
The network difficulty at block 23 was 39,603,666,252. As I type this the network difficulty is 113,354,299,801, 2.86 times larger.
Is there a non-linear increase in how hard it is to find a share higher than value X? If not, then it looks like the first streak was much more impressive.
Jump to: