We're pleased to announce the 0.9.2 release of c-lightning, named by Sergi Delgado.

This is a significant release with new CLI-level notifications, better channel state reporting, and stable plugin-hook call ordering.

Note that as of this release c-lightning-generated PSBTs are only considered valid by bitcoind v0.20.1 and above.

Did you know: c-lightning deprecates features with 6 months warning, and you can set allow-deprecated-apis=false to test?

Highlights for Users

• We now keep track of channel closure rationales. Wonder "why did my channel close" no more. All channel state changes are now listed in listpeers's state_changes.
• NEW CLI/RPC notifications! Tired of waiting for close to finish without getting any updates? With notifications, the close command will publish notifications (think CLI status updates) for slow closes. Must have allow-deprecated-apis set to false for these to work.
• New optional argument commitment_feerate on the multifundchannel command. This is useful for setting one feerate for the funding transaction and another for the channel commitment transactions.
• Two new commands added to hsmtool!
  • generatehsm allows you to create an HSM hsm_secret from a BIP39 pass phrase. (Note that due to c-lightning's current seed derivation process, wallet addresses aren't standard 'BIP39 to BIP32' compliant. Which is a fancy way of saying your pass phrase isn't portable to other, non-clightning wallets.)
  • dumponchaindescriptors will output the xpub for the HD wallet master key. This will let you track swept c-lightning wallet funds – anchor outputs and unswept channel outputs won't be visible until swept.
• The starting feerate for mutual closes has been reduced to 'slow', to avoid overpayment.
• In-memory log buffer now is 10MB, down from 100MB.

Highlights for the Network

• We no longer support receiving full gossip from ancient LND nodes
• Fixed re-transmission order of multiple new HTLCS. This was causing channel closures with LND.

Highlights for Developers

• Plugin hook call ordering. Hooks can now specify that they must be called 'before' or 'after' other plugins.
• pyln-client will handle and send RPC command notifications.
• pyln-proto now includes a pure python implementation of the sphinx onion creation and processing.
• PostgresSQL key-value DSNs now supported.
• Plugin hook htlc_accepted can now return a custom failure_onion.

More details can be found at https://github.com/ElementsProject/lightning/blob/v0.9.2/CHANGELOG.md

Thanks to everyone for their contributions and bug reports; please keep them coming.

Since 0.9.1, we've had 321 commits from 15 different authors over ~58 days, an average commit rate of 5.5344 commits per day.

A special thanks goes to the 4 first time contributors:

• YOSHIDA Masanori @siburu
• @grubles
• Jordi Montes @positiveblue
• @lakshit24

Cheers, Lisa, Christian, Rusty, ZmnSCPxj

• includes https://github.com/LedgerHQ/ledgerjs/releases/tag/v5.31.0 (Upgrade ERC20 list)
• enable all fiats
• Add new errors for satstack node config validation and handling of some specific status (pending-scan)

• bugfixes in cosmos error ids
• small refinement in satstack logic, better errors, check in prepareTransaction

• XRP fixes

• XRP fixes
• naming: SatsStack -> SatStack

• Tron sync performance
• XRP fixes
• Swap fixes for edge case ( https://github.com/LedgerHQ/ledger-live-common/pull/953 )

Complete countervalues rework

This is a breaking changes.

We have completely reworked the way countervalues logic works as well as moved to a new Countervalues API. It have better performance, better accuracy and coverage of countervalues. We fixes through this many known issues like some fiat support missing (AUD for instance), many erc20 countervalues price missing, hole or peaks in the data,… We also add some features like hourly granularity.

Technically, everything has changed: we no longer are expecting the user land to have redux and this logic can in fact be used (and is used) by the CLI. In term of React integration, we have defined some React hooks to solve classical usecases (like calculating countervalues).

This will be documented soon in https://github.com/LedgerHQ/ledger-live-common/blob/master/docs/countervalues.md

You can see these PRs as reference: - live-common https://github.com/LedgerHQ/ledger-live-common/pull/892 - live-desktop https://github.com/LedgerHQ/ledger-live-desktop/pull/3194 - live-mobile https://github.com/LedgerHQ/ledger-live-mobile/pull/1410

quit app logic

The quit app mechanism is now active by default for everyone. During device flows, the device will automatically quit the app when another app is needed (e.g. receive,send,add accounts) or when we need the dashboard (e.g. manager). It makes the whole experience really smooth in worse case scenario: if my device is in the Litecoin app and i need to add Bitcoin accounts, the only thing i need to do on my device is to accept the opening of Bitcoin. If the device is locked, we also will correctly handle the fact that it would get correctly restored and potentially would automatically close Bitcoin and intent-open again in case of 0x6f04 which can happen when device is locked (it's a tradeoff until firmapps address it).

Algorand fixes

To fix LL-3497, we made sure that optimistic operations were working for ASA transactions. This also shall make the parent transaction a "FEE" operation.

ripple-lib upgrade

We have upgraded ripple-lib. No changes expected, things should work as normally.

Others

• Add ANALYTICS_CONSOLE env
• update eth-sig-util
• bot fixes

🚀 Features

• Sell Bitcoin through our partner.
• Added countervalues to the summary when sending crypto.

🐛 Fixes

• Remove BCH fork banner.
• Various improvements in user experience.

• hw-app-eth: fixes Cannot read property 'length' of undefined issue when trying to use some of the new methods using U2F.
• latest ERC20 updates ( https://github.com/LedgerHQ/ledgerjs/commit/49eb08c2c940d983d950985f0d9345d93da5adfd )

• rollback node-hid version ( node-hid/node-hid#398 (comment) )

• Upgrade ERC20 list https://github.com/LedgerHQ/ledgerjs/commit/23648c726b328334705da5d4cd9eccb45f4cba80
• Upgrade build libs (babel, eslint, typescript, prettier)
• Attempt to upgrade node-hid (was reverted in 5.31.1)

ETH 2 deposit contract API (@ledgerhq/hw-app-eth)

see https://github.com/LedgerHQ/ledgerjs/blob/master/packages/hw-app-eth/README.md

• eth2GetPublicKey(path: string, boolDisplay?: boolean): Promise<{ publicKey: string }>
• eth2SetWithdrawalIndex(withdrawalIndex: number): Promise<boolean>

maintenance

• update flow, rollup, uglify-js, typescript

Important security fix

• Due to a privacy leak vulnerability, users of the payment button are strongly encouraged to update as soon as possible.

New features

• Add QR code scan/show for PSBT + Import wallet via QR spec (supported by Cobo vault / Blue wallet) (#1931)
• Checkout experience: Unified QR Code for on-chain and offchain payment (ref #2060) (@rockstardev)
• Greenfield: Clean webhook API github-like (ref #2058) (@NicolasDorier @Kukks)
• Greenfield: Can query invoice payment data (@Kukks)
• Allow users to select block explorers from a list or specify their own URL (@Kukks)
• Allow disabling live notifications globally and disabling specific notifications per user (ref #1991) (@Kukks)
• Allow custom redirect_url for PoS (ref #1924) (@mariodian)
• A new experimental plugin system (@Kukks)

Improvements

• UI: Make store setup more intuitive (ref #2011) (@dennisreimann @dstrukt)
• UI: Improve payment request design (ref #2011) (@dennisreimann @dstrukt) (ref #2011) (@dennisreimann @dstrukt)
• UI: Improve pull payments design (ref #2011) (@dennisreimann @dstrukt)
• UI: Improvement of the modal checkout overlay (see this comment) (@dennisreimann)
• BTCPay Server vault operations can now be retried without having to refresh the page (@NicolasDorier)
• UX: Warning and hint system for stores not completely set up (@dennisreimann @rockstardev)
• Greenfield (Breaking change): Invoice state renamed Confirmed/Complete to Settled. (@NicolasDorier)
• Greenfield (Breaking change): Invoice state renamed Paid to Processing. (@NicolasDorier)
• Breaking change: Remove SQLite as the default database option (@Kukks)
• UI: Make sure transaction labels display correctly when there are many (ref #2076) (@ubolator)
• UI: Properly center payment button content (@ubolator)
• UI: Improvement of the lightning node info view (ref #2066) (@dennisreimann)
• Share the link of a pay button so one can embed in a QR code (fix #635) (@Kukks)
• Checkout experience: Make QR codes with bech32 uppercase again (@rockstardev)
• Add warning if the merchant setup invoice confirmation to zero conf (@ubolator)
• Adds a warning to configure the e-mail server before "Requires a confirmation mail for registering" checkbox can be checked if e-mail server is not configured. (@ubolator)
• Payment requests: Partially paid invoices are reused for future payments in payment requests. (@NicolasDorier)
• API Keys UI: Properly align form items (@dennisreimann)
• Wallets: By default, created PSBT were including previous transactions. Some hardware wallets ended up returning timeouts, so we reverted this decision. (@NicolasDorier)

Bug fixes:

• Fix payment button page title (ref #1952) (@sgracia13)
• Do not log the database connection string (@Kukks)
• Payjoin: Use base64 instead of hex for BIP78 (fix #1984) (@Kukks)
• If a password fail to be reset by mail, show proper error (fix #1986) (@NicolasDorier)
• Email was not included in the invoice text search (@Kukks)
• Greenfield: The create invoice route should not sending back generic errors if it fails (@dennisreimann)
• Fix-up links which were ignoring custom root path (@ubolator)
• Greenfield: Opening a channel with lightning was not working properly (ref #2054) (@dennisreimann)
• Docs: Create invoice route was referencing the wrong type in the doc (@dennisreimann)
• Payment Request user input rounding issue (ref #2014) (@Kukks)
• In store settings, the create new token button was returning an error (@NicolasDorier)
• Wallet: When clicking on the app's label of a transaction, an error 404 occured (@Kukks)
• Checkout experience: If coinswitch was activated, the altcoin tab was missing (@Kukks)
• If Email verification is turned off but you requested a forgot password form, it would ignore the request internally. (@Kukks)
• Docs: Fix swagger format for dates (@Kukks)
• Payjoin: Do not include maxadditionalfeecontribution if there is no change. (ref #2007) (@NicolasDorier)
• Checkout: If an invoice accepting lightning payments was partially paid, the payment of the new lightning invoice was buggy. (@Kukks)