-
Notifications
You must be signed in to change notification settings - Fork 10
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
Labels
Comments
301 redirect from bisq.info Thank you. |
pazza83
added
re:protocol
a:proposal
https://bisq.wiki/Proposals
re:features
and removed
re:protocol
labels
Jul 11, 2024
Nevermind! |
Any update on that project? |
Looks like all is done except deploying a node from this fork. I will do that in the coming days. |
Just an update. I deployed an instance, though ran into a few issues along the way for which I opened a couple PR's. I have a few more changes pending. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: