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

Thank you, and thank you!
W00t!

Payout 365224 sent
49d8a87a242689a544afb684591f9fb3534a3804040a2e8db4b7d921ae438486
and confirmed

Well cool, I look forward to the dust code getting put in some day.  I hope you consider adding a "donate dust to pool" option, I'd probably just do that.

My current <12GH/s usb sticks are just below the minimum payout, last 3 block rewards for their work has been 9400 9600 9500 satoshi.  Almost there... I'll just wait until I upgrade them this summer and then point them back.

There are several miners with less hash than even my sticks whose work is just accruing dust, wonder if they know/care?

Payout 365204 sent
cdd08c3de982710743d7a1c07b753f3199a5ece445f0eb1cf9e4524c76a420e0
and confirmed

Well it involves me writing some code to read a transaction in (well that's only a few lines) and then distribute the transaction to mark the payouts that have been paid - but the catch is I need to also deal with the change (sum of the dust) and the accounts that also mine to a non-account address thus have to be split in 2.
Not difficult, just still on the todo list of course, and other things keep popping up
The point of it is to have a balance (like it should already ...) so when the dust adds up to enough I can then add in some of the change and pay some of the higher than dust balances.

Dust limit is 10,000 satoshi

Payouts 365061 and 365089 sent
aaab398eae4b327ed5f0953d8de6080c312e32fd7a8234e38f51259f7c30a2fe
e40376c6691001bc65ce5974939ad0731c3cef57b5e296e73ea3b0e06a8c1e0d
and confirmed (a little while ago)

So it looks like my measly usb sticks do not hash enough for my block rewards to be more than dust, bummer.  Considering I'm not the lowest hash rate on the pool it makes me wonder what the other folk below me are doing.  If you're not generating enough hash to get over the payout threshold then it's wasted mining effort.  Back to the solo mine they go, until I can upgrade them here pretty soon.

What is the minimum payout the pool will pay?  Any plans to sweep up all the dust and do something with it?  I bet most users would just donate it to the pool.  As btc prices rises, even the dust will be worth something at some point, and right now my dust balance is around 0.0013 which isn't too insignificant.

: ) i meant worker Password! Sure you don't post the password of the account i didn't used while i mined that block. (as a worker password 123 works as good as x) ... i better don't explain why i asked that question ... will have to figure out that by my own.

Yes, regarding reading the code, that will have to be done, thats why i avoided more questions. Thanks

Password? Eh?
Fortunately my web site wont let you enter a password of "123"

It's an internal ID - I changed it.
Just like it says x.x.x.x for createinet

If you are curious what they all are ... read the code
https://bitcointalksearch.org/topic/ckpool-open-source-poolproxypassthroughredirectorlibrary-in-c-for-linux-790323

Well, back on with Hash Rate:150/131GHs OK, its not my 200/170, but its close, i missed the hum of fans at full speed :3

Ok, thanks for the Block info! And sorry for using the quote function wrong! I edit that later, don't like to make it worse right know : )

Last Question regarding this Block:

What tells me this:   "secondaryuserid":"123"   ... is that just random or this my password?

I think i won't find out anymore which worker it was. The Unix Time Stamp and the nonce isn't logged at the SP20's as far as i can see (only for the HW errors)
And at the S5 the log with the nonce is gone after reboots...
I think i won't waste more time on that ... it's enough that the Block was found ... better start understanding the software (cgminer)  : )

See you later...

Maybe if they double-up on chickens, we can hit 4 or 5 block's today 

Payout 365003 sent
d1c2cbef68f63c3d37aaa734fd3523115c7752b9ac0273f781b2678e9fcd65d1
and confirmed about half an hour ago

... and another block a bit over 3 hours ago

Firstly, please check/fix your quotes after you post a message - that's the 2nd time your quote shows me saying something I didn't.
Not a problem here, but I prefer quotes of my posts to match what I said ...

Your block info - after searching the logs ... ... ...

The share that found the block:
shares.43258248.json={"createdate":"1436416061,891007884","workinfoid":6168963369509326287,"workername":"1ALNASMpj75dnrM3BpquyU813VizXHH2CK",
"createcode":"parse_submit","diff":512.0,"clientid":30179,"sdiff":544219642640.01978,"enonce1":"8d069080","createby":"code",
"secondaryuserid":"123","errn":0,"nonce2":"208e030000000000","nonce":"7123e718","ntime":"559df7e5",
"hash":"0000000000000000020533553a45d8dc4d9ffe5613adb36fd50e5958471af23b","result":true,"createinet":"x.x.x.x",
"username":"1ALNASMpj75dnrM3BpquyU813VizXHH2CK","seqstart":1436323711,"seqall":43258248,"seqpid":22612,"seqshares":40726312}

The connection was:
[2015-07-09 13:54:07] Authorised client 30179 x.x.x.x worker 1ALNASMpj75dnrM3BpquyU813VizXHH2CK as user 1ALNASMpj75dnrM3BpquyU813VizXHH2CK

The auth useragent isn't logged in the history for that particular connection for that worker

They seem to still be doing it

Last 5 blocks 224.12% luck

Yea! Another one!

@ WBF1

My concern was not the good luck, also not the bad luck.

It was more the thought that the person who controlls the server is able to decide to ban, IP- adresses completly or temporarly. In that case, someone point 1 PH to the Pool, and the operator has the suspicion that the connection/s from this PH always interuppts when a block is found in the network. It would make sense to ban this one since he harms all other miners at the Pool.... not really my level of mining (i mean1 PH), but somehow iv'e read such thoughts "between the lines" of some posts here"...   But kano's statement that he will inform us before he (if ever) decide to do something like this is enough for me.

And regarding the Good luck / bad luck: No i also think that no one is able to controll that. But if you are willing to, and are able to point (let's say 1PH again) a massive amount of Hash to a 500% PPNLS Pool. Also didn't mined there before, and then in a timeframe of let's 120% you find 4 Blocks, and suddenly taking that hash away. You would have created very good "luck / payouts" for all that where at the pool the 380% before.
On the other side it's possible to run that kind of manipulation the other way round (i think...would have to create scenario : ) .

But that's not the point at this pool! Actually i often had the feeling that someone donates Block to all the longterm miners here .... whoever that may be : )

I posted was i have posted because i don't like mistrust araising ... i left Slush's pool while that is what, i think, happend there. You are fucked up because you think all disconnecting miners are assholes that hop for profit ... create the " Scoring System" ... what leds for some miners (my case) that they sometimes have nearly nothing payed out for one week mining between 12 and 18 hours a day.

Hope you understand know what i mean.

I'm not sure what you mean. If kano has a way to manipulate luck for this pool in a positive way, I'm all for it. Pretty sure he doesn't have that ability though, nor does anyone.

@ WBF1 ...  "Keep Doing"  sacrifice chickens or mining ; )  .... no for real, if i have a look at all the other pools i'm afraid where Bitcoin is going to! Just wanted to adress that i hope my feeling is still right and there is no manipulation here...