-
Notifications
You must be signed in to change notification settings - Fork 411
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
Bug: electrs hangs on get_history
#1069
Comments
This is easy reproducible with |
Here is another example with
|
https://mempool.space/address/1NDyJtNTjmwk5xPNhjgAMu4HDHigtobu1s has >1M txs. Currently, electrs will take quite a while to compute the history for such "popular" addresses - since it fetches whole blocks from bitcoind and applies client-side parsing to find the relevant transactions (see https://www.sparrowwallet.com/docs/server-performance.html for more details). |
@su-sd You can use electrs/internal/config_specification.toml Lines 121 to 125 in 831ab0a
|
@romanz |
Reproduced using
electrs log:
|
Describe the bug
I want to get information about addresses (balances, transactions) via a custom script. While getting information of some addresses with a lot of transactions, electrs hangs, while there is no load on the cpu, disk or bitcoind.
Even Ctrl+C and kill does not work anymore.
Electrs version
603830f
Tag v0.10.5
To Reproduce
blockchain.scripthash.subscribe b3308ec9eb6b94b333e6aba375f681ad5a9630e823eb82c68e3f1cc38f9ea3fa
or alternative
blockchain.scripthash.get_history b3308ec9eb6b94b333e6aba375f681ad5a9630e823eb82c68e3f1cc38f9ea3fa
Expected behavior
A response and no hang
Configuration
electrs --ignore-mempool --network bitcoin --log-filters debug
System running electrs
Electrum client
custom script
Additional context
Log file of electrum:
Edit: I know the time-span in the log is short, but it really hangs for hours.
An example address is: 1NDyJtNTjmwk5xPNhjgAMu4HDHigtobu1s
If there is a way to know in advance if a query will hang, it would be a ok-ish workaround for me.
The text was updated successfully, but these errors were encountered: