Features which would require/benefit from a Bisq hard fork #267
Labels
an:idea
https://github.com/bisq-network/proposals/issues/182#issuecomment-596599174
re:processes
was:stalled
There are several ideas around which come with rather large changes and it will be challenging to implement those in a backward compatible way. In fact to achieve that is often a considerable effort. Of course we want to avoid a hard fork as far as possible as it comes wich severe disruption for users. Bisq only had 1 real hard fork so far. There are severl shades of soft/hard fork and we have several tools at hand. But I consider a hard fork here that users basically need to switch to a new application, using a different network and cannot use the old local data (conversion tool can be provided).
Here is an uncomplete list of features/ideas which would be candidates to require or at least benefit from a hard fork:
Some of those projects would be easier and some harder to implement in a backward compatible way. I am not arguing we should run for a hard fork, I just wanted to bring those ideas to attention and start a discussion about the pro and cons.
The text was updated successfully, but these errors were encountered: