Topic: citb0in Solo-Mining Group - BLOCK SOLVERS (english) - page 6. (Read 3808 times)

Hi and thanks for participating. You were successfully registered for run #11

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Name: 43.6T
My stake, for run: 0.001 BTC, for #011
My TXID: 33da3ad43f5ad83143b46291b6237ce2397207424b7efbba4ac760ebd2ad1ee1
My payout address: bc1qa984hqgagyyw6cvesl60xmu3p398sl9wh5uy8w
My vote for hash rate: 5 P
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Name: Forum Gholly
My stake, for runs: .001 BTC for #011
My TXID:831effa7076905847c002dc9016ec02ceb80bb3e5b733a6b38997fa4da52c3ff
My payout address: bc1q8z868rqv6f3h3gl94qsr58qhd2hhx75qhkmwgr
My vote for hash rate:  2 PH

I am having trouble getting this to post...

Run #10 just started at 2.5 PH/s for a run time of about 21.7h. Let's keep our fingers crossed that we find a block. Good luck Block Solvers !!!
As usual, all statistic updates in thread #2 under run #10

---

We got 1.13 T   come on, a little bit more .. c'mon

---

EDIT:
We achieved 1.13 T. If we had 43.05 T then the block would have been ours. Too bad, only little had been missing. Submitted total diff was 44.3 G. All stats posted as usual on page #2. Round #11 is next and there are plenty of free slots available, stake as usual only 0.001 BTC per slot. If the power runs #15 or #20 are filled before, they will of course start independently from the normal runs. Let's go solo miners ... let's finally mine the block and collect the reward

Great ...

I am curious to see how this all goes.

#crysx #cwi

Hello chrysophylax. Your stake has been gratefully received, I have just updated the list. There was still one slot free, I had overlooked it because I had a typo in the numbering of the number of participants but I have filled the remaining slot, so we are now complete for round #10 and can start soon.

I will prepare everything and start the run #10 with 2.5 PH/s soon.... Stay tuned

Is this Correct?

---

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My BCT Forum Name : chrysophylax
My Stake for Runs : 0.003BTC for #010 at 0.001BTC for Each Slot (8,9,10)
My TXID for Payment : bab3465959985606a9f8beb80869cac09fb16fd83d3af4bc33b5cb8b3db54dce
My PayOut Address : 1A9zUUcoghLwMRLvdhtaYuUZmq47W9fJQT
My Vote for HashRate : 3PetaHash
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---

The BTC Address is a one of the Binance Exchange Addresses so it may change later. Just doing this as a test/play basis ... I more than likely will only want 3 positions in any of the Sessions I enter into. It is just for fun after all.

Let Me know if all is well. I checked all the transaction details and they all check out. The Money is in the wallet right now.

https://btc.cryptoid.info/btc/address.dws?bc1qtyvxwhwctneje9zjvqkzvp6yqtnqc3xs0sf6vd.htm
https://btc.cryptoid.info/btc/tx.dws?811857420.htm

#crysx #cwi

Sure ...

I will look at that this afternoon and organize it.

Thanks Mate!

#crysx #cwi

Hi chrysophylax. Just check the thread #1, it's everything explained there If you like to fill the 3 slots of run #10 then send 0.003 BTC to bc1qtyvxwhwctneje9zjvqkzvp6yqtnqc3xs0sf6vd with the filled template that contains your name, your stake, TXid, your payout address and your vote for the desired hash rate. Looking forward to your deposit and hopefully we could launch run #10 soon ...  

Hi Mate ...

I'm happy to fill those slots.

What do You need?

#crysx #cwi

@mikeywith: thank you so much for the effort you put in to explain this in such detail. You have really helped me with this. It helped a lot in understanding after reading through this several times and reading and delving into various sites around bitcoin. I am quoting the key points you mentioned.


Very important and accurate points. I have now understood that only the current Difficulty plays a role in the probability calculation for a block find and is used as the basis of the calculation. The Bitcoin Wiki page has further assisted in understanding this.
this was also a very helpful information, thanks!

I think this topic belongs in the "technical section" of the forum. I had already asked the moderators to do this, but unfortunately it hasn't been implemented yet. I have meanwhile manually opened a new thread and the relevant posts here #46 to #56 from this topic were moved (quoted) in the new thread as takeover. Let's discuss this matter further there, so that this thread here of the project "Block Solvers" remains clear and does not run further into off-topic.

