-
Notifications
You must be signed in to change notification settings - Fork 99
Update to 0.2.0 and minor tweaks #141
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
base: main
Are you sure you want to change the base?
Conversation
|
👋 Thanks for assigning @valentinewallace as a reviewer! |
|
CI sad |
|
Cause ldk 0.2 isn't uploaded yet :) |
valentinewallace
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
7c8461b to
009a548
Compare
Naively update to LDK 0.2 using the sync wrappers to keep current behavior.
5dfcae9 to
3ca27b5
Compare
With LDK 0.2, most traits now offer async variants. In the previous commit we ignored these but here we migrate to them everywhere except in the `ChannelMonitor` persistence. Note that we have to switch to async stdin reading in cli.rs to ensure we always reach an `await` point in a timely manner on all tasks.
29c4033 to
e0ad51d
Compare
Now that we have `ChainMonitor::load_existing_monitor` we can use it during startup to avoid the excess persistence at startup.
Its always been a bit strange that we persist the addresses of our peers to disk when there's a public gossip db, its not really a thing most LN nodes do. It might be useful for private channels but there's not a lot of reason to have it in `ldk-sample`.
|
I'm good with a squash. Also Windows CI is sad |
|
🔔 1st Reminder Hey @valentinewallace! This PR has been waiting for your review. |
No description provided.