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

You get rewarded for all shares in the last 5Nd that you submitted, even if you were offline when block is found (see workers shift graph to see)

I read somewhere in a forum that, if my Miner is offline when a block is found (or, is it when the reward is distributed?), I will not share in the block reward. 

Is that correct?

I understand that when a block is found, the block reward is shared among the last N shares that miners sent to the pool, up to when the block was found.


But what if, during the shift in which the block was found, I was absent from the pool? (however, I was present for all previous shifts back out over 5Nd).


Put another way: Is it OK for me to take my miner offline for an hour?  Or, could doing so cost me if a block is found during that hour?

Sounds good. I’m back in.

Been having more network problems on and off with the Silicon Valley half of stratum.kano.is
As long as your 2nd pool listed on your miner is some other node (e.g. nya.kano.is) your mining should be unaffected.
The network issues are very random so you may not be affected by them, but if you do failover, that's why.

There will be a DB restart in about 30 minutes, around 12:30 UTC
It will actually be when the zekken shift completes and is processed - which will be about then.

No mining will be affected at all.

The web site and API will reply with lotsa zeros and '?' marks during a DB restart, for about 10 minutes.

This is a minor update to try and deal with the timeouts that occur every once in a while - and I'll now mention the actual cause since I've implemented a way to deal with them
The rewards and payouts pages go back to when the pool started for some miners.
The data back then gets swapped out of ram and sometimes when a long term miner checks their rewards and payouts, it takes too long to swap back into ram and times out on the web page.
I think the actual cause is if two different people do it at the same time - which would also explain why it's not very common.
This change helps stop that data from ever swapping out, since the DB now runs with a RES footprint smaller than bitcoin and a VIRT size smaller than ckpool, it's OK to stop that data from being swapped out.

I'll post again once the DB restart has completed.

Well it doesn't matter when you first connect.

It takes a few hours for a miner to show a close approximation of their hash rate in the "Hash Rate" field.

The point of the "Share Rate" field is to get immediate feedback that the miner is working ok and submitting shares, and to show what that is when converted to a "Share Rate", but it also fluctuates a lot.

You really have to just let it go for a few hours and see what the "Hash Rate" settles down to.

Thanks! I’ll switch over. Can you tell me what a normal share rate range is for a single S9?

Just look at the Workers->Workers page when you first start mining.
It updates immediately whenever you send a share.
You can see the share count going up, ignore the hash rate on the right when you first start until you've mined for at least 10 minutes, but look at the "Share Rate" to see if those shares are counting.

They're not listed due to my dislike of how the node code is implemented in ckpool - it's built upon the fallacy that the internet is perfect, which of course is stupid to assume that.

I started work on the distributed KanoDB code at the start of the year, which replaces the current node setup, spent about 5 months, on and off, working on it and got it to the stage where all the major rewriting is done (about 20% of the code had to be rewritten) and that's already running live, but the actual distribution of the data isn't done yet and the testing of the new block based shifts isn't done so that part of the code isn't activated yet.

Alas, other more critical changes have come up and pushed completing that down in the TODO list:
i.e. the full share checking/block submission code in the DB that's completed and live, and the accounting/payout changes I'm working on.
Once that's complete, I'll get back to doing the distribution code, and then my annoyance with the dodgy node code will no longer be an issue since the nodes will be a sub-pools and not need the node code for mining, any mode.

... THEN I'll list them all in on the web site and in the first post etc.
For now, they are actually listed in the thread title, but indirectly

kano, may i make a humble suggestion of adding all the nodes to the first post so others have a chance to add them appropriately?

Been having more network problems on and off with the Silicon Valley half of stratum.kano.is
As long as your 2nd pool listed on your miner is some other node (e.g. nya.kano.is) your mining should be unaffected.
The network issues are very random so you may not be affected by them, but if you do failover, that's why.

