Bitcoin puzzle transaction ~32 BTC prize to who solves it

[bibilgin]

Just to clarify, the hash is computed on the bytes, as shown in the following example, not directly on the hex string or str, because it would be a different hash.

The part I don't understand is this, my friend,

When you convert Public Key to SHA256, can you detect the Wallet address?

The code you sent only gives the address when you write the public key.
After giving the public key, it takes a few seconds to get information about the Wallet.

[mcdouglasx]

Just to clarify, the hash is computed on the bytes, as shown in the following example, not directly on the hex string or str, because it would be a different hash.

The part I don't understand is this, my friend,

When you convert Public Key to SHA256, can you detect the Wallet address?

The code you sent only gives the address when you write the public key.
After giving the public key, it takes a few seconds to get information about the Wallet.

You don't expose the public key, you only expose the hash (sha256). Calculating the private or public key from there would be equivalent to trying to solve the puzzle.

It should display something like this:

Code:

pubkey (hash): 0f715baf5d4c2ed329785cef29e562f73488c8a2bb9dbc5700b361d54b9b0554
Legacy: 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH

for check:

Code:

import hashlib
import base58

def addr(sha256: str) -> str:
    sha256_pubkey = bytes.fromhex(sha256)
    print("SHA256 (hex):", sha256)
    ripemd160 = hashlib.new('ripemd160', sha256_pubkey).digest()
    versioned_payload = b'\x00' + ripemd160
    checksum = hashlib.sha256(hashlib.sha256(versioned_payload).digest()).digest()[:4]
    address_bytes = versioned_payload + checksum
    return base58.b58encode(address_bytes).decode()

sha256 = "0f715baf5d4c2ed329785cef29e562f73488c8a2bb9dbc5700b361d54b9b0554"
address = addr(sha256)
print("Legacy:", address)

[WanderingPhilospher]

Just to clarify, the hash is computed on the bytes, as shown in the following example, not directly on the hex string or str, because it would be a different hash.

The part I don't understand is this, my friend,

When you convert Public Key to SHA256, can you detect the Wallet address?

The code you sent only gives the address when you write the public key.
After giving the public key, it takes a few seconds to get information about the Wallet.

Do you not understand what is being said / wanted?

McD's script is dead on. You enter the actual public key and it spits out what ktimesG is wanting.

it does not give away any info of the actual address.

Do you not understand that?

And you are wrong, McD's script prints out what ktimesG is wanting plus the address.

print("pubkey (hash):", sha256_pubkey.hex())
print("Legacy:", address)

[zahid888]

Just to clarify, the hash is computed on the bytes, as shown in the following example, not directly on the hex string or str, because it would be a different hash.

The part I don't understand is this, my friend,

When you convert Public Key to SHA256, can you detect the Wallet address?

The code you sent only gives the address when you write the public key.
After giving the public key, it takes a few seconds to get information about the Wallet.

Do you not understand what is being said / wanted?

McD's script is dead on. You enter the actual public key and it spits out what ktimesG is wanting.

it does not give away any info of the actual address.

Do you not understand that?

And you are wrong, McD's script prints out what ktimesG is wanting plus the address.

print("pubkey (hash):", sha256_pubkey.hex())
print("Legacy:", address)

Here maybe he can understand...



Hash - 25964f81c375ae9e760d2029292b322e77307adf5786249e74a1ee616fd913b5

You can check every steps here - https://www.rfctools.com/bitcoin-address-test-tool/

Lets exchange..

1MVDYgVaSN6vHMtgWVWDrBF1F5GYPxnXa7 e0b8a2baee1b781264b95a907312d06a7921c0e9 _________________ 95591430
1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ e0b8a2baee1b77fc703455f39d51477451fc8cfc _________________ 3444afe6
^^^^^^^^^^^           ^            ^^^^^^^^^^^^^       ^

[bibilgin]

Now I get it, guys.

Sha256.Publickey

04D3F8B64D154FFF1092E928A6556A0427EDA693537A0ED85691EC36992EBC88


I guess this proves that I have the password to the wallet.

Lets exchange..

I'm in for the swap. Are you in?

[zahid888]

Now I get it, guys.

Sha256.Publickey

04D3F8B64D154FFF1092E928A6556A0427EDA693537A0ED85691EC36992EBC88


I guess this proves that I have the password to the wallet.

Lets exchange..

I'm in for the swap. Are you in?

Check DM.. waiting yours

[bibilgin]

Check DM.. waiting yours

The exchange with Zahid has taken place.

Thank you, Zahid.

[zahid888]

Check DM.. waiting yours

The exchange with Zahid has taken place.

Thank you, Zahid.

In my opinion, this is of no use, but still, I wish Everyone the best of luck

[Akito S. M. Hosana]

What the hell is going on here? I've never seen so many SHA-256 hashes of public keys before

[nomachine]

What the hell is going on here? I've never seen so many SHA-256 hashes of public keys before

There are still Nine quintillion in puzzle 68.  

The Earth has approximately Seven quintillion grains of sand, covering beaches, coastal areas, deserts, riverbeds, lake shores, ocean floors, and sandstone deposits.

