Add http://mynode.local:3002 as a bitcoin block explorer

[huey735]

No description provided.

[chimp1984]

I get a page not found

[huey735]

It is an implementation of btc-rpc-explorer that can be run with the Mynode project locally.

[chimp1984]

Ah ok. I guess that might confuse other uses as well... Better might be to add a UI to enter a custom explorer or by prog arg.

[huey735]

I find it unlikely. My guess is that most people don't change the default and those that do, choose one that they're familiar with. Anyways, maybe I can add little disclaimer to the name field
Mynode (requires dedicated node)

[cd2357]

Add http://mynode.local:3002 as a bitcoin block explorer

Or even https://custom-ip-or-hostname:3002

Some people run their own explorer on a raspi or some other host.

But that could be a future improvement.

[cd2357]

How about calling it "Local BTC RPC Explorer"?

"BTC RPC Explorer" is the official name of the explorer project: https://github.com/janoside/btc-rpc-explorer

[cd2357]

But no, its fine, please disregard that, its only a cosmetic thing.

[cd2357]

utACK

[huey735]

@cd2357

Some people run their own explorer on a raspi or some other host.

@chimp1984

Ah ok. I guess that might confuse other uses as well... Better might be to add a UI to enter a custom explorer or by prog arg.

These two suggestions make sense together. Maybe it's worth to add custom field where the user would paste in the url because as @cd2357 said many people run their own block explorer. Be it btc-rpc-explorer, mempool.space, or other.

But implementing that in the UI is beyond my skills.

[dcod3d]

There's already an open issue for using custom block explorer #4371

But IMHO, a non public explorer should not be an option that's built into the app.

[cd2357]

But IMHO, a non public explorer should not be an option that's built into the app.

Why not?

Edit: I mean, Bisq allows people to use their own (non-public) bitcoin node. I don't see why letting them use their own (non-public) blockchain explorer would be a problem.

So from my side: ACK 👍

[dcod3d]

I agree that bisq should allow (even encourage) use of an user's own blockchain explorer. However, hard coding in one company's implementation (explorer/url) isn't the right way to do it.

[sqrrm]

NACK

It doesn't make sense to hard code a link that doesn't work for most people. This should be either a command line argument and/or a text field where the specific explorer could be added.

[huey735]

Better implemented on #4733