Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 481. (Read 1514749 times)

Heh, good luck 

Rest assured that if anyone finds a block, you'll all be informed here, though I'm sure you're all watching your wallets hopefully...

This is great, I pointed my s2 to it & am crossing my fingers!

You can leave it off for as long as you like. The bitcoin blockchain has a permanent record if money goes into your wallet. You just have to wait for your wallet to sync up when you turn the computer back on for it to realise it has been filled.

Hi, noob here so don't yell at me for asking a stupid question. You may laugh, but don't yell 

I am a non-tech, but very interested in bitcoins and the whole idea of it.

I am really happy that you provide a service to solo mine. I only know of 3 others and the only reason I am not using them is, that they don't reply back to my question.

Yes it might be a dumb question but I hope you will reply back anyway, so noobs like me can learn a little. (Noob everywhere I am taking this one for you guys!)

Errhmm.. so here it goes...

If I solo mine with you, with my knc jupiter, does my bitcoin-qt wallet on my desktop computer (where my bitcoin-adress is at) always be turned on? or can I just turn the desktop computer off, because the knc jupiter connects directly to your solo mining service?

Thank you in forward for your time and help.

Best regards,

The pool's looking nice and stable, so there shouldn't be any more restarts in the near future. We have over 70 clients connected now, though the total hashrate is not that much (but that's fine since the total pool hashrate does not have any effect on any one miner's chance of finding a block). At the moment the demand is not high, but it wouldn't be too much work to set up standalone nodes elsewhere in the world. This pool instance is currently located in LA.

I've just upgraded the relay network used by this pool as described here:
https://bitcointalksearch.org/topic/how-and-why-pools-and-all-miners-should-use-the-relay-network-766190

There will be another small blip for an update. The only thing you may notice is stats resetting. I've also added port 443 mining.

EDIT: Completed.

I have the tube pointed there now. Looks to be working fine.

Thanks for the response.

Default settings are usually best unless the manufacturer has modified them as in the S3 case.

Tubes of course don't work properly, so I've added another server instance especially for tubes at solo.ckpool.org:3334 . Try that, though your user statistics for that server won't be visible at the moment.

Should I change any of the scan, expiry, or queue settings? I am not getting any rejects on my Jupiter, but the queue is set to 9999.

Edit: Naturally, my freidcat tube will not work. They really gotta fix that stupid controller.

That's about right. Assuming no diff change, you will find a block on average every ~2 years with 2TH, though due to variance it could be in 1 second or it could be never. If you find a block, it's 25BTC in your wallet. If not, it's zero.

Playing with numbers I got to this. Having ~2Th/s will produce one block every 2 years assuming the difficulty doesn't change.

I can easily tell you the average number of blocks based on hashrate, but I can't offhand tell you the percentage chance of it being in either direction (OOC would be able to help you with this).  

Basically you need the current diff in hashes to find a block every 10 minutes. Which means you need the current diff / 600 in hashrate per second. The current diff is 27.4 billion. So you need 27,400,000,000(diff) * 2^32(noncerange) / 600(seconds) hashes per second to get a block every 10 minutes, or ~ 196PH. So then you scale accordingly to figure out how often your hashrate will on average find a block. 1/100th of 196PH will find a block every 10 * 100 minutes or every ~16.7hours.

Thank you for this pool ckolivas.

I would like to do some solo mining, but I need some help. Are you or organofcorti able to reply to this post of mine? https://bitcointalksearch.org/topic/m.8253623 I need to know some % of success before starting it.

There will be a brief interruption to your connections for a minor update. ckpool hands the socket connection over from a running instance to a new one so most likely you will only get the message that the stratum connection was interrupted but be reconnected immediately instead of failing over to a backup pool. If you are watching your miners, what you will see is your difficulty will reset itself to the starting difficulty of 1024. If your hashrate is very large you will see your diff increase very rapidly to a more suitable difficulty, while if you are on a slow miner, difficulty will slowly drop to your base difficulty level. Once again, I'll point out that with solo mining, the difficulty and share value is purely cosmetic to aid monitoring of local hashrate since shares have no intrinsic value of their own.

Most likely most miners (there are ~10 now) will notice nothing apart from some rejected shares which of course means nothing here.

EDIT: Restarts complete. I ended up restarting it a few times to capture some other changes. Total per-user (in this case per bitcoin address) hashrate will be shown more accurately in the users/ subdirectory, and low hashrate miners will drop to a suitable vardiff more rapidly.

EDIT2: Added link to total pool statistics. Bear in mind that the pool's hashrate has absolutely no bearing on each miner's chance of finding a block and getting a reward.

I don't think you can overestimate the value of K&R. It is deceptively simple in its explanations yet there is nothing old school about its programming advice. However I found nothing more valuable than grabbing existing well written code and modifying it and learning from that code. The kernel is tricky because programming on the kernel is a bastard, difficult to debug, and unforgiving unlike a userspace program, so probably not the best way to learn. There also are very few resources available to the kernel besides whatever is already written for it (libraries, floating point etc. are virtually non-existent). As for books, there's a wealth of recommendations out there, just google for best c programming books.

Heh, I see you. It's fun watching connections and trying to guess what hardware people are running. Ah but you see I'm not that crazy. It's the features and support requests and explaining the payout scheme and luck ad nauseum that is the time consuming part of running a pool, and this has no features to support and no payout scheme to explain. There's also no wallet or database to hack or payouts to process.

Thanks Con.

Yes it will be. Here's a sample of what a ckpool blockfind looks like:

https://blockchain.info/tx/256afa96fd5566daf735b0b3d80f6eb21c0e6f4637e54274a690427ebeedfead

So it will be a two generation address split?

I was a bit unsure from what you wrote in the other thread. It's not important, except as it might affect me in tracking pools.

Not quite all.

99.5% goes to the first generation address, 0.5% goes to my address (also generated). Slightly unclear wording perhaps.

EDIT: Updated accordingly to clarify.