For your information: I have undone the change in the info page #1 and reset it to the original state.

For all other questions or comments about "probability calculation" please have a look at the linked thread.

@mod: You can safely delete #46 to #56 as I have successfully moved them to the new thread #2 in the technical sub-forum

Thanks for the attention and support.

---

Now back to the topic. Run #10 still has 3 open slots. Stake is 0.001 BTC as usual

And for those who are interested in more power, take a closer look at the Power Run #20

C'mon Block Solvers . . .

@mikeywith: thank you so much for the effort you put in to explain this in such detail. You have really helped me with this. It helped a lot in understanding after reading through this several times and reading and delving into various sites around bitcoin. I am quoting the key points you mentioned.


Very important and accurate points. I have now understood that only the current Difficulty plays a role in the probability calculation for a block find and is used as the basis of the calculation. The Bitcoin Wiki page has further assisted in understanding this.

this was also a very helpful information, thanks!

I think this topic belongs in the "technical section" of the forum. I had already asked the moderators to do this, but unfortunately it hasn't been implemented yet. I have meanwhile manually opened a new thread and the relevant posts here #46 to #56 from this topic were moved (quoted) in the new thread as takeover. Let's discuss this matter further there, so that this thread here of the project "Block Solvers" remains clear and does not run further into off-topic.

For your information: I have undone the change in the info page #1 and reset it to the original state.

For all other questions or comments about "probability calculation" please have a look at the linked thread.

Thanks for the attention and support.
citb0in

Alas, this is where you both are getting confused, there is no such thing as "reset", you are not competing against any other miners, you are competing against the difficulty and your only weapon is the number of hashes, your luck doesn't reset with every block, it resets with every hash, every hash has the same exact chance of hitting a block regardless of the status of the network, other miners when was the last block found, who found it, or anything else.

Saying that you are competing against other miners suggests that if other miners pull out and stop hashing, your chances of hitting a block will increase, which is false, even if everyone else stops mining and you are left alone, your chances will change by 0%, if your initial chances were to hit a block in 10 days, it will still be the same.

In the first half of your post, it seems like you cleared the confusion, at least got the correct logic for the most part, but the quoted part is where things got messed up, it's a popular belief for many people to fall into, this is the inverse way of thinking that just because 9 minutes have passed since the last block, the chances to hit a block in the following 1 minute is higher, no, it doesn't work this way, every single share submitted to the network has exactly the same chance of hitting a block.

You need to ditch the idea that tells you that miners are mining the same exact same block, and you can only start mining a block when one is done, you need to understand that every hash is trying to mine its own block if it manages to do so, it simply tells the other miners "hey guys, I am going to name my block 1011, so please if any of you manages to find a block, use a different name "1012", don't let this give you the illusion that everyone is now mining block "1012" , NO! NO!, everyone is mining their own random block, and IF they hit one, they will name it "1012".

So long story short, there is no "RESET" here, every share CAN find a block at any given time, and the chances of your hashes hitting a block are 100% independent from every other hash anyone else has.


Now as to why using 144 blocks a day is perfectly valid, it's because the difficulty was set to ENSURE that IF the hashrate was stay constant (i.e the number of hashes for the period of 2 weeks) remains the same, the total shares combined will only find 144 blocks every 24 hours or 2016 in 2 weeks, or 1 every 10 mins, all valid representation of the code which simply calculate the total timespan between the last 2016 blocks against the target timespan which is 2 weeks in seconds.

