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

I have a pretty low hashrate, but the only dust I collected here was during the month or so I had kano as a backup pool and was mining slush. I didnt even realize it existed until I began considering a move over here and saw it. No dust since making the move.

If you're concerned about that, set a lower diff in Workers>Management.

It takes about 500GHs to be out of dust territory, so a couple/five S3's should do well.

No. After 3 shares it switches down.
The shares you find at 4098 will be rewarded accordingly and get what you'd expect.
There's no expected loss.

Also the pool wasn't 4098 for the past year.

I've no idea who put these silly ideas into your head, but I'd suggest you ignore them next time.

Edit: though there does seem to be another complete misunderstanding there also:
Miners find shares ranging from 1 diff to well beyond the value required for a block.
Shares are just showing what work you have done.
A 300GH/s miner will find shares in that range also.
If the pool is asking for 10,000 Diff shares, then that means, on average, one in 10,000 of the 1 Diff shares your miner finds (internally) will be over that value.
So your amount of work will be recorded for each of those 10,000+ Diff shares you find - which is the same as getting rewarded for 10,000 shares of 1 Diff.
The only difference is share variance, which is minor at best even at 500GHs - but the pool will never allow 1 Diff shares due to the risk of someone accidentally or purposefully DDoSing the pool with shares.
Share finding is EXACTLY the same as block finding, with CDF probabilities and luck - it's just a lot 'easier' to find a (low diff) share than to find a block.

"Hi" means the share hash has high - which means the difficulty value was low.
I posted an explanation of "hi" vs "low" before, so I wont repeat that, but basically your miner sent a bunch of shares with the difficulty below what the pool asked for.
e.g. if the pool says send me 4098 diff shares and your miner sends 410 diff shares, then they are "hi" and rejected.

[/quote]

My S3's mine LSDiff average around 360-450 mark I have not seen it ever high like 4098,

So would my shares just be rejected?

I've got one S3 and a half-dozen sticks pointed here. They get paid.   

Good news - more hash is in the mail!

Based on what misunderstanding is that?

I don't think my small hashrate would make much here I have 5 s3's running almost year solo still no luck yet.
If I understand my low diff shares would not be viable here? would be dust?

Ignore them - they're just display of data that was available and I never got them to do anything, since the voltage didn't actually change on my S3.
If the miner is returning 0 and it's also working, then that's what it is
Maybe you should mine here also ...

I updated some old miners with the kano firmware in the status bar it says

RegData   
0x08820000
Voltage   
0x0000

Should the voltage value be 0x0000?

Kano, thanks that makes sense. There is not much hash there, and I am not worried about it, just wanted to understand what caused it. Thank you for the explanation.

Will continue to mine on!

"Hi" means the share hash has high - which means the difficulty value was low.
I posted an explanation of "hi" vs "low" before, so I wont repeat that, but basically your miner sent a bunch of shares with the difficulty below what the pool asked for.
e.g. if the pool says send me 4098 diff shares and your miner sends 410 diff shares, then they are "hi" and rejected.

Firstly, it makes no difference to your reward, since e.g. on average one in every 10 of your 410 diff shares would be above 4098 so you expect to get the same reward.

Secondly, you'd need to check both numbers under "hi" to make proper sense of it.
You probably sent a whole bunch of low diff shares when your miner connected, but the value of those shares probably doesn't add up to much.
The "hi" value will say V/N where V = total value of the shares and N = the number of shares.
As always, it's the value V that actually matters, but if you are sending truck loads of them (high N) then it's probably Bitmain strikes again
Although Bitmain can build miners, their programmers are crap.

Cannan on the other hand Well their top guy setup the OpenWrt OS and wrote the web interface in the first Avalon miner that Bitmain copied directly into their first S1 miner.
He also wrote the first version of the Icarus and Avalon driver in cgminer.
Avalon also had the first ASIC miner - so yeah there are a few more reasons why I think Canaan is better than Bitmain.
Pity their prices were/are high - that's a strike against them IMO - market forces ... the force of many sheeple Hopefully it will go back down ...
Though they did the same with the first Avalon miner ... so it's not unexpected ... and I trashed them back then also

You will not lose all of your ramp it will just go down while your rig is not running. So if it takes 45 minutes with it down you should be back to about the same place with 45 minutes of running. If we hit a block while it is down you still get a payment based on your ramp at that time.

You do not have to be fully ramped in order to get payments. Where ever you are on the ramp you get credit for that amount of hash when payments are made. You just don't get full payments until you are fully ramped.

Hi team,
I plan to clean my S9 from stickies, Im going to detach the 3 hashboards to do so. My machine will be off for 35 - 45 minutes I guess. Will this will affect ramp-up process or I will start again from beginning?. BTW I've got my payment from last 2 block appx 0.001007 and 0.001033 after running the machine 4 or 5 days. Actually Im not expecting this payment since I'm not fully ramp-up 13.5 days. Still confuse wkwkwk....

Ok the talk about stales a bit earlier in this thread reminded me I wanted to ask about the invalids that are in the Hi column. What causes an invalid Hi? I am only running 0.106% on invalids. most being stale but have about 25% of them that are Hi. I probably should know and may have at one time but don't remember now and cannot find anything on it.

That’s great. Glad you got it figured out.

Well I think we've figured out the problem (thanks to all of you!)

I switched the problemchild S9 to a different power supply and runs prefect...

Put the other S9 that had been running good on the bad power supply and it makes that miner speed up and slow down like crazy...

Freakin Bitmain power supply...  Pretty sure I bought it brand new a few months ago!

Ordering another one today...

Thanks everyone for the help...

Pecker!

These miners are a case by case basis too. I have some machines that are overclocked and have not had one problem and others I have to turn the frequency down a bit and set a min fan % to keep them cool or they will lose hash boards. Dust and debris will hinder the units from dissipating heat and heat seems to be the big threat to these. I don't know if the S9's have the same problems as the S7's but if the heat sink is loose, it will not pull heat from the boards so the fans can move that air. If you are having hash problems as well, then you have other issues beyond the fan, though I've swapped for higher rpm fans and have remedied some heat issues. That or turn down the frequency and see what difference, if any, you see. It could have a weak power supply too, but you won't know until you can do more diagnostics.

Order an 821, or wait a bit for the 841. I gave up on Bitmain quite some time ago.

Yeah something like that is on the todo list - I mentioned in the dark reaches of the past pages
https://bitcointalksearch.org/topic/m.29277298

The 5Nd point isn't a simple calculation, it can change every millisecond, and takes a couple of seconds to determine.
Instead I'll have the system keep track of the last 5Nd point based on the last complete shift.
Thus it will be (in)accurate within, on average, about 25 minutes - which should be close enough.

thank you will consider an s9 then or shall i wait till maybe something newer comes out?