v0.7.0-rc.27

Merge pull request #62 from synonymdev/refactor/lazy-sync-requests-ba…

v0.7.0-rc.26

fix: upsert peer address on connect and bump to v0.7.0-rc.26

PeerStore::add_peer previously returned early if a peer already existed,
silently discarding address updates. When an LSP node's IP changed, the
reconnection loop would indefinitely retry the stale cached address.

This commit:
1. Changes add_peer to upsert: if the peer exists but the address
   differs, update and re-persist it.
2. Reorders Node::connect to persist the peer *before* attempting the
   connection, so the new address is saved even if the connection
   races with an in-flight reconnection attempt at the old address.
3. Adds unit tests for the upsert logic and an integration test for
   persist-on-failed-connect.

See upstream issue lightningdevkit/ldk-node#700.

Co-authored-by: Cursor <cursoragent@cursor.com>

v0.7.0-rc.25

chore: bump version and generate bindings

v0.7.0-rc.24

fixes

v0.7.0-rc.23

feat: update address types dynamically

v0.7.0-rc.22

bump version

v0.7.0-rc.21

Multi-address type support for on-chain wallet

v0.7.0-rc.20

Log warning when PSBT extract_tx cannot verify fee

v0.7.0-rc.19

FOR TESTING PURPOSES

v0.7.0-rc.18

0.7.0-rc.18 (Synonym Fork)

Bug Fixes

• Backported upstream Electrum sync fix (PR #4341): Skip unconfirmed get_history entries in
  ElectrumSyncClient. Previously, mempool entries (height=0 or -1) were incorrectly treated as
  confirmed, causing get_merkle to fail for 0-conf channel funding transactions.
• Fixed duplicate payment events (PaymentReceived, PaymentSuccessful, PaymentFailed) being
  emitted when LDK replays events after node restart.

References

• Upstream fix: lightningdevkit/rust-lightning#4341
• Fork diff: ovitrif/rust-lightning@0.2-base...ovitrif:rust-lightning:0.2-electrum-fix