You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+57Lines changed: 57 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,60 @@
1
+
# 0.5.0 - Apr. 29, 2025
2
+
Besides numerous API improvements and bugfixes this fifth minor release notably adds support for sourcing chain and fee rate data from an Electrum backend, requesting channels via the [bLIP-51 / LSPS1](https://github.com/lightning/blips/blob/master/blip-0051.md) protocol, as well as experimental support for operating as a [bLIP-52 / LSPS2](https://github.com/lightning/blips/blob/master/blip-0052.md) service.
3
+
4
+
## Feature and API updates
5
+
- The `PaymentSuccessful` event now exposes a `payment_preimage` field (#392).
6
+
- The node now emits `PaymentForwarded` events for forwarded payments (#404).
7
+
- The ability to send custom TLVs as part of spontaneous payments has been added (#411).
8
+
- The ability to override the used fee rates for on-chain sending has been added (#434).
9
+
- The ability to set a description hash when creating a BOLT11 invoice has been added (#438).
10
+
- The ability to export pathfinding scores has been added (#458).
11
+
- The ability to request inbound channels from an LSP via the bLIP-51 / LSPS1 protocol has been added (#418).
12
+
- The `ChannelDetails` returned by `Node::list_channels` now exposes fields for the channel's SCIDs (#444).
13
+
- Lightning peer-to-peer gossip data is now being verified when syncing from a Bitcoin Core RPC backend (#428).
14
+
- The logging sub-system was reworked to allow logging to backends using the Rust [`log`](https://crates.io/crates/log) facade, as well as via a custom logger trait (#407, #450, #454).
15
+
- On-chain transactions are now added to the internal payment store and exposed via `Node::list_payments` (#432).
16
+
- Inbound announced channels are now rejected if not all requirements for operating as a forwarding node (set listening addresses and node alias) have been met (#467).
17
+
- Initial support for operating as an bLIP-52 / LSPS2 service has been added (#420).
18
+
-**Note**: bLIP-52 / LSPS2 support is considered 'alpha'/'experimental' and should *not* yet be used in production.
19
+
- The `Builder::set_entropy_seed_bytes` method now takes an array rather than a `Vec` (#493).
20
+
- The builder will now return a `NetworkMismatch` error in case of network switching (#485).
21
+
- The `Bolt11Jit` payment variant now exposes a field telling how much fee the LSP withheld (#497).
22
+
- The ability to disable syncing Lightning and on-chain wallets in the background has been added. If it is disabled, the user is responsible for running `Node::sync_wallets` manually (#508).
23
+
- The ability to configure the node's announcement addresses independently from the listening addresses has been added (#484).
24
+
- The ability to choose whether to honor the Anchor reserves when calling `send_all_to_address` has been added (#345).
25
+
- The ability to sync the node via an Electrum backend has been added (#486).
26
+
27
+
## Bug Fixes and Improvements
28
+
- When syncing from Bitcoin Core RPC, syncing mempool entries has been made more efficient (#410, #465).
29
+
- We now ensure the our configured fallback rates are used when the configured chain source would return huge bogus values during fee estimation (#430).
30
+
- We now re-enabled trying to bump Anchor channel transactions for trusted counterparties in the `ContentiousClaimable` case to reduce the risk of losing funds in certain edge cases (#461).
31
+
- An issue that would potentially have us panic on retrying the chain listening initialization when syncing from Bitcoin Core RPC has been fixed (#471).
32
+
- The `Node::remove_payment` now also removes the respective entry from the in-memory state, not only from the persisted payment store (#514).
33
+
34
+
## Compatibility Notes
35
+
- The filesystem logger was simplified and its default path changed to `ldk_node.log` in the configured storage directory (#394).
36
+
- The BDK dependency has been bumped to `bdk_wallet` v1.0 (#426).
37
+
- The LDK dependency has been bumped to `lightning` v0.1 (#426).
38
+
- The `rusqlite` dependency has been bumped to v0.31 (#403).
39
+
- The minimum supported Rust version (MSRV) has been bumped to v1.75 (#429).
40
+
41
+
In total, this release features 53 files changed, 6147 insertions, 1193 deletions, in 191 commits from 14 authors in alphabetical order:
42
+
43
+
- alexanderwiederin
44
+
- Andrei
45
+
- Artur Gontijo
46
+
- Ayla Greystone
47
+
- Elias Rohrer
48
+
- elnosh
49
+
- Enigbe Ochekliye
50
+
- Evan Feenstra
51
+
- G8XSU
52
+
- Joost Jager
53
+
- maan2003
54
+
- moisesPompilio
55
+
- Rob N
56
+
- Vincenzo Palazzo
57
+
1
58
# 0.4.3 - Jan. 23, 2025
2
59
3
60
This patch release fixes the broken Rust build resulting from `cargo` treating the recent v0.1.0 release of `lightning-liquidity` as API-compatible with the previous v0.1.0-alpha.6 release (even though it's not).
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ fn main() {
55
55
LDK Node currently comes with a decidedly opinionated set of design choices:
56
56
57
57
- On-chain data is handled by the integrated [BDK][bdk] wallet.
58
-
- Chain data may currently be sourced from the Bitcoin Core RPC interface or an [Esplora][esplora] server, while support for Electrum will follow soon.
58
+
- Chain data may currently be sourced from the Bitcoin Core RPC interface, or from an [Electrum][electrum] or [Esplora][esplora] server.
59
59
- Wallet and channel state may be persisted to an [SQLite][sqlite] database, to file system, or to a custom back-end to be implemented by the user.
60
60
- Gossip data may be sourced via Lightning's peer-to-peer network or the [Rapid Gossip Sync](https://docs.rs/lightning-rapid-gossip-sync/*/lightning_rapid_gossip_sync/) protocol.
61
61
- Entropy for the Lightning and on-chain wallets may be sourced from raw bytes or a [BIP39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) mnemonic. In addition, LDK Node offers the means to generate and persist the entropy bytes to disk.
@@ -72,6 +72,7 @@ The Minimum Supported Rust Version (MSRV) is currently 1.75.0.
0 commit comments