KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2437 blocks

[kano]

That looks ok to me.
Mining on cksolo and mining here will work the same.
So ... obviously your settings you are using would help to diagnose it

--

Payout 381753 sent
314bb702e9145bf0f1c818161bad5d13c74741036cea57c0413cd4f6a95b429a
and confirmed

[omega015]

That looks ok to me.
Mining on cksolo and mining here will work the same.
So ... obviously your settings you are using would help to diagnose it

--

Payout 381753 sent
314bb702e9145bf0f1c818161bad5d13c74741036cea57c0413cd4f6a95b429a
and confirmed

Pool 1: stratum+tcp://stratum.kano.is:80
Pool1 worker: 18gwf9rn3FMz7ujmabgqjYfCs5aaDBrHki ( and tried adding _06 for the worker)
Pool1 password: <blank> (also tried 123)

I have tried port 3333, 443, 80 but none seem to start mining on that pool.

This is from the system log on a reboot from earlier in the day is this helps?

Tue Nov  3 09:12:08 2015 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum+tcp://stratum.kano.is:80 -O 18gwf9rn3FMz7ujmabgqjYfCs5aaDBrHki_06:123 -o stratum+tcp://zstratum.antpool.com:443 -O xxxxxxx:123 --api-listen --api-network

The z in front of stratum is to make the antpool pool dead so it wouldn't mine there and my settings remains (I am doing this on other miners without issue). Do you want any other information or me to try anything in particular?

Thanks.

[kano]

As per the front page of the web site

stratum+tcp://stratum80.kano.is:80

There's a different name for each port, and the current IP values of all the others doesn't match stratum.kano.is

... though you can also use stratum+tcp://stratum80.kano.space:80

[omega015]

As per the front page of the web site

stratum+tcp://stratum80.kano.is:80

There's a different name for each port, and the current IP values of all the others doesn't match stratum.kano.is

... though you can also use stratum+tcp://stratum80.kano.space:80

  oooops I just took note of the 3333 entry and only changed the port not the subdomain/dns. It also looked like I had to use a dummy password too.

If I followed the instructions for updating cgminer on the github should I be seeing a different version no.? In software I see: cgminer 3.12.0-1

Thanks again.

[kano]

The S1 needs a password in the password field
Yes it can be almost anything (except blank) for kano.is

cgminer itself will report the version of the binary in the API
The web interface doesn't actually use the API to report the version, it uses the installed package version, so since my update just swaps out the binary, it wont change what the web page reports.
When logged into the S1 you can cgminer-api version (Edit: fixed typo)

[omega015]

The S1 needs a password in the password field
Yes it can be almost anything (except blank) for kano.is

cgminer itself will report the version of the binary in the API
The web interface doesn't actually use the API to report the version, it uses the installed package version, so since my update just swaps out the binary, it wont change what the web page reports.
When logged into the S1 you can cgminer-api version (Edit: fixed typo)

Thanks, API is reporting the binary version 4.9.1c Got 1 miner pointed to the pool for a test, and then will be looking to move the rest of them over if it works out. I've not mined on a PPLNS pool before.

[kano]

Well ... ignoring the terrible luck of the 10 blocks in October ... the expected payout is around 99% depending on tx fees.
Even with that bad luck, the long term luck of the pool is still above 100% ... just

We don't find as many blocks as the big pools, so the payouts have greater variance and are less often, but the amount is expected to still average 99% PPS long term.
Short term is very much in the hands of luck and the Block Gods.

Don't forget to read the Help->Payouts web page that explains about the PPLNS 5Nd

[o_solo_miner]

  I've been reading every Evening to forcast, and never be correct... 
never Mind, I trust you in almost everything, whats related to the Payout!

[LoneRangir]

Short term is very much in the hands of luck and the Block Gods.

Short term is very much in the hands of luck and the Block Gods Rubber Chickens.

[gecox22]

I cant believe bitcoin is up to 445. Any one know why the price spike? Think this will have an affect on how many blocks we find since more miner will be turning back on their gear?

[kano]

Diff (and luck) decide

Diff goes up (and hash rate doesn't) means fewer average expected blocks per time frame.

[PPOC]

I cant believe bitcoin is up to 445. Any one know why the price spike? Think this will have an affect on how many blocks we find since more miner will be turning back on their gear?

Many theories, I like the capital controls in China and people using BTC to move money out of China since govt imposed a 50k USD limit. But who knows. At this price and growing the diff increase will be 8-10 percent per adjustment till all new hash is figured in. Old turned back on and ramped up production of new. Bitmain alone is putting about 2.5ph online weekly via HW sales and hashnest sales. This price keeps up and 30 days from now we will have 600ph network

[omega015]

Quick question for the group.... My discarded share # seems to be through the roof (2,362,444), is there something wrong with my miner (Antminer S1) or is it simply weak compared to the rest of the pools miners? If I add more of the S1 to this pool will it be pointless?

Or do discarded shares simply not matter and its other numbers that do? Still learning about mining here  

Thanks,

Michael.


Elapsed: 1d 1h 45m 42s
GH/S(5s):178.52   GH/S(avg): 179.14
FoundBlocks: 0   
Getworks: 3,575   
Accepted: 19,767   
Rejected: 18
HW: 0   
Utility: 12   
Discarded: 2,362,444   
Stale: 0   
LocalWork: 4,684,393
WU: 2,502           
DiffA: 3,886,176           
DiffR: 3,528       
DiffS: 0   
BestShare: 5,690,648

[o_solo_miner]

Quick question for the group.... My discarded share # seems to be through the roof (2,362,444), is there something wrong with my miner (Antminer S1) or is it simply weak compared to the rest of the pools miners? If I add more of the S1 to this pool will it be pointless?

Or do discarded shares simply not matter and its other numbers that do? Still learning about mining here 

Thanks,

Michael.


Elapsed: 1d 1h 45m 42s
GH/S(5s):178.52   GH/S(avg): 179.14
FoundBlocks: 0   
Getworks: 3,575   
Accepted: 19,767   
Rejected: 18
HW: 0   
Utility: 12   
Discarded: 2,362,444   
Stale: 0   
LocalWork: 4,684,393
WU: 2,502          
DiffA: 3,886,176          
DiffR: 3,528        
DiffS: 0   
BestShare: 5,690,648

Don't worry, everything is fine.
The Accepted Value is the important one and that looks ok.
The Discarded Value is the number of calculations wich are not in the hight to be transferd, this is normal.

[omega015]

Don't worry, everything is fine.
The Accepted Value is the important one and that looks ok.
The Discarded Value is the number of calculations wich are not in the hight to be transferd, this is normal.

Thanks for confirming, hopefully will be getting some more of my rig online this week

[kano]

Discarded, as I've mentioned elsewhere recently , has nothing to do with shares.
I removed it from my version of the S3 display.

[elduderino]

By the way, folks: Block! 

[gupik65]

Kano tell what you need to put the difficulty for Ant S1 on your pool that would be fewer errors, for example 128, which would not hurt the pool

[kano]

Kano tell what you need to put the difficulty for Ant S1 on your pool that would be fewer errors, for example 128, which would not hurt the pool

It will currently drop down as low as 42 - just no lower.
It starts at 1042 if you don't set the start.

You can set it on the Workers->Management web page to 128 if you want that.

The ONLY difference the diff makes is variance, it wont cause more or less errors.

128 is a bad choice since it's a power of 2 and some of the bitmain firmware don't record the best share if work diff is a power of 2.

[o_solo_miner]

It will currently drop down as low as 42 - just no lower.

  As allways the Answer is 42 

That seem' s to be affecting our live also in the bitcoin world.