Quote from: WanderingPhilospher on Today at 02:25:58 AM

Quote from: bibilgin on Today at 01:56:13 AM

Quote from: mcdouglasx on Today at 01:42:39 AM

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. Wink

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.. Wink

But Why do I feel that revealing the SHA-256 of a public key isn’t safe and could be easily guessed, especially if the private key range is known? I’m not entirely sure, but building such a tool wouldn’t be too difficult (I could even make it)—who knows, maybe someone already has! Roll Eyes