 Show Posts
|
|
Pages: « 1 [2] 3 »
|
Great to see us back to "normal". I like the biggish payments these days  Will the gone hashpower come back in a while kano? Thanks and MINE ON! Well I'm still processing 60 days of data (it's completed more than 21 days and 35 blocks from the start of September) Once I complete that I'll report the results here (and to the large miners that left) and I guess we'll see if they come back or not. I'm also going to have a zero-fee month coming soon to see if that will bring on board more miners. More miners means less variance - and that's what's been the aim this year. Seems like bad luck popped it's head up and destroyed that idea  The fact that we already have less than half the fees of slush seems to not bother anyone mining there, so the only way I can lower that is to temporarily have no fees Obviously I'll announce things when they are ready ... I read about the data processing. And I am a bit impressed that even in this situation you have a real concept for going through this and checking every possible thing and make it transparent to the community!! I really appreciate this! Very cool and very reliable! I can't imagine why we're not getting much more miners in our game. Your plan with the zero fee month sounds good. But maybe the problem is that the only way to get more miners here is to move them from another pool. That's very difficult if the other pools are running fine. Maybe you should do a bit more advertisement.  A bright shiny website in front with some pool facts or FAQ etc. maybe will bring some miners too. For Login and config is the actual website absolutly fine and very straight. But you know... it's all about the look and feel when a prospective new miner enters the website. Another fact is that I searched last few days where i possibly could buy another miner (in germany or without getting trouble with duty or so). But seems all sellers are out of stock. On ebay it's too expensive. So adding hashpower by ourselfs is even if you have space left a difficult job. |
|
|
|
Great to see us back to "normal". I like the biggish payments these days Will the gone hashpower come back in a while kano? Thanks and MINE ON! |
|
|
|
Like I said. Just playing around with my half knowledge. So 0.6% "stale" shares are pretty low, if I remember earlier postings here. Okay. About your Log analysis...this sounds really horrible work to do. I hope it's worth it and you'll find anything interesting or helpful. Thanks for all this! |
|
|
|
|
I'm wondering what is the actual status of our luck or block finding "problem"?
Did you find something particular while doing your research?
Or are we officially back to normal?
Sorry about spreading half knowledge, but was our stale block last time a "problem" of latencies in any kind of way?
COME ON BLOCKS!!!
|
|
|
|
Nice hack!! Much easier than changing the /config/bmminer.conf over ssh Is there also a way to control the fanspeed manually?? |
|
|
|
Great! You:'re the man! Thanks kanosan Now crackin a block would be nice |
|
|
|
|
Will a interval of 30 mins be okay?
Or one hour?
|
|
|
|
|
Question about kano.is
Is it possible to just get the time when we found the last block
by wget Or something similar?
Nothing else,just the time or the last block we found.
For example By adding something to the url
Thx
Mine on!
|
|
|
|
Kano; just a thought, could the problem have been a batch 1 S9? These were an issue last year.
There are still some S9v1s on the pool but obviously no where near as many as before. But yes, the S9v1 stats still have a CDF[Erl] over 0.99 In the last 3 months (27-Jul to 26-Oct) they've submitted just over 8 Blocks worth of shares but only found 5 blocks. Yep they continue to suck, but the luck in general over the last 3 months has been below expected for all miners as you can see in the monthly table. How do we know if we have an S9v1? auto tune is good. The older ones that allow for freq are s9v1. I moved mine last winter and only had Avalon here. I posted with philipma1957 a few days ago. Because I felt rentals were killing the pool. I am on a cell phone so I am using this account Was it a problem with the hardware or software with the S9v1? I'm having a. S9 which was delivered with autotune. I disabled the autotune over ssh and make it run with 400mhz for more silent working. |
|
|
|
I reeeeeeally like to see we got a block this night!! good night!! hopefully the god of blocks is well-disposed to kanopool after this many sacrificed chicks, cat, dogs and virgins ... COOOOMMEEE OOOOON BLOCKS!!! |
|
|
|
Question @kano:
Is the blockfinding in any way connected to the core client?
The only thing changed in the last few weeks is core update to 15.x. Isn't this right?
Okay beside the split.
Sorry for this unqualified Question. This just came to my mind cause I updated my node to 15.0.1.
Come ON BLOCKS!!!!
I'll answer that...no, Core doesn't affect finding blocks. It's your wallet, or if you're running a full node, you're helping process the mempool (the way I understand it). That's not mining. Anyway...I've been running a full node for a long time, and have been running 15.0.1 with no issues. Mine on! Sorry for not digging deeper into my question. I meant: Could it be "a problem" with the new 0.15 core (or maybe not just the core itself) or let's say the network ALL OVER THE WOLRD with probably more than 50% hosted in china!!?? Somehow the new block must be provided to the network (which is build by many many full node core hosts). So if we find a block or are about to find a block in a second and another pool in china is finding the "same" block and provides it to the chinese nodes because of the lower latency ( and which are probably more than 50% of the network) and they get their block committed in that second we find the "right" block, we even didn't get a chance to provide our block to the network or something like this. So my question is: Could we do anything, maybe by providing more full nodes in the western hemisphere, to get "more luck" or just an even playground for this? I think much of this stuff is also connected to low latencies (so it's also connected to how well the network is spread all over the world or near kanosan's server :-D ) Maybe I'm completely wrong but just for the protocol my 2 cents. Oh and never mind kano. I think you're doing a great job!!! I don't think there is anything wrong with your system. I know it's just bad bad luck actually. |
|
|
|
I'm 100% positive that like anyone else kano would like to see us get as many blocks as we can. More blocks means more btc for him out of his tiny .9% commission.
Do the math on the "tiny 0.9%" commission. 12.5 BTC * 5700 * 0.009. M EDIT: I'm not disagreeing with you... just pointing out tiny isn't so tiny anymore. Not really tiny in first place. But he also has to pay all the serverhosting, fibre connections for low latencies etc. Question @kano: Is the blockfinding in any way connected to the core client? The only thing changed in the last few weeks is core update to 15.x. Isn't this right? Okay beside the split. Sorry for this unqualified Question. This just came to my mind cause I updated my node to 15.0.1. Come ON BLOCKS!!!! |
|
|
|
did anybody write to --- for kicking this site?
Or doesn't this make any sense?
I mean the domain was created on 2017-06-30
so it's obvious that they steal the data and name from your pool kano.
Yep - I emailed them. Will it help, when some of us email them too? The more the better / faster shutdown from this scam site? |
|
|
|
did anybody write to abuse-contact@publicdomainregistry.com for kicking this site? Or doesn't this make any sense? I mean the domain was created on 2017-06-30 so it's obvious that they steal the data and name from your pool kano. |
|
|
|
The mining code is ckpool. For this update I've just done a few changes as mentioned above (and rolled forward to the current ckpool git ... that failed) Seems the node code can't handle a pool version update It may need a complete restart of everything. I'll do some node<->pool testing and work out what's up with that - I was more concerned about block code, and I tested that thoroughly - didn't expect a network protocol problem. Weird, coz some of the nodes are current code also. As I said ... more work to do  Everything else is my KanoDB That's the name for the updated closed source version - so no one has any wrong ideas about who wrote almost all of it The CKDB in the public ckpool git (that I got thrown out of) works fine for a single pool and can handle a few hundred PH - but has no support at all. A few pools use it: Ver's bitcoin.com did (no idea if they still do) BitClub does, so does LinuxJounal There's 1 other I know of but I wont mention their names since: they removed my copyright off the web site and replaced it with their own copyright ... scumbags Mine on Nice. Thanks for the input :-) I can't understand why some people are not having esteem for a programmer who build some serious cool code and share it with the rest of the world for free. So good luck the node<->pool testings. |
|
|
|
Updating suckz Hope you'll find the faulty codesnipped soon! Is there a posting somewhere out here where you explain how the pool is build up? Which programming language, which hardware you use etc...? No details about the code or hardware but maybe some infos about. I don't wanna build up a pool but i'm coding every now and than some stuff. So I'm a bit curious bout all this pool stuff.  You're doing a great job kano! I like the pool you build! Your avarage working time seems to be nearly 24/7/356 ...RESPECT! Don't waste your time with morons trying to annoy you.  I think you have to do much more important stuff. Mine ON guys. |
|
|
|
Short question: Can anybody post a link to a information page about this maybe upcoming bitcoin fork on 21st july? Or did you guys discuss this in earlier postings here? Will this affect mining on kano.is in any way? Or is it not worthy talking bout it? greetz |
|
|
|
|
Maybe you should put some new cooling paste onto your chips.
This dropped ym temps by 10°!
If your S5 still has its original colling paste on it, i think you should change it.
Cause after 2 or 3 years the paste isn't working well anymore.
Costs a bit of time and maybe 10-20€ for cooling paste but i think it's worth it.
And don't test the nf12 on the S9. They are way too weak for the S9 and will burn it!!
|
|
|
|
|
Hi guys,
i read about that the noctua NF-F12 are too weak for the S9. I have some on my S5 and the work like a charm!
So I try to figure out how I could get this S9 more silent.
I am thinking about taking 2 noctua nf-a14 industrialppc-3000 pwm and a fan adapter that downsizes from 140 to 120mm.
The nf-a14 industrialppc-3000 pwm has 269 CFM, so it should blow more air at 3000rpm as the original at 6000rpm with 210cfm.
What are you thinking bout this guys?
mine on!
|
|
|
|
Hi guys, i mine on kano since february. Great pool!! Thanks kano! Actually i have a little problem with my first bitcoin transaction ever. I didn't calculate the fee right. Sadly i set the fee to 10/B https://blockchain.info/de/tx/bdb7d17a41693b4a4de88917161f4bfc9a30cac1df9190b3265dd5a0bd6f2c69I read a lot of stuff about how to get the transaction confirmed anyway. But CPFP didn't work with my wallet. So is it possible to get my transaction into one of the next blocks from our pool? Of course i would pay another fee for it if it's necessary if there is a way to get the transaction confirmed. I just don't want to loose the BTCs i send cause i actually didn't get the trick how to get back my btc from this unconfirmed transaction. Thanks for your advise. Mine On! :-D This thread could be helpful to you: https://bitcointalk.org/index.php?topic=1802212.0Thank you wmabern. I tried most of this stuff. That's y I asked "a mine" to confirm my transaction Maybe I just had to be a bit more chilled about this cause now the transaction is confirmed or maybe SOMEBODY assisted a bit with it. But on http://bitcoinfees.21.co/ it looks like 10/B fee is way to small for getting confirmed, so I thought I ask here for help. :-) Thanks and whoooopwhooop I like this light shiny green!! Ordered a brand new S9 13,5TH. Hope I can fire it up till end of month. :-) |
|
|
|
|
