Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 442. (Read 5352527 times)

jr. member
Activity: 33
Merit: 2
I keep seeing all this about pool x, pool y, pool z vs here or maybe I should just say PPS vs here.

So after 35 days I figured it was time for a few real numbers.

I started here on the 18 (night) of January, with what was 15Th as the time, but that quickly doubled to 30 a day or 2 later and has been pretty flat since (just added 22 more, but I'll ignore that at the moment)

The other day when I brought up my 821's, I put them on slush for 2 hrs, just because I wanted to see what the daily CDT was there at my full hashrate.  Then I moved them back to here.

So here is the basis to my numbers.

30Th/s for 35 days
Actual numbers from Kano based upon the above.

Let's start with my Kano experience.
I received .0976473 BTC in 35 days
this equals .0027899 per day
or .0000930 CDT

for the same amount of hash at slush, we'll work backwards
.00008703 CDT
.0026109 per day
or .0913815 BTC

You can say what you want and this is just a snapshot of 35 days, but even with the really ugly luck we've had, I've still made more here than the equivalent time at slush (who btw is averaging slightly *better* than 100% luck).

The upside that isn't in the above, if we find a block today, my numbers would go up again to a much larger amount of BTC than slush (e.g. .0045 (would be .007, but I'll factor out the .0027899 CDT) BTC to .002), if we improve on luck, we shatter the slush numbers.  If I left today and went somewhere else, I'd still be paid for 5Nd ramp down along with where-ever else I go's take.

I just can't see any downside.  Ok, except the fact that you don't have a little graphical ticker that is counting up based upon predicted BTC.... Oh but wait, it simply matches the number above, so what real benefit is it?

EDIT1: with 30Th/s this should work for anyone curious with a 14-15Th/s S9 or anything else because I took all the numbers down to CDT (Coin per Day per TeraHash/s)

Started mining with 11Th/s at kano in 13/Jan 01:54.
When i fully ramped up after a really bad luck i got 0.00294833BTC.(9/Feb 20:11)
Between January 13 and February 19(37days) i made 0.01504784 BTC in total( + what the pools finds in the next ~13days).

One S9 on slush made (between the same time) 0.05241363 BTC.

Kano(~11th/s) vs. Slush(~13.7th/s)
0.01504784 vs. 0.05241363

Slush: https://docs.google.com/spreadsheets/d/1UCQ0pmTAjNYnTWyLShSFMWQ0u3_K68OlgvVsstsUPMg/edit#gid=1557054697
Kano: https://i.imgur.com/2gTRFof.png

After 3days at slush i made: 0.00348309BTC

Not sure how u get higher on kano.


akadamson just cheated a few.

He extrapolated the results of mining short period (couple of hours) at latest difficulty at slush to a longer period (1 month, at more more little difficulties). This obviously created an error: luck of profit in slush.
Later on he calculates the real profit obtained mining at Kano and compares with the "extrapolated" profit in slush.... and the conclusion is:

Almost the same!! isn't it marvellous?

The worse thing here is that legendary one applaud this and even give merit...

I hope no new miners will come and trust this non sense without verifying the data!!! we are talking about loosing money!!!
newbie
Activity: 6
Merit: 0
I keep seeing all this about pool x, pool y, pool z vs here or maybe I should just say PPS vs here.

So after 35 days I figured it was time for a few real numbers.

I started here on the 18 (night) of January, with what was 15Th as the time, but that quickly doubled to 30 a day or 2 later and has been pretty flat since (just added 22 more, but I'll ignore that at the moment)

The other day when I brought up my 821's, I put them on slush for 2 hrs, just because I wanted to see what the daily CDT was there at my full hashrate.  Then I moved them back to here.

So here is the basis to my numbers.

30Th/s for 35 days
Actual numbers from Kano based upon the above.

Let's start with my Kano experience.
I received .0976473 BTC in 35 days
this equals .0027899 per day
or .0000930 CDT

for the same amount of hash at slush, we'll work backwards
.00008703 CDT
.0026109 per day
or .0913815 BTC

You can say what you want and this is just a snapshot of 35 days, but even with the really ugly luck we've had, I've still made more here than the equivalent time at slush (who btw is averaging slightly *better* than 100% luck).

The upside that isn't in the above, if we find a block today, my numbers would go up again to a much larger amount of BTC than slush (e.g. .0045 (would be .007, but I'll factor out the .0027899 CDT) BTC to .002), if we improve on luck, we shatter the slush numbers.  If I left today and went somewhere else, I'd still be paid for 5Nd ramp down along with where-ever else I go's take.

