Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It has been observed that different API routes declared in different back-end configurations, which makes any one Mempool deploy with a particular backend 'incomplete', i.e. routes that are available in 'esplora' are not available with 'electrum', even though the underlying endpoints work.
An obvsious solution is to merge all routes for all back-ends.
However, it would be good to understand the original reason the Mempool developers decided to split routes the way they have. It seems that the current set-up would only work with at least two instances of Mempool, each with its own backend configuration, deployed at the same time.