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

The block payment transactions were just sent.
There was a delay while I had to do some code updates.
Visit discord for more information

 Hi, from the last block that the pool found yesterday I have a reward for about 0.00015 BTC but I did not receive payment for it. Can you please tell me why?

he just went to bed about 40 mins ago so will have to wait till he is up and back online.

Yea just realised that. Been kicked twice now    I can see you guys in there but still waiting on the 10 min timer  


EDIT:-

Always kicks me before the timer runs out  If someone could point him in my direction that would be appreciated as I am assuming he doesn't really respond to PM's too often. Cheers.

Read the pinned msgs in the Discord kanopool channel on how to get a Miner role to help keep Discord from kicking you. Also once you are registered, bookmark the page. The invite link is just to get in to start there.

Yep just done that. Forgot I had Discord. Only downloaded it at the start of Covid Lockdown to do video chats with mates but never really got used to it. Just got to wait another 5 mins before posting the question. Cheers for the nudge in the right direction 

try to join the discord and ask Kano directly.

Because I have tried so many times to guess my old login, it says I need to "try again later". That was yesterday and still reads the same today 

Just reset your password on the web site.  You can also create another account if you like.  It's up to you.

Hi everyone. Looking to switch over to here when bitminter shuts at the end of the month. Im only a hobby miner with some gekkos (1.8Th) so wont be winning any prizes or blocks for my contribution lol.

I did mine here a couple of years ago when I had some bigger gear but im in the UK and electricity prices suck so had to scale down. What I wanted to know is whether my old account would still be stored in the system or would I need to create another one?  Can’t for the life of me remember my password but can provide email addresses. Thanks.

Sweet!

Can't wait to see my name on that list

BLOCK by Canaan!
Woot!

I've moved my reply here since it belongs here (as does Phil's ...)


The smallest blocks we've found were obviously those very shortly after another network block when the mempool was close to empty, but not empty.
There's always between 0 and 30 seconds of network time for more transactions to appear, so that's why it's VERY rare for work to be empty.

You are ignoring the CDF[Erl] and not applying any statistical results to your "really bad luck"
It isn't really bad luck, it's quite well within expected probabilities.

kano.is shows CDF[Erl] which states quite clearly how expected the results are:

Also note that the PAPPS% reward for the last 500 blocks (the worst CDF[Erl] value) is 99.68% PPS

Not really.

Assuming 5ND was kept instead of changed to 3 days in Jan:

Say you had 54TH mining end of Feb, and turned them off March 1st, ramp down time was around 146 days in Jan, it would have been more in March, but for arguments sake lets keep it the same.

Block was found on 2th May, which is 81 days after you turned off your miners. So by then you would have ramped down by at least 55% or roughly 24TH.

Pool N avg was 7.45PH when the block was found and the block was worth 8.31423879 BTC

So your pool reward percentage would have been 0.024/7.45*100 which equals 0.322147651%

That's 8.31423879 x 0.322147651% or 0.026784125 BTC

BTC price was aprox $9750 so the most you could have lost was pretty much $261

If you would have kept mining the entire time after the switch to 3 days you would have made 0.05356825 or around $522 when the block was found in May

Well, if you mean illegal firmware violating the cgminer license, put out by hackers on this forum who charge ridiculous fees ...
why would I be happy about supporting people using that?
Of course not.

As for rentals, or that 'other' legal firmware,
that's part of the reason why it's not ready yet ... though that part is complete, but requires the rest of the solo code to be complete of course.

The new system completely automatically disconnects and bans miners when they connect, and can also ban their IP permanently.
Some of the banning in the past was automatic and some required me to trigger it manually when I checked things.
The new one is fully automatic, but it doesn't replace the old one, just adds another method to do it.

It also has an option in those rules to allow solo users for some of the rules.
If you want to risk using some rental source, it will allow you to do that for some rental sources on solo.

It also means I am able to more easily detect issues related to where different types of mining are coming from and what they are using.
i.e. KDB now includes reports of it immediately upon request.

CPU/GPU will always be banned since they are a waste of any pool's resources, and you'd require millions of them to match a single miner ...
Edit: even a tiny NewPac USB miner is over 1000 times faster than a CPU and over 100 times faster than a GPU

Edit2: the next update also includes the correction of the pool block difficulties, since the pool has now got so small.
Using the TotalDiff/NetworkDiff is incorrect.
While in the past, we were a much larger pool, and this made negligible difference and on only a very few blocks that crossed difficulty boundaries, over the past year this has been clearly incorrect and noticeable (like all the other small pools has for years ...)
With the update, blocks in the last year will be updated also, and the new code (in testing) already handles this correctly.
It is actually a major issue in calculating the value correctly also even using the largest language double value available in C, due to lack of precision.
Using a running total also gives rise to incorrect values, however, as has always been the case here, KDB shows an estimate first when the block is found, but re-calculates it with an update. The new estimate is calculated correctly but contains the small running precision issue, that gets larger as the number of shares increases, however the re-calculation resolves that by grouping results within shifts, within difficulty ranges, before doing the calculation.

Are you lifting the firmware restrictions to solo miners?

Hey Diesel,
Yes, all of us long-term kanopool miners lost months of shares when the N (number of shares) changed from 5Nd (5 times current network diff) to just 3 days some time back.  Kano explained why, and with your miners off you lost all your shares after 3 days once that change happened.
Bummer, but it is the way if a smaller pool is to survive.

I've had a few PM questions about this, so I'll post it here (again) and reply with this link if anyone else asks:

Firstly, this is a PPLNS pool.
It means that every time we find a block, the reward is distributed to all shares in the last N

However, as discussed extensively back in January in Discord and a little in here also, from January, I changed the N to be 3 days.

In the past the pool N was 5Nd which was 5 times the network difficulty.
Alas, with a (now) small pool, no one would get their expected reward for something close to a year when they join.
Which no one in their right mind would do that.

As I stated many times, this change affects negatively (very quickly) those who stop mining or leave the pool.
Solution: don't do that

P.S. this of course also means that the badly named and misunderstood 'ramp up' is also only 3 days.
Get back in and you'll be back to expecting full reward per block in only 3 days.

lol i dont think he thinks you are, more like looking for a way to show that you are not. like proof - rather than taking your word. he may not have history with you to yet trust you. I think those that do have history though do trust you - especially with no empty blocks and no blocks lost.

I have lost blocks on other pools but never here.

Discussion when it's finished and ready, I'm really only replying since someone seems to think I'm trying to rip people off