REWARD offered for hash collisions for SHA1, SHA256, RIPEMD160 and other

[digaran]

Guess that explains why the following inputs have the same hash:
"ffffffffffffffffffff000000"  ,  "ffffffffffffffffffff00000". =
"02de980e731d160a92b4f41fe07d1b2763f167906db488e4cd380f3936e51ff4". The software I use is a broken open source implementation.😉

[1715019718]

1715019718

[1715019718]

1715019718

[1715019718]

1715019718

[Sha256explorer]

But even if a collision related to sh256 or double sha256 were found, this would not be a problem for Bitcoin.  not for wallet security and not for mining.  Right?

[digaran]

But even if a collision related to sh256 or double sha256 were found, this would not be a problem for Bitcoin.  not for wallet security and not for mining.  Right?

They already exist, we just don't know whether they have been found and are being exploited or not, however if they become publicly known then we'd be sure they can be exploited, thus requiring a major change which will render all miners useless, this is what worries me.

[Jason Brendon]

But even if a collision related to sh256 or double sha256 were found, this would not be a problem for Bitcoin.  not for wallet security and not for mining.  Right?

They already exist, we just don't know whether they have been found and are being exploited or not, however if they become publicly known then we'd be sure they can be exploited, thus requiring a major change which will render all miners useless, this is what worries me.

No, it doesn't exist. If it does, then all the news would say it. If you insist, show me the proof.

[digaran]

No, it doesn't exist. If it does, then all the news would say it. If you insist, show me the proof.

Read back the previous pages, I have explained how to find them with 100% certainty, there is no other proof that I know of, and what I have explained is good for sha256 and rmd160, I was unable to even understand what does (sha256(rmd160) mean, but I know what does sha256 double collision mean, having 2 different inputs generating 2 different first hash but having identical second hash, that's a bit (very) hard to construct a sure method.

However, every problem has not one but many solutions, and in order to find them you need no computational power at first, what you need is to come up with an algorithm to perform a task and then you let the computer to do the heavy work. For now the safety of all hash functions and elliptic curves depend on DLP.
~dig.

[garlonicon]

Do they all operate based on 2 character set hexadecimal or we can hash a single hex character as well?

We can hash single bits.

SHA-256 can technically be used on an arbitrary number of bits that don't divide by 8, but in practice no implementations ever use that feature, and only do full byte sequences.

It depends on implementation. Here we go again: https://sha256algorithm.com/
And it seems I wrote about that before: https://bitcointalk.org/index.php?topic=293382.msg61864044#msg61864044

Edit:

Real example: "1" and "01" give this "4bf5122f344554c53bde2ebb8cd2b7e3d1600ad631c385a5d7cce23c7785459a"

You use identical message. In binary, it is "00000001". In hex, this implementation for some reason use padding to 8-bit values, so better switch to binary values. In general, for every message you have at least one 512-bit block, for example for your message it looks like that:

Code:

01800000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000008

Here, you can see that the raw data is "01", then you have "80", because of that added "1" bit, and then you have a lot of zeroes (padding), and "8" in the end, as the size of the message in bits (not bytes, for that reason you can hash single bits).

[GR Sasa]

I was curious about a question that came to my mind.

I saw a dead wallet address from 2010 which holds about 30,000BTC. Pretty sure either owner is already dead by now, or he's now at least 50 years old. Anyways...

What would happen if someone miraculously hit the jackpot and successfully managed to generate the same hashes that produces the same address that holds the coins?

Can he sells the coins and just change from nothing to Billionaire overnight? Could we try to lock and prevent him from selling the coins that he stoleny illegally took and held?

[digaran]

I was curious about a question that came to my mind.

I saw a dead wallet address from 2010 which holds about 30,000BTC. Pretty sure either owner is already dead by now, or he's now at least 50 years old. Anyways...

What would happen if someone miraculously hit the jackpot and successfully managed to generate the same hashes that produces the same address that holds the coins?

Can he sells the coins and just change from nothing to Billionaire overnight? Could we try to lock and prevent him from selling the coins that he stoleny illegally took and held?

Hash alone is not enough, if he finds a valid private key that has a public key with the same hash as the hash of that address's public key then he can spend them and no one can stop him.