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

Thanks for the comparison figures.

There are two things that I think are worth pointing out, that I'm sure you know:

1 - Prior results have no impact on future results.  Just because there is a huge "bad luck" spell doesn't mean it's "likely" to change soon.
2 - The "long game" is fair luck wise if difficulty stops increasing.

M

What was up with the Blockmines phantom Hash Rates on the site about 10 minutes ago? Was hoping he was coming back.

Even with October's bad luck variance, it was still no match for the good luck variance during April.
Here is to hoping November is the new April.

I ran some approximate BTC per Day per TH numbers.  I will be gathering more accurate details over the coming months since I will be storing 15 minute hash rates for pools we monitor.

For KanoPool.  
August was .000276 with 48 blocks (81Ph)
Sept was .000264 with 47 blocks (84Ph)
Oct was .000158 with 35 blocks (102Ph)

My backup (and what I originally started with) is slush.  I have averaged out details for them:
.000225 for August with 241 blocks and a rough average of 350Ph
.000255 for September with 273 blocks and a rough average of 500Ph
.000235 for October with 327 blocks and a rough average of 650Ph

So as you can see, things vary wildly and generally Kano is higher.  Obviously we have hit a bit of a downturn here, but I am confident that it will turn the other way after averaging a few months out.  Of course there are never guarantees, but my feeling is that anyone who has already ridden out the downturn for October would be missing the turnaround boat by leaving.  Kano has had 5 blocks in a day before with similar hash rates, so when the luck turns, we could be exceeding .0005 BTC per day per Th for a fair stretch.  It's all a waiting game and miners need to remember to go for the long game.

Getting the cow ready for sacrifice!  Fuck........

It not 'our' block until we find a block and keep it

What mining is, is simply hashing a set of data (work) and hoping it gets a value in the range we want.
That work of course (usually) includes a set of transactions.

Mining is a bit like rolling 2 dice and wanting snake eyes (1 + 1)
With dice it's expected to happen, on average, once every 36 rolls.
With Bitcoin, at the current difficulty of D=1,452,839,779,145.919 it expected to happen, on average, once every D*2^32 hashes = once every ~6.23x10^21 hashes.
Sometimes more often, sometimes less often, but it should average that over time.
But it's simply just random for everyone.

As for transactions, all transactions are distributed over the network to (mostly) all bitcoin nodes on the network.
Each pool generates work (usually) with the best combination of the available transactions to get the most fees in their work.
Some may have different rules about what they think is the best, and different rules about what they will include.

When one pool finds a block, the transactions confirmed in that block are of course no longer available to be used in any future blocks.
We all then start with the next best available transactions after the ones used up and of course add on any new transactions that appear, and continue on randomly getting hashes.

FYI the pool sends out new work to all the miners every 30 seconds, which of course includes all the better available transaction that have come available in the past 30 seconds.
And, as mentioned above, the pool also sends out new work each time someone on the bitcoin network finds a block, excluding all those transactions that were confirmed by that block.

I'm trying to view this from another angle.

even with getting paid out on transactions, when we are getting this far behind even 100% variance, and the price getting as high as it is, this leaves alot of money on the table. If other mines are hitting 100% vs where we are at this month, thats alot of money left on the table.

I know its abnormal for this pool, but running for a week without a block (I know we got one that went stale) is not good, thats why all the big guys left I assume.

I'm only a 110ths miner but I need some kind of a return.

Million dollar question is how long do you stick it out? As good/ethical of a guy kano is, I still need to pay my power bills.

Out of curiosity, when our block takes 74 hours, does that mean the transactions we are processing have not had a single confirmation for that many hours?  Or does the bitcoin network system have all pools grab a new set of transactions once a block is found on the network? 

Main pool node restart all ok.

KanoDB restart all ok also.

Again note there are some minor changes to the web site - mainly the account verification.
Related to that, it disables any input page fields that can't be changed when your account says so at the top.
Also, the top of the web page shows all messages correctly now, before it would sometimes show the old state after you made a change - that's been fixed also.

Anyone finds any problems or questions about the web changes - ask away

This is a very low hashrate pool, which means it has very high variance.

Variance means it will take a few months for luck to work out to 100%.  That means there will be long dry spells, like this one.

M

I'll be doing another main node restart in about 30 minutes (at 12:15 UTC)
This will cause EVERYONE to failover and fail back.
More patches.

Within about 10 minutes after I do that, I'll also do a KanoDB restart.
This will have some web updates and a few new rules about email addresses.
1) There's a new page Account->Verify that you can verify your email address
2) If you ever change your email address, it require you to verify it before allowing you to change anything else
3) Some accounts I will force on them requiring them to verify their email address before changing anything or mining, if the email address is junk
4) Other accounts I will force on them to verify their email address before changing anything if the email is invalid.

Am I missing something?   Is there a problem with the pool?   (software, config, etc.)   

Relax buddy!   If 4 days without a reward has you all worked up, you may want to find another hobby, because this is how it goes sometimes.

What a bad luck.
just started to mine and joined kano's pool - 4 days without any reward.

I tend to see blocks needing more hashes after a stale block in most if not all the pools I've mined in.  I have a s9 and a ebit e9+ running on this pool, stable finally.  I'm not going to just leave because others are giving up.  We need to band together and be welcoming to new miners big or small.  I'm a tiny fraction of this pools power but if we can get 1000 people like me to become apart of us or 100 people with larger mines then we'll run smooth again.  My advice....Invite, be friendly, beg if you need to lol, jk, just get miners here.  Unless this becomes a situation like bitminter which I mined at for a while that is at 1.5 Ph atm I believe.....not a fact, I haven't checked but that's why I came here.  Whatever, it's way late, i'm rambling all i'm saying is let's keep kano alive!!!!!!!!!!

This luck is starting to get painful. I want to hold out but it's getting harder as time goes by.

As the pools hash decreases our variance obviously increases and makes it even harder which only leads to more hash moving off the pool which increase variance even more and so the cycle continues.

64hrs, wow! 

I've had better stability with my two 741s (each uses two 1KW server bricks) with each 741 on its own USB input to the RPi...requires another AUC, but that was nothing. Dunno if that helps.

Not sure if it has been brought up here but given -ck's post on the upcoming B2x fork just to be clear, at least for the foreseeable future we will be mining strictly the Real BTC right?

Personally I say a huge 2x to the fork.

Perfect - I didn't even think of the controller/auc3. I ordered all of that from Amazon, and I'll get them connected as soon as they get here.

If that doesn't work, I'll try the auc3. I don't think it's the psus but I will isolate.

Appreciate the suggestions.