To understand the last part more, you need to think of all miners as one miner (but please don't let this confuse you with the previous part), all miners combined have x amount of hashes to try, in theory, those x hashes combined will find a block every 10 mins.

If things are not crystal clear by now, I am sorry, I don't think I can make this any clearer, hopefully, someone else who knows how to explain things better can chime in.

@mod: Since this topic is very off-topic and for reasons of clarity and sense would be better in the technical part of our forum, I hereby ask a moderator to move the last 9 posts starting from post #46 into the subforum Development & Technical Discussion. You could the thread title "probability / chance of hitting a block" or anything else you might find useful for it. Thanks a bunch in advance.

---

Hi @mikeywith and sorry for late reply. I took time today to look at this question and better understand the connections. Thank you for your detailed explanation, which helped me a lot to understand. For a better understanding I wrote a Python program in parallel to be able to implement and compare what I learned right away. Please correct me if I made any incorrect statements or thoughts about this below.

First things first.

Wikipedia says:
Probability is the branch of mathematics concerning numerical descriptions of how likely an event is to occur, or how likely it is that a proposition is true. The probability of an event is a number between 0 and 1, where, roughly speaking, 0 indicates impossibility of the event and 1 indicates certainty. The higher the probability of an event, the more likely it is that the event will occur. A simple example is the tossing of a fair (unbiased) coin. Since the coin is fair, the two outcomes ("heads" and "tails") are both equally probable; the probability of "heads" equals the probability of "tails"; and since no other outcomes are possible, the probability of either "heads" or "tails" is 1/2 (which could also be written as 0.5 or 50%).

For the sake of simplicity lets not considering the competition from other miners. In that case, if only you participate in the Bitcoin mining network as a solo miner and the difficulty remains static, then the probability of finding a block is equal to 1 since you provide the entire hashrate of the network. It's certain that we will hit the block. The only thing we need to know is the expected average time to hit the block. To calculate the expected time until we find a block, we can calculate the average number of hashes needed to find a block. The average number of hashes needed to find a block can be calculated by multiplying the difficulty of the network by 2^32.

So the average number of hashes needed to find a block is:
* 2^32 = 37,590,453,655,497.09 * 2^32 = 161,449,769,092,163,668,279,296

To calculate the expected time until you hit the block we divide the average number of hashes/sec needed to find a block by the hashrate of the solo miner. Let's take for example the Bitmain Antminer S19 XP @ 140 TH/sec or 140,000,000,000,000 hashes/sec. Thus:
average number of hashes per second / hash rate of the miner = time in seconds needed to find a block.
161,449,769,092,163,668,279,296 / 140,000,000,000,000 =  seconds

Code:

hashrate_value = 140,000,000,000,000
diff = 37590453655497.09
expected_blockhit_time_in_hours = (diff * 2**32) / hashrate_value / 3600

= 36.57 years

Note, however, that this is an average time and it may take longer or shorter to find the block. The scenario explained so far can be compared to VanitySearch for a better understanding, where you try to search for a matching hit with your GPU. You are the only searcher and it is certain that you will land the hit in the future even if it would take light years in the case of very complex calculations. But also here, like VanitySearch, you can give an expected time at which you will find what you are looking for. The probability to find a match is 1.

I want to know the probability of a given hash rate to hit a block within the time frame of 10 minutes. Following formula only takes into account the miner's hash rate and the current network difficulty. It assumes that the miner is the only one mining on the network and that the network difficulty remains constant.

P = (hash rate of solo miner) * 600 / (difficulty * 2^32)

- 2^32 is used because Bitcoin uses double SHA-256 and thus there are 2^32 possible solutions per each block. A better explanation can be found HERE

Two examples:
hash rate: 140 TH/s will result in probability of 0.0000005203 (decimal value) or expressed as a percentage value = 0.00005203 %
hash rate:   50 PH/s will result in probability of 0.0001858163 (decimal value) or expressed as a percentage value = 0.01858163 %

- this probability so far only applies to a single block for the given time frame of 10 min and not a continuous mining period
- the total network hash rate is not used directly in the calculation, but it is used indirectly through the current network difficulty we retrieved

I fully agree to:

Quote

[chance with 50 PH/s for 3h] = [chance with 25 PH/s for 6h] = [chance with 5 PH/s for 30h]

Now let's take all the other miners into consideration, so we are competing against them. I guess that @akaki meant that after a block discovery the cards are reshuffled and it has no meaning what had taken place in the past. From the time of each new block the point of view starts again from zero.

I still fully agree to akaki's statement which sounds correct to me. An essential characteristic of that is memoryless, the intervals between any two events are independent of, and statistically identical to, each other.

However, you say that you can calculate the probability of finding a block within 1 day (=24 hours) by multiplying the result we got before (probability per 10-min = 0.0000005203) by the number of 10-minute intervals in a day (=144). So you say 0.0000005203 * 144 = 0.0000749232 (decimal value) which represents the probability of hitting a block with 140 TH/s within one day. The probability is 144 times higher and if you extend this to a whole week or month the probability raises accordingly. If I understood correctly from what you said, the reason for this is that if the network difficulty remains constant the probability of finding a block within a certain time frame is directly proportional to the number of 10-minute intervals in that time frame. This is because the probability of finding a block is determined by the miner's hash rate, the current network difficulty, and the number of possible solutions for each block (2^32) which remains constant. But this approach does not take into account the fact that once a block is found, everything is reset and you start from scratch. This is exactly what akaki says and wanted to point out and in my opinion is also correct. Other important points that should not be ignored are: the Difficulty changes every 2016 blocks and is therefore variable. You cannot simply use the previously calculated probability per block as a basis and multiply it by a time span x, that would not be correct in this context.

Another point worth considering in this context would be the difference between probability and chance. There is a lot of information about this on the Internet, e.g. HERE. These two terms are often used mixed.

Finally, since you are competing against other miners in the real case, you can determine the probability of a block hit within a block period for the solo miner quite simply as follows. When mining Bitcoin, the miner performs a double SHA-256 hash of the block header, and the miner's goal is to find a value that is less than the target. The target is a 256-bit number that is dynamically adjusted by the protocol every 2016 blocks (about two weeks) to ensure that the average time to find a block is 10 minutes. The target is inversely proportional to the difficulty, so the lower the difficulty, the higher the target, and vice versa. The difficulty is a measure of how difficult it is to find a block relative to the easiest it can ever be. The hashrate is measured in hashes per second. The probability of adding a block as a solo miner are determined by the number of hashes the miner's rig is computing per second in relation to the total number of hashes that all of the machines on the network are computing each second. The probability of finding a block for a solo miner is determined by the miner's hashrate relative to the total network hashrate and the difficulty of the network so a miner with a higher hashrate can perform more hashes per second and thus have a higher probability of finding a block.

Here is some output from the Python program I wrote during this excursion. The part with brown color is not correct in my opinion but I have included it in the output for comparison reasons.

Quote

Current Bitcoin network difficulty is: 37,590,453,655,497.09
Current overall hashrate of the Bitcoin network is: 288,814,703,183,075,200,000 hashes/sec
==============================================================================================================
Enter the hashrate/sec of your solo miner: 140TH

Entered hash rate of 140.0 TH/sec equals to: 140,000,000,000,000 hashes/sec
The ratio of your solo mining hash rate to the total network hash rate is: 0.000048 %
and expresses the probability of hitting the next block.

==============================================================================================================
Probability per 10min: 0.000000520 (0.000052029 %) or 1 in 1,922,021
==============================================================================================================
Probability per hour: 0.000003122 (0.00 %) or 1 in 320,337
Probability per day: 0.000074921 (0.01 %) or 1 in 13,347
Probability per week: 0.000524448 (0.05 %) or 1 in 1,907
Probability per month: 0.002247634 (0.22 %) or 1 in 445
Probability per half-year: 0.013673107 (1.37 %) or 1 in 73
Probability per year: 0.027346214 (2.73 %) or 1 in 37
==============================================================================================================
Expected average time to hit a block: 320,336.8 h = 13,347.4 days = 1,906.8 weeks = 439.3 months = 36.6 years
==============================================================================================================
In words: The chance of mining a block with the given hashrate within a 10min period is similar to
the probability of picking a red winning ball from a jar containing 1,922,021 white balls.

The chance of mining a block with the given hashrate is similar to trying to find a needle in a haystack.

Quote

Current Bitcoin network difficulty is: 37,590,453,655,497.09
Current overall hashrate of the Bitcoin network is: 288,814,703,183,075,200,000 hashes/sec
==============================================================================================================
Enter the hashrate/sec of your solo miner: 5p

Entered hash rate of 5.0 PH/sec equals to: 5,000,000,000,000,000 hashes/sec
The ratio of your solo mining hash rate to the total network hash rate is: 0.0017 %
and expresses the probability of hitting the next block.

==============================================================================================================
Probability per 10min: 0.0000186 (0.0018582 %) or 1 in 53,817
==============================================================================================================
Probability per hour: 0.0001115 (0.01 %) or 1 in 8,969
Probability per day: 0.0026758 (0.27 %) or 1 in 374
Probability per week: 0.0187303 (1.87 %) or 1 in 53
Probability per month: 0.0802726 (8.03 %) or 1 in 12
Probability per half-year: 0.4883253 (48.83 %) or 1 in 2
Probability per year: 0.9766505 (97.67 %) or 1 in 1
==============================================================================================================
Expected average time to hit a block: 8,969.4 h = 373.7 days = 53.4 weeks = 12.3 months = 1.0 years
==============================================================================================================
In words: The chance of mining a block with the given hashrate within a 10min period is similar to
the probability of picking a red winning ball from a jar containing 53,817 white balls.

The chance of mining a block with the given hashrate is similar to trying to find a needle in a haystack.

Quote

Current Bitcoin network difficulty is: 37,590,453,655,497.09
Current overall hashrate of the Bitcoin network is: 288,814,703,183,075,200,000 hashes/sec
==============================================================================================================
Enter the hashrate/sec of your solo miner: 50phs

Entered hash rate of 50.0 PH/sec equals to: 50,000,000,000,000,000 hashes/sec
The ratio of your solo mining hash rate to the total network hash rate is: 0.017 %
and expresses the probability of hitting the next block.

==============================================================================================================
Probability per 10min: 0.000 (0.019 %) or 1 in 5,382
==============================================================================================================
Probability per hour: 0.001 (0.11 %) or 1 in 897
Probability per day: 0.027 (2.68 %) or 1 in 37
Probability per week: 0.187 (18.73 %) or 1 in 5
Probability per month: 0.803 (80.27 %) or 1 in 1
Probability per half-year: 4.883 (488.33 %) or 1 in 0
Probability per year: 9.767 (976.65 %) or 1 in 0
==============================================================================================================
Expected average time to hit a block: 896.9 h = 37.4 days = 5.3 weeks = 1.2 months = 0.1 years
==============================================================================================================
In words: The chance of mining a block with the given hashrate within a 10min period is similar to
the probability of picking a red winning ball from a jar containing 5,382 white balls.

The chance of mining a block with the given hashrate is similar to winning a lottery with a few
hundred participants.

Quote

Current Bitcoin network difficulty is: 37,590,453,655,497.09
Current overall hashrate of the Bitcoin network is: 288,814,703,183,075,200,000 hashes/sec
==============================================================================================================
Enter the hashrate/sec of your solo miner: 150EH/s

Entered hash rate of 150.0 EH/sec equals to: 150,000,000,000,000,000,000 hashes/sec
The ratio of your solo mining hash rate to the total network hash rate is: 52 %
and expresses the probability of hitting the next block.


Probability of mining a block:
==============================================================================================================
Probability per 10min: 0.557 (55.745 %) or 1 in 2
==============================================================================================================
Probability per hour: 3.345 (334.47 %) or 1 in 0
Probability per day: 80.273 (8,027.26 %) or 1 in 0
Probability per week: 561.909 (56,190.85 %) or 1 in 0
Probability per month: 2,408.179 (240,817.94 %) or 1 in 0
Probability per half-year: 14,649.758 (1,464,975.77 %) or 1 in 0
Probability per year: 29,299.515 (2,929,951.54 %) or 1 in 0
==============================================================================================================
Expected average time to hit a block: 0.3 h = 0.0 days = 0.0 weeks = 0.0 months = 0.0 years
==============================================================================================================
In words: The chance of mining a block with the given hashrate within a 10min period is similar to
the probability of picking a red winning ball from a jar containing 2 white balls.

The chance of mining a block with the given hashrate is ... damn good!

I have to disagree, akaki put and end to all speculation by saying


The quoted statement is just wrong, the correct statement would be


or





I don't think this is what he meant, but anyways, this illustration is wrong, there is no such thing as "roll once every 10 min" you roll as often as you can, it's just that difficulty that "ensures" you only get 2016 six in 2 weeks assuming you don't increase the rolls.


 

The numbers on solochance.com are perfectly correct, looking at akaki post history, I am surprised to why he is confusing himself, he seems to be pretty good at math, maybe missing the logic.


Let's clear up some confusion:

The difficulty adjusts based on the time it took to solve the previous 2016 blocks (more like 2015 blocks due to some bug in the code but can be ignored for now)

So, if the difficulty of the previous epoch was 10 units, and the time it took to solve 2016 blocks was 2 weeks, the difficulty will stay at 10 units, this brings the question, how did the pace of finding blocks get to exactly 2 weeks or 10 minutes average block time? it's because the NUMBER of hahses produced by miners remained the same.


So epoch A had a diff of 10 units and the number of hashes was 1000, based on the difficulty of 10 those 10000 shares can only possibly find 2016 blocks in a period of 2 weeks/avg block time was 10 mins.

see that 10 units of difficulty couldn't care less how the 1000 hahses were generated, if all the miners shutdown their gears for 13 days and do manage to hash 1000 hashes on the 14th day, the block average will still be 10 mins and thus no diff change will accur.

using the dice analogy, you are required to roll 6 at the first epoch, the protocol wants you to hit just one 6 every 10 mins, if you manage to hit more 6s in under 10 mins, the requirement will change, and you are now forced to roll two 6s in a row, now that will need 10 mins to happen, if you do more rolls and manage to hit two 6s in less than 10 mins you will be required to roll three 6s and so on.

while rolling a die every time is an independent event, you will still hit a 6 on average every 6 rolls, you can test it yourself, roll a dice 60000 times and you will likely get 10000 six ,

Still at the dice analogy, the bitcoin dice is actually 2^256, the number of dice sides that can solve a block is determined by the difficulty/target, simply put, with the current difficulty of 37.89T every hash has 1 in 37,885,054,421,573 chance of hitting a block.

let's do more math for fun, the time it takes you to find a block is

time in seconds = difficulty * 2^32 / hashrate in seconds

with 50PH the equation is

((37885054421573 * 2^32 / 50000000000000000) / (3600))  = 903 hours
 on average to hit a block, let this 903 hours sink in for a while because we will use it later, and by the way, the division by 3600 is just to convert seconds to hours.

so the above equation suggests that IF you hash 50,000,000,000,000,000 (50PH) every second for 903 hours, you are likely to hit a block, that is 50000000000000000*60*60*903 hashes in a total of 162,540,000,000,000,000,000,000 hashes submit over the period of 903 hours gets you a block on average.

*(60*60 to convert seconds to minutes > minutes to hours )


Now let's say I want to produce the same hashes in just 9.03 hours instead of 903 hours, 9.03 hours has 32,508 seconds, so 162,540,000,000,000,000,000,000/32,508 = 5,000,000,000,000,000,000 hashes/second ( 5000PH)

using the same equation above we now have

((37885054421573 * 2^32 / 5000000000000000000) / (3600)) = 9.03 hours.

now just for fun, I want to produce the same number of hashes over the course of 9,030 hours, without doing any more equations, I know I can just hash at 5 peta hash/second for 9,030 and still get the same result as 50PH over 903 hours, but while the calculator is still open, why not?

5 petahash = 5000000000000000

((37885054421573 * 2^32 / 5000000000000000) / (3600)) = 9039 hours.


Notice how everything here revolves around the total number of hashes (162,540,000,000,000,000,000,000), if I hash them at a rate of 50PH/S i need 903 hours, if I hash them at 5000PH/second all I need is 9.03 hours, if I hash them at 5PH/second I'll need 9039 hours.

By now, it should be clear that it's all about the TOTAL NUMBER of hashes you submit, so back to Nicehack or any rental services, you actually pay per HASH, when you go buy those 162,540,000,000,000,000,000,000 hashes on nice hash you will pay x BTC and it's up to you how fast you want to "consume" them.

for economical reasons and supply/demand, it's sometimes wiser not to put massive orders in the order book as that could trigger a price increase.


Also, it's perfectly fine and correct to say


akaki insisted that you can't say so, not sure what's the reasoning behind it, the difficulty does keep block inteverals at 10 minutes average, so using 144/day to get a daily chance for x hashrate/second is perfectly correct.

In my opinion, two different statements are considered, both of which are correct and are unintentionally mixed, which is why they lead to different opinions.

A)
What akaki meant is that the odds calculation related to the block is correct. To illustrate it in another example: you have a dice and the goal is to roll a six. You are only allowed to roll once every 10min. To the question "What is the chance to roll a six?" the correct answer is always the same, it is "1/6", so the probability is 0.16667 % to roll a six. Just because you are allowed to roll again the dice 10min later, it does not mean that the probability to roll a six increases. It always and steadily remains 1/6.