[cctv5go]

Is there anyone dumber than me who doesn't know what public key hash 256 is? ha ha

[kTimesG]

Now I get it, guys.

Sha256.Publickey

04D3F8B64D154FFF1092E928A6556A0427EDA693537A0ED85691EC36992EBC88

I guess this proves that I have the password to the wallet.

Finally, 3 attempts later (after getting step by step guides, scripts, and pictures) of what was being asked.

So yeah, I guess I can now apologize for thinking you don't have the private key to that address.

I also guess you could have done this way earlier instead of engaging in e totally useless emotional roller-coaster. But I forgive you - you had no idea how to generate the hash, or of what to generate it. Or even why I asked it, lol. It's ok, bib.

But since you needed like several people to help you understand something so basic, it shows your extensive skills in hash functions, and more generally in how Bitcoin works. I mean, for the love of God, I fear you fail to understand what exactly you are searching in these puzzles, and why. You are just using some tools made by other people, without even knowing how they work.

[White hat hacker]

Lol... Congratulations on wasting your 5 years. The hash function was specifically designed so that there wouldn’t be any pattern or relationship between the private key and the address.

First, go and research how a hash is created in the first place; you will automatically understand everything you talked about is BS. Your research is just nonsense and a complete waste of time. You wasted 5 years trying to find a pattern, but if you had invested those 5 years studying how a hash works, it would have been much better.

I know the hashing process starting from the 02-03-04 relation and going back to the n point combination at which point in the loop.

So understand this well, right now I said it is a valid transaction from 1 to 90 bits.

Now let me 67. I have some things to say to you after the wallet is found. So just wait.

I already told him he wasted his time, energy & electricity. I think he finally got a reality check now 😂

[bibilgin]

Finally, 3 attempts later (after getting step by step guides, scripts, and pictures) of what was being asked.

So yeah, I guess I can now apologize for thinking you don't have the private key to that address.

I also guess you could have done this way earlier instead of engaging in e totally useless emotional roller-coaster. But I forgive you - you had no idea how to generate the hash, or of what to generate it. Or even why I asked it, lol. It's ok, bib.

But since you needed like several people to help you understand something so basic, it shows your extensive skills in hash functions, and more generally in how Bitcoin works. I mean, for the love of God, I fear you fail to understand what exactly you are searching in these puzzles, and why. You are just using some tools made by other people, without even knowing how they work.