I just can't see any downside.  Ok, except the fact that you don't have a little graphical ticker that is counting up based upon predicted BTC.... Oh but wait, it simply matches the number above, so what real benefit is it?

EDIT1: with 30Th/s this should work for anyone curious with a 14-15Th/s S9 or anything else because I took all the numbers down to CDT (Coin per Day per TeraHash/s)

Started mining with 11Th/s at kano in 13/Jan 01:54.
When i fully ramped up after a really bad luck i got 0.00294833BTC.(9/Feb 20:11)
Between January 13 and February 19(37days) i made 0.01504784 BTC in total( + what the pools finds in the next ~13days).

One S9 on slush made (between the same time) 0.05241363 BTC.

Kano(~11th/s) vs. Slush(~13.7th/s)
0.01504784 vs. 0.05241363

Slush: https://docs.google.com/spreadsheets/d/1UCQ0pmTAjNYnTWyLShSFMWQ0u3_K68OlgvVsstsUPMg/edit#gid=1557054697
Kano: https://i.imgur.com/2gTRFof.png

After 3days at slush i made: 0.00348309BTC

Not sure how u get higher on kano.
sr. member
Activity: 308
Merit: 251
I like big BITS and I cannot lie.
I wonder how many grandmas have bitcoin?

Mine on! Let's crack this block!

legendary
Activity: 4004
Merit: 4656
I keep seeing all this about pool x, pool y, pool z vs here or maybe I should just say PPS vs here.

So after 35 days I figured it was time for a few real numbers.
Nicely done!

You can't take a short time frame and make any conclusion one way or another.

I can see from long term numbers that they are OK.
The last, say, few months starting about 6 mo ago are not great, but luck should get back at some point, i agree with that.
It better be soon to attract those bonus miners.
member
Activity: 140
Merit: 18
I keep seeing all this about pool x, pool y, pool z vs here or maybe I should just say PPS vs here.

So after 35 days I figured it was time for a few real numbers.

I started here on the 18 (night) of January, with what was 15Th as the time, but that quickly doubled to 30 a day or 2 later and has been pretty flat since (just added 22 more, but I'll ignore that at the moment)

The other day when I brought up my 821's, I put them on slush for 2 hrs, just because I wanted to see what the daily CDT was there at my full hashrate.  Then I moved them back to here.

So here is the basis to my numbers.

30Th/s for 35 days
Actual numbers from Kano based upon the above.

Let's start with my Kano experience.
I received .0976473 BTC in 35 days
this equals .0027899 per day
or .0000930 CDT

for the same amount of hash at slush, we'll work backwards
.00008703 CDT
.0026109 per day
or .0913815 BTC

You can say what you want and this is just a snapshot of 35 days, but even with the really ugly luck we've had, I've still made more here than the equivalent time at slush (who btw is averaging slightly *better* than 100% luck).

The upside that isn't in the above, if we find a block today, my numbers would go up again to a much larger amount of BTC than slush (e.g. .0045 (would be .007, but I'll factor out the .0027899 CDT) BTC to .002), if we improve on luck, we shatter the slush numbers.  If I left today and went somewhere else, I'd still be paid for 5Nd ramp down along with where-ever else I go's take.

I just can't see any downside.  Ok, except the fact that you don't have a little graphical ticker that is counting up based upon predicted BTC.... Oh but wait, it simply matches the number above, so what real benefit is it?

EDIT1: with 30Th/s this should work for anyone curious with a 14-15Th/s S9 or anything else because I took all the numbers down to CDT (Coin per Day per TeraHash/s)

Can I highlight one other thing.  If you are getting into this to *make money*.  Please understand, it took me 35 days @ 30Th/s to make *almost* .1 BTC, that means if I were a single S9, it would have taken approx 70 days to do the same.  And that is only going to get harder with the growing network hash rate and diff changes.  But most important.  70 * 10 is ~700 days to make 1BTC - that's a freaking long time  (like almost 2 years) and why most people say if you *just* want to make money in this game *don't mine* go trade currencies!
full member
Activity: 658
Merit: 118

