Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
JimsR
on 11/03/2025, 16:35:29 UTC
I still dont see how skipping is more efficient than scanning everything.
A certain density of X bits prefixes (what you call being lucky) in an arbitrary range has zero impact on the probability of finding something on the next key, or on 100m keys later.
You can think of it this way : since distribution is random, any key can be replaced by any other key. As a result changing the traversal order does not improve odds of success.

Everyone can say that scanning by jumping is not logical.

But I explained that it is possible with PROBABILITY calculation and some data.

Example;
You bought mixed colored candies sold in the market. You prioritize the colors or flavors you like. Then it is up to you to eat or not eat the others.

Actually, the range is within a certain area. But since your hardware power is too much, I understand that you do not want to miss it.

Edit:
I can prove it to you like this.
Send me a few wallets with the prefix 1MVDYgVaS, which are in order. I will tell you in which direction and how far away the nearest 1MVDYgVaSN prefix is ​​on AVERAGE.

You want to prove something like this ?

b71b3ed7348484a74 -> Address: 1MVDYM7EJ783viaKHqnELxmjmChE7r1pqz   -> e0b8a17fadc11deab8283c551a2b7b64afcc82fb
b7b96fbb25f78bd6f   -> Address: 1MVDYN3C8NRQaSkukCurdFjKRDBSEVGAYX -> e0b8a18ecf2119138251d432f6c565f648db4f4a


and continue to the next prefix?
1MVDYgVaSN6iKKEsbyjwnJhmjw8FFcGFWh -> e0b8a2baee1b77fc703455f37934dcda00c9acc0
1MVDYgVaSN6iKKEsbyrjzeEecNkBtnrAYw -> e0b8a2baee1b77fc703455f37f6a9743ac4bb6d4
1MVDYgVaSN6iKKEsbz2NL978m2L1drKTAj -> e0b8a2baee1b77fc703455f388362c96c023dbc1
1MVDYgVaSN6iKKEsbz4MVwBjXREGNsM2w9 -> e0b8a2baee1b77fc703455f38a069c9cac5acaf5
1MVDYgVaSN6iKKEsbz8Ns2ByakjEZR9ScZ -> e0b8a2baee1b77fc703455f38db3b065bdc4ba1a
1MVDYgVaSN6iKKEsbzDYbcWpXTPKPajKQV -> e0b8a2baee1b77fc703455f3926c6ae481234a3e
1MVDYgVaSN6iKKEsbzJUSjn7GFZzjpGbMp -> e0b8a2baee1b77fc703455f396ed249a7d44a59b
1MVDYgVaSN6iKKEsbzLMJFCnBjRxyQM58K -> e0b8a2baee1b77fc703455f398a41cf3cee942c0
1MVDYgVaSN6iKKEsbzN9YUX9yK8skSHq58 -> e0b8a2baee1b77fc703455f39a487fee2fb09828
                                ||
1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ
^^^^^^^^^^^^^^

untill the next Prefix ??