Quote from: AgentofCoin on January 07, 2017, 09:17:07 PM

-snip-

Quote from: shorena on January 07, 2017, 07:39:57 PM

-snip-
Id say the collision happened even when no one noticed it. Shit already broke you just didnt realize it yet. Whoever sends coins to the address in question first will reveal the information to the other person also in control.

Not according to quantum theory.

Storing data on a disk is not a quantum thing though. Even if, the data was stored at the very least in memory by a machine and thus it was observed. Furthermore it was not only observed but also modified and stored.

Quote from: Lauda on January 08, 2017, 11:00:22 AM

Quote from: RawDog on January 08, 2017, 04:59:23 AM

Your dumb fucking idea relates to finding the key to 1 specific address. I am looking for the key to any of millions addresses that have bitcoin stored on them. So, my problem is much, much, much easier than your stupid problem.

Wrong. The 'fastest' method would be a birthday attack, and you still need O(n/2) operations (i.e. 2^128 operations for SHA256 if you had enough memory). Just because you aren't looking for a specific key to collide with, that doesn't really make it likely to find a collision in this case.

Quote from: SaltySpitoon on January 08, 2017, 05:23:34 AM

Nope. 300 million seems like a lot until you realize billions, trillions, quadrillions, octodecillions are nothing compared to the probability of a collision.

Let's add some numbers in here:

Quote

In order to spend money sent to a Bitcoin address, you just need to find a ECDSA public key that hashes to the same 160-bit value. That will take, on average, 2^160 key generations.

Supposing you could generate a billion (2^30) per second, you need 2^130 seconds.

Doing this in parallel using a billion machines requires only 2^100 seconds.

Getting a billion of your richest friends to join you gets it down to only 2^70 seconds.

There are about 2^25 seconds per year, so you need 2^45 years.

The age of the Universe is about 2^34 years so far better get cracking!

Source.

Your source is ~~wrong~~ slightly off as it ignores the birthday paradox. Due to it, on average you have found a collision after checking half of the keyspace with almost certainty. Thus you only need 2^159 key generations. Not that it changes the numbers in any significant way.