We're pleased to announce the 0.10.2 release of c-lightning, named by @vincenzopalazzo.
This is a recommended upgrade: this release includes the patch for the recently disclosed CVE-2021-41592.
Highlights for Users
- Payments can now be retried without affecting the status of prior attempts.
- The route selection will now use the log-propability-based channel selection to increase success rate and reduce time to completion.
close
now reports the feeranges each side enforced, which allows users to determine which side caused a high or low feerate.- Removal of old HTLC information and vacuuming shrinks large lightningd.sqlite3 by a factor of 2-3.
Highlights for the Network
setchannelfee
now has a grace period during which both old and new fee policies are considered. This prevents a fee update from making the channel unusable until the update propagated.- We now perform quick-close if the peer supports it.
- We send regular pings to detect dead connections (particularly for Tor).
- Errors returning a channel_update no longer return an outdated one.
- Anchor output mutual close allow a fee higher than the final commitment transaction
Highlights for Developers
- Plugins now are notified about an upcoming shutdown, allowing them to store data and clean up before exiting.
- The datastore API (
datastore
,deldatastore
, andlistdatastore
) exposes a simple key-value store, allowing plugin authors to store data in the c-lightning database. ping
now only works if we have a channel with the peer.- Relaxed the sqlite3 version match requirements to be at least a minimum version and a major version match
More details can be found in the changelog.
Thanks to everyone for their contributions and bug reports; please keep them coming.
Since 0.10.1, we've had 333 commits from 19 different authors over 85 days.
A special thanks goes to the 4 first time contributors:
- Dustin Dettmer
- Michael Folkson
- jerzybrzoska
- Devrandom
Cheers,
Christian, Rusty, Lisa.