NiceHash multi-algorithm SOLO mining pool [BTC/LTC/DASH blocks found!]

[nicehash]

Hye all. I just want to know if my miner is only got k/h, how much my percentage to earning block of bitcoin.

Thanks

You've got a better chance of stepping in fresh dinosaur crap while being struck by lightning.

So did you mean what im doing is useless right.

Not really useless, but a low-chance high-bet lottery

[1714318777]

1714318777

[AmDD]

Hye all. I just want to know if my miner is only got k/h, how much my percentage to earning block of bitcoin.

Thanks

You've got a better chance of stepping in fresh dinosaur crap while being struck by lightning.

Thats an interesting and probably quite accurate way to put it.

[jonnybravo0311]

Hye all. I just want to know if my miner is only got k/h, how much my percentage to earning block of bitcoin.

Thanks

You've got a better chance of stepping in fresh dinosaur crap while being struck by lightning.

So did you mean what im doing is useless right.

Not really useless, but a low-chance high-bet lottery

LOL... ok, I'll actually do the math . Since the question was expressed in hash rate of kh/s, I'll give the median value of 500:

Code:

diff * 2^32 / hash / 86400 = number of days to solve block
241227200229 * 2^32 / 500000 / 86400 = 23982938330.768488675555556

That means you've got about a 1 in 23,982,938,331 chance of finding a block in a day (i.e. 0.0000000041696% chance).  You have a significantly better chance of winning the US Powerball lottery (1 in 292,000,000) than you do of finding a block.

Random luck stats...

Chance of being struck by lightning in a year: 1 in 960,000
Chance of being struck by lightning twice in your life: 1 in 9,000,000
Chance of getting a hole in one: 1 in 5,000
Chance of winning an Olympic medal: 1 in 662,000
Chance of stepping in fresh dinosaur crap: 0

[Confusman]

Hye all. I just want to know if my miner is only got k/h, how much my percentage to earning block of bitcoin.

Thanks

You've got a better chance of stepping in fresh dinosaur crap while being struck by lightning.

So did you mean what im doing is useless right.

Not really useless, but a low-chance high-bet lottery

LOL... ok, I'll actually do the math . Since the question was expressed in hash rate of kh/s, I'll give the median value of 500:

Code:

diff * 2^32 / hash / 86400 = number of days to solve block
241227200229 * 2^32 / 500000 / 86400 = 23982938330.768488675555556

That means you've got about a 1 in 23,982,938,331 chance of finding a block in a day (i.e. 0.0000000041696% chance).  You have a significantly better chance of winning the US Powerball lottery (1 in 292,000,000) than you do of finding a block.

Random luck stats...

Chance of being struck by lightning in a year: 1 in 960,000
Chance of being struck by lightning twice in your life: 1 in 9,000,000
Chance of getting a hole in one: 1 in 5,000
Chance of winning an Olympic medal: 1 in 662,000
Chance of stepping in fresh dinosaur crap: 0

Thanks mate. Just now i can see what u talk about it

[MemberCount+1]

A question: can anybody explain the var-diff on nicehash.com? Is a high diff better for rewards? In other words, 20H/s on diff 16 are better than 15H/s on diff 8? It is clearly that 20 are better than 15 but with diff 16, is it much more, equal 2x20 ... or so?

values are only examples.

[jonnybravo0311]

When solo mining diff means absolutely nothing.  You either submit a share that solves a block, or you do not.  The only reason diff even exists is for your gratification.  It allows you to visually see that your miner is actually doing something.  As a human, what makes you think something is working properly... this:

Code:

share accepted 129ccced5 Diff 14/9
share accepted 213cdfes6 Diff 23/9
share accepted 522hsues2 Diff 188/9
...

or a completely blank screen?

[MemberCount+1]

When solo mining diff means absolutely nothing.  You either submit a share that solves a block, or you do not.  The only reason diff even exists is for your gratification.  It allows you to visually see that your miner is actually doing something.  As a human, what makes you think something is working properly... this:

Code:

share accepted 129ccced5 Diff 14/9
share accepted 213cdfes6 Diff 23/9
share accepted 522hsues2 Diff 188/9
...

or a completely blank screen?

You mean the usability or action/reaction of a program, I mean not the output from the miner rather the output from the webinterface:
Is this Diff-Col obsolete? Hmm

[jonnybravo0311]

Those statistics are meaningless, except to give you visual reassurance that the miner is working.  In pooled mining, every miner is compensated based upon the work the miner submits.  In variable diff, the pool determines how "difficult" the shares it will accept from the miner are.  It bases this on figuring out how many shares the miner is submitting in a given time frame, and adjusts it according to how many shares the pool wants to accept in that same time frame.

Let's take BTC mining as an example.  A pool wants to get six shares a minute, which translates into expecting to receive one share every 10 seconds.  You have an S9, which hashes at 13TH/s.  You can calculate how many diff 1 shares that miner expects to solve per second based on the following formula:

Code:

hash rate / 2^32 * difficulty

So, for our S9 at 13TH/s, we can see that it expects to solve 3026.8 diff 1 shares per second.  That's considerably higher than what the pool wants to track, so to compensate, it adjusts the difficulty of the share it will accept from the miner.  As difficulty increases, the number of shares solved per second decreases.  To get to our target value of 0.1 shares per second, we simply solve for difficulty in the above formula:

Code:

13000000000000 / 2^32 * diff = 0.1

In this case, the diff would be adjusted to 30268.  This way, every time the miner successfully solves a share of that difficulty or better, the pool records the miner having submitted a share.  The pool will typically constantly adjust that value based upon how many shares the miner actually has submitted during the time period.  If it has gotten more shares than expected, it will increase the difficulty.  If it has gotten fewer, it will decrease it.

