Bitcoin Project Release Tracker

unchained-capital/caravan: caravan-v1.0.1

Published: 2024-01-10 20:55:53 UTC

1.0.1 (2024-01-10)

Bug Fixes

  • build: pass git sha to build properly (a93d65b)

Go to Repo Go to Release

unchained-capital/caravan: caravan-v1.0.0

Published: 2024-01-10 19:33:19 UTC

1.0.0 (2024-01-10)

⚠ BREAKING CHANGES

  • adds typescript and node v20 support (#350)

Features

Bug Fixes

  • deps: upgrade uc-bitcoin dep for fixture fix (67077c2)
  • incorrect fee error check conditional operator (2b417c6)
  • max spend button (0884745)
  • more dependency cleanup (593c48d)
  • psbt download in coldcard test suite (cd88354)
  • test-suite: key origins sorted by base58 xpub (444e083)
  • upgrade uc-bitcoin and pin broken ledger deps (64b9613)
  • utility accepts string instead of BN (607d9b8)

Go to Repo Go to Release

vulpemventures/marina: v0.6.3

Published: 2024-01-03 17:58:53 UTC

What's Changed

Full Changelog: https://github.com/vulpemventures/marina/compare/v0.6.2...v0.6.3

Go to Repo Go to Release

vulpemventures/marina: v0.6.2

Published: 2024-01-02 21:59:38 UTC

What's Changed

Full Changelog: https://github.com/vulpemventures/marina/compare/v0.6.1...v0.6.2

Go to Repo Go to Release

btcsuite/btcd: v0.24.0

Published: 2023-12-31 01:22:04 UTC

This release is a major release that includes several general bug fixes, security bug fixes (please update!), and also a series of performance improvements that dramatically reduce the time for initial block download from ~45 hours+ to around 6 hours! With this release,btcd now also supports BIP 155 and has gained support for pruning (--prune=MiB).

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.24.0.sig and manifest-v0.24.0.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.24.0.sig manifest-v0.24.0.txt

You should see the following if the verification was successful:

gpg: Signature made Sat Dec 30 17:11:22 2023 PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed

New Contributors

Full Changelog: https://github.com/btcsuite/btcd/compare/v0.23.4...v0.24.0

Go to Repo Go to Release

btcsuite/btcd: v0.24.0

Published: 2023-12-31 01:22:04 UTC

This release is a major release that includes several general bug fixes, security bug fixes (please update!), and also a series of performance improvements that dramatically reduce the time for initial block download from ~45 hours+ to around 6 hours! With this release,btcd now also supports BIP 155 and has gained support for pruning (--prune=MiB).

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.24.0.sig and manifest-v0.24.0.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.24.0.sig manifest-v0.24.0.txt

You should see the following if the verification was successful:

gpg: Signature made Sat Dec 30 17:11:22 2023 PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed

New Contributors

Full Changelog: https://github.com/btcsuite/btcd/compare/v0.23.4...v0.24.0

Go to Repo Go to Release

romanz/electrs: v0.10.2

Published: 2023-12-30 18:51:29 UTC

https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#0102-dec-31-2023

Go to Repo Go to Release

BlueWallet/BlueWallet: v6.4.14

Published: 2023-12-29 10:55:40 UTC

  • FIX: exception trying broadcast after scanning PSBT from QR
  • FIX: correctly work with addresses funded by coinbase transactions

Go to Repo Go to Release

ElementsProject/lightning: v23.11.2

Published: 2023-12-22 16:03:07 UTC

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.

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.12.3

Published: 2023-12-22 05:32:16 UTC

Bug fixes

  • Fix: Crashes would happen on some plugins introducing new apps type (#5590) @dennisreimann

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.12.2

Published: 2023-12-22 02:00:14 UTC

Please also see v1.12.1 which was released at the same time.

Bug fixes

  • Plugins: Fix missing uninstall button (#5587) @dennisreimann
  • Webhooks: Fix invoice interpolation (#5586 #5584) @dennisreimann

Go to Repo Go to Release

bitcoin-core/secp256k1: v0.4.1

Published: 2023-12-21 16:02:43 UTC

This release slightly increases the speed of the ECDH operation and significantly enhances the performance of many library functions when using the default configuration on x86_64.

For a list of changes, see the CHANGELOG.md.

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.12.1

Published: 2023-12-21 15:03:10 UTC

Recommended update for users using Boltcard with pull payments or Top-Up invoices.

Breaking change: Boltcards linked to pull payments in version 1.12.0 are not compatible with version 1.12.1.

New Features

  • A disabled plugin can now be uninstalled in the UI (#5570) @Kukks

Bug fixes

  • Fix: Payments to Top-Up could go undetected due to a race condition (#5568) @NicolasDorier
  • Lightning: Fixed the connection display name in LN settings (#5569) @dennisreimann
  • Prevent redirection to archived store after login (#5566) @dennisreimann
  • Use PullPaymentId to derive the cardkey of a Boltcard (#5575) @NicolasDorier
  • Greenfield: The Link a boltcard to a pull payment route would not generate new keys for the boltcard when onExisting was set to UpdateVersion. @NicolasDorier

Improvements

  • Lightning Address: Use lowercase usernames when resolving (#5579) @dennisreimann
  • UI: Form validation summary now matches alert style (#5576, #5564) @dennisreimann
  • Improved error message in Vault if a hardware device isn't supported @NicolasDorier
  • Lightning: Allow LND to be used with non-admin macaroons (#5567) @dennisreimann
  • Fix in API Documentation: The Link a boltcard to a pull payment had incorrectly documented permissions. @NicolasDorier

Go to Repo Go to Release

vulpemventures/marina: v0.6.1

Published: 2023-12-21 13:13:06 UTC

Go to Repo Go to Release

BlueWallet/BlueWallet: v6.4.12

Published: 2023-12-21 12:16:48 UTC

  • ADD: RON currency for widget
  • ADD: See currency when tap and hold on balance

  • ADD: tool to generate last mnemonic word (#5722)

  • FIX: better tracking opt out (related #5688)

  • FIX: correct merge of params when navigating between screens

  • FIX: Lightning wallet CSV export does not differentiate between paid and expired invoices #5835

  • FIX: Sometimes would crash due to lack of initialParams

  • FIX: Wrong Suite was being targeted

  • FIX: Call dismiss on ActionSheet to avoid duplicate firing

  • FIX: Re-enable groups on watch app

  • FIX: Show alert with error message when a selected file isn't valid

  • FIX: Apple Watch app not working #5470

  • FIX: Wait for transitions to finish before showing sheet

Go to Repo Go to Release

vulpemventures/marina: v0.6.0

Published: 2023-12-20 16:51:32 UTC

Go to Repo Go to Release

zkSNACKs/WalletWasabi: v2.0.5

Published: 2023-12-20 13:33:43 UTC

Wasabi Wallet is an easy to use, privacy-focused, open-source, non-custodial, Bitcoin wallet

Download

:window: Windows :green_apple: Apple M1/M2 :apple: Apple Intel :penguin: Ubuntu / Debian :penguin: Other Linux

Release Highlights

🛒 Buy Anything Button

Release Summary

Purchase stuff inside Wasabi Wallet with bitcoin by using the Buy Anything Button:

Buying anything with bitcoin has never been more effortless. With the click of a button you can now request the purchase of physical and digital goods, while protecting your privacy and revealing as little information about you as possible. Let your personal team of butlers find, arrange and ship the products you are looking for. From phones, to cars, even hotels and flights, get it all with Wasabi's new Buy Anything Button.

To learn more, check out our blog post.

Installation Guide

Download the operating system relevant software package and install Wasabi like you would with any other software on your computer. For a detailed installation guide, including signature verification, see the documentation.

Documentation

:spiderweb: Website :onion: Tor onion site :orangebook: Documentation :grey_question: FAQ

Advanced Guide

If you want to build or update Wasabi from source code, check out these easy instructions.

Wasabi uses reproducible builds, which you can verify with this guide.

Requirements

  • Windows 10 1607+
  • Windows 11 22000+
  • macOS 10.15+
  • Ubuntu 18.04+
  • Fedora 36+

- Debian 10+

Full Changelog

Full Changelog: https://github.com/zkSNACKs/WalletWasabi/compare/v2.0.4...v2.0.5

This discussion was created from the release Wasabi Wallet v2.0.5 - Buy Anything Button.

Go to Repo Go to Release

ACINQ/phoenix: android-v2.1.1

Published: 2023-12-20 13:15:25 UTC

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

This minor release fixes the Czech translation (#490, thanks @MasterixCZ) and English typos (#491 thanks @dluvian). It also bumps the feerate used for liquidity requests to help with the current high fees environment.

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.1.0...android-v2.1.1

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.12.0

Published: 2023-12-19 12:10:40 UTC

Noteworthy

  • With this release we upgrade to .NET 8, which also requires a current version of the Docker engine for docker deployments (>= 20.10.10). We will try to migrate outdated versions when upgrading BTCPay Server, but if you see these symptoms after updating, please upgrade Docker engine manually.
  • We changed a lot of things under the hood, making the Lightning integrations extendible by plugins and also preparing the migration of Altcoins to plugins. If you are using plugins, you will most likely find them disabled after this update, because new versions compatible with BTCPay Server v1.12 are required. Please see the "Manage Plugins" section once updated.
  • We are ending support for Postgresql 11 as it reached 5 years after its initial release. Read more about end-of-life (EOL) of postgresql. While Postgresql 11 should still work with BTCPay Server, we will not keep compatibility moving forward.

New feature

  • Webhooks: Support for Payment Requests, Payouts and extendibility by plugins (#5421) @Kukks
  • Support BIP129 Multisig wallet import (#5389) @Kukks
  • POS Keypad: Add plus and change clear functionality (#5396) @dennisreimann @dstrukt
  • Forms: Support adjusting invoice amount by multiplier, enables percentage-based discount codes (#5463) @Kukks
  • Can pair or reset a Boltcard to a pull payment (#5419) @NicolasDorier
  • Plugins: Allow scheduling installs/updates of future plugins (#5537) @Kukks

Bug fixes

  • Webhooks: Re-add OverPaid property to WebhookInvoiceSettledEvent (#5538 #5496) @dennisreimann
  • Apps: Filter list lookups by available app types (#5482) @dennisreimann
  • Wallet: Use application/jsonl as MIME type for BIP329 label export (#5489) @dennisreimann
  • Wallet: Fill label from BIP21 (#5428) @dennisreimann
  • Greenfield: LNURLPay store payment method fixes (#5446) @dennisreimann
  • Greenfield: Fix invoice refund permission (#5558) @Kukks
  • Do not activate Blazor in Wizard screens (#5435) @NicolasDorier
  • Pull Payment: Display the amount of claims (#5427) @NicolasDorier
  • Dashboard: LND limbo balance had the wrong unit (a 1 BTC limbo balance would show as 0.001 BTC) @NicolasDorier
  • Fix occasional concurrency issue which would result in app settings change not being properly saved (#5565) @NicolasDorier

Improvements

  • Upgrade to .NET 8.0 (#5479) @NicolasDorier
  • Enhance fine grain permissions (#5502) @Kukks
  • Checkout: NFC improvements (#5509) @dennisreimann
  • Checkout: Receipt improvements (#5505) @rockstardev @dennisreimann
  • Payment Request: Improve public view (#5413) @dennisreimann @dstrukt
  • POS Keypad: List recent transactions (#5478) @dennisreimann @dstrukt
  • POS Cart: Add options for search and categories display (#5438) @dennisreimann
  • POS Cart: Horizontal scrollable filters (#5391) @dennisreimann
  • POS and Crowdfund: Item editor improvements (#5418 #5449) @dennisreimann
  • Reporting: UI improvements (#5432) @dennisreimann @dstrukt
  • Wallet: Use Mempool.space fee estimation (#5490 #5556) @Kukks @NicolasDorier
  • Wallet: Update Passport instructions for import (#5423) @sethforprivacy
  • Plugins: Send notification when a new plugin version is available (#5450) @Kukks
  • Plugins: Improve crash detection on startup and hint at disabled plugins (#5514) @dennisreimann
  • Plugins: Add disclaimer (#5552) @dennisreimann
  • Server Policies: Add warnings for certain options (#5554) @dennisreimann
  • Greenfield: Remove unused checkout type setting from POS (#5512) @dennisreimann
  • Greenfield: Make checkout type V2 default for new stores (#5495) @dennisreimann
  • Domain mapping: Redirect root app to canonical URL (#5471) @dennisreimann
  • Lightning: Make implementations extendible by plugins (#5422) @Kukks
  • Lightning: Upgrade LND to 0.17.2-beta @rockstardev
  • Store Branding: Use store logo as favicon (#5519) @dennisreimann
  • Rate Providers: Remove Bittrex (#5553) @Kukks
  • UI: Unify list views (#5399) @dennisreimann @dstrukt
  • UI: Unify public page styles (#5460 #5462 #5466) @dennisreimann @dstrukt
  • UI: Add system option for theme switch (#5473) @dennisreimann
  • UI: Pull payment improvements (#5453) @dennisreimann
  • UI: Switch pos data to metadata in invoice create view (#5412) @Kukks
  • UI: Improve invoice's webhooks table (#5545) @NicolasDorier
  • UI: Remove forced center alignment for POS description (#5555) @dennisreimann

Go to Repo Go to Release

ACINQ/bitcoin-lib: v0.31

Published: 2023-12-18 15:12:41 UTC

What's Changed

Full Changelog: https://github.com/ACINQ/bitcoin-lib/compare/v0.30...v0.31

Go to Repo Go to Release

ElementsProject/lightning: v23.11.1

Published: 2023-12-16 12:49:39 UTC

This hotfix release addresses an issue where an unexpected message could be delivered to a subdaemon, causing it to abort.

  • build: 32-bit status_debug fix (#6890)
  • channeld: We could crash closingd by sending it a channeld message (#6937)

Go to Repo Go to Release

ACINQ/phoenix: android-v2.1.0

Published: 2023-12-15 16:45:57 UTC

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

Request inbound liquidity from your peer (#489) If you keep receiving funds over Lightning, you'll consume your inbound liquidity fast and may end up having to splice-in every incoming LN payments, which can be expensive because each splice is an on-chain transaction. By requesting liquidity from the peer, you can plan ahead and avoid future on-chain fees. This is now supported in Phoenix starting from 2.1.0, thanks to liquidity-ads (a new feature in the Lightning protocol).

Requesting liquidity is done manually (for now at least). A button to the liquidity screen has been added in the Home screen. Your inbound liquidity is also displayed in the channels view.

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.15...android-v2.1.0 - lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.5.12...v1.5.14

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.15

Published: 2023-12-12 14:56:33 UTC

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Hotfix release

This release fixes an incorrect error message displayed when opening the Send screen (#487).

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

lnbits/lnbits: 0.11.3

Published: 2023-12-12 10:24:55 UTC

What's Changed

New Contributors

Full Changelog: https://github.com/lnbits/lnbits/compare/0.11.2...0.11.3

Go to Repo Go to Release

bitcoinknots/bitcoin: v25.1.knots20231115

Published: 2023-12-10 16:29:28 UTC

25.1 Release Notes

Bitcoin Knots version 25.1.knots20231115 is now available from:

https://bitcoinknots.org/files/25.x/25.1.knots20231115/

This release includes new features, various bug fixes and performance improvements, as well as updated translations.

Please report bugs using the issue tracker at GitHub:

https://github.com/bitcoinknots/bitcoin/issues

To receive security and update notifications, please subscribe to:

https://bitcoinknots.org/list/announcements/join/

How to Upgrade

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes in some cases), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on macOS) or bitcoind/bitcoin-qt (on Linux).

Upgrading directly from very old versions of Bitcoin Core or Knots is possible, but it might take some time if the data directory needs to be migrated. Old wallet versions of Bitcoin Knots are generally supported.

Compatibility

Bitcoin Knots is supported on operating systems using the Linux kernel, macOS 10.15+, and Windows 7 and newer. It is not recommended to use Bitcoin Knots on unsupported systems.

Known Bugs

In various locations, including the GUI's transaction details dialog, transaction virtual sizes may not account for an unusually high number of sigops (ie, as determined by the -bytespersigop policy). This could result in reporting a lower virtual size than is actually used for mempool or mining purposes.

In the interest of time, this release does not include updated translations. Please open an issue on GitHub if this is of particular importance to you or anyone you know. If nobody expresses interest in localization, it may continue to be skipped going forward.

Notable changes

Security vulnerabilities fixed

Several security issues (CVEs CVE-2023-40257, CVE-2023-40258, and CVE-2023-40259) were identified in the extended rpcauth wallet-restriction syntax, which is intended to enable semi-trusted local applications using the Bitcoin Knots API to access only specific wallets (or none at all) and not others. The full details of these issues will be disclosed at a future time, but they have all been fixed in this release.

P2P and network changes

  • To address a potential denial-of-service, the logic to download headers from peers has been reworked. This is particularly relevant for nodes starting up for the first time (or for nodes which are starting up after being offline for a long time).

Whenever headers are received from a peer that have a total chainwork that is either less than the node's -minimumchainwork value or is sufficiently below the work at the node's tip, a "presync" phase will begin, in which the node will download the peer's headers and verify the cumulative work on the peer's chain, prior to storing those headers permanently. Once that cumulative work is verified to be sufficiently high, the headers will be redownloaded from that peer and fully validated and stored.

This may result in initial headers sync taking longer for new nodes starting up for the first time, both because the headers will be downloaded twice, and because the effect of a peer disconnecting during the presync phase (or while the node's best headers chain has less than -minimumchainwork), will result in the node needing to use the headers presync mechanism with the next peer as well (downloading the headers twice, again). (#25717)

  • Enable parallel compact block downloads to mitigate temporary stalls from a slow peer. (#27626)

  • The rate limit on transaction relay has been doubled to 14 transactions per second (35 tx/s for outbound connections) to better adapt to present network conditions. (#28592)

  • Transactions of non-witness size 65 and above are now allowed by mempool and relay policy. This is to better reflect the actual afforded protections against CVE-2017-12842 and open up additional use-cases of smaller transaction sizes. (#26265)

  • With I2P connections, a new, transient address is used for each outbound connection if -i2pacceptincoming=0. (#25355)

  • A new net permission forceinbound (set with -whitelist=forceinbound@... or -whitebind=forceinbound@...) is introduced that extends noban permissions. Inbound connections from hosts protected by forceinbound will now be more likely to connect even if maxconnections is reached and the node's inbound slots are full. This is achieved by attempting to force the eviction of a random, inbound, otherwise unprotected peer. RPC getpeerinfo will also now indicate forced_inbound. (#27600)

  • The -datacarriersize policy limit has been updated to match newer style datacarrier transactions. (#28408)

  • An additional -datacarriercost option has also been added to avoid giving the "segwit discount" to aribitrary data (and can be increased to require datacarrier transactions to pay higher fees).

  • The spam filters limiting smart contract code sizes for pre-Segwit and Segwit "v0" scripts have been expanded to also cover Taproot. Since the sizes were inconsistent, the lower size of 1650 which actually had a rationale has been used as the default for this release. The size limit can be adjusted with the new -maxscriptsize option. If you know of any legitimate scripts that are larger than the default, please report a bug.

New RPCs

  • A new getprioritisedtransactions RPC has been added. It returns a map of all fee deltas created by the user with prioritisetransaction, indexed by txid. The map also indicates whether each transaction is present in the mempool.

  • getaddrmaninfo has been added to view the distribution of addresses in the new and tried table of the node's address manager across different networks (ipv4, ipv6, onion, i2p, cjdns). The RPC returns count of addresses in new and tried table as well as their sum for all networks. (#27511, #28565)

Updated RPCs

  • The verifychain RPC will now return false if the checks didn't fail, but couldn't be completed at the desired depth and level. This could be due to missing data while pruning, due to an insufficient dbcache or due to the node being shutdown before the call could finish. (#25574)

  • sendrawtransaction has a new, optional argument, maxburnamount with a default value of 0. Any transaction containing an unspendable output with a value greater than maxburnamount will not be submitted. At present, the outputs deemed unspendable are those with scripts that begin with an OP_RETURN code (known as 'datacarriers'), scripts that exceed the maximum script size, and scripts that contain invalid opcodes.

  • The testmempoolaccept RPC now returns 2 additional results within the "fees" result: "effective-feerate" is the feerate including fees and sizes of transactions validated together if package validation was used, and also includes any modified fees from prioritisetransaction. The "effective-includes" result lists the wtxids of transactions whose modified fees and sizes were used in the effective-feerate (#26646).

  • decodescript may now infer a Miniscript descriptor under P2WSH context if it is not lacking information. (#27037)

  • finalizepsbt is now able to finalize a transaction with inputs spending Miniscript-compatible P2WSH scripts. (#24149)

  • The -deprecatedrpc=softforks configuration option has been removed. The RPC getblockchaininfo no longer returns the softforks field, which was previously deprecated in 23.0. (#23508) Information on soft fork status is now only available via the getdeploymentinfo RPC.

  • The deprecatedrpc=exclude_coinbase configuration option has been removed. The receivedby RPCs (listreceivedbyaddress, listreceivedbylabel, getreceivedbyaddress and getreceivedbylabel) now always return results accounting for received coins from coinbase outputs, without an option to change that behaviour. Excluding coinbases was previously deprecated in 23.0. (#25171)

  • The deprecatedrpc=fees configuration option has been removed. The top-level fee fields fee, modifiedfee, ancestorfees and descendantfees are no longer returned by RPCs getmempoolentry, getrawmempool(verbose=true), getmempoolancestors(verbose=true) and getmempooldescendants(verbose=true). The same fee fields can be accessed through the fees object in the result. The top-level fee fields were previously deprecated in 23.0. (#25204)

  • The getpeerinfo RPC has been updated with a new presynced_headers field, indicating the progress on the presync phase mentioned in the "P2P and network changes" section above.

  • RPC disconnectnode now accepts a subnet into address argument. (#26576)

  • The output from getmempoolinfo is extended to include a rbf_policy key briefly describing the current replace-by-fee policy ("never", "optin", or "always").

Changes to wallet related RPCs can be found in the Wallet section below.

Build System

  • The --enable-upnp-default and --enable-natpmp-default options have been removed. If you want to use port mapping, you can configure it using a .conf file, or by passing the relevant options at runtime. (#26896)

Updated settings

  • If the -checkblocks or -checklevel options are explicitly provided by the user, but the verification checks cannot be completed due to an insufficient dbcache, Bitcoin Knots will now return an error at startup. (#25574)

  • Setting -blocksonly will now reduce the maximum mempool memory to 5MB (users may still use -maxmempool to override). Previously, the default 300MB would be used, leading to unexpected memory usage for users running with -blocksonly expecting it to eliminate mempool memory usage.

As unused mempool memory is shared with dbcache, this also reduces the dbcache size for users running with -blocksonly, potentially impacting performance. - Setting -maxconnections=0 will now disable -dnsseed and -listen (users may still set them to override).

Changes to GUI or wallet related settings can be found in the GUI or Wallet section below.

New settings

  • The shutdownnotify option is used to specify a command to execute synchronously before Bitcoin Knots has begun its shutdown sequence. (#23395)

  • To assist in controlling access to the RPC "cookie" file on multiuser systems, a new rpccookieperms setting has been added to set the file permissions mode before writing the access token.

Wallet

  • Added a new next_index field in the response in listdescriptors to have the same format as importdescriptors (#26194)

  • RPC listunspent now has a new argument include_immature_coinbase to include coinbase UTXOs that don't meet the minimum spendability depth requirement (which before were silently skipped). (#25730)

  • Rescans for descriptor wallets are now significantly faster if compact block filters (BIP158) are available. Since those are not constructed by default, the configuration option "-blockfilterindex=1" has to be provided to take advantage of the optimization. This improves the performance of the RPC calls rescanblockchain, importdescriptors and restorewallet. (#25957)

  • RPC unloadwallet now fails if a rescan is in progress. (#26618)

  • Wallet passphrases may now contain null characters. Prior to this change, only characters up to the first null character were recognized and accepted. (#27068)

  • Address Purposes strings are now restricted to the currently known values of "send", "receive", and "refund". Wallets that have unrecognized purpose strings will have loading warnings, and the listlabels RPC will raise an error if an unrecognized purpose is requested. (#27217)

  • In the createwallet, loadwallet, unloadwallet, and restorewallet RPCs, the "warning" string field is deprecated in favor of a "warnings" field that returns a JSON array of strings to better handle multiple warning messages and for consistency with other wallet RPCs. The "warning" field will be fully removed from these RPCs in v26. It can be temporarily re-enabled during the deprecation period by launching bitcoind with the configuration option -deprecatedrpc=walletwarningfield. (#27279)

  • Descriptor wallets can now spend coins sent to P2WSH Miniscript descriptors. (#24149)

  • The -walletrbf startup option will now default to true. The wallet will now default to opt-in RBF on transactions that it creates. (#25610)

  • The replaceable option for the createrawtransaction and createpsbt RPCs will now default to true. Transactions created with these RPCs will default to having opt-in RBF enabled. (#25610)

  • The wsh() output descriptor was extended with Miniscript support. You can import Miniscript descriptors for P2WSH in a watchonly wallet to track coins, but you can't spend from them using the Bitcoin Core wallet yet. You can find more about Miniscript on the reference website. (#24148)

  • The tr() output descriptor now supports multisig scripts through the multi_a() and sortedmulti_a() functions. (#24043)

  • The importdescriptors RPC can now be used to import BIP 93 (codex32) seeds. (#27351)

  • To help prevent fingerprinting transactions created by the Bitcoin Core wallet, change output amounts are now randomized. (#24494)

  • The listsinceblock, listtransactions and gettransaction output now contain a new parent_descs field for every "receive" entry. (#25504)

  • A new optional include_change parameter was added to the listsinceblock command. (#25504)

  • RPC importaddress now supports watch-only descriptor wallets.

  • RPC walletprocesspsbt return object now includes field hex (if the transaction is complete) containing the serialized transaction suitable for RPC sendrawtransaction. (#28414)

  • The result of RPC getaddressinfo adds an isactive key which can be used to determine if the address is derived from the currently active wallet seed. (#27216)

  • RPC getreceivedbylabel now returns an error, "Label not found in wallet" (-4), if the label is not in the address book. (#25122)

Migrating Legacy Wallets to Descriptor Wallets

An experimental RPC migratewallet has been added to migrate Legacy (non-descriptor) wallets to Descriptor wallets. More information about the migration process is available in the documentation.

GUI changes

  • The "Mask values" is a persistent option now. (gui#701)

  • The "Mask values" option affects the "Transaction" view now, in addition to the "Overview" one. (gui#708)

  • A new menu item to restore a wallet from a backup file has been added (gui#471).

  • Configuration changes made in the bitcoin GUI (such as the pruning setting, proxy settings, UPNP preferences) are now saved to <datadir>/settings.json file rather than to the Qt settings backend (windows registry or unix desktop config files), so these settings will now apply to bitcoind, instead of being ignored. (#15936, gui#602)

  • Also, the interaction between GUI settings and bitcoin.conf settings is simplified. Settings from bitcoin.conf are now displayed normally in the GUI settings dialog, instead of in a separate warning message ("Options set in this dialog are overridden by the configuration file: -setting=value"). And these settings can now be edited because settings.json values take precedence over bitcoin.conf values. (#15936)

REST

  • A new /rest/deploymentinfo endpoint has been added for fetching various state info regarding deployments of consensus changes. (#25412)

  • The /headers/ and /blockfilterheaders/ endpoints have been updated to use a query parameter instead of path parameter to specify the result count. The count parameter is now optional, and defaults to 5 for both endpoints. The old endpoints are still functional, and have no documented behaviour change.

For /headers, use GET /rest/headers/<BLOCK-HASH>.<bin|hex|json>?count=<COUNT=5> instead of GET /rest/headers/<COUNT>/<BLOCK-HASH>.<bin|hex|json> (deprecated)

For /blockfilterheaders/, use GET /rest/blockfilterheaders/<FILTERTYPE>/<BLOCK-HASH>.<bin|hex|json>?count=<COUNT=5> instead of GET /rest/blockfilterheaders/<FILTERTYPE>/<COUNT>/<BLOCK-HASH>.<bin|hex|json> (deprecated)

(#24098)

Binary verification

Low-level changes

RPC

  • The JSON-RPC server now rejects requests where a parameter is specified multiple times with the same name, instead of silently overwriting earlier parameter values with later ones. (#26628)

  • RPC listsinceblock now accepts an optional label argument to fetch incoming transactions having the specified label. (#25934)

  • Previously setban, addpeeraddress, walletcreatefundedpsbt, methods allowed non-boolean and non-null values to be passed as boolean parameters. Any string, number, array, or object value that was passed would be treated as false. After this change, passing any value except true, false, or null now triggers a JSON value is not of expected type error. (#26213)

  • The deriveaddresses, getdescriptorinfo, importdescriptors and scantxoutset commands now accept Miniscript expression within a wsh() descriptor. (#24148)

  • The getaddressinfo, decodescript, listdescriptors and listunspent commands may now output a Miniscript descriptor inside a wsh() where a wsh(raw()) descriptor was previously returned. (#24148)

Go to Repo Go to Release

bitcoin/bitcoin: v26.0

Published: 2023-12-07 19:53:00 UTC

Bitcoin Core version 26.0 is now available from:

https://bitcoincore.org/bin/bitcoin-core-26.0/

For the release notes please see the git repository:

https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-26.0.md

Do not use the links provided by GitHub, rather use the above download links, they are guaranteed to be generated deterministically and signed.

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.14

Published: 2023-12-07 13:37:14 UTC

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Main changes from 2.0.13

  • Added a screen to delete the wallet (4ffc78d1)
  • Fixed an issue reading bip-21 URIs with a Lightning invoice fallback, see #466 (f0ae9044)

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.13...android-v2.0.14

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

lightningnetwork/lnd: v0.17.3-beta

Published: 2023-12-06 21:26:54 UTC

This is a hot fix release that fixes multiple concurrency and memory related bugs. Memory consumption for lnd nodes running with bitcoind using the rpcpolling has been significantly reduced (previously scaled with total mempool size).

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.17.3-beta.sig and manifest-v0.17.3-beta.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.17.3-beta.sig manifest-v0.17.3-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Dec 6 13:24:12 2023 PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Timestamp

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.17.3-beta.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands: ots verify manifest-roasbeef-v0.17.3-beta.sig.ots -f manifest-roasbeef-v0.17.3-beta.sig

Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Verifying the Release Binaries

Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.21.0, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.

The make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag> can be used.

Finally, you can also verify the tag itself with the following command:

$ git verify-tag v0.17.3-beta gpg: Signature made Tue 05 Dec 2023 04:38:50 PM PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

Verifying the Docker Images

To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):

shell $ docker run --rm --entrypoint="" lightninglabs/lnd:v0.17.3-beta /verify-install.sh v0.17.3-beta $ OK=$? $ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done $ docker run lightninglabs/lnd [command-line options]

Building the Contained Release

Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that vendor.tar.gz and lnd-source-v0.17.3-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.17.3-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.3-beta" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.3-beta" ./cmd/lncli

The -mod=vendor flag tells the go build command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.

Additionally, it's now possible to use the enclosed release.sh script to bundle a release for a specific system like so:

make release sys="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

Release Notes

https://github.com/lightningnetwork/lnd/blob/v0.17.3-beta/docs/release-notes/release-notes-0.17.3.md

Contributors (Alphabetical Order)

  • Eugene Siegel
  • Yong Yu

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.13

Published: 2023-12-01 16:32:36 UTC

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.12

Full Changelog:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

vulpemventures/marina: v0.5.7

Published: 2023-11-29 16:00:47 UTC

Go to Repo Go to Release

ElementsProject/lightning: v23.11

Published: 2023-11-28 18:41:46 UTC

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

Go to Repo Go to Release

ElementsProject/elements: elements-23.2.1

Published: 2023-11-28 17:37:13 UTC

This release includes the following changes: * Brings Elements up to date with Bitcoin Core version 23.2. To see the Bitcoin 23.2 release notes please click here. * Adds support for arm64 macos native builds. * Fixes a problem in the getnewaddress rpc: getnewaddress will now return an unblinded bech32 address even when -blindedaddresses=1 in config (PR #1246, issue #1245). * In contrast to Bitcoin, Elements is not changing the default wallet format from legacy to descriptors, this is because many things (like peg-ins and peg-outs) still work only on legacy wallets.

Go to Repo Go to Release

lnbits/lnbits: 0.11.2

Published: 2023-11-27 14:57:41 UTC

New in this release

  • New service fee settings that lets you earn a transaction fee for all internal or external transaction on an LNbits instance. Set these environment variables in your .env file or use the Admin-UI to enable this feature:
    • LNBITS_SERVICE_FEE: the service fee (in percent)
    • LNBITS_SERVICE_FEE_WALLET: the wallet where fees go to
    • LNBITS_SERVICE_FEE_MAX: the maximum fee per transaction (in satoshis)
    • LNBITS_SERVICE_FEE_IGNORE_INTERNAL: disable fees for internal transactions
  • lnbits-cli can now manage extensions
  • New funding source: Alby wallet
  • Node Management via .env file without Admin-UI
  • Core Lightning bug fixes
  • LND REST bug fixes
  • New Czech (cs), Slovak (sk) and Korean (kr) localizations
  • FakeWallet fix for providing Lightning preimages

All changes in detail

New Contributors

Full Changelog: https://github.com/lnbits/lnbits/compare/0.11.1...0.11.2

Go to Repo Go to Release

zkSNACKs/WalletWasabi: v2.0.4.1b

Published: 2023-11-22 15:01:40 UTC

Wasabi is an easy to use, privacy-focused, open-source, non-custodial, Bitcoin wallet

Download

:window: Windows :green_apple: Apple M1/M2 :apple: Apple Intel :penguin: Ubuntu / Debian :penguin: Other Linux

Release Highlights

🛠️ Fix hardware wallets with updat to HWI 2.3.1 - Pull Request 🔧 Local Prison mitigation - Pull Request

Release Summary

This is a silent release aiming to fix two specific issues:

  1. Out-dated HWI, ensuring that Wasabi works with all hardware wallets.
  2. There were some issues with the server-side prison banning coins for ~1-2 years. The clients saved this information and Wasabi never chose those coins again until ban period is over. Not even if the server-side prison was cleared.

Installation Guide

Download the operating system relevant software package and install Wasabi like you would any other software on your computer. For a detailed installation guide, including signature verification, see the documentation.

Advanced Guide

If you want to build or update Wasabi from source code, check out these easy instructions.

Wasabi uses reproducible builds, which you can verify with this guide.

Documentation

:spiderweb: Website :onion: Tor onion site :greyquestion: FAQ

Requirements

  • Windows 10+
  • macOs 10.15+
  • Ubuntu 16.04, 18.04, 20.04+
  • Fedora 33+
  • Debian 10+

What's Changed

https://github.com/zkSNACKs/WalletWasabi/pull/11979 https://github.com/zkSNACKs/WalletWasabi/pull/11981 https://github.com/zkSNACKs/WalletWasabi/pull/11980

Go to Repo Go to Release

sparrowwallet/sparrow: 1.8.1

Published: 2023-11-22 09:46:51 UTC

  • Add oxt.me as fee rates source (configure in Preferences)
  • Add historical fiat values to the transactions CSV (from Export Wallet or the Transactions tab) where an exchange source is configured
  • Increase and decrease maximum limit on fee rate slider where fee rate equals or exceeds current range
  • Add QR display (with save to PDF) to the Export Wallet > Output Descriptor option
  • Set non-mainnet fallback fee rates to 1 sat/vb
  • Switch from HttpUrlConnection to Jetty HTTP client for all external HTTP calls to avoid spurious DNS query
  • In Cormorant, check the wallet gap limit and increase the Bitcoin Core descriptor range if necessary
  • Set a smaller increment amount on the fee range slider for keyboard adjustments
  • Use fallback fee rate estimates if the connected server returns an error estimating fee rates
  • Show an error dialog on attempting CPFP where no outputs are spendable
  • Add Krux to the Import Wallet options
  • Bug fix: Set dialog minimum height to preferred height (or make it resizable) to avoid window sizing bug in some Linux environments
  • Bug fix: Fix transaction diagram output size indicators in transactions with non-address outputs
  • Bug fix: Add null safe tests for standard account types
  • Bug fix: In Cormorant, handle checking imports and stopping before server is started
  • Bug fix: Save previously used Mix To wallet index to skip used addresses if mix fails

Go to Repo Go to Release

lightningnetwork/lnd: v0.17.2-beta

Published: 2023-11-21 21:28:38 UTC

This is a hot fix release to fix a concurrency related bug in the peer/server that could lead to a panic. The only change included in this release is: https://github.com/lightningnetwork/lnd/pull/8186.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.17.2-beta.sig and manifest-v0.17.2-beta.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.17.2-beta.sig manifest-v0.17.2-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Nov 20 18:56:09 2023 CST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Timestamp

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.17.2-beta.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands: ots verify manifest-roasbeef-v0.17.2-beta.sig.ots -f manifest-roasbeef-v0.17.2-beta.sig

Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Verifying the Release Binaries

Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.21.0, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.

The make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag> can be used.

Finally, you can also verify the tag itself with the following command:

$ git verify-tag v0.17.2-beta gpg: Signature made Mon 20 Nov 2023 12:32:30 PM PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

Verifying the Docker Images

To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):

shell $ docker run --rm --entrypoint="" lightninglabs/lnd:v0.17.2-beta /verify-install.sh v0.17.2-beta $ OK=$? $ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done $ docker run lightninglabs/lnd [command-line options]

Building the Contained Release

Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that vendor.tar.gz and lnd-source-v0.17.2-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.17.2-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.2-beta" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.2-beta" ./cmd/lncli

The -mod=vendor flag tells the go build command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.

Additionally, it's now possible to use the enclosed release.sh script to bundle a release for a specific system like so:

make release sys="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

Release Notes

https://github.com/lightningnetwork/lnd/blob/v0.17.2-beta/docs/release-notes/release-notes-0.17.2.md

Contributors (Alphabetical Order)

  • Eugene Siegel
  • Matt Morehouse

Go to Repo Go to Release

Start9Labs/start-os: v0.3.5.1

Published: 2023-11-21 19:34:28 UTC

Highlights

  • Revert perpetual performance mode for quieter fan
  • Minor bug fixes

What's Changed

Full Changelog: https://github.com/Start9Labs/start-os/compare/v0.3.5...v0.3.5.1

Checksums

BLAKE-3 5e3d6e4865fa3417bbe2a89d9a53181140abcfbc6b7f7eb1ad1be72067e8a73f startos-0.3.5.1-39de098_aarch64.iso c8357d0e49962120960e843aa8a77b24bb6a98e2a2a7415902598736fd32d020 startos-0.3.5.1-39de098_aarch64-nonfree.iso 49d635fbcb3d8239a5550158acc21f6d9cd67f1bfc4fae124eac625673ec5a80 startos-0.3.5.1-39de098_raspberrypi.img.gz afd33094c90faade9f7fa8df1752558d4c708287f3237e638975aceec302bc84 startos-0.3.5.1-39de098_x86_64.iso 92f1a6f88e4da72d081babf9a47bd09d1870ddfb624756f3cd8d1cf2440d9cbd startos-0.3.5.1-39de098_x86_64-nonfree.iso SHA-256 aa3c70b411e5ad2c52ccf927e7bae0394d816d8e197511cbebf0503e23a1a964 startos-0.3.5.1-39de098_aarch64.iso 8ebae051ccff4a99b23326ac40e8c2ce85d40438f2093bb1be967e3aa2961178 startos-0.3.5.1-39de098_aarch64-nonfree.iso daba5d01f93a53433db2347a81cf46accba9096711eccef9c90836ccc78a7e69 startos-0.3.5.1-39de098_raspberrypi.img.gz 181fec43a3b7287fe6c6cdb70bcba79a5596fc2be1dbe5a54e09a4c142272155 startos-0.3.5.1-39de098_x86_64.iso 29b0f1e0211568ea66d6b729536ff84aed3b6cbc1c38540a7c80a391fd01616e startos-0.3.5.1-39de098_x86_64-nonfree.iso

Go to Repo Go to Release

lightningnetwork/lnd: v0.17.1-beta

Published: 2023-11-14 18:58:32 UTC

This marks the first minor release in the 0.17.x cycle. This release includes a number of bug fixes and optimizations, including: a reduction in CPU utilization due to the new mempool scanning safety logic, enchantments to the CPFP logic for anchor outputs, a fix to a peer/server deadlock, and a bug fix for the new taproot channel type that may have otherwise caused a channel to show as inactive until reconnection.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.17.1-beta.sig and manifest-v0.17.1-beta.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.17.1-beta.sig manifest-v0.17.1-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Nov 13 15:45:38 2023 PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Timestamp

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.17.1-beta.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands: ots verify manifest-roasbeef-v0.17.1-beta.sig.ots -f manifest-roasbeef-v0.17.1-beta.sig

Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Verifying the Release Binaries

Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.21.0, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.

The make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag> can be used.

Finally, you can also verify the tag itself with the following command:

$ git verify-tag v0.17.1-beta gpg: Signature made Mon 13 Nov 2023 11:13:31 AM PST gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

Verifying the Docker Images

To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):

shell $ docker run --rm --entrypoint="" lightninglabs/lnd:v0.17.1-beta /verify-install.sh v0.17.1-beta $ OK=$? $ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done $ docker run lightninglabs/lnd [command-line options]

Building the Contained Release

Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that vendor.tar.gz and lnd-source-v0.17.1-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.17.1-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.1-beta" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.1-beta" ./cmd/lncli

The -mod=vendor flag tells the go build command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.

Additionally, it's now possible to use the enclosed release.sh script to bundle a release for a specific system like so:

make release sys="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

Release Notes

https://github.com/lightningnetwork/lnd/blob/v0-17-1-branch/docs/release-notes/release-notes-0.17.1.md

Contributors (Alphabetical Order)

  • Eugene Siegel
  • Olaoluwa Osuntokun
  • Yong Yu

Go to Repo Go to Release

sparrowwallet/sparrow: 1.8.0

Published: 2023-11-09 12:17:59 UTC

  • Add a figure caption to the overview diagram on a transaction tab to describe the transaction
  • Enlarge the QR display dialog and increase the default QR code density
  • Add Search All Wallets functionality to the View menu to search across all open wallets
  • Add airgapped message signing via QR
  • Increase the gap limit where necessary to sign a PSBT where its global xpubs match an open wallet
  • Add fee rate selection slider to the Private Key Sweep dialog
  • Add a Scan button to QR display dialog to progress immediately to scanning
  • Support opening multiple wallet or transaction files at once
  • When searching, show transactions with a matching output address if a full address is provided
  • Add Satochip card support as an airgapped or connected hardware wallet (@Toporin)
  • Add Krux as an airgapped hardware wallet
  • Temporarily disconnect from Whirlpool if the wallet gap limit is increasing rapidly during mixing due to network issues
  • Add Whirlpool Postmix to the list of possible accounts that can be added to any Legacy or Segwit wallet
  • Add additional testnet public server qtornado.com
  • Freeze and unfreeze UTXOs in Sparrow Terminal by pressing f on the UTXOs table
  • Check and indicate in the title bar if a proxy is configured and working in Sparrow Terminal
  • Add keyboard shortcut cmd+alt+arrow on MacOS to switch tabs (ctrl+pageup/pagedown already works on all platforms)
  • Select all text in the message sign signature field on mouse click
  • Reload Cormorant wallet if unloaded when polling Bitcoin Core
  • Support hexadecimal Border Wallets grid PDFs
  • Improve fullscreen behaviour by setting dialog ownership to parent window
  • Add duplicate payment address warning to transaction diagram
  • Display an error message when attempting to mix from account 0 and it is not the master wallet
  • Remove block hash from transaction tab fields, add to context menu for block height and timestamp
  • Add Bisq segwit custom derivation to mnemonic wallet discovery
  • Bug fix: Suppress script type change warning when replacing the entire wallet in Settings
  • Bug fix: Force selection of a new configured server if currently configured server is deleted
  • Bug fix: Fix mixing from Whirlpool wallets with special characters in the passphrase
  • Bug fix: Fix possible thread race issue when connecting to an Electrum server

Go to Repo Go to Release

Start9Labs/start-os: v0.3.5

Published: 2023-11-08 20:35:06 UTC

This release contains significant under-the-hood improvements to performance and reliability

Highlights

  • Ditch Docker, replace with Podman
  • Remove locking behavior from PatchDB and optimize
  • Boost efficiency of service manager
  • Require HTTPS on LAN, and improve setup flow for trusting Root CA
  • Better default privacy settings for Firefox kiosk mode
  • Eliminate memory leak from Javascript runtime
  • Other small bug fixes
  • Update license to MIT

What's Changed

New Contributors

Full Changelog: https://github.com/Start9Labs/start-os/compare/v0.3.4.4...v0.3.5

Checksums

BLAKE-3 3f330020dc3e0ca8ff0c819630f0364f8a1f1f7e2492fee913aba21aff8565df startos-0.3.5-871f78b_aarch64.iso d06d99cae87e36236bcb62f0fe3ee400be8c369ef3bfb555c6cd282dcd152dcd startos-0.3.5-871f78b_aarch64-nonfree.iso 6cb626c802c8e0903bb0c1789036c22f20ada42c69853531f3ad629f58f864f9 startos-0.3.5-871f78b_raspberrypi.img.gz 3ca3a87c93eef1ba8399f3b1014c75d1a8f0889aef0b76a11e054b01febca9d0 startos-0.3.5-871f78b_x86_64.iso 19d4a6c8b96b12efe5009e2da9bf3513c2d7802d1f09af2287e736bdc62a0a00 startos-0.3.5-871f78b_x86_64-nonfree.iso SHA-256 4bcdabe1421881873d00376f7e1d2efc197af2342854e4c8beba0911f12afcf9 startos-0.3.5-871f78b_aarch64.iso 3761da1e2b3d1bc3d68c48bd7bf985d1d333c6989fb11f9c0f4960a62607604d startos-0.3.5-871f78b_aarch64-nonfree.iso 00d1dc0c05f7b304a802d85505536a372efd0649160081d5daf963914e7cf38e startos-0.3.5-871f78b_raspberrypi.img.gz d27f88f31e0d8d183b181f2629794d423fb777d9edfaefe406f8b3e478edab57 startos-0.3.5-871f78b_x86_64.iso ed9b774d9ceae32e1ff8e765985d21fd05a83ca5e0caab9a245194ba4207da3d startos-0.3.5-871f78b_x86_64-nonfree.iso

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.12

Published: 2023-11-06 10:08:47 UTC

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.11

  • Gracefully handle Android keystore failures at startup, and fall back to manual seed input to unlock the wallet. See 945b640 for details.
  • Fixed camera staying online after leaving the scan view. Thanks @kotasjan for the help! See issue #442 for details.
  • Several fixes and improvements. Thanks @MasterixCZ for the Czech localisation fixes.

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.11...android-v2.0.12 - lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.5.10...v1.5.11

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

romanz/electrs: v0.10.1

Published: 2023-11-01 20:21:16 UTC

https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#0101-nov-01-2023

Go to Repo Go to Release

bitcoin/bitcoin: v24.2

Published: 2023-11-01 09:57:16 UTC

Bitcoin Core version 24.2 is now available from:

https://bitcoincore.org/bin/bitcoin-core-24.2/

For the release notes please see the git repository:

https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-24.2.md

Do not use the links provided by GitHub, rather use the above download links, they are guaranteed to be generated deterministically and signed.

Go to Repo Go to Release

vulpemventures/marina: v0.5.6

Published: 2023-10-25 15:53:21 UTC

Go to Repo Go to Release

BlueWallet/BlueWallet: v6.4.10

Published: 2023-10-25 15:33:03 UTC

  • FIX: Check if theres a string before triggering the clipboard alert
  • FIX: The scrolling behavior after deleting a wallet was not natural. Let the component figure it out
  • FIX: iOS version is showing wallets' balance on Home Screen even when option is disabled #5500
  • FIX: Bug: CNY price is wrong #5705
  • FIX: View controller-based status bar appearance
  • FIX: Notifications Permission issues on newer Android APIs
  • REF: Privacy screen

Go to Repo Go to Release

lightningdevkit/rust-lightning: v0.0.118

Published: 2023-10-24 01:34:52 UTC

0.0.118 - Oct 23, 2023 - "Just the Twelve Sinks"

API Updates

  • BOLT12 sending and receiving is now supported as an alpha feature. You may run into unexpected issues and will need to have a direct connection with the offer's blinded path introduction points as messages are not yet routed. We are seeking feedback from early testers (#2578, #2039).
  • ConfirmationTarget has been rewritten to provide information about the specific use LDK needs the feerate estimate for, rather than the generic low-, medium-, and high-priority estimates. This allows LDK users to more accurately target their feerate estimates (#2660). For those wishing to retain their existing behavior, see the table below for conversion.
  • ChainHash is now used in place of BlockHash where it represents the genesis block (#2662).
  • lightning-invoice payment utilities now take a Deref to AChannelManager (#2652).
  • peel_onion is provided to statelessly decode an OnionMessage (#2599).
  • ToSocketAddrs + Display are now impl'd for SocketAddress (#2636, #2670)
  • Display is now implemented for OutPoint (#2649).
  • Features::from_be_bytes is now provided (#2640).

For those moving to the new ConfirmationTarget, the new variants in terms of the old mempool/low/medium/high priorities are as follows: * OnChainSweep = HighPriority * MaxAllowedNonAnchorChannelRemoteFee = max(25 * 250, HighPriority * 10) * MinAllowedAnchorChannelRemoteFee = MempoolMinimum * MinAllowedNonAnchorChannelRemoteFee = Background - 250 * AnchorChannelFee = Background * NonAnchorChannelFee = Normal * ChannelCloseMinimum = Background

Bug Fixes

  • Calling ChannelManager::close_channel[_with_feerate_and_script] on a channel which did not exist would immediately hang holding several key ChannelManager-internal locks (#2657).
  • Channel information updates received from a failing HTLC are no longer applied to our NetworkGraph. This prevents a node which we attempted to route a payment through from being able to learn the sender of the payment. In some rare cases, this may result in marginally reduced payment success rates (#2666).
  • Anchor outputs are now properly considered when calculating the amount available to send in HTLCs. This can prevent force-closes in anchor channels when sending payments which overflow the available balance (#2674).
  • A peer that sends an update_fulfill_htlc message for a forwarded HTLC, then reconnects prior to sending a commitment_signed (thus retransmitting their update_fulfill_htlc) may result in the channel stalling and being unable to make progress (#2661).
  • In exceedingly rare circumstances, messages intended to be sent to a peer prior to reconnection can be sent after reconnection. This could result in undefined channel state and force-closes (#2663).

Backwards Compatibility

  • Creating a blinded path to receive a payment then downgrading to LDK prior to 0.0.117 may result in failure to receive the payment (#2413).
  • Calling ChannelManager::pay_for_offer or ChannelManager::create_refund_builder may prevent downgrading to LDK prior to 0.0.118 until the payment times out and has been removed (#2039).

Node Compatibility

  • LDK now sends a bogus channel_reestablish message to peers when they ask to resume an unknown channel. This should cause LND nodes to force-close and broadcast the latest channel state to the chain. In order to trigger this when we wish to force-close a channel, LDK now disconnects immediately after sending a channel-closing error message. This should result in cooperative peers also working to confirm the latest commitment transaction when we wish to force-close (#2658).

Security

0.0.118 expands mitigations against transaction cycling attacks to non-anchor channels, though note that no mitigations which exist today are considered robust to prevent the class of attacks. * In order to mitigate against transaction cycling attacks, non-anchor HTLC transactions are now properly re-signed before broadcasting (#2667).

In total, this release features 61 files changed, 3470 insertions, 1503 deletions in 85 commits from 12 authors, in alphabetical order: * Antonio Yang * Elias Rohrer * Evan Feenstra * Fedeparma74 * Gursharan Singh * Jeffrey Czyz * Matt Corallo * Sergi Delgado Segura * Vladimir Fomene * Wilmer Paulino * benthecarman * slanesuke

Go to Repo Go to Release

unchained-capital/caravan: caravan-v0.7.0

Published: 2023-10-23 21:23:28 UTC

0.7.0 (2023-10-23)

Features

  • hermit: hermit PSBT signing for pre-product key recovery (#308) (04ca0ce)

Go to Repo Go to Release

vulpemventures/marina: v0.5.5

Published: 2023-10-20 15:13:40 UTC

Go to Repo Go to Release

bitcoin/bitcoin: v25.1

Published: 2023-10-19 14:46:01 UTC

Bitcoin Core version 25.1 is now available from:

https://bitcoincore.org/bin/bitcoin-core-25.1/

For the release notes please see the git repository:

https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-25.1.md

Do not use the links provided by GitHub, rather use the above download links, they are guaranteed to be generated deterministically and signed.

Go to Repo Go to Release

unchained-capital/caravan: caravan-v0.6.3

Published: 2023-10-18 17:05:12 UTC

0.6.3 (2023-10-18)

Bug Fixes

  • deps: bump @babel/traverse from 7.21.3 to 7.23.2 (#344) (5f231e0)

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.7

Published: 2023-10-18 11:08:00 UTC

New feature

  • Pull Payment: Add QR scanner for destination and infer payment method (#5358) @dennisreimann
  • Greenfield: Allow deleting user by email (#5372) @Kukks
  • Greenfield: Add missing checkout (V2) settings (#5406, #5403) @dennisreimann

Bug fixes

  • The payments report wasn't properly accounting for Liquid assets and some altcoins (#5388 #5371) @Kukks
  • Switching currencies in the checkout page may have inversed Amount Due and Recommended Fee (#5390) @dennisreimann
  • Reporting now properly formats decimals (#5363) @dennisreimann
  • API docs: Fix several errors and warnings (#5380) @ai-oleynikov
  • Fix Poloniex and Ripio rate provider (#5365) @Kukks
  • Removed unused Argoneum and Exchangerate.host rate provider (#5365) @Kukks
  • Fix: If a store was accepting USDt, invoices wouldn't be processed properly. @Kukks
  • Email rules, Recipients required even if "send mail to buyer" (#5345 #5357) @dennisreimann
  • Fix: BTCPayServer.HostedServices.BitpayIPNSender fail to send notifications on some locale (Fix #5361) @AdilElFarissi

Improvements

  • Invoice: Improve payment details page (#5362) @dennisreimann
  • Crowdfund: Improve no perks case (#5378 #5376) @dennisreimann
  • Switched recommended exchanges for COP and UGX to yadio @Kukks
  • Forms: Make zip code a required field in predefined address form (#5405) @dennisreimann
  • Adjust swagger doc to latest change in Greenfield API @ndeet

Go to Repo Go to Release

BlueWallet/BlueWallet: v6.4.9

Published: 2023-10-17 18:41:35 UTC

  • ADD: airdrop ms cosigner (#5682)

  • FIX: Only make call if watch is reachable

  • FIX: better tx list update when transactions actually changed (rel #5615)

  • FIX: pull-to-refresh while inside the wallet doesnt update the tx list (closes #5615)

  • FIX: incorrect fees occasionally (for some electrum servers); better fee estimation

  • FIX: unable to delete faulty wallet (rel #5661)

  • FIX: Settings was not fully visible on newer iPhone models

  • FIX: round circles on Multisig screen

  • FIX: stateURL default value

  • FIX: import single-sig wallet descriptor (closes #5637)

  • REF: Camera Authorization Request

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.11

Published: 2023-10-17 15:39:11 UTC

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.10

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.10...android-v2.0.11 - lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.5.9...v1.5.10

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

lnbits/lnbits: 0.11.1

Published: 2023-10-17 11:50:32 UTC

This bugfix release fixes several issues with 0.11.0

Warning

Due to a mistake on the last merge into main, we had to revert some commits on it. If you run into issues pulling from main, reset your local main branch like this git reset origin/main --hard

What's Changed

Go to Repo Go to Release

rust-bitcoin/rust-bitcoin: bitcoin-0.30.2

Published: 2023-10-14 20:30:14 UTC

What's Changed

New Contributors

Full Changelog: https://github.com/rust-bitcoin/rust-bitcoin/commits/bitcoin-0.30.2

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.10

Published: 2023-10-10 11:42:51 UTC

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.9

  • Updated the wording of the migration message in the legacy application. Added a date where some legacy services (swap-in and pay-to-open) will be disabled (November 1st).
  • 2 bug fixes in lightning-kmp.

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.9...android-v2.0.10 - lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.5.8...v1.5.9

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

bisq-network/bisq: v1.9.14

Published: 2023-10-09 22:06:35 UTC

Note: We re-uploaded the binary for macOS on the 26th of October. The new binary fixes several issues that caused crashes on macOS.

Release notes

In this release, we add MercadoPago as a new payment method for our Argentinian users. Moreover, the Bisq Price Index uses the blue dollar (free market rate) rate for the Argentine Pesos market. Other changes include an updated Java runtime, bug fixes, and performance improvements.

See https://github.com/bisq-network/bisq/milestone/82?closed=1 for more details.

Improvements

Bug fixes

Verification

For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file

Url of the signing key (Alejandro García): https://bisq.network/pubkey/E222AA02.asc Full fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02

Import the key: curl https://bisq.network/pubkey/E222AA02.asc | gpg --import GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.

How to verify signatures? gpg --digest-algo SHA256 --verify BINARY{.asc*,} Replace BINARY with the file you downloaded (e.g. Bisq-1.9.14.dmg)

Verify jar file inside binary: You can verify on OSX the jar file with: shasum -a256 [PATH TO BISQ APP]/Bisq.app/Contents/app/desktop-1.9.14-all.jar The output need to match the value from the Bisq-1.9.14.jar.txt file.

There are three hashes within the Bisq-1.9.14.jar.txt file (macOS, Windows, Linux). If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 15.0.9 and the v1.9.14 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.

API

Starting with v1.9.0 you can use pre-built versions of the Bisq cli (bisq-cli-v1.9.14.zip) and Bisq daemon (bisq-daemon-v1.9.14.zip) to use Bisq without touching the user interface.

Just download the archives and extract them locally. You have to run the daemon to access the local Bisq daemon API endpoints.

To run daemon.jar on Mainnet: bash $ java -jar daemon.jar --apiPassword=becareful

If you just want to control your headless daemon within your terminal you have to run the Bisq cli as well.

Again just download the bisq-cli archive and extract it locally.

To call getversion from cli.jar bash $ java -jar cli.jar --password=becareful getversion

You can use the Bisq API to access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades.

The Bisq API is based on the gRPC framework, and any supported gRPC language binding can be used to call Bisq API endpoints.

You'll find in-depth documentation and examples under following link: https://bisq-network.github.io/slate/#introduction

Bisq gRPC API reference documentation example source code is hosted on GitHub at https://github.com/bisq-network/bisq-api-reference. Java and Python developers interested in bot development may find this Intellij project useful for running the existing examples, and writing their own bots.

For additional developer support please join Development - Bisq v1 on Matrix.

Known issues with installation

macOS:

We removed notarization from our build pipeline because of of the risk of Apple certification revocation (see https://github.com/bisq-network/bisq/discussions/6341). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section If you want to open an app that hasn’t been notarized or is from an unidentified developer

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:

enter following command in Apple Terminal sudo xattr -rd com.apple.quarantine /Applications/Bisq.app hit enter and you will be prompted to enter your password to be able to execute the command as super user After running this successfully you should be able to start Bisq as always.

Windows:

We removed the developer code signing because of the same reason as with Apple. For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.

If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files): C:\Users<username>\AppData\Local\Bisq

[2] Data directory (contains all Bisq data including wallet): C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)

Linux:

Hint for Debian users: If you have problems starting Bisq on Debian use: /opt/bisq/bin/Bisq

If your Linux distro does not support .deb files please follow this instruction: cd ~/Downloads mkdir tmp cd tmp ar x ../Bisq-64bit-1.9.14.deb sudo tar Jxvf data.tar.xz sudo cp -rp opt/Bisq /opt/ That instruction is not tested on many different distros. If you encounter problems please report it in a Github issue so we can improve it.

Credits

Thanks to everyone who directly contributed to this release:

  • @alejandrogarcia83
  • @alvasw
  • @alyokaz
  • @gabernard
  • @HenrikJannsen
  • @jmacxx
  • @napoly
  • @rodvar

A special thanks to our first time contributor: - @alyokaz - @rodvar

As well as to everyone that helped with translations on Transifex.

Go to Repo Go to Release

lnbits/lnbits: 0.11.0

Published: 2023-10-05 10:38:53 UTC

This release's name is dedicated to Leo. Leo is easily one of the nicest people in Bitcoin and has been active in the LNbits chat since the beginning, helping people debug, and coming up with new great ideas such as his Bitcoin Laisee (red envelopes of bitcoin given to people on the Chinese New Year). Thank you Leo!

Among countless optimizations and stability improvements that make LNbits faster and more reliable, we are thrilled to announce a new exciting feature which we (with the incredible work of @jackstar12) have been working on for some time: The LNbits node manager.

LNbits node manager

This release introduces the LNbits node manager which allows you to manage your Lightning channels directly from within your LNbits. The node manager works with Core Lightning and LND and we plan to add support for more Lightning backends soon.

telegram-cloud-photo-size-4-5834447956625964640-y

Channel management

Manage your Lightning channels directly from within your LNbits.

telegram-cloud-photo-size-4-5834447956625964638-x

Transaction history

View the transaction history on your node to see a list of all incoming and outgoing payments.

telegram-cloud-photo-size-4-5834447956625964634-y

Public node page

The node manager also offers a public node page that you can share with others who want to open a channel to your node.

telegram-cloud-photo-size-4-5834447956625964635-y

Activate in admin UI

You can activate the node UI in your LNbits admin panel.

telegram-cloud-photo-size-4-5834447956625964636-y

Other notable changes

Upgrade FastAPI

We have upgraded the API framework that we use in LNbits. That means that most extensions need to be update to work with this release. Please log in as an admin user and update your extensions to the latest version after upgrading your LNbits. (Thank you @dni and @talvasconcelos grinding through and patching ALL the extensions)

What's Changed

New Contributors

Full Changelog: https://github.com/lnbits/lnbits/compare/0.10.10...0.11.0

Go to Repo Go to Release

rsksmart/rskj: FINGERROOT-5.3.0

Published: 2023-10-05 02:22:58 UTC

Summary

This update introduces several enhancements to the client's JSON-RPC interface, along with notable improvements in performance and the resolution of a few non-critical bugs.

Although this upgrade is not mandatory, we always recommend that users upgrade their nodes to the latest version available.

What's New in RSKj 5.3.0

A non-comprehensive list of changes included in this version is:

  • Introducing support for blockNumber and blockID arguments in the eth_estimateGas JSON-RPC method in #2080.
  • Ignore replaced transactions in pending transactions gas cost calculations in #2105.
  • Fix the response format on the eth_hashrate JSON-RPC method in #2074.
  • Get rid of manual command-line arguments parsing and introduce --help and --version command-line flags using the Picocli framework in #2027.
  • Show the rsk_protocolVersion JSON-RPC method return value as hexadecimal in #2134.
  • Support the input field in JSON-RPC requests for compatibility with the Web3js framework library in #2075.
  • Increased receipts cache size and reduced blooms block size in #2127.

Full Changelog: https://github.com/rsksmart/rskj/compare/FINGERROOT-5.2.0...FINGERROOT-5.3.0

Fingerroot 5.3.0 Milestone: https://github.com/rsksmart/rskj/milestone/38

Reproducible Build

SHA256 (see Reproducible Build guide for further details): a9d5c6080aecd96c849e153dd4648072323c772f860c0c4fd812a321fc18ae90 rskj-core-5.4.0-FINGERROOT-all.jar

Go to Repo Go to Release

lightningdevkit/rust-lightning: v0.0.117

Published: 2023-10-04 02:29:10 UTC

0.0.117 - Oct 3, 2023 - "Everything but the Twelve Sinks"

API Updates

  • ProbabilisticScorer's internal models have been substantially improved, including better decaying (#1789), a more granular historical channel liquidity tracker (#2176) and a now-default option to make our estimate for a channel's current liquidity nonlinear in the channel's capacity (#2547). In total, these changes should result in improved payment success rates at the cost of slightly worse routefinding performance.
  • Support for custom TLVs for recipients of HTLCs has been added (#2308).
  • Support for generating transactions for third-party watchtowers has been added to ChannelMonitor/Updates (#2337).
  • KVStorePersister has been replaced with a more generic and featureful KVStore interface (#2472).
  • A new MonitorUpdatingPersister is provided which wraps a KVStore and implements Persist by writing differential updates rather than full ChannelMonitors (#2359).
  • Batch funding of outbound channels is now supported using the new ChannelManager::batch_funding_transaction_generated method (#2486).
  • ChannelManager::send_preflight_probes has been added to probe a payment's potential paths while a user is providing approval for a payment (#2534).
  • Fully asynchronous ChannelMonitor updating is available as an alpha preview. There remain a few known but incredibly rare race conditions which may lead to loss of funds (#2112, #2169, #2562).
  • ChannelMonitorUpdateStatus::PermanentFailure has been removed in favor of a new ChannelMonitorUpdateStatus::UnrecoverableError. The new variant panics on use, rather than force-closing a channel in an unsafe manner, which the previous variant did (#2562). Rather than panicking with the new variant, users may wish to use the new asynchronous ChannelMonitor updating using ChannelMonitorUpdateStatus::InProgress.
  • RouteParameters::max_total_routing_fee_msat was added to limit the fees paid when routing, defaulting to 1% + 50sats when using the new from_payment_params_and_value constructor (#2417, #2603, #2604).
  • Implementations of UtxoSource are now provided in lightning-block-sync. Those running with a full node should use this to validate gossip (#2248).
  • LockableScore now supports read locking for parallel routefinding (#2197).
  • ChannelMonitor::get_spendable_outputs was added to allow for re-generation of SpendableOutputDescriptors for a channel after they were provided via Event::SpendableOutputs (#2609, #2624).
  • [u8; 32] has been replaced with a ChannelId newtype for chan ids (#2485).
  • NetAddress was renamed SocketAddress (#2549) and FromStr impl'd (#2134)
  • For no-std users, parse_onion_address was added which creates a NetAddress from a "...onion" string and port (#2134, #2633).
  • HTLC information is now provided in Event::PaymentClaimed::htlcs (#2478).
  • The success probability used in historical penalties when scoring is now available via historical_estimated_payment_success_probability (#2466).
  • RecentPaymentDetails::*::payment_id has been added (#2567).
  • Route now contains a RouteParameters rather than a PaymentParameters, tracking the original arguments passed to routefinding (#2555).
  • Balance::*::claimable_amount_satoshis was renamed amount_satoshis (#2460)
  • *Features::set_*_feature_bit have been added for non-custom flags (#2522).
  • channel_id was added to SpendableOutputs events (#2511).
  • counterparty_node_id and channel_capacity_sats were added to ChannelClosed events (#2387).
  • ChannelMonitor now implements Clone for Cloneable signers (#2448).
  • create_onion_message was added to build an onion message (#2583, #2595).
  • HTLCDescriptor now implements Writeable/Readable (#2571).
  • SpendableOutputDescriptor now implements Hash (#2602).
  • MonitorUpdateId now implements Debug (#2594).
  • Payment{Hash,Id,Preimage} now implement Display (#2492).
  • NodeSigner::sign_bolt12_invoice{,request} were added for future use (#2432)

Backwards Compatibility

  • Users migrating to the new KVStore can use a concatentation of [{primary_namespace}/[{secondary_namespace}/]]{key} to build a key compatible with the previous KVStorePersister interface (#2472).
  • Downgrading after receipt of a payment with custom HTLC TLVs may result in unintentionally accepting payments with TLVs you do not understand (#2308).
  • Route objects (including pending payments) written by LDK versions prior to 0.0.117 won't be retryable after being deserialized by LDK 0.0.117 or above (#2555).
  • Users of the MonitorUpdatingPersister can upgrade seamlessly from the default KVStore Persist implementation, however the stored ChannelMonitors are deliberately unreadable by the default Persist. This ensures the correct downgrade procedure is followed, which is: (#2359)
    • First, make a backup copy of all channel state,
    • then ensure all ChannelMonitorUpdates stored are fully applied to the relevant ChannelMonitor,
    • finally, write each full ChannelMonitor using your new Persist impl.

Bug Fixes

  • Anchor channels which were closed by a counterparty broadcasting its commitment transaction (i.e. force-closing) would previously not generate a SpendableOutputs event for our to_remote (i.e. non-HTLC-encumbered) balance. Those with such balances available should fetch the missing SpendableOutputDescriptors using the new ChannelMonitor::get_spendable_outputs method (#2605).
  • Anchor channels may result in spurious or missing Balance entries for HTLC balances (#2610).
  • ChannelManager::send_spontaneous_payment_with_retry spuriously did not provide the recipient with enough information to claim the payment, leading to all spontaneous payments failing (#2475). send_spontaneous_payment_with_route was unaffected.
  • The keysend feature on node announcements was spuriously un-set in 0.0.112 and has been re-enabled (#2465).
  • Fixed several races which could lead to deadlock when force-closing a channel (#2597). These races have not been seen in production.
  • The ChannelManager is persisted substantially less when it has not changed, leading to substantially less I/O traffic for it (#2521, #2617).
  • Passing new block data to ChainMonitor no longer results in all other monitor operations being blocked until it completes (#2528).
  • When retrying payments, any excess amount sent to the recipient in order to meet an htlc_minimum constraint on the path is now no longer included in the amount we send in the retry (#2575).
  • Several edge cases in route-finding around HTLC minimums were fixed which could have caused invalid routes or panics when built with debug assertions (#2570, #2575).
  • Several edge cases in route-finding around HTLC minimums and route hints were fixed which would spuriously result in no route found (#2575, #2604).
  • The user_channel_id passed to SignerProvider::generate_channel_keys_id for inbound channels is now correctly using the one passed to ChannelManager::accept_inbound_channel rather than a default value (#2428).
  • Users of impl_writeable_tlv_based! no longer have use requirements (#2506).
  • No longer force-close channels when counterparties send a channel_update with a bogus htlc_minimum_msat, which LND users can manually build (#2611).

Node Compatibility

  • LDK now ignores error messages generated by LND in response to a shutdown message, avoiding force-closes due to LND bug 6039. This may lead to non-trivial bandwidth usage with LND peers exhibiting this bug during the cooperative shutdown process (#2507).

Security

0.0.117 fixes several loss-of-funds vulnerabilities in anchor output channels, support for which was added in 0.0.116, in reorg handling, and when accepting channel(s) from counterparties which are miners. * When a counterparty broadcasts their latest commitment transaction for a channel with anchor outputs, we'd previously fail to build claiming transactions against any HTLC outputs in that transaction. This could lead to loss of funds if the counterparty is able to eventually claim the HTLC after a timeout (#2606). * Anchor channels HTLC claims on-chain previously spent the entire value of any HTLCs as fee, which has now been fixed (#2587). * If a channel is closed via an on-chain commitment transaction confirmation with a pending outbound HTLC in the commitment transaction, followed by a reorg which replaces the confirmed commitment transaction with a different (but non-revoked) commitment transaction, all before we learn the payment preimage for this HTLC, we may previously have not generated a proper claiming transaction for the HTLC's value (#2623). * 0.0.117 now correctly handles channels for which our counterparty funded the channel with a coinbase transaction. As such transactions are not spendable until they've reached 100 confirmations, this could have resulted in accepting HTLC(s) which are not enforcible on-chain (#1924).

In total, this release features 121 files changed, 20477 insertions, 8184 deletions in 381 commits from 27 authors, in alphabetical order: * Alec Chen * Allan Douglas R. de Oliveira * Antonio Yang * Arik Sosman * Chris Waterson * David Caseria * DhananjayPurohit * Dom Zippilli * Duncan Dean * Elias Rohrer * Erik De Smedt * Evan Feenstra * Gabor Szabo * Gursharan Singh * Jeffrey Czyz * Joseph Goulden * Lalitmohansharma1 * Matt Corallo * Rachel Malonson * Sergi Delgado Segura * Valentine Wallace * Vladimir Fomene * Willem Van Lint * Wilmer Paulino * benthecarman * jbesraa * optout

Go to Repo Go to Release

lightningnetwork/lnd: v0.17.0-beta

Published: 2023-10-03 18:16:00 UTC

Database Migrations

There is a single database migration in this release. This migration deletes some space on disk that previously stored the last sweep transaction in the sweeper.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.17.0-beta.sig and manifest-v0.17.0-beta.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.17.0-beta.sig manifest-v0.17.0-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Tue Oct 3 11:03:53 2023 PDT gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Timestamp

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.17.0-beta.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands: ots verify manifest-roasbeef-v0.17.0-beta.sig.ots -f manifest-roasbeef-v0.17.0-beta.sig

Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Verifying the Release Binaries

Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.21.0, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.

The make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag> can be used.

Finally, you can also verify the tag itself with the following command:

$ git verify-tag v0.17.0-beta gpg: Signature made Tue 03 Oct 2023 05:22:22 PM UTC using RSA key ID 9B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>"

Verifying the Docker Images

To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):

shell $ docker run --rm --entrypoint="" lightninglabs/lnd:v0.17.0-beta /verify-install.sh v0.17.0-beta $ OK=$? $ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done $ docker run lightninglabs/lnd [command-line options]

Building the Contained Release

Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that vendor.tar.gz and lnd-source-v0.17.0-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.17.0-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.0-beta" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.17.0-beta" ./cmd/lncli

The -mod=vendor flag tells the go build command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.

Additionally, it's now possible to use the enclosed release.sh script to bundle a release for a specific system like so:

make release sys="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

Release Notes

https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.17.0.md

Contributors (Alphabetical Order)

  • Aljaz Ceru
  • Amin Bashiri
  • BhhagBoseDK
  • Bjarne Magnussen
  • Carla Kirk-Cohen
  • Daniel McNally
  • djkazic
  • Elle Mouton
  • Emilio Ziniades
  • Erik Arvstedt
  • ErikEk
  • Eval EXEC
  • feelancer21
  • gabbyprecious
  • George Tsagkarelis
  • Guillermo Caracuel
  • Hampus Sjöberg
  • Harsha
  • hieblmi
  • Jamal James
  • Jordi Montes
  • Keagan McClelland
  • Konstantin Nick
  • Lele Calo
  • Matheus Degiovani
  • Matt Morehouse
  • Maxwell Sayles
  • Michael Street
  • MG-ng
  • Olaoluwa Osuntokun
  • Oliver Gugger
  • P. Reis
  • Peter Todd
  • Pierre Beugnet
  • RandyMcMillan
  • Satarupa Deb
  • Shaurya Arora
  • Slyghtning
  • Suheb
  • Torkel Rogstad
  • Viktor Tigerström
  • Yong Yu
  • ziggie1984
  • zx9r

Go to Repo Go to Release

ACINQ/bitcoin-lib: v0.30

Published: 2023-10-03 11:55:34 UTC

What's Changed

Full Changelog: https://github.com/ACINQ/bitcoin-lib/compare/v0.29...v0.30

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.9

Published: 2023-09-29 08:54:35 UTC

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.8

  • Added notice in home screen when incoming Lightning payments are rejected, to make them more visible.
  • Added the last swap-in failed attempt in the swap-in screen.
  • Several bug fixes in lightning-kmp.

Full changelog: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.8...android-v2.0.9 - lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.5.6...v1.5.8

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

raspiblitz/raspiblitz: v1.10.0

Published: 2023-09-28 16:04:02 UTC

Based on new RaspiOS image, increased stability & much updates: Bitcoin 25.0.0, LND 0.16.4, Core Lightning 23.08.1 .. see CHANGES for details.

Go to Repo Go to Release

vulpemventures/marina: v0.5.4

Published: 2023-09-28 12:00:56 UTC

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.6

Published: 2023-09-27 08:35:24 UTC

An update is recommended if you share your server with many users. Your server could crash (Error HTTP 500) if you have a high number of users.

Bug fixes

  • Fix: After a while, a busy server would send error HTTP 500 (#5354) @NicolasDorier
  • Fix: Exchangerate.host falsly appear as Yadio in the UI (#5347) @NicolasDorier

Improvements

  • Improve receipt info display (#5350) @dennisreimann
  • Recommend Yadio for ARS currency rate (#5347) @NicolasDorier
  • Recommend exchangeratehost for COP currency rate @NicolasDorier
  • Hide 'Connection established' when connection to server come back (#5352) @NicolasDorier

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.5

Published: 2023-09-22 14:49:08 UTC

New feature

  • Reporting: Add payouts (#5320) @Kukks
  • Wallet: Delete custom labels (#5324, #5237) @dennisreimann
  • Dashboard: Show revenue data for keypad (#5317) @dennisreimann
  • Dashboard: Show the number of paid invoices in the last 7 days (#5316, #5300) @dennisreimann
  • Login: Add Remember Me button (#5307, #5302) @dennisreimann
  • Archive stores and apps (#5296) @dennisreimann
  • New permission: Can archive pull payment (#5274) @Kukks
  • Pull Payment: Show QR code for LNURL-Withdraw (#5274) @Kukks

Bug fixes

  • Fix: Transient error 500 when accessing the wallet page (#5326, #5328) @NicolasDorier
  • Fix: Revert to default block explorer button wasn't working (#5340) @NicolasDorier
  • Payment Request: Reflect processing status for on-chain payments (#5309, #5297) @dennisreimann
  • NFC: Fix error display (#5305) @dennisreimann

Improvements

  • Email Rules: Add default texts and document placeholders (#5314) @dennisreimann
  • UI: The on-chain addresses should only be truncated on the middle (#5313, #5311) @dennisreimann
  • Store settings: Allow configuring NFC permission beforehand (#5319) @Kukks
  • Remove legacy export (#5293) @NicolasDorier

Go to Repo Go to Release

cryptoadvance/specter-desktop: v2.0.2

Published: 2023-09-21 13:40:05 UTC

Please create a full backup before migrating or any major internal changes like switching to an electrum based installation. You can easily create a backup in Settings --> Backup Specter (zip file).

Artifacts

Specter is available in several forms: as a GUI application, as a binary that can be executed like a web app, and as a PyPI package. Additionally, Specter is available as a Docker image via the awesome Chiang Mai LN devs.

Signed hashsum files are available for all binaries.

GUI Application

This is a GUI application with a windowed interface, which includes the Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)

Note on Linux: you need to set up udev rules (included in the archive). Check out the readme.

Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.

specterd

Specterd is a command-line program that runs only the Specter server, behaving like a traditional web application. Supported platforms: Windows, MacOS, Linux (x86_64)

PyPi Packages

If you’re experienced Python user and/or developer, you might appreciate the pypi-packages which are also available on our github-release-page.

Signatures and hashes

SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key. You can get the public key from here. Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7 This key has been signed by @k9ert's key. For more information about Verifying signatures, see, e.g. this video.

Release notes

  • Bugfix: Add missing signet key #2368 (Manolis Mandrapilias)
  • Bugfix: Jade displaying wrong multisig addresses for descriptors using multi() #2366 (Manolis Mandrapilias)
  • Bugfix: JSON parsing issues when copy & pasting wallet data from PDF #2355 (Manolis Mandrapilias)
  • Bugfix: #2319 #2330 (k9ert)
  • Bugfix: fix specter.node has no getrpc() #2327 (k9ert)
  • Bugfix: Update spotbit api url and path #2372 (Benjamin B)
  • Chore(deps): Bump semver from 5.7.1 to 5.7.2 #2353 (dependabot[bot])
  • Chore(deps): Bump semver from 6.3.0 to 6.3.1 in /pyinstaller/electron #2352 (dependabot[bot])
  • Chore: Regex change to capture labels in wallet data imports better #2357 (Manolis Mandrapilias)
  • Chore: Use prettier for Electron app #2347 (Manolis Mandrapilias)
  • Chore: Optional ENFORCEHWIINITIALISATIONATSTARTUP #2383 (k9ert)
  • Chore: remove SpecterUri #2358 (k9ert)
  • Chore: updating flask_babel fixes #2218 #2359 (k9ert)
  • Feature: Enable import of a multisig wallet that uses a multi-descriptor #2349 (Manolis Mandrapilias)
  • Feature: Implement automatic wallet import via Specter URI for MacOS #2344 (Manolis Mandrapilias)
  • Security: Patched Fix Electron vulnerable to out-of-package code execution when launched with arbitrary cwd #2380 (Sergev ₱)
  • Security: Fix login open redirect due to next parameter manipulation #2350 (zealsham)

Remarks

We fixed #2343 and that fix did, in some cases, cause trouble when signing transactions with Jades. If you're suffering that issue, you can enforce an hwi-initialisation which is known to fix that issue. This might then have the downside to with usb-devices being plugged in at startup. In order to do that, you need to setup the env-var ENFORCEHWIINITIALISATIONATSTARTUP to true. This is currently not that easy if you run Specter via an Application.

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.8

Published: 2023-09-20 17:35:10 UTC

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.7

This is a bug fix release. - Fixed an issue where payment would be prevented when channels were in closing - Fixed an issue where swaps would not be attempted due to a race condition between the swap-in wallet and the peer connection.

Diff: - phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.0.7...android-v2.0.8 - lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.5.5...v1.5.6

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.7

Published: 2023-09-19 08:45:45 UTC

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.6

Electrum Client rework

The Electrum connection logic has been improved. There should be less issues with Electrum connection, especially when connection fails and needs to be reestablished. See ACINQ/lightning-kmp#512 for details

Increased size of logs export

The log file could be sometimes truncated by the SL4J rolling system which could result in less logs than available.

Added support for per-app localisation

Phoenix can now use a different language than the rest of the device. This feature is only available on Android 13+.

Improved Czech and French translation

Thanks @MasterixCZ for working on this.

Several bug fixes and UI improvements

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

ElementsProject/lightning: v23.08.1

Published: 2023-09-13 20:30:34 UTC

Bugfix release for bad issues found since 23.08 which can't wait for 23.11, and some minor low-impact fixes (e.g. docker images, documentation, CI).

  • JSON-RPC: Fixed a wrong number type being used in routes (#6642) and showrunes on a specific rune would always say stored: false. (#6640)
  • clnrest now works on MacOS (#6605)
  • Build: test for python3 or python, rather than assuming python3 (#6630)
  • Plugins: renepay: various minor fixes. (#6632)

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.6

Published: 2023-09-13 13:28:11 UTC

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Phoenix Android app (1.x) to 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.5

Fixed several issues related to LNURL

  • withdrawals will now offer the user to withdraw the maximum amount available, instead of the minimum;
  • LUD-17 urls (starting with lnurlp, lnurlw, keyauth) are now properly parsed.

The Czech translation has been improved

Thanks @MasterixCZ and @margre8 for working on this.

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

lnbits/lnbits: 0.10.10

Published: 2023-09-11 10:07:28 UTC

What's Changed

New Contributors

Full Changelog: https://github.com/lnbits/lnbits/compare/0.10.9...0.10.10

Go to Repo Go to Release

vulpemventures/marina: v0.5.3

Published: 2023-09-09 00:34:30 UTC

What's Changed

Full Changelog: https://github.com/vulpemventures/marina/compare/v0.5.2...v0.5.3

Go to Repo Go to Release

rsksmart/rskj: FINGERROOT-5.2.0

Published: 2023-09-05 16:04:59 UTC

Summary

This update establishes RocksDB as the default storage library, delivering relevant performance enhancements for database operations. It's important to emphasize that nodes currently utilizing LevelDB will remain unaffected by this update. To switch to RocksDB as the default database, users must take the following steps: delete their existing database files and restart the node to perform a complete blockchain synchronization.

Although this upgrade is not mandatory, we always recommend that users upgrade their nodes to the latest version available.

What's New in RSKj 5.2.0

A non-comprehensive list of changes included in this version is:

  • Make RocksDb the default database library in #2063.
  • Change default networkCidr config value in #2070.

Full Changelog: https://github.com/rsksmart/rskj/compare/FINGERROOT-5.1.0...FINGERROOT-5.2.0

Fingerroot 5.2.0 Milestone: https://github.com/rsksmart/rskj/milestone/37

Reproducible Build

SHA256 (see Reproducible Build guide for further details): 70ae5209720ad6477c1c32d8a8d94e29ebb0db25d57e9903546519d614eddf9f rskj-core-5.2.0-FINGERROOT-all.jar

Go to Repo Go to Release

bitcoin-core/secp256k1: v0.4.0

Published: 2023-09-04 16:49:43 UTC

This release adds a new ellswift module that implements ElligatorSwift encoding for public keys and x-only Diffie-Hellman key exchange for them.

For a list of changes, see the CHANGELOG.md.

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.4

Published: 2023-09-02 14:28:20 UTC

Minor update recommended for deployment stacks which were using MySQL/SQLite backend in the past such as Raspiblitz, Umbrel, Embassy OS.

We fix a migration to postgres error that has been introduced a few versions ago.

New feature

  • Display wallet balance in default currency in the on-chain wallet navigation (#5281) @vbouzon

Bug fixes

  • Fix: Error on the MigrationStartupTask (#5233) @NicolasDorier
  • Fix: The "Open in wallet" button in the checkout page was not working properly on some browsers (#5284) @dennisreimann

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.5

Published: 2023-09-01 19:04:07 UTC

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Phoenix Android app (1.x) to 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.4

Added localisation for 🇩🇪 German, 🇪🇸 Spanish, 🇵🇹 Portuguese and 🇨🇿 Czech localisation.

Thanks @myxmaster for the help with German translation!

Spanish, Portuguese, and Czech localisation are partial, and may not be accurate. However, it's still better than just displaying English.

Handle callback action for sucessful LNURL payments

Also, LNURL payments made prior to this version should display the successAction result correctly. See #404.

Add warning regarding legacy swap addresses

For users who migrate from v1.4.x, warnings have been added about reusing legacy swap-in addresses. These addresses should not be used anymore after migration. The new wallet will only support the new address displayed in the receive screen.

If an old legacy address has benn used after the migration is done, contact support: phoenix@acinq.co

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

sparrowwallet/sparrow: 1.7.9

Published: 2023-08-31 11:25:46 UTC

  • Add wallet accounts summary dialog (View menu)
  • Support import and export of keystore labels in descriptor (ur:crypto-output) QR codes
  • Propagate transaction label changes to inputs, outputs and addresses where their existing labels were set in the same manner
  • Upgrade to HWI v2.3.1
  • Suggest clearing any existing keystores when the script type is changed in the Settings tab
  • Add fulcrum.sethforprivacy.com public mainnet Electrum server
  • Avoid adding inputs when constructing a consolidation transaction replacement, allowing output to decrease
  • Add mempoolFullRbf config variable to enable RBF functionality on mempool transactions without checking sequence flags (default false)
  • Refactor transaction and UTXO table column sorting, add default sorting on new history if table was previously empty
  • Add tooltip to account tab where label is truncated
  • Add Jade multisig wallet import
  • Bug fix: In Terminal, check if theme is present to avoid exception on UTXO history update
  • Bug fix: Support CompactSeedQR scanning using zbar
  • Bug fix: Fix single character multisig threshold parsing issue
  • Bug fix: Handle Bitcoin Core bug where listwalletdir returns empty results even when wallets are loaded
  • Bug fix: Use ControlPort auto instead of UNIX socket for internal Tor control to avoid a bug where UNIX socket path is too long

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.4

Published: 2023-08-30 09:29:10 UTC

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Android app (1.x) to Android 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.2

This release fixes several issues and brings a few improvements in the app.

Swaps are now attempted at each block

Previous versions required the app to be restarted in order to attempt pending swap-ins. This is not the case anymore, the app will attempt swaps at each new block. System notifications for failed swaps have been reduced to prevent spam.

Added link to scanner in receive screen

Receiving funds over LNURL required users to click on Send in order to open the scanner, which is counterintuitive. This has been fixed by adding back the "Use LNURL link" button in the Receive screen, like in the legacy app.

Other

  • Reconnecting to the Peer and the Electrum servers should be snappier
  • Fixed an issue where connection to the Peer would not be made (#400)

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.3

Published: 2023-08-26 12:16:21 UTC

Bug fixes

  • Fix LNDHub connection strings parsing @Kukks
  • Paying through LNDHub with an explicit amount wouldn't send the right amount @Kukks
  • The Open with wallet deep link in the checkout page wasn't working properly on some browsers. @dennisreimann
  • POS: Fix alignment of items in static view (#5271) @dennisreimann
  • Only show LNAddress section if the user has the permission @Kukks
  • Fix crash on /wallets/transactions with non zero skip parameter (#5183) @NicolasDorier
  • Do not block payments on LN while syncing if it is not internal node (#5269) @Kukks
  • Fix LN payout manual payments UI crashing when payouts are not tied to pull payment @Kukks

Improvements

  • If the PoSData property is a stringified JSON, presents it nicely in invoice details (#5275) @dennisreimann
  • POS: Unify item display in editor (#5266 #5272) @dennisreimann
  • remove store ID from view request url (#5256) @dstrukt

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.2

Published: 2023-08-24 13:09:28 UTC

This release bumps the minimal Android version to android 8+ to prevent installing the app on old, incompatible devices.

Users with Android 7.1 or older can still use version 1.4.27, but we strongly recommend upgrading to a recent Android version that receives security patches.

Migration for existing wallets

For users upgrading from the legacy app (1.x) to the new app, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

ElementsProject/lightning: v23.08

Published: 2023-08-23 20:03:31 UTC

We're pleased to announce the 23.08 release of Core Lightning, named by Matt Morehouse.

For a list of all changes, please see the changelog

Highlights for Users

  • Several pay plugin improvements for better payment reliability.
  • New setconfig command to change config lines dynamically without node restart: limited now, but more coming in future.
  • BIP-93 seed backup support thanks to @adi2011's Summer of Bitcoin project.
  • @Lagrang3 (under a grant from BuildOnLayer2) implemented Pickhardt Payment in a new experimental renepay plugin (and corresponding renepay command) offers a much more sophisticated method of making payments (and much more experimental!).

Highlights for the Network

  • Per-channel ignorefeelimits setting for getting fee disagreements unstuck.
  • Taproot address support: now the default for change addresses.
  • Preemptive failure of incoming HTLCs if the outgoing is stuck due to high fees, to avoid channel loss.
  • Dual-funding has been tweaked to the latest spec, but it's still experimental.
  • The new experimental-splicing option implements the new splicing draft to move funds in and out of live channels.

Highlights for Developers

  • A new wait command supports invoices, along with listinvoices allowing ordering and pagination (with more commands to come!)
  • pay supports self-payment: you can pay your own invoices.
  • pay int a bolt11 with a description hash without providing a description has been temporarily undeprecated (but descriptions now work properly with \ in them now!).
  • Experimental builds are no longer required: all experimental features are now explicit runtime options.
  • User-defined tracepoints have been added to the a few paths, to help with tracing bottlenecks in production systems.

Since 23.05, we've had 660 commits by 37 authors in 104 days!

A special thanks to the 12 first time contributors:

  • Eduardo Quintana
  • sumBTC
  • Paul Miller
  • Orbital
  • Jonathan Underwood
  • Ilya Evdokimov
  • Erik De Smedt
  • Chase
  • Bryan Ramos
  • Bitkarrot
  • avatar4d
  • Amin Bashiri

~ @rustyrussell, @ShahanaFarooqui, @EndothermicDev, @cdecker, and @niftynei

Go to Repo Go to Release

zkSNACKs/WalletWasabi: v2.0.4

Published: 2023-08-21 14:38:35 UTC

Wasabi is an easy to use, privacy-focused, open-source, non-custodial, Bitcoin wallet

Download

:window: Windows :green_apple: Apple M1/M2 :apple: Apple Intel :penguin: Ubuntu / Debian :penguin: Other Linux

Release Highlights

⏩ Faster wallet load 🚀 Speed up unconfirmed transactions 🛡️ Privacy warnings and improvement suggestions for payments 🐳 Cheaper coinjoins especially for whales 👻 Headless daemon and improved RPC interface 📸 QR code scanning on linux

Release Summary

Turbosync Drastically Reduces Wallet Load Times

This release optimizes the filter checking process to reduce wallet loading times by 90% thanks to code cleanup and a clever key prioritization process dubbed “Turbosync”. With Turbosync, internal addresses that have already been used are not checked for coins in new blocks until after unused addresses have been checked first.

Don’t Float in the Mempool

Incoming funds can now be confirmed faster with Child Pays For Parent (CPFP) to self-spend an unconfirmed UTXO, and outgoing transactions can use Replace By Fee (RBF) to increase confirmation priority or cancel the payment entirely. You don't have to worry about the details, it just works magically under the hood.

Privacy Warnings and Spending Suggestion

New Privacy Warnings present users with one click fixes if they are attempting to construct a transaction that spends nonprivate funds or creates change. Notifications are provided when consolidating more than 10 UTXOs or spending unconfirmed funds, allowing users to avoid potential mistakes without restricting intentional usage.

More Privacy, Less Blockspace

The amount decomposer was refined to make the most effective use of scarce block space so that whales who set a high anonymity score target now need fewer coinjoin rounds to reach 100% privacy. The amount of outputs a client can create in a round has been increased from 8 to 10, and decompositions that produce change outputs are now rarely chosen. Adjustments to the anonymity score calculator and default settings additionally reduce the amount of coinjoining required before all coins are considered private. The anonymity score target of the “Maximize Privacy” coinjoin strategy setting was reduced from a random value between 50-100 to a less conservative range of 27-76, which brings the behavior closer in line with the two efficiency based strategies.

A specter is haunting this world

Wasabi now has a daemon! More experienced users can directly interact with core features of the wallet through an RPC (Remote Procedure Call) interface making it easy for developers to customize their experience and build features that are not available in the GUI version. This release bundles the Daemon, an executable called ‘wassabeed’ that runs the wallet without the graphical interface. The wallet can be run in the background by using the RPC interface, or the Wasabi command line interface allowing users to coinjoin, see their balance, and perform every other function of the wallet without the resource consumption of the graphical interface.

Penguins love black and white

Wasabi can now scan QR codes on Linux computers. This makes importing an address from a phone a lot more private, easier and faster. This feature is now available for Linux and Windows, but not yet for macOS.

Database migration to SQLite

Wallet loading speed improved even more by storing the filters in an SQLite database instead of a plaintext file, reducing disk space requirements by about 1 GB and increasing resilience against file corruption.

Fighting Entropy

Included are several updates to dependencies (HWI, Tor, Avalonia) and a lot of the usual bug squashing and UI polishing.

Read the related blog for more information.

Installation Guide

Download the operating system relevant software package and install Wasabi like you would any other software on your computer. For a detailed installation guide, including signature verification, see the documentation.

Advanced Guide

If you want to build or update Wasabi from source code, check out these easy instructions.

Wasabi uses reproducible builds, which you can verify with this guide.

Documentation

:spiderweb: Website :onion: Tor onion site :orangebook: Docs :grey_question: FAQ

Requirements

  • Windows 10 1607+
  • Windows 11 22000+
  • macOS 10.15+
  • Ubuntu 18.04+
  • Fedora 36+
  • Debian 10+

Full Changelog

New Contributors

Full Changelog: https://github.com/zkSNACKs/WalletWasabi/compare/v2.0.2.1...v2.0.4

Go to Repo Go to Release

ACINQ/bitcoin-lib: v0.29

Published: 2023-08-21 08:34:25 UTC

What's Changed

Full Changelog: https://github.com/ACINQ/bitcoin-lib/compare/v0.28...v0.29

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.1

Published: 2023-08-19 08:22:36 UTC

This release fixes an issue (see #394) with withdrawals/payments done through LNURL affecting the new 2.0.0 version (legacy app is not affected).

Migration for existing wallets

For users upgrading from the legacy app (1.x) to the new app, a migration is needed. See the 2.0.0 release notes for details about the migration process.

All changes:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

bitcoin-core/HWI: 2.3.1

Published: 2023-08-17 00:39:28 UTC

Also available on PyPi and can be installed with pip install -U hwi

Fixed

  • Base58 address decoding used by BitBox02
  • Various issues with the Qt GUI

Go to Repo Go to Release

ACINQ/phoenix: android-v2.0.0

Published: 2023-08-16 14:55:38 UTC

This is a major release that reworks most of the application. An automated migration is available for existing users.

Migration

Due to the changes in the LN engine and the switch to splicing (see below), existing channels created with v1.x cannot be used by the new app. A migration process merges them together resulting in a single channel.

Users with existing wallets will remain on the legacy app, until their funds are migrated. This migration is triggered manually by the user from the legacy app.

⚠️ Important notes - The migration process will only migrate channels that have at least 546 satoshi on the user's side. Channels with less than 546 sat cannot be migrated since their balance is below the Bitcoin dust limit, and funds are swiped by the miners. The app will display a warning when that's the case. - Once the app has migrated, the legacy swap-in address must not be used ever again. Contact support if you accidentally send funds to the legacy swap-in address. - The migration process may sometimes be disabled, usually when the mempool is congested. When that happens, the migration button is not available, and users can keep using the legacy app.

Main changes

Switch the LN engine from eclair to lightning-kmp

Both eclair and lightning-kmp are implementations of a Lightning node and are developed by us (ACINQ). However eclair is written in scala, targets server use-cases (relaying payments) and only runs on Android. Lightning-kmp is written in kotlin multiplatform, targets mobile platforms, and can run on iOS and Android.

Phoenix Android used to be powered by eclair, and Phoenix iOS by lightning-kmp. With this new versions, both Android/iOS use lightning-kmp.

Support for splicing and dual-funding

Splicing allows altering channels by adding or removing funds. Instead of managing multiple channels, the app only has one single channel, which will then be modified depending on usage. This brings significant improvements: - on-chain swaps (swap-in or swap-out) are now trustless. - the static 1% fee for incoming payments that need new channels has been removed. Instead users pay the mining fee for the splicing operation. - that fee cannot exceed the maximum fee set by the user (in settings > channels management). Default maximum is 5000 sat. - a notification is displayed when an incoming payment is rejected because of the fee. - the fee for outgoing Lightning payments is now static (0.4 %) and is displayed before sending the payment. - unconfirmed on-chain transactions can be accelerated.

See https://github.com/ACINQ/phoenix/pull/356 and https://acinq.co/blog/phoenix-splicing-update for more information, especially the fee comparison.

Improved fiat currencies support

The Android app is now able to convert prices to 150+ currencies, including free market rates (like for the Argentine Peso). Exchange rates should also be more accurate.

Export payments history

Successful payments can now be exported to a CSV file.

Compatibility with iOS

The iOS and Android apps are not compatible yet, since the iOS app does not support splicing yet. Using the same seed on both iOS and Android Phoenix apps will lead to issues.

All changes

https://github.com/ACINQ/phoenix/compare/android-legacy-v1.4.27...android-v2.0.0

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it: - from our website: https://acinq.co/pgp/drouinf.asc - from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

To import our signing key: $ gpg --import drouinf.asc

To verify the release file checksums and signatures: $ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped $ sha256sum -c SHA256SUMS.stripped

Go to Repo Go to Release

rsksmart/rskj: FINGERROOT-5.1.0

Published: 2023-08-14 21:57:49 UTC

Summary

This update brings additions and enhancements to the JSON-RPC API and security and performance improvements. Although this upgrade is not mandatory, we highly recommend that users upgrade their nodes to the latest version.

What's New in RSKj 5.1.0

A non-comprehensive list of changes included in this version is:

  • Fixed issues with the evm_reset JSON-RPC method in #2024.
  • Introduced configurable limits for the eth_getLogs JSON-RPC method in #2035.
  • Introduced configurable limit for JSON-RPC responses size in #1997.
  • New rsk_flush JSON-RPC method lets users flush the node’s databases to disk without interrupting the node in #1856.
  • Allow specifying VM options when running RSKj in a docker container in #1998.

Full Changelog: https://github.com/rsksmart/rskj/compare/FINGERROOT-5.0.0...FINGERROOT-5.1.0

Fingerroot 5.1.0 Milestone: https://github.com/rsksmart/rskj/milestone/36

New Contributors

Reproducible Build

SHA256 (see Reproducible Build guide for further details): 0c0707d01d14c7bef5a53407aace8b2a637d42964f9847b14aa38e2088e5cf3b rskj-core-5.1.0-FINGERROOT-all.jar

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.2

Published: 2023-08-11 17:50:21 UTC

Bug fixes

  • Language Select box cut off on checkout (#5210) @evanc-ole
  • POS: Multiple fixes (#5228 #5241 #5252) @dennisreimann
  • Greenfield: Fix invoice lookup by capitalized status (#5245) @dennisreimann
  • Fix temporary file downloads for local storage option @Kukks

Improvements

  • POS: Handle flexible price items in cart view (#5238) @dennisreimann
  • POS: Combine search term and category selector (#5241) @dennisreimann
  • Email Rules: Improve validation (#5234) @dennisreimann
  • Receipt improvements (#5239) @dennisreimann
  • Improve invoices status filter (#5248 #5251) @dennisreimann

Go to Repo Go to Release

Start9Labs/start-os: v0.3.4.4-hotfix

Published: 2023-08-11 01:30:37 UTC

Highlights

Hotfix for compatibility with some DIY hardware

Full release details: https://github.com/Start9Labs/start-os/releases/tag/v0.3.4.4

What's Changed

Full Changelog: https://github.com/Start9Labs/start-os/compare/v0.3.4.4...v0.3.4.4-hotfix

Checksums

BLAKE-3 ceeaacfb27d5b5e196e695a43413e1020f67c96df5b2606ec7087eb8ad8fe69e aarch64-nonfree.iso/startos-0.3.4.4-9322b3d-20230810_aarch64-nonfree.iso b48047ea7df90ac07075a0aeda730ee656d9a6080731e651c255283d1fb9f8bd aarch64.iso/startos-0.3.4.4-9322b3d-20230810_aarch64.iso dafece5f39df1a3fafd9ea3f30eb1d945e09e09a4929c3a0e7863f7b1d80d188 x86_64-nonfree.iso/startos-0.3.4.4-9322b3d-20230810_x86_64-nonfree.iso 4a599a5d4de198fd126c05dcb303d523d80a3d54ac5eb63c871991d8456a0a54 x86_64.iso/startos-0.3.4.4-9322b3d-20230810_x86_64.iso d80711dda524b09a14c4be71d34e17c6820d6603007a09d7f030f7ed69fd9a31 raspberrypi.img/startos-0.3.4.4-9322b3d-20230810_raspberrypi.img.gz

SHA-256 e4615623a25cc2490e31d80ff0bed3cd960e8b08b65109a955e760a130e463c0 aarch64-nonfree.iso/startos-0.3.4.4-9322b3d-20230810_aarch64-nonfree.iso 693e7c4749bffb82f450f1ad291e738837402b9baf78874dd2c7afaba28be5d1 aarch64.iso/startos-0.3.4.4-9322b3d-20230810_aarch64.iso 3d85e0f55ac56745cb8722e84a2dfd295d33d3c69a23c36cac1d89abb08132dd x86_64-nonfree.iso/startos-0.3.4.4-9322b3d-20230810_x86_64-nonfree.iso a6c5c874818f6d76147fc89e93d795d2c0d511451c6e5cd4354cb2499156c606 x86_64.iso/startos-0.3.4.4-9322b3d-20230810_x86_64.iso 1a809c06379ec2be65add56081747d8cfe6f5d004c1e8ebe9b4fb9e9030159fb raspberrypi.img/startos-0.3.4.4-9322b3d-20230810_raspberrypi.img.gz

Go to Repo Go to Release

Start9Labs/start-os: v0.3.4.4

Published: 2023-08-07 23:20:41 UTC

Highlights

  • Https over Tor for faster UI loading times
  • Change password through UI
  • Use IP address for Network Folder backups
  • Multiple bug fixes, performance enhancements, and other small features

What's Changed

New Contributors

Full Changelog: https://github.com/Start9Labs/start-os/compare/v0.3.4.3...v0.3.4.4

Updates

  • Updated aarch64.iso to fix compatibility issue with UTM for macOS

Checksums

BLAKE-3 29f0a4f8a22072fc6f604e650eb3c47d6f9c60ae4312b8105a1b680f7c04b382 startos-0.3.4.4-9322b3d-20230809_aarch64.iso 1d8c6a896ee1d2755be444c483f93ab87a60d63cedc8b8a23c30cfb236757181 startos-0.3.4.4-55f5329-20230807_aarch64-nonfree.iso 51c1d466c0696390d5a0072808b8e65b5caf8d8d34c276da27f0f943bc00c6c0 startos-0.3.4.4-55f5329-20230807_raspberrypi.img.gz e596d981407823eb2c1d7ebd1f83ac3d4afd9a23ebbd3b669b85cba7fe7daa17 startos-0.3.4.4-55f5329-20230807_x86_64.iso 112999b2ed3d86d9ae394aa3de08dbd78a04c95d19f8a68303bd99368a23fda2 startos-0.3.4.4-55f5329-20230807_x86_64-nonfree.iso

SHA-256 b8e099e011058532ffe95b76d067fe3cc27f2924873d9e193cf541d4557d3af9 startos-0.3.4.4-9322b3d-20230809_aarch64.iso bfac354c9b8e8a619b9faafb5e9e5339b78a80e752aaf64a44d9bc0004a83448 startos-0.3.4.4-55f5329-20230807_aarch64-nonfree.iso f61f90083abf0972990a6c982b803854d9d53d312bbfe1e28ceb0ad978249ec0 startos-0.3.4.4-55f5329-20230807_raspberrypi.img.gz 3e44c9a42773f2ab797f337efe2b8b9a3af0410f262e948d1dec4dd0452da3d9 startos-0.3.4.4-55f5329-20230807_x86_64.iso 4852b649f17328aad0e9725410d219d9edf9caff9bb9a3dc91e23743afb37c96 startos-0.3.4.4-55f5329-20230807_x86_64-nonfree.iso

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.1

Published: 2023-07-29 08:02:07 UTC

Bug fixes

  • Language Select box cut off on checkout (#5210) @dstrukt
  • POS Cart view malformed when special characters are in items (#5203 #5211) @Kukks
  • Errors creating invoice from public form were not shown in the UI (#5208 #5211) @Kukks
  • Cart view doesn't show item when the amount field is custom (#5204 #5211) @Kukks
  • Can't save the item when adding a new category in POS (#5205 #5211) @Kukks

Go to Repo Go to Release

btcpayserver/btcpayserver: v1.11.0

Published: 2023-07-27 13:21:02 UTC

New Features

  • Complete overhaul of Invoice Reporting (#5095 #5155) @NicolasDorier
  • POS Cart redesign (#5109 #5171) @dennisreimann @dstrukt
  • Add product categories to POS apps (#5088 #5078) @NicolasDorier
  • Checkout v2: Play sound when invoice is paid (#5085 #5113) @dennisreimann @webwworthy
  • Add support for ExchangeRateHost and FreeCurrencyRates rate providers (#5166) @Kukks

Bug fixes

  • Support NFC on modal (#4251 #5033) @Kukks @dennisreimann
  • Fixed setting of minimum or custom price for LNURL POS items (#5170 #5172) @Kukks
  • Preventing entering of negative tips and discounts in POS (#5192 #5198) @rockstardev
  • Fixing display of amount paid on Receipt page (#5195 #5197) @rockstardev
  • Form invoice amount adjusters, useful for shipping and other addon amounts to the invoice (#5087 #5158) @Kukks @dennisreimann

Improvements

  • Improved Payment Requests List View (#3872 #5065) @TChukwuleta
  • Improve create first store view (#5008 #5181) @dennisreimann
  • Invoice lists: Show icons for payment methods (#5084 #5137) @dennisreimann
  • Apps: Add direct file upload in item editor (#5086 #5140) @dennisreimann
  • Add OpenSats supporters logo (#5202) @Kukks @Pavlenex
  • Add recommended rate providers for UGX and RSD (#5166) @Kukks

Go to Repo Go to Release

BlueWallet/BlueWallet: v6.4.8

Published: 2023-07-27 00:41:23 UTC

  • FIX: invalid cosigner when scanning cosigner during multigig vault setup (closes #5616)

Go to Repo Go to Release

bitcoin-core/HWI: 2.3.0

Published: 2023-07-25 02:54:41 UTC

Also available on PyPi and can be installed with pip install -U hwi

Added

  • Jade DIY devices
  • GUI import/export of PSBTs to/from file
  • Apple Silicon hwi binary for MacOS 12.0+ (hwi-qt cannot be built yet)

Fixed

  • Bumped hidapi dependency for upstream bugfix

Go to Repo Go to Release

lightningdevkit/rust-lightning: v0.0.116

Published: 2023-07-21 23:22:36 UTC

0.0.116 - Jul 21, 2023 - "Anchoring the Roadmap"

API Updates

  • Support for zero-HTLC-fee anchor output channels has been added and is now considered beta (#2367). Users who set ChannelHandshakeConfig::negotiate_anchors_zero_fee_htlc_tx should be prepared to handle the new Event::BumpTransaction, e.g. via the BumpTransactionEventHandler (#2089). Note that in order to do so you must ensure you always have a reserve of available unspent on-chain funds to use for CPFP. LDK currently makes no attempt to ensure this for you.
  • Users who set ChannelHandshakeConfig::negotiate_anchors_zero_fee_htlc_tx and wish to accept inbound anchor-based channels must do so manually by setting UserConfig::manually_accept_inbound_channels (#2368).
  • Support forwarding and accepting HTLCs with a reduced amount has been added, to support LSPs skimming a fee on the penultimate hop (#2319).
  • BOLT11 and BOLT12 Invoice and related types have been renamed to include a BOLTNN prefix, ensuring uniqueness in lightning{,-invoice} crates (#2416).
  • Scorers now have an associated type which represents a parameter passed when calculating penalties. This allows for the same Scorer to be used with different penalty calculation parameters (#2237).
  • DefaultRouter is no longer restrained to a Mutex-wrapped Score, allowing it to be used in no-std builds (#2383).
  • CustomMessageHandler::provided_{node,init}_features and various custom feature bit methods on *Features were added (#2204).
  • Keysend/push payments using MPP are now supported when receiving if UserConfig::accept_mpp_keysend is set and when sending if specified in the PaymentParameters. Note that not all recipients support this (#2156).
  • A new ConfirmationTarget::MempoolMinimum has been added (#2415).
  • SpendableOutputDescriptor::to_psbt_input was added (#2286).
  • ChannelManager::update_partial_channel_config was added (#2330).
  • ChannelDetails::channel_shutdown_state was added (#2347).
  • The shutdown script can now be provided at shutdown time via ChannelManager::close_channel_with_feerate_and_script (#2219).
  • BroadcasterInterface now takes multiple transactions at once. While not available today, in the future single calls should be passed to a full node via a single batch/package transaction acceptance API (#2272).
  • Balance::claimable_amount_satoshis was added (#2333).
  • payment_{hash,preimage} have been added to some Balance variants (#2217).
  • The lightning::chain::keysinterface is now lightning::sign (#2246).
  • Routing to a blinded path has been implemented, though sending to such a route is not yet supported in ChannelManager (#2120).
  • OffersMessageHandler was added for offers-related onion messages (#2294).
  • The CustomMessageHandler parameter to PeerManager has moved to MessageHandler from PeerManager::new explicitly (#2249).
  • Various P2P messages for dual funding channel establishment have been added, though handling for them is not yet in ChannelManager (#1794)
  • Script-fetching methods in sign interfaces can now return errors, see docs for the implications of failing (#2213).
  • The data_loss_protect option is now required when reading channel_reestablish messages, as many others have done (#2253).
  • InFlightHtlcs::add_inflight_htlc has been added (#2042).
  • The init message networks field is now written and checked (#2329).
  • PeerManager generics have been simplified with the introduction of the APeerManager trait (#2249).
  • ParitalOrd and Ord are now implemented for Invoice (#2279).
  • ParitalEq and Debug are now implemented for InMemorySigner (#2328).
  • ParitalEq and Eq are now implemented for PaymentError (#2316).
  • NetworkGraph::update_channel_from_announcement_no_lookup was added (#2222).
  • lightning::routing::gossip::verify_{channel,node}_announcement was added (#2307).

Backwards Compatibility

  • PaymentParameters written with blinded path info using LDK 0.0.115 will not be readable in LDK 0.0.116, and vice versa.
  • Forwarding less than Event::HTLCIntercepted::expected_outbound_amount_msat in ChannelManager::forward_intercepted_htlc may prevent the ChannelManager from being read by LDK prior to 0.0.116 (#2319)
  • Setting ChannelConfig::accept_underpaying_htlcs may prevent the ChannelManager from being read by LDK prior to 0.0.116 and un-setting the parameter between restarts may lead to payment failures (#2319).
  • ChannelManager::create_inbound_payment{,_for_hash}_legacy has been removed, removing the ability to create inbound payments which are claimable after downgrade to LDK 0.0.103 and prior. In the future handling such payments will also be removed (#2351).
  • Some fields required by LDK 0.0.103 and earlier are no longer written, thus deserializing objects written by 0.0.116 with 0.0.103 may now fail (#2351).

Bug Fixes

  • ChannelDetails::next_outbound_htlc_limit_msat was made substantially more accurate and a corresponding next_outbound_htlc_minimum_msat was added. This resolves issues where unpayable routes were generated due to overestimation of the amount which is payable over one of our channels as the first hop (#2312).
  • A rare case where delays in processing Events generated by ChannelMonitors could lead to loss of those events in case of an untimely crash. This could lead to the loss of an Event::SpendableOutputs (#2369).
  • Fixed a regression in 0.0.115 which caused PendingHTLCsForwardable events to be missed when processing phantom node receives. This caused such payments to be delayed until a further, unrelated HTLC came in (#2395).
  • Peers which are unresponsive to channel messages for several timer ticks are now disconnected to allow for on-reconnection state machine reset. This works around some issues in LND prior to 16.3 which can cause channels to hang and eventually force-close (#2293).
  • ChannelManager::new now requires the current time (either from a recent block header or the system clock), ensuring invoices created immediately after startup aren't already expired (#2372).
  • Resolved an issue where reading a ProbabilisticScorer on some platforms (e.g. iOS) can lead to a panic (#2322).
  • ChannelConfig::max_dust_htlc_exposure is now allowed to scale based on current fees, and the default has been updated to do so. This substantially reduces the chance of force-closure due to dust exposure. Note that existing channels will retain their current value and you may wish to update the value on your existing channels on upgrade (#2354).
  • PeerManager::process_events no longer blocks in any case. This fixes a bug where reentrancy from PeerManager into user code which eventually calls process_events could lead to a deadlock (#2280).
  • The persist timing of network graph and scoring in lightning-background-processor has been tweaked to provide more reliable persistence after updates to either (#2226).
  • The number of route hints added to BOLT 11 invoices by the lightning-invoice::utils builders has been reduced to three to ensure invoices can be represented in scan-able QR codes (#2044).
  • Fixed sending large onion messages, which would previously have resulted in an HMAC error on the second hop (#2277).
  • Fixed a memory leak that may occur when a ChannelManager or ChannelMonitor is droped (#2233).
  • A potential deadlock in calling NetworkGraph::eq was resolved (#2284).
  • Fixed an overflow which prevented disconnecting peers in some minor cases with more than 31 peers (#2245).
  • Gossip messages with an unknown chain hash are now ignored (#2230).
  • Rapid Gossip Sync processing now fails on an unknown chain hash (#2324).
  • RouteHintHop::htlc_maximum_msat is now enforced. Note that BOLT11 route hints do not have such a field so this code is generally unused (#2305).

Security

0.0.116 fixes a denial-of-service vulnerability which is reachable from untrusted input from channel counterparties if a 0-conf channel exists with that counterparty. * A premature announcement_signatures message from a peer prior to a 0-conf channel's funding transaction receiving any confirmations would panic in any version since 0-conf channels were introduced (#2439).

In total, this release features 142 files changed, 21033 insertions, 11066 deletions in 327 commits from 21 authors, in alphabetical order: * Alec Chen * Andrei * Antoine Riard * Arik Sosman * Chad Upjohn * Daniel Granhão * Duncan Dean * Elias Rohrer * Fred Walker * Gleb Naumenko * Jeffrey Czyz * Martin Habovstiak * Matt Corallo * Tony Giorgio * Valentine Wallace * Vladimir Fomene * Willem Van Lint * Wilmer Paulino * benthecarman * ff * henghonglee

Go to Repo Go to Release

romanz/electrs: v0.10.0

Published: 2023-07-21 13:40:17 UTC

https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#0100-jul-22-2023

Go to Repo Go to Release

unchained-capital/caravan: caravan-v0.6.2

Published: 2023-07-18 21:39:13 UTC

0.6.2 (2023-07-18)

Bug Fixes

  • sign: pass wallet uuid for signing (a748d97)

Go to Repo Go to Release

sparrowwallet/sparrow: 1.7.8

Published: 2023-07-18 14:16:09 UTC

  • Add BIP322 message signing for singlesig addresses including P2TR
  • Add zbar QR reader for all QR scans (wide, cropped and inverted)
  • Add useZbar config variable to disable zbar scanning (enabled by default)
  • Add Rename Wallet command to File menu
  • Set initial fee for proposed RBF transaction to satisfy minimum relay requirements
  • When constructing RBF and CPFP transactions, add any additional UTXOs by output group only if effective fee is sufficient
  • Make the Send to Many dialog non-modal, where reselecting the menu command brings an existing dialog to the foreground
  • Show a warning in the General Preferences if currencies could not be retrieved from the exchange rate source
  • Optimize memory store used for calculating the fee rate histogram in Cormorant
  • For memory efficiency, only keep older mempool histogram entries at ten minute intervals
  • Add additional UTXOs to CPFP transaction if the output value is below the dust threshold
  • Set the transaction label to a comma separated list of the payment labels when a multiple payment transaction is broadcasted
  • Show a warning dialog on Submit Bug Report to redirect users to the support channel where appropriate
  • Add the Taproot script type to connected wallet import options
  • Add a tooltip to the Save Final Transaction button to suggest connecting to a server in order to broadcast
  • Make alert dialogs resizable
  • Bug fix: Fix overselection of inputs during RBF
  • Bug fix: Preserve payment labels when using RBF on multiple payment transactions
  • Bug fix: Retain UTXO frozen status on wallet refresh
  • Bug fix: Preserve wallet order on application restart after tabs are moved left or right
  • Bug fix: On updating UTXO history in Terminal, set the scrollbar to the top if the table view is scrolled below new UTXO table row count

Go to Repo Go to Release
Follow the RSS Feed!

Featured Repos

Want to add another project? Make a PR!