Apology accepted. (You don't seem to like apologizing. )

My friend, the problem here is that since my English is weak, I didn't understand why you wanted the sha256 converted version of the public key. lol

As I said, I know the hashing process.
My work is on hex and decimal.
I can calculate the AVERAGE PROBABILITY of which hex range the wallets are in with their prefixes.
For example; I found the 18th 1MVDYgVaSN prefix 45 minutes ago.
It would take months or years to scan all the ranges with my hardware.

That's why I'm focusing on the 1MVDYgVaSN prefixes. After it comes out in the range I calculated, I move on to the next one. To save time.

I already told him he wasted his time, energy & electricity. I think he finally got a reality check now 😂

As I wrote above, as a result of misunderstanding (because of my bad English)
KTimesG wanted - Sha256.Publickey
What I understood - Public Key, Sha256 converted version.
Also, I said it before. I don't have any costs, the hardware works in the office I work in. The company accepting the work and calculations I do = cost-free work.

[mcdouglasx]

Check DM.. waiting yours

The exchange with Zahid has taken place.

Thank you, Zahid.

In my opinion, this is of no use, but still, I wish Everyone the best of luck

I think it's contradictory to exchange prefixes via DM if you consider it a useless search. In principle, it would even be illogical to search for prefixes if they think that way, and even more illogical to keep them as something valuable if that's their belief. Are there doubts? Or is it simply to avoid giving a possible advantage, no matter how remote, to someone else?

Still, I think it's a bit silly to focus on puzzles now in the conventional way. We have competition using farms for both 135 and 68. Although we have statistical advantages with probabilistic methods, we cannot compete against a colossal brute force. That's why I share my ideas, whether they seem good or bad, it doesn't matter. This is just a hobby for me at the moment. The real candidates to succeed are the new "puzzle miners".

[zahid888]

Check DM.. waiting yours

The exchange with Zahid has taken place.

Thank you, Zahid.

In my opinion, this is of no use, but still, I wish Everyone the best of luck

I think it's contradictory to exchange prefixes via DM if you consider it a useless search. In principle, it would even be illogical to search for prefixes if they think that way, and even more illogical to keep them as something valuable if that's their belief. Are there doubts? Or is it simply to avoid giving a possible advantage, no matter how remote, to someone else?

Still, I think it's a bit silly to focus on puzzles now in the conventional way. We have competition using farms for both 135 and 68. Although we have statistical advantages with probabilistic methods, we cannot compete against a colossal brute force. That's why I share my ideas, whether they seem good or bad, it doesn't matter. This is just a hobby for me at the moment. The real candidates to succeed are the new "puzzle miners".

If any of your experiments find this useful, I have no problem sharing the prefix with you. From all the research I’ve done on prefixes so far, the probability still seems to be a balanced 50-50. But if we can refine the approach to push it to even 60-40, that would already be a major step forward—granted that we find a solid logic that makes this shift consistently reliable. In the end, it’s all about exploring possibilities, whether they seem promising or not.

1MVDYgVaSN6vHMtgWVWDrBF1F5GYPxnXa7 e0b8a2baee1b781264b95a907312d06a7921c0e9___________________95591430
1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ_e0b8a2baee1b77fc703455f39d51477451fc8cfc____ _______________3444afe6
^^^^^^^^^^^           ^            ^^^^^^^^^^^^^       ^
1MVDYgVaSN6ApM5LJXriH8cFZkgfCia6Dh e0b8a2baee1b77c2a50d9cc9edf5ea16135e582c___________________08311b2c
1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ_e0b8a2baee1b77fc703455f39d51477451fc8cfc____ _______________3444afe6
^^^^^^^^^^^                        ^^^^^^^^^^^^^^           ^             ^

Someone asked me via DM if this blue hex is the suffix of a private key. Let me clarify: this is the checksum of its corresponding address, not a suffix.

[mcdouglasx]

If any of your experiments find this useful, I have no problem sharing the prefix with you. From all the research I’ve done on prefixes so far, the probability still seems to be a balanced 50-50. But if we can refine the approach to push it to even 60-40, that would already be a major step forward—granted that we find a solid logic that makes this shift consistently reliable. In the end, it’s all about exploring possibilities, whether they seem promising or not.

Thank you, but I would be lying if I told you that I am currently focused on solving the puzzles, mostly because I am busy with other things. However, I am sure that this method is much more efficient than what the pools do, searching the entire range with semi-random points, and just like this, it is also 100% guaranteed to find the target 100% of the time. The technique is to prioritize probability without fear of missing the target because they are just statistics. We cannot leave open flanks or margins of error. When I finish some programming details, I will upload it calmly. Besides, it's not like ideas are supported here; everyone just wants personal success, and they don't realize that this only stagnates everything. The science of puzzles lies in intelligent search.

If someone can solve bit 100 quickly with kangaroo, they can solve 135 in record time using a little ingenuity.

[aby3er]

If someone can solve bit 100 quickly with kangaroo, they can solve 135 in record time using a little ingenuity.
[/quote]

quickly like few minutes or quickly like few hours  ?

[kTimesG]

If someone can solve bit 100 quickly with kangaroo, they can solve 135 in record time using a little ingenuity.

So you went from prob. stat. 90% reduction achievements straight to breaking the DLP sqrt(N) bound theorem, which is proven for 40 years?

The public keys are nothing more than labels, unless one actually breaks the EC math itself. In a N-bit set / interval / whatever, there are 2**N colors. Or 2**N emojis. Or 2**N fruits. Using any kind of binary logic on their index / value / counter has exactly zero relevance, because it is totally relative and can always be rebased to some other base value. This is like saying you have telepathic capacities and can read someone's mind when they think of a color / emoji / fruit.

And it would be a stupid idea to solve 135 using a 100-bit solver, it just increases the complexity terribly, no matter how you approach the problem (splitting to 2**35 100-bit solve steps, introducing statistical non-sense, mixing unicorn algorithms, etc.). Because it would defy the laws of nature to find something that goes below sqrt(N) (on long-term average, not on a lucky hit exception).

[mcdouglasx]

If someone can solve bit 100 quickly with kangaroo, they can solve 135 in record time using a little ingenuity.

So you went from prob. stat. 90% reduction achievements straight to breaking the DLP sqrt(N) bound theorem, which is proven for 40 years?

The public keys are nothing more than labels, unless one actually breaks the EC math itself. In a N-bit set / interval / whatever, there are 2**N colors. Or 2**N emojis. Or 2**N fruits. Using any kind of binary logic on their index / value / counter has exactly zero relevance, because it is totally relative and can always be rebased to some other base value. This is like saying you have telepathic capacities and can read someone's mind when they think of a color / emoji / fruit.

And it would be a stupid idea to solve 135 using a 100-bit solver, it just increases the complexity terribly, no matter how you approach the problem (splitting to 2**35 100-bit solve steps, introducing statistical non-sense, mixing unicorn algorithms, etc.). Because it would defy the laws of nature to find something that goes below sqrt(N) (on long-term average, not on a lucky hit exception).

Your brain, with all due respect, does not allow for intuitive solutions. That is why some of us believe your responses are based on AI. Without knowing what I'm referring to, you complain and attack. You assume too much without understanding what I'm talking about.

That's why Bibilgin humiliated you, you assured that he didn't have the key and he slapped you. You don't give anyone the benefit of the doubt, that's being arrogant, and the most ignorant person is always the one who thinks they know everything.

Next time you want to refute something, at least ask what I mean because I made an assertion but not the how. That way you don't reveal your frustration and need to stand out; you only make yourself look ridiculous. How can someone who considers themselves moderately intelligent refute an idea they don't know? It's like if I said that your ultra-fast Kangaroo code that you promised is impossible, I would never say that because I haven't seen it, nor do I know what your futuristic Kangaroo does to jump to a conclusion.