Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Features which would require/benefit from a Bisq hard fork #267

Closed
chimp1984 opened this issue Oct 20, 2020 · 2 comments
Closed

Features which would require/benefit from a Bisq hard fork #267

chimp1984 opened this issue Oct 20, 2020 · 2 comments
Labels
an:idea https://github.com/bisq-network/proposals/issues/182#issuecomment-596599174 re:processes was:stalled

Comments

@chimp1984
Copy link

chimp1984 commented Oct 20, 2020

This is a Bisq Network proposal. Please familiarize yourself with the submission and review process.

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.

@MwithM MwithM added an:idea https://github.com/bisq-network/proposals/issues/182#issuecomment-596599174 re:processes labels Oct 23, 2020
@RefundAgent
Copy link

These are important improvements. E. g. DDOS-attacks could kill Bisq and need to be prevented. Bisq is presently growing by about 5-10%/month by trades and any hard fork should be done early rather than late.

@ripcurlx
Copy link

I think those are all great ideas to improve Bisq, even if it requires a hard fork. But I think the bigger threat that is slowly approaching are the rising mining fees, that might make Bisq not feasible anymore for small trades. I do know that we ran into a dead end with the off-chain protocol, but I guess we have to put all our brainpower to alternative solutions sooner than later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
an:idea https://github.com/bisq-network/proposals/issues/182#issuecomment-596599174 re:processes was:stalled
Projects
None yet
Development

No branches or pull requests

5 participants