Eclair v0.8.0 issues #2517
Replies: 2 comments 7 replies
-
Thanks for the feedback! Let's go through these issues one by one.
This is because we deprecated support for channel updates that don't contain an
That very likely linked to the previous point: we have to do a first pass on the DB to read all previously stored channel updates and drop those that don't contain an
We migrated to a new library for all bitcoin-related tasks that is shared with our mobile wallet: https://github.com/acinq/lightning-kmp
That is linked to the
A new flag was added to channel updates (linked to the If the channel is private, you're not emitting your channel update correctly (and probably previously leaked private channel data to the whole network): if that's the case, you should use the |
Beta Was this translation helpful? Give feedback.
-
Can you push a https://hub.docker.com/r/acinq/eclair/tags?page=1&ordering=last_updated |
Beta Was this translation helpful? Give feedback.
-
I've upgraded my node to Eclair v0.8.0 and run into a few problems along the way.
I would like to discuss, what problems I encountered and if they are worth opening an issue.
1.) Error spam during initial synch with peer
I got thousands of these errors after the upgrade and had to enable sync-whitelist to stop the flood.
2.) Extremely high CPU and RAM usage
The CPU usage is usually very high during start-up and then drops fast afterwards.
After the first start-up it constantly stayed at 200% (2 CPU x 100%) and the Memory usage kept climbing steadily. After like 20 minutes it reached 4 GB and I shut down the node.
I suspected that the node is doing something on the DB and because my DB is so large has problem and runs out of Memory.
I went into DB. Deleted all expired invoices by hand. Increased the Memory for my Node to 8 GB and started it up again.
After another 10 minutes of high resources usage the node finally returned to normal levels.
3.) A lot of changed classed that broke all of my plugins.
Changed class names:
Incompatible code changes:
The hiding of the ShortChannelID behind RealScidStatus
The change of the Constructor for PublicKey
Those changes where all fairly straight forward but it still took me about 3 hours to identify all the correct solutions and change it in all the files.
I have one open problem an this regard. Currently I am unable to create a Channel Update and publish it by hand. I get this error:
2022-12-02 09:00:00,582 ERROR f.a.e.io.PeerConnection SYN n:03423790614f023e3c0cdaa654a3578e919947e4c3a14bf5044e7c787ebd11af1a - private channel update for scid=764005x553x1 was incorrectly added to staggered broadcast
I have not yet figured out, what exactly I have to change in my code.
Beta Was this translation helpful? Give feedback.
All reactions