Core Lightning — Lightning Network implementation focusing on spec compliance and performance
This point release addresses a [small incompatibility][#7174] in the gossip protocol.
We're pleased to announce the 24.02 release of Core Lightning, named by @ErikDeSmedt. For a list of all changes, please see the changelog.
recover
plugin can now detect dataloss and guide you through the recovery process, making emergency recoveries less stressful.reckless
, our plugin manager, now knows how to create python virtualenvs for each plugin. This allows running multiple plugins with conflicting dependencies. Furthermore it can be told an exact version or commit to install.libwally
which is used for parsing Bitcoin blocks and transaction. It failed parsing a large transaction on testnet. This is now addressed in this release, and we want to encourage everyone to upgrade.gossip_store
file can now be shared with others, since it no longer contains local unpublished gossip.--no-reconnect-private
, which tells lightningd
not to reconnect private peers. This is useful for service-providers and LSPs if the majority of peers is flaky.Since 24.02, we've had 418 commits by 36 authors in 91 days!
A special thanks to the 13 first time contributors, a new record for us:
~ @cdecker, @nepet, @ShahanaFarooqui, @EndothermicDev, @niftynei and @RustyRussell
Release candidate 2 for v24.02
This hotfix release re-introduces a temporary shim that includes the final CLTV delta in the invoice even if the default of 18 is used. This is necessary since the default changed, and for backwards compatibility we were always specifying it. We removed it expecting that all modern implementations had switched to 18 blocks by default, but some did not, and caused payments to fail if the sender still had a default of 9 configured.
This hotfix release addresses an issue where an unexpected message could be delivered to a subdaemon, causing it to abort.
closingd
by sending it a channeld
message (#6937)We're pleased to announce the 23.11 release of Core Lightning, named by @ShahanaFarooqui. For a list of all changes, please see the changelog.
check
command just got more powerful. Instead of only checking the parameters of a command, it will do all checks up to the point where something in the system would need to be altered now.per
for even more powerful access control. This also comes with a new field last_used
for the showrunes
command.decode
command.invoices-onchain-fallback
is set, Core-Lightning automatically adds a taproot fallback address to all invoices produced by invoice
. This allows for onchain payments as a fallback mechanism.large-channels
is now set by default.commitment_signed
now. This allows to continue the funding process after a temporary connection loss.--commit-fee-offset
allows to set an offset that can potentially reduce disagreements on feerate updates.wait
and pagination api got extended, one can now also wait for listsendpays
and listforwards
.recover
command can now be used to recover an unused node from a hsmsecret just as the --recover
flag would do. This currently only works for sqlite3
backends.datastoreusage
command will tell you.--developer-enabled
. To enable developer features use ./configure --enable-debugbuild
and set the config option --developer
instead.Since 23.08, we've had 499 commits by 29 authors in 97 days!
A special thanks to the 5 first time contributors:
~ @nepet, @ShahanaFarooqui, @EndothermicDev, @cdecker, @niftynei and @RustyRussell
Release candidate for v23.11
Release candidate for 23.11