Bitcoin puzzle transaction ~32 BTC prize to who solves it

[AlanJohnson]

I am silently watching and learning from all you guys that have been in this space for quite some long time and doing the puzzle, but again and again people say you need to find more than one or that. What exactly does that mean? Is it if someone has multiple addresses with private key in 69bit range that starts with 19vkiEajf, does it help to achieve goal faster

No it doesn't  but some people don't like the truth cause it's too brutal for them.

[Bram24732]

Got bored this morning so I wrote a little snippet which looks for a value in a uniform space.
It does it using both methods :

• Sequential random (i.e. the one I use)
• Prefix based, I believe this is the WP version, but the code can easily be adjusted to your flavor of prefix optimization.

By defaults it runs 1000 simulations of a search in a 100M elements space with a range of 100k.
This is exactly equivalent to the 69 problem in terms of statistics. Just simpler because it uses integers instead of hashes, so we can run many more simulations for cheap.

How to run :

Code:

Have nodeJs installed on your machine.
Download script
Run "node prefixVsSequential.js"

Results, as you can see there is very little deviation. The more simulations/bigger ranges you run, the closer both values will be to 50% :

Code:

Average match percentage for random sequential method : 49.63%
Average match percentage for prefix sequential method : 52.35%

Link to script :

Code:

https://gist.github.com/Kowala24731/e9a52fcf08b14934a5e8e96ae967c729

You can change those parameters to update number of simulations / size of problem / ranges / percentage of deviation before skipping a range

Code:

const PREFIX_DEVIATION = 1.35;
const TOTAL_SIZE = 100_000_000;
const RANGE_SIZE = 100_000;
const NUMBER_SIMULATIONS = 1000;

[bibilgin]

Up.

I am calling out to everyone from here. This is an example.

The first prefix you find is similar to "19vkiEajfh" wallets,

78000000000009990000 - 7890000000000990000 between decimal difference, it does not matter whether it is above or below.

You will find at least 1 more wallet starting with the prefix 19vkiEajfh.

Note:
1- 7800000000000999000 - 78900000000000990000 is not a decimal that remains constant.

2- After the similar prefix wallet found in the range of 78000000000009990000 - 78900000000000990000, there are several different decimal differences for the other first 10 prefix similar wallets.

Important; After finding a 10 similar prefix wallet, I analyze 30+ decimal differences and find the other 10 prefix similar wallets. Then I calculate the common decimal values ​​of the wallet I found and the previous wallets I found.

Question to you,
Can you tell me the method to find John without knocking on 10 thousand doors?
My method is to ask the region of the other after finding any John.

I repeat it again and again. This is not a Sha256, h160, base58 or anything else. It is the calculation of the next hash range of each created hash. (Decimal range values ​​more than 30+ are important.)

[Bram24732]

Question to you,
Can you tell me the method to find John without knocking on 10 thousand doors?
My method is to ask the region of the other after finding any John.

Does the fact that a John lives somewhere have any impact on where the actual John lives ?

[POD5]

Have you try With Non Standard Decoding Like a, heuristic Methode  - checksum-ignored Base58 decoding.
it can be faster.

Do you have GITHUB? 

[bibilgin]

Does the fact that a John lives somewhere have any impact on where the actual John lives ?

Does John live somewhere? Yes.

Does this living situation indicate where he actually is? Yes.

So the fact that he lives somewhere indicates that he is already there; so the living situation does not change his actual location, it merely expresses it.

[Bram24732]

Does the fact that a John lives somewhere have any impact on where the actual John lives ?

Does John live somewhere? Yes.

Does this living situation indicate where he actually is? Yes.

So the fact that he lives somewhere indicates that he is already there; so the living situation does not change his actual location, it merely expresses it.

I don't understand what you're saying I'm sorry.

[bibilgin]

I don't understand what you're saying I'm sorry.

The question you asked has 2 perspectives.

Reality = Where John lives is the situation as it really is. In other words, if John really lives in Türkiye, this situation reflects a reality in the outside world and this reality exists independently.

Knowledge = Saying "where John lives" is valid if the reality is where he lives. But it does not change where John really lives right now.

I don't know which answer will make you happy.

Here, we don't need to confuse many people in a philosophical, ontological, epistemological cycle. It is enough to tell the answer to the question I asked and which method you will use.

There was an article that I mentioned before and you also mentioned.

I = Every brave man eats yogurt differently.
You = We all have different learning/understanding abilities.

[kTimesG]

Up.

I am calling out to everyone from here. This is an example.

Can you tell me the method to find John without knocking on 10 thousand doors?
My method is to ask the region of the other after finding any John.

I repeat it again and again. This is not a Sha256, h160, base58 or anything else. It is the calculation of the next hash range of each created hash. (Decimal range values ​​more than 30+ are important.)

