Releases: ElementsProject/lightning
24.05 - The Infinitely Divisible Satoshi
We are pleased to announce the v24.05 release of Core Lightning, code named "The Infinitely Divisible Satoshi" - named by CLN contributor @daywalker90. For a full list of the changes, please see the changelog
Highlights for Users
- New rune restrictions can now be applied to invoices with the
pinv
restriction! - Documentation is more thorough and up-to-date as much of it is now generated from the schemas.
- Stability fixes to gossip and anchor channel spends.
- Increased file descriptor limits for large nodes.
- Pruned node operation is better supported by bcli with more robust block fetching.
Highlights for Developers
- A plethora of grpc methods have been backfilled!
Pay
can now pay part of an invoice with thepartial_msat
parameter. Get someone else to pay the remainder!Check
can now be used to validatesetconfig
settings and values. It can also check for approval by the hsmd of keysend payments.
Highlights for the Network
- Offers will now make an outgoing connection if necessary to reply to an invoice request.
- Offer invoices now correctly use the
node_id
and the final cltv delta in blinded paths.
Since the 24.02 release, there have been 380 commits in 109 days by 21 authors!
A special thanks to three first time contributors!
@Se7eNz
@snoppy
@bstin
~ @endothermicdev, @cdecker, @nepet, @ShahanaFarooqui, @niftynei and @rustyrussell
v24.05rc2
release candidate 2 for v24.05
v24.05rc1
release candidate for v24.05
24.02.2 - 2024-04-06: "uint needs signature"
This point release addresses a [small incompatibility][#7174] in the gossip protocol.
v24.02.1 -- uint needs signature
v24.02 uint needs signature
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.
Highlights for Users
- The
recover
plugin can now detect dataloss and guide you through the recovery process, making emergency recoveries less stressful. - The logic of the anchor channels has been overhauled and channel fundings and closing should now be more flexible and reliable.
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.
Highlights for the Network
⚠️ This release includes a patch forlibwally
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.- Dual-funding has been merged into the Lightning Specification! This is a major milestone for more efficient channel management.
- The
gossip_store
file can now be shared with others, since it no longer contains local unpublished gossip. - Optimizations in the way we process blocks means that we can sync with the blockchain 50% faster than before
Highlights for Developers
- CLN now has a
--no-reconnect-private
, which tellslightningd
not to reconnect private peers. This is useful for service-providers and LSPs if the majority of peers is flaky. - The newest version of the splicing proposal was implemented. Though experimental we encourage anyone to try it out, as it informs the specification process as well.
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:
- @vacwmX
- @evansmj
- @saisuraj27
- @yaslama
- @Vayras
- @ssantos21
- @singlebeam
- @shuoer86
- @royalpinto007
- @ok300
- @Harshit933
- @gkrizek
- @bitcoin-lightning
~ @cdecker, @nepet, @ShahanaFarooqui, @endothermicdev, @niftynei and @rustyrussell
v24.02rc2
v24.02rc1
v23.11.2 Bitcoin Orangepaper
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.
Fixed
- Default bolt11 invoices are payable by LND nodes.