B)
What mikeywith and willi9974 mean refers to the comparison between using 50 PH/s for 3h or renting 10 PH/s for 30h with the same money available for the hashrate rent. Here, the factor of the amount of use comes into consideration, since you have to rent the hashrate on the marketplace at the prices available. And inevitably coupled to the hash rate and the price is also the factor time. Therefore, this consideration should only be compared within this group (B), but not mixed with (A).

What the creator of the solochance.com website and many others do is: they multiply/divide the probability of a block hit (related to the block) by the number of 10min periods and thus mix the result with time. However, the time factor has no consideration in the probability calculation. The result of the thus faked probability is thereby glossed over.  At least that's how I understood it, which is why I think that both statements are correct.

And a second point is: when you rent the hashrate, the more hashrate you rent at the same time, the higher the price, you get less shares for the same budget. So rather rent less speed but longer time.
At the end the same price, but you get more shares. Cost per share is lower at lower speed. Supply and demand on a hash rental place.

Best regards,
Willi

They do not increase the chances by mining for a longer period with a lower hashrate, but also, no one is losing money, I am not sure why are you taking the time factor out of the equation when you are hashing against x for x period.

To put this in a simpler form, when you pay 100$ you get 100 shares, in other words, 100 shots to solve a block, whether you take those chances in 1 minute or over the course of 10 days it makes exactly no difference, the chances of those 100 shares hitting a block remain the same.