New guy here. I really want to join Kano but I’m not too sure about a couple things. Wondering if someone here could help me. First, I have a single antminer S9. The firmware on it seems to work well with antpool, but not work well on slush. Slush requires cgminer and I could not figure out how to update my S9 to cgminer fw. So for now I’m on antpool because it clearly shows me that everything is working.

I joined Kano for about 20 min earlier tonight and I didn’t know what to look for to make sure everything was working correctly. My anminer showed a rejected count at one point. So can someone first tell me if my S9 with default firmware from bitmain will work on Kano? And then what do I look for to make sure my miner is contributing properly once I mine to Kano? Is it worth mining to Kano with a single S9?

Thanks in advance!

New guy here. I really want to join Kano but I’m not too sure about a couple things. Wondering if someone here could help me. First, I have a single antminer S9. The firmware on it seems to work well with antpool, but not work well on slush. Slush requires cgminer and I could not figure out how to update my S9 to cgminer fw. So for now I’m on antpool because it clearly shows me that everything is working.

I joined Kano for about 20 min earlier tonight and I didn’t know what to look for to make sure everything was working correctly. My anminer showed a rejected count at one point. So can someone first tell me if my S9 with default firmware from bitmain will work on Kano? And then what do I look for to make sure my miner is contributing properly once I mine to Kano? Is it worth mining to Kano with a single S9?

Thanks in advance!

Difficulty has 2 ways to look at it.

The Network Difficulty value increases as it gets harder to find a block.
However, that is to simplify what it really is, and make it easier for people to understand it.

A block hash (498508) looks like this:
0000 0000 0000 0000 001c711eaa8898f83d737d5941a1c13a3bc0822a84906f0e
The required difficulty is 0x1800b0ed = 1,590,896,927,258.1 = 1.59*10^12

Out first ever block (325306) looks like this:
0000 0000 0000 0000 0c061098cb88b86cd48b9e7a6644c4ec26af471dcc779be4
It has fewer zeros, thus it is a larger number
The network difficulty was 0x181f6973 = 3,500,2482,026.1 = 3.50*10^9
A much smaller number, yet the block hash is a larger number.

So what all this means is, if you return a share with a difficulty that isn't good enough, it's actually "High" not "Low"
So under "Invalids" it says "Hi" - these are shares that should not have been sent since they didn't meet the difficulty requirements.
Although their difficulty 'number' was below the difficulty required by the pool, their difficulty value was "High".
e.g. if the pool says to send share with difficulty 8192 but you send lots of shares with difficulty 512, they will of course be rejected, but in the stats, listed under "Hi"

Hello, "ramping up" means how long it takes to reach full payout for blocks.  The length of the period is determined by the current block difficulty and pool hashrate.  Right now I'm pretty sure the period is pretty long --- someone else here can opine on that.

"ramping up" has its upsides and downside.  

The obvious downside is how long it takes to reach full payout.

The upsides are, if you have a power outage, or have to power off your equipment, you'll still get paid if a block is found during that period.  Obviously it won't be full 100%, but it'll be pretty close.

Another upside is, if/when you decide to leave the pool, you "ramp down", such that any blocks found during that period you still get paid for, based on how far through the "ramp down" you are.

Every legit pool has this type of thing, usually implemented in slightly different forms.  The net result is the same, and it's largely to dissuade "pool hoppers" from taking advantage of the pool.  In other words, someone can't join the pool at the tail end end of a 5 day block, for an hour, and get paid the same as someone who's been mining there the full 5 days.

One upside to this pool is that, in the long run, you will probably get paid better.  The flipside is, because it's a small pool, there will be times when payouts are scarce because of variance.  For example, right now it's been almost 5 days since a block was found.

One downside to the pool is you can't configure a payout threshold.  Since transaction fees are high, and it's based on the number of transactions you are paying from, that can be painful and expensive to pay.

One upside is the pool op, Kano, is 100% transparent about what's going on.  To the point that he'll make your eyes glaze over with details about why something is the way it is.

M