-
Notifications
You must be signed in to change notification settings - Fork 433
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
electrs logs report "less efficient method of querying" electrs server #652
Comments
I guess ignore the warning then? Anyway, may be interesting if we had some alternative notification mechanism so that electrs could wake up the app (e.g. by POSTing to some notification server). This would require extending the protocol and maybe even authentication. What do you think @romanz? |
I prefer to refactor the code so the index-related functionality will be in a seprarate crate from the RPC-related functionality. |
Is there a timeline on when this will be worked upon? |
I'm seeing the same logs with Sparrow wallet |
I'm getting many log messages reporting this while using Liana wallet. I opened an issue with Liana so they are aware they are using a "less efficient method of querying" electrs: wizardsardine/liana#1574 It looks like Liana uses the bdk client library and that project knows of this issue
But I'm getting thousands of these log messages from electrs with Liana open for an hour or so. Not a major issue, but it might be nice to rate limit that log message to keep the duplicate log lines from making it difficult to find or notice other log messages. |
We have an issue: BlueWallet/BlueWallet#4336
Probably electrs wants us to always connect, keep connection alive and subscribe to all scripthashes we are interested in.
In BW we dont subscribe, as user sessions might be very short, so we try our best to quickly connect, query about scripthashes, and then dont care if user terminates the app or connection closes (which happens when user suspends the app on iOS. OS simply closes all sockets of suspended apps)
The text was updated successfully, but these errors were encountered: