You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When eclair starts, it checks that it can connect to a Bitcoin Core node, and that this node is "ready" to be used (fully synced). But we don't detect that Bitcoin Core is reindexing which will interfere with our ability to detect that funding transactions are confirmed for example (see #734).
Further to this, Eclair should continue to attempt RPC connections on start-up until told otherwise.
At the moment, on machine boot where Bitcoin Core and Eclair are started at the same time, Eclair fails to connect to Bitcoin simply because it started first and fails on it first and only attempt.
I agree. It throws an error in several conditions that really only call for one or more of:
Getting the user to do something.
Waiting for something to get finished.
Instead of an error, eclair could create an information dialog that updates on what it's doing and a few troubleshooting tips - Waiting for RPC to come available ("Is your Bitcoin client started?") or waiting for indexing to be completed ("Are you connected to the Internet?"). This way the significant time spent during initialization could be skipped. Right now, it seems the only choice is to close and then start eclair again once the conditions have been corrected.
When eclair starts, it checks that it can connect to a Bitcoin Core node, and that this node is "ready" to be used (fully synced). But we don't detect that Bitcoin Core is reindexing which will interfere with our ability to detect that funding transactions are confirmed for example (see #734).
Reported by @Flekoun
The text was updated successfully, but these errors were encountered: