diff --git a/frontend/src/app/docs/api-docs/api-docs-data.ts b/frontend/src/app/docs/api-docs/api-docs-data.ts index badd02619..9b0fe5df7 100644 --- a/frontend/src/app/docs/api-docs/api-docs-data.ts +++ b/frontend/src/app/docs/api-docs/api-docs-data.ts @@ -4583,5 +4583,13 @@ export const faqData = [ fragment: "install-mempool-with-docker", title: "Can I install Mempool using Docker?", answer: "Yes, we publish Docker images (or you can build your own). Check out the documentation for details." + }, + { + type: "endpoint", + category: "advanced", + showConditions: bitcoinNetworks, + fragment: "address-lookup-issues", + title: "Why do I get an error for certain address lookups on my Mempool instance?", + answer: "
Mempool uses an Electrum server to do address lookups. There are several implementations of the Electrum server protocol, and Mempool can use any of them.
But the implementation you use affects performance. romanz/electrs is a common choice for its low resource requirements, and most full-node distros use it. While this implementation works great for basic queries, it will struggle with queries to look up addresses with many transactions—especially when run on low-power hardware like a Raspberry Pi.
To remedy this, you will need to power Mempool with a more powerful Electrum server. Consider Fulcrum. Fulcrum requires more resources than romanz/electrs but can still run on a Raspberry Pi and handles heavy queries much more efficiently.
If you have stronger hardware, consider running blockstream/electrs, which is the backend mempool.space uses.
" } ];