All of that data is collected, and when some miner finally does submit a share that actually solves a block, then the pool calculates how to distribute the block reward amongst the miners.  That distribution is based on whatever payout mechanism the pool employs.

That's all well and good for pooled mining, but when you're solo mining, none of it matters.  You can submit a trillion shares and not find a block.  Or, you could submit just a single share and that one solves a block.  No matter how many shares you submit, the only one that will ever matter is the one that solves the block.  When that occurs, the pool will distribute the reward.  Either the pool generates the reward to its own address, then pays out later, or more likely the case in solo mining, the reward is distributed to you as the coinbase transaction.

The values you're seeing in the screenshot you shared are there purely for you.  It's a reassurance that your miner is working by providing a visualization of things.  In the screenshot, the pool has assigned a difficulty of 8 to your worker, and that worker is submitting 15.87 solutions per second.  None of that means anything to the pool, or to the network, or even to your miner.  Only if the miner submits a share that solves a block will you receive anything for your work.

[MemberCount+1]

Ah ok, thx for your excellent answer 

[proce55or]

Hello,

Anyone could help me, please?

So, I have this little USB miner called FutureBit MoonLander and I am trying to mine solo at NiceHash. I set up this in my .bat file

Code:

bfgminer.exe --scrypt -o stratum+tcp://stratum.solo.nicehash.com:3333 -u ADDRESS.WORKER -p 1,d=8 -S MLD:all --set MLD:clock=144

After 10, maybe 20 minutes I got red light from my miner and "Stratum from pool 0 detected new block" communicates. What am I doing wrong?

 https://s22.postimg.org/d3c2a7dsh/IMG_3383.jpg

[jonnybravo0311]

I can't answer questions specific to that hardware, however, I can answer your question about the message.  When you see the message "Stratum from pool 0 detected new block", that is just the mining software letting you know a new block was added to the chain.  This is completely normal, and completely expected.  Behind the scenes, when the pool notices a block was found, it sends out new work to miners to work on.

From your screenshot, I see a 7.3% HW error rate.  That's exceptionally high for any miner.  Not sure if that's the cause of the red light you're seeing... you'd have to check to see if any documentation is available about your miner to determine what the light means.

[proce55or]

Thank you very much for the answer, @jonnybravo0311

[bachel]

Can someone pls explain this to me ? how reliable is the antminer backend ?

[aarons6]

I can't answer questions specific to that hardware, however, I can answer your question about the message.  When you see the message "Stratum from pool 0 detected new block", that is just the mining software letting you know a new block was added to the chain.  This is completely normal, and completely expected.  Behind the scenes, when the pool notices a block was found, it sends out new work to miners to work on.

From your screenshot, I see a 7.3% HW error rate.  That's exceptionally high for any miner.  Not sure if that's the cause of the red light you're seeing... you'd have to check to see if any documentation is available about your miner to determine what the light means.

unfortunately these futurbit scrypt miners have a pretty high hardware error rate. mine are in the 15-30% range.

they also arent very reliable. they go zombie pretty often and stop mining.. and they only like certain pools.. and this one is NOT one of them..

i told him in the futurebit thread what pool to use for solo mining.. i think he figured it out.

[MyRig]

45 chips model frequency should be 700M not 600m  lower the frequency, lower the hash rate

Can someone pls explain this to me ? how reliable is the antminer backend ?

[jonnybravo0311]

45 chips model frequency should be 700M not 600m  lower the frequency, lower the hash rate

Can someone pls explain this to me ? how reliable is the antminer backend ?

I'm pretty sure the question is more about why it is showing 3 blocks found.  The only explanation I can even think of giving here is that for the very short time your miner was hashing at NH (not solo) it was mining a very low diff alt coin.  It certainly didn't hit a block of BTC.  The highest diff is nowhere near what the BTC network difficulty is.

[MyRig]

sorry,

the bottom portion was cut off.... 

Found Block stats probably came from the alt coin mining at NiceHash.  (If you did not intentionally change the frequency to 600M, you may have upgraded the wrong version of the firmware, please check!!)

[bachel]

45 chips model frequency should be 700M not 600m  lower the frequency, lower the hash rate

Can someone pls explain this to me ? how reliable is the antminer backend ?

I'm pretty sure the question is more about why it is showing 3 blocks found.  The only explanation I can even think of giving here is that for the very short time your miner was hashing at NH (not solo) it was mining a very low diff alt coin.  It certainly didn't hit a block of BTC.  The highest diff is nowhere near what the BTC network difficulty is.

it wasnt mining at the multipool thats 100% logs of solo even proof that but who cares build my own node now and will point them their its anyway just for fun not profit

[nicehash]

NiceHash signaling support for SegWit:

https://www.nicehash.com/index.jsp?p=news&id=116

[jonnybravo0311]

45 chips model frequency should be 700M not 600m  lower the frequency, lower the hash rate

Can someone pls explain this to me ? how reliable is the antminer backend ?

I'm pretty sure the question is more about why it is showing 3 blocks found.  The only explanation I can even think of giving here is that for the very short time your miner was hashing at NH (not solo) it was mining a very low diff alt coin.  It certainly didn't hit a block of BTC.  The highest diff is nowhere near what the BTC network difficulty is.

it wasnt mining at the multipool thats 100% logs of solo even proof that but who cares build my own node now and will point them their its anyway just for fun not profit

Look at your screenshot again.  There was a very short time that your miner was pointed to sha256.eu.nicehash.com.  That is not the solo pool.  It is in the realm of possibility that your miner found 3 low-diff alt-coin blocks during that time.  You certainly didn't even come close to a block of Bitcoin.