What really matters here is the TOTAL NUMBER of shares you submit, not how FAST you submit them, every share is an independent event that has the ability to be a block solver, if what you think is true then mining pools would operate in a different manner.

Binance and Viabtc will join forces to increase their hashrate, say each has 10EH worth of hashrate, they would mine for Binance wallet with 20EH for 12 hours, and then 20EH for Viabtc wallet for the remaining 12 hours, and then at the end of the day, they would end up with more coins than having mined individually for 24 hours with 10EH each, that is not true by any means.

The fact is, that 20EH produced 20EH per second for 12 hours which is the same number of shares that 2*10EH*24 hours, you are missing a major point here which is the power you rent is sold as in Hashes per SECONDS.

And as for the Gambler's fallacy, it has nothing to do with why OP's initial numbers are correct,  not sure why he agreed to your claim and changed the post.


If anyone still thinks that 50PH for 3 hours doesn't have the exact same chances of hitting a block with 25PH for 6 hours, go ahead and email all the large 10 pools that make up 90% of the hashrate and tell them you found a cheat code for mining, let them join their 300EH together and mine to one wallet every 24/10 hours so they can increase their chances of hitting blocks and end up with more BTC by the end of the month.

The more I have dealt with it, the more clearly I agree with you. You are absolutely right. There's no guarantee you'll hit a block with any amount of hashrate, simply better odds the more hash rate you use. Time is useless in that calculation. I have adjusted the original post in this section. Thank you for your attention and advice.

Sorry, I insist because people might be fooled (and loose money) by the chances of mining a block that were announced.

You say that I'm correct about the Gambler's Fallacy but you are still talking about time. Hashrate and only hashrate matters for the probability of mining a block.

[chance with 50 PH/s for 3h] > [chance with 25 PH/s for 6h] > [chance with 5 PH/s for 30h] that is simply because you can remove "for xh".

The post should be edited to :

Chances to mine a block are :

at   1 PH/s --> 1 in 267.342 per block
at 2.5 PH/s --> 1 in 106,937 per block
at   5 PH/s --> 1 in  53,468 per block
at  10 PH/s --> 1 in  26,734 per block
at  25 PH/s --> 1 in  10,694 per block
at  50 PH/s --> 1 in   5,347 per block

and yet I didn't check the latter, it could be worse.

The calculation in "solochance.com" is also wrong. I don't know if it's intentionally to just encourage people to use a solo-mining service.