-
-
Notifications
You must be signed in to change notification settings - Fork 41
Bucketd ElectrumConnectivity connectivity error when spawned by contract register #225
Comments
Hi @dr-orlovsky, This error occurs because the electrum server pandora.network is not accepting connections, and bucketd "freezes" when try to connect to it. I detected it today when I tried to execute rgb-cli transfer finalize |
Thanks for reporting! I will check what's wrong with the server. You know that the server can be replaced with a command-line option? |
You can pass server parameter when start Would you like me to make this change? |
When bucketd is spawned by rgbd it have this error. Maybe it is because rgbd does not pass the same electrum server that is uses to bucketd and bucketd goes to pandora.network? Btw when I tried pandora.network on rgbd it seemed to work. |
I tested here and the server cannot be accept the connection. Do you tried run Also, you can use some projects to help you tests lnpbp projects, like https://github.com/LNP-BP/nodes/issues and https://github.com/crisdut/lnpbp-regtest |
I changed default electrum server for now to blockstream.info. Will be doing a big update to the code for v0.10 and than will change the way electrum server handled anyway |
Ooh, this ought to be good! I'm looking forward to seeing the solution. Will it be using bp-node, or something else? |
Hopefully BP Node. It is needed for LN as well (for computing short channel ids which can't be handled by neither electrum server nor bitcoin core) |
LFG! 🚀 |
Bucketd when spawned by rgbd when running rgb-cli contract register does not connect to the electrum server giving this error:
thread 'main' panicked at 'running bucketd runtime: AppLevel(ElectrumConnectivity)', src/bin/bucketd.rs:48:26
Instead, when I spawn a bucketd process, with everything as default, before running the command everything works fine.
The text was updated successfully, but these errors were encountered: