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

Remove reference to non-functioning BSQ explorer #7041

Merged
merged 1 commit into from Feb 25, 2024
Merged

Remove reference to non-functioning BSQ explorer #7041

merged 1 commit into from Feb 25, 2024

Conversation

ghost
Copy link

@ghost ghost commented Feb 17, 2024

wizbsq

The (@wiz) BSQ explorer is no longer functioning.
Remove it from the list of available explorers.
If a user already had that explorer selected, choose the next available one from the list.

@wiz
Copy link
Contributor

wiz commented Feb 17, 2024

I reported the issue a few times over the years, but I have been unable to upgrade Bisq since ~2 years ago, because it stopped working with external Tor on FreeBSD.

If this is the response then that's great for us, mempool.space will simply stop supporting Bisq.

@ghost
Copy link
Author

ghost commented Feb 18, 2024

Hi wiz! I will look into why Bisq is not working on FreeBSD.

@ghost
Copy link
Author

ghost commented Feb 21, 2024

Hi wiz! I will look into why Bisq is not working on FreeBSD.

I installed FreeBSD and attempted to build Bisq. Unfortunately the gradle/javafx build ecosystem only supports Linux/Mac/Windows. However, it is possible to build on Linux and move the source+jars over to FreeBSD where it will run OK. I successfully ran bisq-pricenode, bisq-seednode, and bisq-statsnode (the latter two using external rather than built-in Tor). I did not try the GUI as my FreeBSD system did not have a windowing environment.

ref: #4419, #2969


So anyway the infrastructure can run on FreeBSD. If there are other reasons why 2/3 BSQ explorers are currently non-functional (and the 3rd having impaired performance), it can be discussed perhaps in a project proposal. (cc @pazza83)

@pazza83
Copy link

pazza83 commented Feb 22, 2024

Hi @wiz It would be great if mempool.space can continue to provide support for Bisq by way of maintaining https://bisq.markets/

Would also be good if all the BSQ explorers showed consistent data. Not sure what would be needed from me, tagging in @Emzy also.

@wiz
Copy link
Contributor

wiz commented Feb 22, 2024

@pazza83 I'm glad that mempool.space was able to develop a proper BSQ explorer for Bisq and operate the bisq.markets website over the years, but it's time to pass the torch on to who wants to takeover this responsibility for the community.

Bisq has a fork of The Mempool Open Source Project up at https://github.com/bisq-network/mempool and I've created bisq-network/mempool#1 that will update the project to the point before we remove Bisq support. Now the maintainers of Bisq can takeover this role of maintaining the BSQ explorer.

@pazza83
Copy link

pazza83 commented Feb 22, 2024

@wiz thanks for developing the explorer and markets website and transitioning things smoothly.

@jmacxx would you be able/interested to run a BSQ explorer for users? Then we could keep with 3 explorers in total?

Copy link
Contributor

@alvasw alvasw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@wiz Thank you very much for running everything over the last years!

Copy link
Contributor

@alejandrogarcia83 alejandrogarcia83 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@alejandrogarcia83 alejandrogarcia83 merged commit 42d40e5 into bisq-network:master Feb 25, 2024
3 checks passed
@ghost ghost mentioned this pull request Feb 29, 2024
@alejandrogarcia83 alejandrogarcia83 added this to the v1.9.16 milestone Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants