-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Support to run electrs offline #410
Comments
I think the solution for this is the same as for listening during sync. I swear I've seen an issue about it, can't find it right now. |
I agree that this is a useful feature. There are legitimate reasons to run it offline with no internet connection. The check for whether or not it's doing an initial block download is done by bitcoind, not electrs. However electrs then refuses to progress any further until bitcoind says that the initial block download is complete. A workaround while we wait for a fix is to edit src/daemon.rs, and in the function rpc_poll(), change:
to:
|
The reason electrs is waiting for IBD to finish is to make sure it won't "compete" with bitcoind on CPU/IO resources during the IBD process, which is preferable when running on modest hardware. |
Interesting. I think it could be configurable but I'm wondering how much does it even help. At least the blocks which verify signatures are CPU-bound and |
Thanks romanz. I can confirm that it works after putting |
Is your feature request related to a problem? Please describe.
Runnin bitcoind and electrs in an offline machine. No internet. Copy of blockchain on machine for bitcoind. When blockchain is old, maybe some hours, electrs refuse all requests. Message about IBD, initial block download.
Describe the solution you'd like
Option to ignore IBD and serve all requests.
Describe alternatives you've considered
Other option to answer all request when blockchain is out of date would also work.
Additional context
Performance of electrs is excellent in offline machine.
The text was updated successfully, but these errors were encountered: