Quote from: xeroc on August 29, 2014, 06:23:12 AM

Quote from: Gentso1 on August 29, 2014, 12:38:10 AM
What does it actually take to do a hard fork? 51 delegates?

+ one programmer :)

yes

lol yes a small but important part

Quote from: Gentso1 on August 29, 2014, 12:38:10 AM
What does it actually take to do a hard fork? 51 delegates?

+ one programmer :)

yes

What does it actually take to do a hard fork? 51 delegates?

Hard fork means node software has to be upgraded, as there is some change in the blockchain going forward.  Soft fork just means a software upgrade that will not change the blockchain and thus is not "required". 

So often people can ignore soft-fork updates because their wallet will continue working.

Quote from: Brent.Allsop on August 28, 2014, 06:11:48 PM


People were talking about the 'hard fork' on BitsharesX on the first day.  How do the mechanics of this work?  What was done?

If it's a fork, does that mean a fork in the block chain?...

What types of "forks" are possible, and what are the implications?

Brent Allsop

A hard fork is when code is changed such that a cutoff block has to be established which old clients won't be able to process past, from what I understand. This is why user need to upgrade ASAP to avoid not being able to sync past that block. If you look at this commit you can see the block # constants which each fork has taken place declared as well as being checked against segments of code in IF blocks.

https://github.com/dacsunlimited/bitsharesx/commit/4426a64b7cca9d74f8bcd90ecc78b73713d58700#diff-a8ff4a17487f03f1e51cf382fab75ceeL9

People were talking about the 'hard fork' on BitsharesX on the first day.  How do the mechanics of this work?  What was done?

If it's a fork, does that mean a fork in the block chain?...

What types of "forks" are possible, and what are the implications?

Brent Allsop