I just can't see any downside.  Ok, except the fact that you don't have a little graphical ticker that is counting up based upon predicted BTC.... Oh but wait, it simply matches the number above, so what real benefit is it?

Some people didn't budget to have their miners go for a run of bad luck, so they're willing to earn less money sooner than more money later on.
member
Activity: 140
Merit: 18
I keep seeing all this about pool x, pool y, pool z vs here or maybe I should just say PPS vs here.

So after 35 days I figured it was time for a few real numbers.

I started here on the 18 (night) of January, with what was 15Th as the time, but that quickly doubled to 30 a day or 2 later and has been pretty flat since (just added 22 more, but I'll ignore that at the moment)

The other day when I brought up my 821's, I put them on slush for 2 hrs, just because I wanted to see what the daily CDT was there at my full hashrate.  Then I moved them back to here.

So here is the basis to my numbers.

30Th/s for 35 days
Actual numbers from Kano based upon the above.

Let's start with my Kano experience.
I received .0976473 BTC in 35 days
this equals .0027899 per day
or .0000930 CDT

for the same amount of hash at slush, we'll work backwards
.00008703 CDT
.0026109 per day
or .0913815 BTC

You can say what you want and this is just a snapshot of 35 days, but even with the really ugly luck we've had, I've still made more here than the equivalent time at slush (who btw is averaging slightly *better* than 100% luck).

The upside that isn't in the above, if we find a block today, my numbers would go up again to a much larger amount of BTC than slush (e.g. .0045 (would be .007, but I'll factor out the .0027899 CDT) BTC to .002), if we improve on luck, we shatter the slush numbers.  If I left today and went somewhere else, I'd still be paid for 5Nd ramp down along with where-ever else I go's take.

I just can't see any downside.  Ok, except the fact that you don't have a little graphical ticker that is counting up based upon predicted BTC.... Oh but wait, it simply matches the number above, so what real benefit is it?

EDIT1: with 30Th/s this should work for anyone curious with a 14-15Th/s S9 or anything else because I took all the numbers down to CDT (Coin per Day per TeraHash/s)
jr. member
Activity: 136
Merit: 2
Well, I'm back at ramping up, after a 5hr power loss. I don't know what sucks worse, losing the time or freezing my ass off!
No heat on a 20°f Michigan night, is not fun at all. Back to business!

Look at the bright side...it was only 5 hours...20 degrees is a lot better than it could have been up there...and finally, you didn't cause the outage with blowing a transformer or something stupid and your gear is good so no surge. YAY!

Can I get a second on starting "Block Friday" a day early this week? Any votes?

Mine the F On!
full member
Activity: 350
Merit: 158
#takeminingback
Well, I'm back at ramping up, after a 5hr power loss. I don't know what sucks worse, losing the time or freezing my ass off!
No heat on a 20°f Michigan night, is not fun at all. Back to business!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Canaan has some big swings in hashrate to the pool. They must switch around a lot.
They make miners and sell them ...
So I expect their hash rate to be quite variable.
member
Activity: 266
Merit: 13
Canaan has some big swings in hashrate to the pool. They must switch around a lot.
jr. member
Activity: 168
Merit: 2
Haha, who's the sensitive one?

It's a double entendre.

It's a "good luck" as in that is what mining is...luck and also you're leaving to try out another pool, so "good luck". That's why I put it in quotes. If it doesn't turn out, then you'll be back. I'm not mad if you leave, that's all on you.

Though, if you think about it, taking terahash away from the pool when you know the pool needs terahash does hurt the pool, so don't be surprised if some are upset. I'm just hoping Kano's promotion will work out and drown out your hash anyway.

Good luck!
newbie
Activity: 5
Merit: 0
Just joined up today.  Starting off with one s9 to get my feet wet and understand how it all works. 
jr. member
Activity: 35
Merit: 2
"Good Luck"

Man I don't get why some people in this community is so sensitive, things like leaving the pool or criticism always get responses like this one. Is like this pool have his own internet defense force 24/7.

