[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[vg54dett]

I am mining since a year with pools and I'm considering trying solo.
So I have a newbie question:
if you want to use few devices at solo mining , what is the best strategy ? all devices to the same address with workers name ? or each device working on a different address ?
 Another newbie question : is there a strategy in rebooting devices some times with solo mining ? or instead should we try to manage to avoid reboot or power cuts ?

sorry if this has been already asked, and thanks for any help !

Half a year ago, I was in your situation.

I have tried all of the scenarios you mentioned above.

Yes, I have invested (gambled) many BTCs on solo mining and even at one time got half of my s7 farm to point to ckpool instead of full time at kano.is

Conclusion: No difference. As CK once said, it's all random luck, big TH rental or small miners, anything can happen!

I hit a solo block here in January this year - how did I got that? By accident!

I was doing some maintenance on 4 of my S7s and had to poweroff them that day.

The next morning, I let them run and decided to get them warmed up to ckpool just for heck of it.

All looked OK, and I was about to point them back to main pool at kano.is, then this Fedex guy came to deliver a package for me so I was delayed for a few minutes.

By the time I came back to my desktop.... I saw CK's email on block announcement and the rest is history.

if you want to use few devices at solo mining , what is the best strategy ? all devices to the same address with workers name ? or each device working on a different address ?

It doesn't have any effect on your chance of solving a block, only a matter of how you personally keep track of stuff.

is there a strategy in rebooting devices some times with solo mining ? or instead should we try to manage to avoid reboot or power cuts ?

The only way you can solve a block is if you are hashing.  Any time your machine is not hashing, e.g. when it is rebooting, you have 0 chance, so that should be self-explanatory.

Thank you both guys.
Please correct me if I'm wrong :
any hash at any moment could solve a block ? including the first hashes of an old device just connected at the same chance as ones from a newer device like S7 ?
example : S7 provide about 10x more hash than S3. If both are working the same amount of time , the S7 will have 10x more chance to solve the block ? (because it made 10x more attempt , or is that different ?)

[vg54dett]

another question :
I've read on the pevious pages of the post that people were worried about not many block solved recently at CK.
Is that a pure "luck" consideration ?
Because I guess a miner (for example a S7) has exactly the same chance to solve a block if a block has already been solved a minute ago or a month ago ? Am I wrong ??

[wmtomlinso]

Wow, 11 blocks yesterday at Kano.  It was my birthday - and i even solved one of those really green blocks.   Dang, i should've mined CKsolo yesterday...

[chiguireitor]

...

I've read on the pevious pages of the post that people were worried about not many block solved recently at CK.
Is that a pure "luck" consideration ?
Because I guess a miner (for example a S7) has exactly the same chance to solve a block if a block has already been solved a minute ago or a month ago ? Am I wrong ??

Pure

Simple

Random

Luck

(If you want to get academic, mining is what is called a Stochastic Process, if you understand the gist of it, you'll understand that the only difference is how much hashing power you put into the equation, nothing else).

[jonnybravo0311]

Please correct me if I'm wrong :
any hash at any moment could solve a block ? including the first hashes of an old device just connected at the same chance as ones from a newer device like S7 ?
example : S7 provide about 10x more hash than S3. If both are working the same amount of time , the S7 will have 10x more chance to solve the block ? (because it made 10x more attempt , or is that different ?)

That is correct.  At 4.75T, the S7 has just over 10x the hash rate of the S3, therefore, statistically it should find a block in 10x less time.

another question :
I've read on the pevious pages of the post that people were worried about not many block solved recently at CK.
Is that a pure "luck" consideration ?
Because I guess a miner (for example a S7) has exactly the same chance to solve a block if a block has already been solved a minute ago or a month ago ? Am I wrong ??

Again, your understanding is correct.  It doesn't matter if a block was solved 1 minute ago or 1 month ago.  That has no influence whatsoever.  The only influencing factor is how much hash you have at your disposal.  The more you have, the less time you would expect it to take to find a block.

[vg54dett]

Please correct me if I'm wrong :
any hash at any moment could solve a block ? including the first hashes of an old device just connected at the same chance as ones from a newer device like S7 ?
example : S7 provide about 10x more hash than S3. If both are working the same amount of time , the S7 will have 10x more chance to solve the block ? (because it made 10x more attempt , or is that different ?)

That is correct.  At 4.75T, the S7 has just over 10x the hash rate of the S3, therefore, statistically it should find a block in 10x less time.

another question :
I've read on the pevious pages of the post that people were worried about not many block solved recently at CK.
Is that a pure "luck" consideration ?
Because I guess a miner (for example a S7) has exactly the same chance to solve a block if a block has already been solved a minute ago or a month ago ? Am I wrong ??

Again, your understanding is correct.  It doesn't matter if a block was solved 1 minute ago or 1 month ago.  That has no influence whatsoever.  The only influencing factor is how much hash you have at your disposal.  The more you have, the less time you would expect it to take to find a block.

Thanks chiguireitor and jonnybravo,
Just to be sure I have a good understanding could you confirm that :
If we compare a S3 and a 10x better S7, in fact the block won't be find in 10x less time because it can be find by the S7 as well as by the S3 in a minute (for example), depending on the luck.
Probabilities are just 10x better for the S7 because it is exactly like using 10 S3 ? (like playing lotterie with 10 tickets instead of 1 ?)
Sorry if it sounds stupid, english is not my mother language so details are sometimes hard to get !
Thanks again.

[jonnybravo0311]

No problem, and you've got it.  Either the S3 or the S7 can find a block at any time.  Statistically, the S7 will find a block in 10x less time than the S3.

If you're using the lottery analogy, your S3 checks 440,000,000,000 times a second to see if it's found a winner.  The S7 checks 4,750,000,000,000 times a second.  When talking about pools and "shares", we are referring to a baseline called a "difficulty 1 share".  We use the large numbers because it's frankly easier for the human mind to comprehend something being more "difficult" if it's perceived as a large number.  The reality is that the share is actually a very small number (lots of leading zeroes).

At any rate, you can use math to figure out how long you would expect it to take to find that baseline share (diff 1).  The formula for doing so can be simplified to:

Code:

2^32 / hashrate = time to find a diff 1 share

Applying that formula, you can easily calculate that your S7 expects to find a diff 1 share every 0.00090420364126 seconds.  Inverting that gives you how many diff 1 shares per second your S7 should find: 1105.94555735974321.

Now that you have this, and you know the current network difficulty, you can figure out the expected time to solve a block:

Code:

current diff / shares per second = time in seconds to find a block

Again, using the S7 as an example, at the current difficulty, you would expect to find a block after hashing for 161561576.41029279010546 seconds.  Convert that into days and you'll see an S7 would expect to take 1869.92565289690729 days to find a block.

Given this information, you can then figure out what your expected daily earnings are for an S7 because you know the current block reward is 25BTC.  Simply take 25 and divide it by the number of days to solve a block and you'll get 0.01336952BTC a day.

Putting all that together into a single formula:

Code:

25 / (current diff * 2^32 / hashrate / 86400) = expected earnings per day

If you want the more advanced version of that formula (one that doesn't approximate a diff 1 share to 2^32), here it is:

Code:

(reward / (2^256 / (((2^224 - 2^208) / difficulty) * hashrate))) * 86400 = expected earnings per day

[vg54dett]

Again, using the S7 as an example, at the current difficulty, you would expect to find a block after hashing for 161561576.41029279010546 seconds.  Convert that into days and you'll see an S7 would expect to take 1869.92565289690729 days to find a block.

I think I have a better view now!
But when we say "an S7 would expect to take 1869.92565289690729 days to find a block" , I suppose it is an average ? in solo mining, it could be in a minute or never , right?

[jonnybravo0311]

Yes, it's all about the statistical average time expected.  You could find a block one second from now, or you could find it 10 years from now.  It's not only in solo mining, it's any mining.

[madmartyk]

6 hours left in my 150T rental.  I keep hoping to see the number change to 172 blocks found and my popup open!!  So far I haven't even gotten by my last high of 2B... 

[HerbPean]

6 hours left in my 150T rental.  I keep hoping to see the number change to 172 blocks found and my popup open!!  So far I haven't even gotten by my last high of 2B...  

Yeah, I think i never pulled a better share then 6G with a few rentals. Even my Antfurnace pulled a 20G a longtime ago

[citronick]

6 hours left in my 150T rental.  I keep hoping to see the number change to 172 blocks found and my popup open!!  So far I haven't even gotten by my last high of 2B...  

Yeah, I think i never pulled a better share then 6G with a few rentals. Even my Antfurnace pulled a 20G a longtime ago

I had some extra BTC from yesterday's Kano's 11 blocks party... and I have 3 hours left from 111TH rental, just touched 13B... hoping for Juvia magic in a few hours...

[madmartyk]

6 hours left in my 150T rental.  I keep hoping to see the number change to 172 blocks found and my popup open!!  So far I haven't even gotten by my last high of 2B... 

Yeah, I think i never pulled a better share then 6G with a few rentals. Even my Antfurnace pulled a 20G a longtime ago

I had some extra BTC from yesterday's Kano's 11 blocks party... and I have 3 hours left from 111TH rental, just touched 13B... hoping for Juvia magic in a few hours...

Nice!!  When I hit my one and only block last Dec. I had 50T rented.  Crossing fingers and toes!!!

[thedreamer]

I threw my 800TH at it for 1/2 a day. Nothing.. 

[welshy9]

throwing 50th at it atm 1st ever rental with nicehash lets hope we havent  for a while

[Sierra8561]

I use rentals from time to time on kano.is can't get it to work here any suggestions?

[mathisforlosersdude]

No problem, and you've got it.  Either the S3 or the S7 can find a block at any time.  Statistically, the S7 will find a block in 10x less time than the S3.

If you're using the lottery analogy, your S3 checks 440,000,000,000 times a second to see if it's found a winner.  The S7 checks 4,750,000,000,000 times a second.  When talking about pools and "shares", we are referring to a baseline called a "difficulty 1 share".  We use the large numbers because it's frankly easier for the human mind to comprehend something being more "difficult" if it's perceived as a large number.  The reality is that the share is actually a very small number (lots of leading zeroes).

At any rate, you can use math to figure out how long you would expect it to take to find that baseline share (diff 1).  The formula for doing so can be simplified to:

Code:

2^32 / hashrate = time to find a diff 1 share

Applying that formula, you can easily calculate that your S7 expects to find a diff 1 share every 0.00090420364126 seconds.  Inverting that gives you how many diff 1 shares per second your S7 should find: 1105.94555735974321.

Now that you have this, and you know the current network difficulty, you can figure out the expected time to solve a block:

Code:

current diff / shares per second = time in seconds to find a block

Again, using the S7 as an example, at the current difficulty, you would expect to find a block after hashing for 161561576.41029279010546 seconds.  Convert that into days and you'll see an S7 would expect to take 1869.92565289690729 days to find a block.

Given this information, you can then figure out what your expected daily earnings are for an S7 because you know the current block reward is 25BTC.  Simply take 25 and divide it by the number of days to solve a block and you'll get 0.01336952BTC a day.

Putting all that together into a single formula:

Code:

25 / (current diff * 2^32 / hashrate / 86400) = expected earnings per day

If you want the more advanced version of that formula (one that doesn't approximate a diff 1 share to 2^32), here it is:

Code:

(reward / (2^256 / (((2^224 - 2^208) / difficulty) * hashrate))) * 86400 = expected earnings per day

This is the most concise, informative post I've read on the subject.  Maybe you wouldn't mind explaining to me how the stratum protocol works. When I mine on a pool that uses stratum does my miner receive the same exact work as all other miners? 

All miners receive the same work, produce a hash and then increment a random number called the nonce in an attempt to get a share above network difficulty, which solves the block. Is that correct?

Also, congrats on your extraordinary luck lately.

[citronick]

I use rentals from time to time on kano.is can't get it to work here any suggestions?

"...If you use an incompatible rental service that refuses to work on port 3333 try port 3334..."

Refer to 1st post in this thread -- all the information you need for solo mining here.

[Sierra8561]

I use rentals from time to time on kano.is can't get it to work here any suggestions?

"...If you use an incompatible rental service that refuses to work on port 3333 try port 3334..."

Refer to 1st post in this thread -- all the information you need for solo mining here.

I use NiceHash, I've tried both ports with no luck

[-ck]

I use rentals from time to time on kano.is can't get it to work here any suggestions?

"...If you use an incompatible rental service that refuses to work on port 3333 try port 3334..."

Refer to 1st post in this thread -- all the information you need for solo mining here.

I use NiceHash, I've tried both ports with no luck

999 times out of 1000 if someone can't mine on this pool it's because they're not using a valid bitcoin address as their username.