Bitcoin Forum
May 06, 2024, 01:57:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Fork, and other problems  (Read 161 times)
Johannson (OP)
Newbie
*
Offline Offline

Activity: 70
Merit: 0


View Profile
April 26, 2018, 01:42:46 PM
 #1

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) ?
1715003842
Hero Member
*
Offline Offline

Posts: 1715003842

View Profile Personal Message (Offline)

Ignore
1715003842
Reply with quote  #2

1715003842
Report to moderator
1715003842
Hero Member
*
Offline Offline

Posts: 1715003842

View Profile Personal Message (Offline)

Ignore
1715003842
Reply with quote  #2

1715003842
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715003842
Hero Member
*
Offline Offline

Posts: 1715003842

View Profile Personal Message (Offline)

Ignore
1715003842
Reply with quote  #2

1715003842
Report to moderator
AdolfinWolf
Legendary
*
Offline Offline

Activity: 1946
Merit: 1427


View Profile
April 26, 2018, 01:52:24 PM
 #2

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)

DannyHamilton
Legendary
*
Offline Offline

Activity: 3388
Merit: 4616



View Profile
April 26, 2018, 01:54:43 PM
 #3

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.
bob123
Legendary
*
Offline Offline

Activity: 1624
Merit: 2481



View Profile WWW
April 29, 2018, 05:32:44 PM
 #4

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  Tongue




@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 ?

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!