v23.11: Bitcoin Orangepaper

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.

Highlights for Users

• The 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.
• Control all the runes! Runes got an additional restriction field per for even more powerful access control. This also comes with a new field last_used for the showrunes command.
• Users can now verify the validity of their existing emergency backups using the decode command.
• When the new config option 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.

Highlights for the Network

• Wumbology for all! The configuration option large-channels is now set by default.
• The dual-funding process stores the state when sending commitment_signed now. This allows to continue the funding process after a temporary connection loss.
• A new flag --commit-fee-offset allows to set an offset that can potentially reduce disagreements on feerate updates.
• Plugins can now allow even unknown messages by registration and also are allowed sending them.
• Some stability improvements and bugfixes regarding splices.
• A whole lot of cleanups to stay on track with small specification changes. This adds additional stability and reduces disconnects.

Highlights for Developers

• Wait a second: The wait and pagination api got extended, one can now also wait for listsendpays and listforwards.
• A new 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.
• Ever wondered how much space a plugin occupies in your database? The new datastoreusage command will tell you.
• The rust bindings got some more coverage.
• Core-Lightning can no longer be build with --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:

• Mariusz Kogen
• dergoegge
• Tony Giorgio
• maxwedwards
• hMsats

~ @nepet, @ShahanaFarooqui, @endothermicdev, @cdecker, @niftynei and @rustyrussell