Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Custom block explorer #234

Open
mariodian opened this issue Aug 26, 2019 · 2 comments
Open

Custom block explorer #234

mariodian opened this issue Aug 26, 2019 · 2 comments

Comments

@mariodian
Copy link

I think users should have an option of opening onchain transactions in their own block explorers.

There are so many opensource explorers available these days which you can run on your server that people should avoid 3rd party ones.

@ottosuess
Copy link
Member

that's not an easy problem because all block explorers have a different api.
how would the UX of this feature look like?

@mariodian
Copy link
Author

Trezor web lets you add any explorer and if it follows the following scheme then it works, if it doesn't well then it doesn't:

/tx/:id
/block/:hash
/address/:address

To at least partially prevent user from adding bogus explorers, you could check in the background whether the above returns HTTP 200. If not, the explorer won't be added to the list.

I would say regular users will be perfectly happy with blockstream and power users will understand that the explorer of their choice should follow the above schema.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants