You are viewing a single comment's thread from:

RE: Stahp

in #hive2 years ago

In theory, the problem is only one "team" working on hive code. If multiple would work on it, there would be more conflict.

And more "competition".

I think hardforks on hive are more like auto updates. I'm sure most of the witnesses in total don't look over the code. Even in top 20 I think it's not common to look line by line at the code and try to understand it.

I would really wonder if an HF gets rejected.

Sort:  

Yeah, if there were multiple teams working on it simultaniously, it would likely be a different process. Both teams would work on their own branch and try to offer two different, probably very small implementations, with probably very different priorities.

Then, if one branch is activated, the other team will have to merge that branch into theirs, or adopt the winning branch, which will likely knock them out of contention for a very long time.