Number of private keys: ~2**256
Number of SHA256 hashes: 2**256
Number of H160 hashes: 2**160

Naive answer: on average around 2**96 private keys for every address (one key in every other 2**160 tries, on average).

Better answer: since SHA256 is uniform, only around 63.4% of all possible SHA hashes will come up after 2**256 hash operations (any given hash has only a 63.4% probability to show up at least once or more). 36% of all possible SHAs won't make it. 28% will show up at least twice, etc.

So, around 0.63 * 2**256 unique SHA hashes go into RIPEMD-160.

Since RIPEMD-160 is also uniform, but the number of hash ops is much larger than 2**160, almost every possible H160 hash is likely to be seen at least once (but the average goes down a tiny little bit from the naive 2**96).

So, final answer: an address may be generated by no private key at all, or by a ton more of private keys than is expected, but the sweet spot of 99.9999% confidence is some small interval around the <2**96 average.

If you plan to find an address collision (this is what your idea sounds like, right?) best of luck. You'll likely need much more than 2**160 hashing ops before you can reach some 99.999% chances to get a collision. That's equivalent to solving Puzzle 71 several billion septillion times, instead of just once. If you take a billion RTX 4090 and start today, it would still take 10**21 years before you get a collision. That's 500 billion times more time than the age of our Universe.

I have a question. Each address theoritically can be generated by how many different private key ?

Since h160 is less than the private key hex

ktimesg, did you see the partial match found late last night/early this morn: 19vkiEajfhu8gnX5QUJZReqALvkTncJtgu

I found the prefix 19vkiEajfhi9, does anyone else have one? puzzle 69

10 GB/s refers to the throughput or the rate at which the PRNG can produce random data.
A Bitcoin private key is a 256-bit (32-byte) number. This is the size of the data required to generate one Bitcoin key.

You would need a PRNG or hardware setup that can generate random data at 320 GB/s to achieve 10 GK/s.

P.S. Xoshiro256plus could achieve the required throughput of 320 GB/s with 128 cores.

Do I correctly understand that solving elementary school equation:
x * 55066263022277343669578718895168534326250603453777594175500187360389116729240 mod 115792089237316195423570985008687907853269984665640564039457584007908834671663 = 9210836494447108270027136741376870869791784014198948301625976867708124077590

will make you owner of 1 377 000 USD?

In all seriousness, how many (sticking to averages of math / the curve) BY8GQbnueY prefixes are in a 66 bit space? I come up with 171. Is that correct or close to what others think / know?

And for the prefix, BY8GQbnue, a little less than 10k inside a 66 bit space?


I think the issue with your statement, is, others have tried this method, and to my knowledge, no one has found the key, using the same or similar methods. But maybe you will be the first!

I see that 135 is risky too, the creator already has the private keys, I'm waiting for someone lucky enough to find it and when he withdraws the funds from the 135 challenge the creator will replace it with higher fees immediately with rbf, stealing for himself again, what do you guys do you think? Because, for example, if 2 people have the same private key of 135 and withdraw together to compete for higher rates, it would be a problem if the creator intends to troll for fun, the original creator for protection must have a scrypt monitoring the withdrawals to nullify the lucky and then troll the winner, just like in 66?  That's why my withdrawal method is private and very well formulated, where no one can override it with higher rates, my TX is strong. who did all this to troll fools... maybe

child?

Go ahead, Iranian.

Are people the same 20 years ago as they are now? If you are not even capable of distinguishing that, you are too young to talk to you.

Development is something that happens in every field.

But the backward ones like you are usually in countries like IRAN and AFGHANISTAN. But that is written in my past when I was TURKISH.

I don't need to erase any of my past, because no one knows anything 100% for sure. They are learning.

But I am sorry to the brat kids like you who love the ready-made. You think that you are doing something by stealing everything that is ready-made. So now put that cell phone you wrote about in your pocket and pull yourself together. Be well-mannered. Because you are a child. In fact, you are not even 15 years old, little one.

Ok kid, you should have added it after these messages.

What nickname were you using before? Kid? I'm sure your birth date is in the 2000s.

Be quiet now, your adults are busy with work.
If you don't delete these messages soon, you'll be in a very funny situation. I promise.

We have a nice saying here.

"Let's pick up the kids from the track." Now go drink your milk and go to sleep. When you wake up, you'll scream it's a dream.

Hello friends;
I think I found a clue.
66. The probability that the wallet is in these ranges is over 90%

3B320044788A17DA0 - 3BC0ABFC3654BAE80
3475FBD690F7B3880 - 34B85C9495BA98840
30389466D233BCDE0 - 305E58789566D2EA0
2E1325EAAC24E8A40 - 2E6917C76BF8F5340

If the result is within these ranges, I will inform you partially about the tip.

Thank you...

Yes, this is not a place to write for nothing.

You got the answer to your question and the things you wrote for nothing.

Now, stop asking pointless questions.
If you have the power to do something, we are waiting. Otherwise, do not waste our time.

Hi friend,

There is a tip for 64 wallets,

The beginning starts with the letter B. The next most likely is the number 2.

The highly probable start starts with B2, possibly with B25 or B26.

5 years of experience, I said only about algorithms. You need to have at least 5 years of experience with all algorithms such as AES, SHA, MD5, Cyrpt etc. (I have been interested in Computers, Software and Hardware since August 2003.)

It is really difficult to explain these to someone who does not know. That's why you can go fishing, take a tour by car, or even travel around the country by boat if you are rich.

I am one of the first people to solve the AES CBC algorithm. For this reason, I do not think of sharing any of my work with anyone who does not deserve it. If you want, even if you give 5 million dollars, it will still be like this.

Nothing in life is random.
Because even randomness includes mathematics.
A little luck, the right time, the right thought, the right hardware etc. etc. but I do not expect people who work in plain logic to understand this anyway.

Now continue scanning straight, only when the time comes, you will learn to respect everyone.

Long-term research, interest in mathematics, and at least 5+ years of experience.

No one says to anyone, "I couldn't eat it. Here you go, eat it."

I think,
I said with some information.

Thans bro.

Non-fancy 400x RTX4090??

I think with some information you can find wallet 67 in 20-30 days. Maybe even less.

from what range you thant start ? My scruot what you help me make downgrade pubkey to 30 bits, from  2^130 to 2^100. Can you brute 2^100 fast ?
..

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..