fix: update ldk node for lightning security fixes

[ovitrif]

Refs: synonymdev/ldk-node#123

Description

• Updates LDK Node from 0.7.0-rc.71 to 0.7.0-rc.72 for the 2.6.0 release, so the shipped node picks up the lightning, lightning-liquidity and lightning-transaction-sync 0.2.7 security fixes.
• 0.7.0-rc.72 is rc.71 with only those three dependencies updated (release).

Design

N/A — no UI changes.

Preview

N/A — no user-visible changes.

QA Notes

Manual Tests

• Upgrade from the previous 2.6.0 build with an existing wallet and open channels: the node starts, channels reconnect, balances match.
• Restore a wallet: on-chain and Lightning balances and activity come back.
• Send and receive a Lightning payment and an on-chain payment.

Automated Checks

• xcodebuild -resolvePackageDependencies resolves ldk-node at 0.7.0-rc.72; Package.resolved pins the release tag's commit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-13T11:55:03.521870Z	2784a0d	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2784a0d249

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Move the release note into a changelog fragment

This normal fix: commit edits CHANGELOG.md directly and adds no corresponding fragment, bypassing the repository's fragment-based release workflow. Move this sentence into exactly one appropriately named file under changelog.d/next/ (likely .security.md or .fixed.md) so release automation can collect and consume it.

AGENTS.md reference: AGENTS.md:L437-L440

Useful? React with 👍 / 👎.

[greptile-apps]

Confidence Score: 5/5

[High impact] The PR appears safe to merge, with no actionable issues found.

Summary

Updates ldk-node from 0.7.0-rc.71 to 0.7.0-rc.72 for the stated Lightning security fixes.

• Bitkit builds now use LDK Node 0.7.0-rc.72.

_{Reviews (1) · Last reviewed commit: "fix: update ldk node for lightning secur..." · Reviewed by Greptile}

[ovitrif]

Closing: per @piotr-iohk, the bump is committed directly on release-2.6.0, so it rides in #925 and CI runs once.