Whats with the "good luck" comment buddy? Are you mad or something? Jesus, mining here for almost 6 months straight and I can't comment I'm leaving?
jr. member
Activity: 168
Merit: 2
I gotta say I started mining here at the beginning of the 600 block and I'm questioning my sanity. I want to contribute to decentralization and all but .......3 S9's isn't much but sheesh I'd like to make a buck.

Oh yea Mine On LOL

I was mining at Kano since Sep 2017, a couple hours ago took my 85THs to another pool. This month has been brutal.

"Good Luck"
jr. member
Activity: 35
Merit: 2
I gotta say I started mining here at the beginning of the 600 block and I'm questioning my sanity. I want to contribute to decentralization and all but .......3 S9's isn't much but sheesh I'd like to make a buck.

Oh yea Mine On LOL

I was mining at Kano since Sep 2017, a couple hours ago took my 85THs to another pool. This month has been brutal.
newbie
Activity: 6
Merit: 0
I gotta say I started mining here at the beginning of the 600 block and I'm questioning my sanity. I want to contribute to decentralization and all but .......3 S9's isn't much but sheesh I'd like to make a buck.

Oh yea Mine On LOL
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I was watching BTC.com last block time posted, and then kano.is timer at the top of web page is about 18 seconds behind..  Just wondering what is up with the time difference?  Or any other way to check that is not so crude like my method?


Just checked last block  509209 and its time stamp on kano server is 2018‑02‑14 19:53:00
Time stamp of the same block on BTC.com                                      2018-02-14 12:52:44

Kano is 16 seconds later than the BTC, ( disregard time zone differences for the hour)

Blockchain.ifo has the same  2018-02-14 19:52:44 for block 509209

Funny, I picked blocks at random that kano found, and they are all on average 15 - 20 dseconds behind on time stamp from blockchain info.
Wierd..


509209 was a week ago.
Please try to at least look at current blocks so I can more easily show what's wrong Tongue

My guess is that you are looking at the block header time shown on blockchain.info
That is NOT the time the block was found.
It should be BEFORE it was found.

A pool creates work with a timestamp in it then sends it to the miners.
The miner can then find a block some time in the 30 seconds (in our case) or worse with some pools 60 or even 90 seconds, after that time.
The pool doesn't know in advance when you will find a block - fortunately.
So the block header time stamp will usually show the time the work was sent to the miner which is pretty much unrelated to when the miner finds a block.

There is no data in a block that says exactly when it was found.

Edit: also note that the timestamp is allowed to be wrong by about 1.5 hrs

Edit2: heh I thought you were talking about our block change time vs other pools.
I just realised you were talking about our last block 509209.
Yes the timestamp in the block was the time the work was sent to the miner who found it.
Obviously there is no way for anyone else to see our blocks before we do ... since we need to actually send the block out before anyone else will see it.
legendary
Activity: 4004
Merit: 4656
I was watching BTC.com last block time posted, and then kano.is timer at the top of web page is about 18 seconds behind..  Just wondering what is up with the time difference?  Or any other way to check that is not so crude like my method?


Just checked last block  509209 and its time stamp on kano server is 2018‑02‑14 19:53:00
Time stamp of the same block on BTC.com                                      2018-02-14 12:52:44

Kano is 16 seconds later than the BTC, ( disregard time zone differences for the hour)

Blockchain.ifo has the same  2018-02-14 19:52:44 for block 509209

Funny, I picked blocks at random that kano found, and they are all on average 15 - 20 dseconds behind on time stamp from blockchain info.
Wierd..



Probably just means his servers are not getting time from a time server.

Weird
I hope that this is not something affecting our "luck".....
In any case, why exactly he is not getting time from a time server?
newbie
Activity: 65
Merit: 0
I was watching BTC.com last block time posted, and then kano.is timer at the top of web page is about 18 seconds behind..  Just wondering what is up with the time difference?  Or any other way to check that is not so crude like my method?


Just checked last block  509209 and its time stamp on kano server is 2018‑02‑14 19:53:00
Time stamp of the same block on BTC.com                                      2018-02-14 12:52:44

Kano is 16 seconds later than the BTC, ( disregard time zone differences for the hour)

Blockchain.ifo has the same  2018-02-14 19:52:44 for block 509209

Funny, I picked blocks at random that kano found, and they are all on average 15 - 20 dseconds behind on time stamp from blockchain info.
Wierd..



Probably just means his servers are not getting time from a time server.
Jump to: