|
Title: Fork, and other problems Post by: Johannson on April 26, 2018, 01:42:46 PM A Fork is the same as a collision? How many technical problems do you know about, and which one is the most dangerous ( with Bitcoin) ?
Title: Re: Fork, and other problems Post by: AdolfinWolf on April 26, 2018, 01:52:24 PM A Fork is the same as a collision? How many technical problems do you know about, and which one is the most dangerous ( with Bitcoin) ? What do you mean with collision? Key collision? If so, no, a fork is entirely different, and the two are barely (if not) related. Also, i'd say that a key collision isn't really a problem. Although it is possible, it is extremely unlikely to happen on the regular. See https://bitcoin.stackexchange.com/questions/7724/what-happens-if-your-bitcoin-client-generates-an-address-identical-to-another-pe Also, ( soft/hard) forks aren't a "danger" for bitcoin per se. More often than not they're done to improve the state of the bitcoin network. (SW) Title: Re: Fork, and other problems Post by: DannyHamilton on April 26, 2018, 01:54:43 PM A Fork is the same as a collision? No. There are multiple types of forks. (Soft chain fork, Hard chain fork, code fork ,etc). You need to explain which type of fork you are asking about. None of them have anything to do with collisions. I'm not sure what type of collision you are asking about. Are you asking about hash collisions or communications collisions? As far as I am aware there have never been any instances of a hash collision with SHA256 or RIPEMD160. How many technical problems do you know about, and which one is the most dangerous ( with Bitcoin) ? Most dangerous? Uneducated users. Title: Re: Fork, and other problems Post by: bob123 on April 29, 2018, 05:32:44 PM How many technical problems do you know about, and which one is the most dangerous ( with Bitcoin) ? Most dangerous? Uneducated users. Uneducated user fall under the non-technical category :P @OP: A fork is not a 'technical problem'. A fork (in terms of soft-/hard- fork of the network) describes the 'status of the consens'. This is not directly technical. And a code fork is simply just 'copying' the code at a specific time (and eventually changing things), creating a new version. You have to be more specific regarding collisions. What exactly is your concern/question ? |