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

Let's keep these small miner giveaways going with another (although slightly less impressive 3.5THs)...

'PASS THE HASH' GIVEAWAY!

After being inspired by luxMiner's generosity, I want to pass on my only Avalon6's hashpower next week to one (1) lucky miner who meets the following criteria that I've edited below to keep things in line with the ~4x increase that I was blessed with:


Once the lucky miner is picked, Kano will fact-check that miner's stats and rewards to make sure they "fit the bill", and I'll announce the winner to everyone.

Also, in an effort to promote the pool and these types of small miner giveaways, Kano approved of me including this...



Although this is all freely donated with no strings attached, my hope is that others would consider participating and put some action behind all the discussions about what we can do to 1) grow the pool and 2) keep things interesting for those of us that don't qualify for the 10BTC big miner giveaway. 

Best of luck, and as always... Mine on!

sorry for the extra notifications - working on the alerts...  we did not find a block yet....

My little podunk town lost power again today!!! Grrrr!!! This time, I was at work and had noway of resetting my miners. So, about 7hrs down on my ramp.

I am officially a proud user of Awesome Miner!

Total hash rate is all that matters with the 'ramp'

---

Edit: I guess to explain what actually happens:
So for (say) 10 hours you were mining at (say) 13TH/s lower.
Of course, somehow, that not-mining means an expected loss of some reward (10hrs times 13TH/s)

How it actually happens is that over the 5ND from the start of the drop in hash rate, your 10 hours of not-mining is lost.
i.e. instead of losing 10hours of mining on the next block we find, you lose 10 hours of mining over the next 5Nd.
So the expected 5 blocks per 5Nd would mean you'd lose about 2 hours of mining of each of the 5 expected blocks.
Of course it's not an exact 2 hours off each block, but rather it will go down and back up to give that 'expected' result.

Now here's an interesting thing about pools (like slush) that use a VERY short time for the N in their PPLNS.
It's of course random on such a pool if you will lose your reward on the next block(s) found when you have an outage.
You can be lucky and not lose anything coz your outage is in the range not counted in the next block, or you could lose everything coz your outage covered the range of the next block(s)

HOWEVER, the point about the long term probability of recuperating that loss or losing that gain, is of course assuming that you disconnect often.
Who does that? Most people don't disconnect from the pool regularly, and thus they rarely average out those losses or gains.
So if you get lucky on that rare disconnect you have on such a pool, and gain more than expected, it's a gain that you are unlikely to ever lose.
If you are unlucky on that rare disconnect you have on such a pool, and lose more than expected, it's a loss that you are unlikely to ever recover.

Thus why the 5Nd here is really the best solution for miners.

Quick question....

Had a S9 miner go down so I swapped another one in as soon as I could (about 8-10 hours down)

In order to avoid the ramp up, does the worker name have to be the same as the one that went down?

If it is not the same name, will I start the ramp ip procedure all over again for that miner?

Lets crack one open! 

Pecker

nice.
so my Pi Butler didn't fool me when he told me somethings wrong with my hashrate.

Kano...your system works like a swiss clockwork!
And of course you obviously too with these accurate timings
you wrote every single time something gets done.

great job!
thanks man!

I hope your plan with the giveaway will work soon!

What we do is wait until we build up a certain number payouts in one wallet and when the network fees are low (like now) send everything to a second wallet or a hardware wallet and manually set the fees low or with the lowest priority.  It can take a while to get confirmed but it does consolidate all of your payouts so your BTC will be ready to use with good fees in the future.

This all went as planned.
Disconnect was 23:30:01 UTC and miners starting reconnecting and mining at 23:35:17 UTC
Mine on!

Not to worry - and thank you for letting us know.  I too use it to get notified right away...  I would have been on top of it long before now if not traveling. 

I did decide to change the code so that when the new block is detected, I force the public block page (https://kano.is/index.php?k=blocks) to get read 10 seconds later.  That has the a lot of the details that would be interesting for all of us to have on an email / text alert including the price - and I am saving the number of shares submitted as it goes, so I will be able to come pretty close to the CDT (coin per day per Th/s) and BTC per Th value that will be paid to us.  Eventually you will be able to enter your costs  per miner and it will show your your profit / loss on the block.

I figured it was worth the few extra second delay to have the ability to get all this additional info.  I also am queuing emails up, so they are sent between the other processing jobs.  So if we end up having 10,000 people getting the immediate notifications, it could take a couple minutes before everyone gets them.

Yep, if you have multiple inputs in your wallet, now is the time to consolidate those into one....fees are SUPER LOW.

Just a reminder - this will be in about 45 minutes.

I went out for a smoke, came back in to a block. The kano.is page said 4m, took another 5m to get the notification from ckpool app for android, but still no issues. I did notice with the new update you need to hit the home button on your phone to keep the app running, if you hit the back button it exits the app. If you are having problems this may be your solution.

No worries at all, you offer a free service to the community. Please don't feel like that was frustration at you or your awesome notifications. Yours is (in my opinion) the quickest to notify me! I'm just glad it was an issue that could be brought to your attention. I was more frustrated at my luck assuming it was something on my end since both failed at the same time. What a coincidence!

Thanks again!

... and quite unexpectedly, the payout was confirmed only a few minutes after I sent it out.
Seems there's a lot space in the blocks at the moment, so low fee consolidation would be ideal to do now if anyone needs to.

Look at your Workers->Shift Graph to find out when the drop happened.
(Or Workers->Shifts to see just the numbers)
Most likely a miner problem - maybe needs a restart?
If there's a section of zero on the Shift Graph then most likely an internet problem.

Setting a withdraw amount hasn't been implemented yet.

What some do, is mine to a coinbase or cex.io wallet.

yay all my miners online now mining on kano.is
s1
s3
sp20
rockbox new 130ghz

old equipment but all helps the pool i hope lol

I'm using an Avalon 741.
Tested with slushpool gives me scoring hash rate of 7.xx Th/s after an hour which is the normal value.

Hi All,

I apologize in advance for a newbie question. As I understand, BTC transaction fee depends on the amount of data in the transaction. If one has many smaller incoming transactions, and then wants to send some (greater) amount of BTC to a new address, transaction fee may become quite high. On the other hand, the less incoming transactions are there, the "cheaper" it will be to send money elsewhere later on. Is that correct?

If so, is there a way to set a minimum payout threshold on this pool?  I read somewhere this feature was still in the "to-do" list of Kano. So I wonder if it was implemented at some point, or maybe there's some other way to do it? I just want to minimize transaction fees for payments I will make in the future.

Could be a plethora of issues as you'll find on many pages throughout.

Depends on what equipment you have first of all. I'm assuming you have maybe 2 S7's or something? If you have an asic it could be your controller, hash boards, power supply, cables, fan, heat, etc.

Would definitely need more info than that if you're looking to get any sort of a solid direction.