Prep for the hackathon: running regtest locally

[andresgalante]

We'd like the locally running stack-explorer to direct to the locally running regtest blockchain explorer instead of the default testnet blockchain explorer.

We've prepped the sBTC repo for the hackathon with a devnet, where within this devenv directory the hackers can spin up a docker compose file that launches a bunch of services. You can give it a look here: link

When we use the stacks explorer locally clicking on the bitcoin block number directs us to the default testnet blockchain explorer. We'd like it to connect to the explorer that shows the regtest bitcoin block. This would only be relevant when the stacks explorer is running locally so I'd think an environment variable or configuration for the container running stacks explorer would be sufficient.

There is a video of the issue here https://github.com/hirosystems/explorer/assets/1832037/78ad310b-0ce3-4bc3-bcc6-18f54f73d0bc

And an branch with an (unfinished fix) has been started here: https://github.com/EmbeddedAndroid/explorer/commits/cfg-btc-endpoint

[He1DAr]

We can customize the base BTC explorer URL (https://mempool.space/block/https://mempool.space/block/testnet) using an environment variable. Additionally, we can introduce a new optional field "BTC explorer base URL" when adding a custom network, so the final BTC block URL would look like: ${BTC_EXPLORER_BASE_URL}/${btcBlockHeight}

[EmbeddedAndroid]

We can customize the base BTC explorer URL (https://mempool.space/block/https://mempool.space/block/testnet) using an environment variable. Additionally, we can introduce a new optional field "BTC explorer base URL" when adding a custom network, so the final BTC block URL would look like: ${BTC_EXPLORER_BASE_URL}/${btcBlockHeight}

This sounds like a good solution to me, thanks for the consideration!

[He1DAr]

@EmbeddedAndroid here's the PR #1306, also deployed to dev https://explorer.dev.hiro.so/?chain=mainnet
Please let me know if you have any suggestions. I'm looking forward to your feedback!

[blockstack-devops]

🎉 This issue has been resolved in version 1.126.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