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

Network:     55m 1s (501394)  WOW, a 55 minute block and counting.

Edit: 60 minutes and still going.

So Interesting fun fact.  My new S9's some have firmware from July, while others have firmware from Nov 17, and a version like S9_V2.54   But on their website, they only have the newest from Aug 15..  Now Why would they not have the newest one on there?  I had an issue with the first S9 I got like a month ago, with fan speed ramping constantly, the firmware fixed that so it stayed on more consistent.  So Now I am baffled if I should overwrite the Nov 17 with the Aug 15 that had better fan control.

Any opinions?

in the stats Kano - "shifts"

what does "Inv Diff" actually mean?  and why would I get some zeros here while actively mining?

Thanks - usukan

Isn't bitpay what newegg uses? They gave me some kind of BS message about my wallet not being configured correctly, when I chose to send a 26 dollar tran fee rather than whatever larger tran fee the wallet had setup for. The transaction still went through, they just whined about it. If I recall correctly credit cards charge about a 4% fee for transactions. I think anything over 2% for bitcoin it too large. I also notice they hide the percentage so it is not easy to see. I examine the sending of a payment when the wallet finally gives me what it plans to use as a tran fee and check it against the dollar value of bitcoin at the time. I hate smoke and mirrors when it comes to my money.

And don't forget the website has a help section that explains concisely how it works.

Don't forget to bust a move for a minute, too

Welcome, read the thread, lots of good info on 5ND, payouts and how the pool works. You found the best bitcoin mining pool available.

Just started mining with Kano pool

Come On Block. Come on Luck, you 50/50 coin toss flip flop gorgeous jewel of an Anime Goddess that you are. A ribeye steak was sacrificed about 30 minutes ago for the good of the order and in the name of Lady Luck. Mine On with Kano-San, the operator of the best Bitcoin Pool on earth.

I use Bitpay, and the new "protocol" works okay for me.  Actually works better.

The old way, it could sit there for 15 minutes when I "charge" it, and then expire, despite my payment being sent within the first minute.  (On the flipside, this forced me to learn how to "double spend" transactions.)

The new way, it may still say it expires, but it accepts it anyhow apparently because of the "payment protocol".  I guess the "invoice" front end hasn't been updated to match the back end.

Also, both ways I can pick my transaction fees.  And, like you, in both cases it says the tx fees are too low and it's because of a problem with my wallet.  Front end problem?

I think they are extremely overwhelmed.  I've opened a few tickets with them, and so far they've only responded once, and it was a good few weeks afterwards.  Unfortunately it was the typical corporate "I have no idea what you're talking about but I'll pretend I do and give you a canned answer" response that was rather useless.

M

Don't cross Kano-san!

Not sure how many people ever use BitPay to pay for anything, but they're landed themselves on my ban list ... well I guess you could say that they put themselves there, I can't use BitPay at the moment and probably wont want to ever again

It seems they no longer allow Bitcoin payments to an address, they require you to use a "Bitcoin Payment Protocol" (that's supposedly in core 0.15 but not in 0.14) that also decides your transaction fees for you ... hmm.

Every time I make payments I choose my fees, and every time I've used BitPay, it has said my fees were too low, even when my payments were picked up in the very next block on the network ...

The NL node just had a short complete network outage.
All connections to NL will have failed over to your 2nd pool listed in your miner.
The network is back up again (less than a minute later) so all is OK again there.
Mine on!

--

... and a little aside about mining fees.
They're around 6-7BTC per 10 minute block at the moment - so have stayed down below that 10BTC mark for a while now.

It's actually an extremely fair process.  There's no reason why someone should be able to join at the tail end of a 3 day block and get paid the same amount as all the miners that were mining that entire 3 days.

M

... and just to clarify a few things about the 'ramp'

It isn't expected to reduce your rewards if you do hop.
The 'ramp' is simply a side effect of spreading out your rewards over a longer period of time - in our case 5Nd - to reduce your reward variance - and of course stop pool hopping from taking expected rewards from long term miners - that's what the PPLNS payout does (that many pools use)
You can hop in and get lucky and you can hop in and get unlucky - it's random and COMPLETELY outside anyone's control.
The length of the 5Nd however makes the variance of the 'hop luck' expected to be much lower.
A pool with a smaller N will have much higher variance in the 'hop luck'.

Lastly, I can't just go and reduce the 5Nd with no effect.
The effect of changing it a lot would be to the advantage of all miners who haven't 'ramped up' and thus to the detriment of all miners who have 'ramped up'.

Once again, KANO-SAN The Subject Matter Expert Speaks and this Grasshopper listens with both ears. Thanks.

Heh, sounds like Bitmain is worried about Canaan and sending out the hardware they have rather than keeping it

Glad to see you got some early!

An orphan occurs when the pool is slow to send out the blocks it finds or another pool found a block at the same time.

The Fibre Relay is the biggest help in reducing orphans.
Though for some unknown reason, no pools pay for it except me, according to the person who runs it
(and I pay about half what he expects since we are clearly a lot smaller than the large pools that use it)

However, there's 2 classifications for 'orphans' due to the 2 reasons why they can occur:

1) Normal Orphan - when 2 pools find a block at the same time and neither pool sees the other pool's block before their own.
 The internet isn't perfect so data can take time to get around it.

2) Stale - when we get a block late, 'after' another pool gets a block.
 This is due to a miner sending a block late to the pool, after the pool has switched to new work on a new block height.
 When this happens, most pools don't tell you about them, or to be correct, you will probably find that no pool tells you about them other than pools using my database code.
 They represent a block that should not exist - but since the pool code will (now) switch to it, we try to confirm it ourselves, so if we get lucky and get a double block, then we will keep the stale and switch the network over to it instead.

Stales don't count as orphans since they shouldn't exist - but there's still the (small) chance we might confirm it anyway

Congrats Gopher! Lets see the blocks roll in

Grats!  We could use it.

M

OFFICIAL ANNOUNCEMENT:

Gopher is up to 70 TH/s   4x 13.5TH and 1 x 14 TH And they do just a wee bit more, making it 70 TH ish  :-)    Jan 21-30 Delivery came EARLY!!! YEAH!