The probability of this happening at random is around 1 in 250 million (if you care that the hash prefix is all zeroes, versus just all the same character: 1 in 4 billion).
Github has officially announced that they have over 100 million active users, and over 400 million repositories.
At Github's scale this is a common event; on the order of monthly.
Having N leading zeroes is very similar to what "Bitcoin mining" consists of. Brutforcing small-ish N is possible on Raspberry PI in seconds, large-ish is almost impossible
The most zeroes at the start is 14, and there's only one commit with that many zeroes, which is https://github.com/seungwonpark/ghudegy-chain/commit/0000000....
The Nth commit there has N leading zeroes
[dead]
The probability of this happening at random is around 1 in 250 million (if you care that the hash prefix is all zeroes, versus just all the same character: 1 in 4 billion).
Github has officially announced that they have over 100 million active users, and over 400 million repositories.
At Github's scale this is a common event; on the order of monthly.
That's not the full hash of course. The complete hash is 000000007dac9715520764e334380ae8ab26d598.
There's a reason Git doesn't simply use CRC32 or the like.
https://github.com/not-an-aardvark/lucky-commit and others have shown up to engineer (read: brute-force) these early hash digits
I just stumbled across this commit and couldn't believe my eyes, thought it may be interesting to some of you as well.
EDIT: Looking further into it, it looks like there's almost two thousand commits on github starting with this exact hash: https://github.com/search?q=hash%3A0000000&type=commits&p=1
Having N leading zeroes is very similar to what "Bitcoin mining" consists of. Brutforcing small-ish N is possible on Raspberry PI in seconds, large-ish is almost impossible
Wow that's shiny pokemon odds!