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

Restore mempool fork #454

Open
2 of 4 tasks
runbtc opened this issue Jun 28, 2024 · 3 comments
Open
2 of 4 tasks

Restore mempool fork #454

runbtc opened this issue Jun 28, 2024 · 3 comments
Assignees
Labels
a:proposal https://bisq.wiki/Proposals re:features

Comments

@runbtc
Copy link

runbtc commented Jun 28, 2024

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

Summary

Since Bisq has been removed from the mempool project, we will now need to maintain our fork which was archived after a PR to merge in the latest upstream changes stalled.

Along with some changes I made to the install scripts, I was able to successfully deploy an instance from the latest commit in that PR, and is currently running at http://runbtcx3wfygbq2wdde6qzjnpyrqn3gvbks7t5jdymmunxttdvvttpyd.onion. So there should not be a lot of work to get the fork up to date and in a functional state.

Action Items

Future Maintenance

Going forward, we will need to maintain the fork on an as-needed basis. Mainly if any worth while functionality or bug fixes are implemented upstream. I am not able to commit to taking ownership of this, but will likely be able to help as necessary.

@clearwater-trust
Copy link
Member

301 redirect from bisq.info

Thank you.

@alvasw
Copy link

alvasw commented Sep 21, 2024

Nevermind!

@HenrikJannsen
Copy link

Any update on that project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:proposal https://bisq.wiki/Proposals re:features
Projects
None yet
Development

No branches or pull requests

5 participants