- Telepathy - call up John via brain waves / tachyons to share location.

- Remote viewing: don't knock, see through. Requires specific genetic skills (CIA leaked it?)

- Quantum entanglement: spin up the quarks and get the door number; need John's quantum signature / state at some point in time and space in advance.

- Multiverse interpretation or multiworld: collapse the correct door by observing all doors at once. Requires Infinity rings.

- Proximity bias [© mcdouglasx] - piss on the very basic definitions and properties of ECC arithmetic / hash functions. Avalanche effect? Nope. Independent doors? Nope. After all, we've all been living next door to Alice for 20 years, right? Immutable before you even open the doors. Call people AI / NPCs / FUD? YES!

[AlanJohnson]

It seems like some people here wants to solve it so badly they become mental and starting  to see things and connections that aren't really there...

[benjaniah]

I found this exact prefix '19vkiEajfhu' within the 69-bit range, but from what I've read from more knowledgeable people on the forum, it may not have much significance idk. I'm just a hobbyist

You need to prove the 19vkiEajfhu prefix you found.

Otherwise, you won't be listened to much.


Edit;

After scanning 9000 trillion keys for the actual address (the good hash) of Puzzle 69, there was still no 53 bits or larger prefix found.

61eb8a50c86b0584bb727dd65bed8d2400d6d5aa

H160 - Is the first 61eb8a50c86b0 the one you mentioned as 53 bits?

If that's what you mean, I have it.

Freebie for all you prefix hunters.
While you guys were scanning hundreds of trillions of keys for a 53 bit prefix match, I found one using grep on the Loyce Club All BTC addresses list.
Used by someone on Nov 20, 2024, a few days after 66 was solved. The pubkey is there so the private key can be found in a few seconds.
https://mempool.space/address/19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS
Newbie Disclaimer: This information is for entertainment purposes only, and cannot and will not aid you in your search for the prize, no matter how strongly you believe so.

[kTimesG]

The pubkey is there so the private key can be found in a few seconds.

How?

[vneos]

The pubkey is there so the private key can be found in a few seconds.

How?

000000000000000000000000000000000000000000000017724AFA4320DAF4A7

He assumed the address was within 69.

[JimsR]

Have you try With Non Standard Decoding Like a, heuristic Methode  - checksum-ignored Base58 decoding.
it can be faster.

Do you have GITHUB? 

i dont have Github, my program is not Final. your CPU will melted, need to run with GPU.
https://drive.google.com/file/d/1oe_VWof79mFiHTqXW8sTp2RTpvW0UZrk/view?usp=sharing

[POD5]

i dont have Github, my program is not Final. your CPU will melted, need to run with GPU.

Never run your hardware at maximum speed for a long time, in order to spare it...
And 100k keys/second it not much for 12 cores.

[brainless]

My guess is 69 key is even
Redesign your search work

[CriptoGiga]

The pubkey is there so the private key can be found in a few seconds.

How?

000000000000000000000000000000000000000000000017724AFA4320DAF4A7

He assumed the address was within 69.

Good morning, but how did you get the private key for address 19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS, having only the public key?

[Bram24732]

so you were going to prove that I was wrong, someday?

The arrogance is astounding.
You probably have to chage 20 or so lines of code to accomodate the script to your theory and run it by yourself, but you wont.
If this does not change your mind, nothing will and I wish you all the best.

[CriptoGiga]

#Has anyone ever searched for hidden messages within hashes?

import base58

addr = '18bsqCiFJRy6iLQuomV9uQWuJG2TCzkK3h' 
h160 = base58.b58decode_check(addr)[1:]
print (h160)

addr = '1Ax1Ske5KLG8NuBbhVQ3594DViop8RMPUC' 
h160 = base58.b58decode_check(addr)[1:]
print (h160)

addr = '1BX5TLkQe5YEHYfQAFXEKnWgVmqTSGZhsF' 
h160 = base58.b58decode_check(addr)[1:]
print (h160)

[Bram24732]

so you were going to prove that I was wrong, someday?

The arrogance is astounding.
You probably have to chage 20 or so lines of code to accomodate the script to your theory and run it by yourself, but you wont.
If this does not change your mind, nothing will and I wish you all the best.

20 lines, lol, I just want to make it clear that you shouldn't criticize without knowing. I don't criticize anyone's ideas here, so why would you come and criticize mine? If it's 20 lines, why didn't you do it? That was your main purpose, wasn't it?

I did not do it because it will never be good enough to convince you. I realize that now.
If it shows no improvement over random, you'll say it's because its numbers and not private keys..
if I change it to be private keys and your method, you'll find another way to dismiss it, and so on.
To be honest I'm quite sure you didn't bother reading it or running it. So well, you win this argument Enjoy !