Allow the mempool instance for on-chain transactions to be configurable. | ⚫ Alby Hub - 💡 Request a Feature

It would be nice if the mempool instance used to refer to on-chain channel related transactions was configurable. I run my own LND based node, with my own instance of the mempool explorer. I would prefer to be able to open channel on-chain transactions in my own explorer for privacy reasons. At the moment, I have to copy the link, and then copy the transaction id from that link to enter into my own explorer.

Merged posts

Make mempool address configurable

Comments

roland

Feb 9, 2026

This has already been configurable for a long time via env with MEMPOOL_API (default is "https://mempool.space/api")

charbelgereige

Feb 8, 2026

I think this is an important feature to be configurable. In my situation, for some reason I don't know, mempool.space is unreachable from my location, I don't know if it's my ISP that's blocking mempool.space or mempool.space banning my IP, whichever it is, because mempool.space is unreachable, alby hub fails silently to create a channel. Currently I have to run a vpn, so that mempool.pace becomes accessible to be able to start my channel on alby hub.

I have my own instance of mempool.space running against my own node, I would rather have alby hub use my own instance.

Additionally, it would be of great help to bubble the mempool.space being unaccessible error up to the front end... currently it took me a lot of debugging and guesswork to find the root cause of the error!