CryptoSlate
Lightning Development Kit (LDK) has a privacy fix that blocks an onion-message probe linking an unannounced Lightning channel to the Bitcoin output funding it. The attack required connections to both suspected endpoints and a guessed short-channel ID derived from the output’s location onchain.
Why it matters
Unannounced channels do not appear in the public Lightning network map, but that alone did not prevent LDK’s forwarding lookup from confirming a channel’s funding link. A short-channel ID identifies a specific Bitcoin output using its block height, transaction position and output position. An attacker could derive a candidate ID from an output, then use a message routed through both suspected nodes to test whether the channel and output matched.
Before the fix, LDK could resolve a real short-channel ID for an unannounced channel after its funding transaction confirmed. A successful onion-message return could therefore connect the Bitcoin output to the Lightning nodes using it, exposing information the channel’s unannounced status was intended to keep private.
Market impact
LDK now refuses to resolve an unannounced channel’s real short-channel ID for onion-message forwarding. Valid aliases remain usable, letting senders address the channel without using its real blockchain coordinates. The change closes this lookup route while preserving forwarding through an allowed alias, consistent with BOLT 4’s rules for onion-message identifiers.
Bitcoin Optech highlighted the change on October 30. Its presence in installed wallet versions has not been confirmed, so users should check with their wallet providers before assuming their software includes the protection.
Frequently asked questions
-
What information could the Lightning probe reveal?
It could link a Bitcoin funding output to the Lightning nodes using an unannounced channel.
-
What did an attacker need to carry out the probe?
The attacker needed connections to both suspected endpoints and a guessed short-channel ID derived from a Bitcoin output.
-
How does a short-channel ID identify a funding output?
It uses the block height, the transaction’s position in the block and the output’s position in the transaction.
-
Does the LDK fix prevent forwarding through channel aliases?
No. LDK refuses to resolve an unannounced channel’s real short-channel ID for onion-message forwarding, while valid aliases remain usable.
-
How can users know whether their wallet includes the fix?
The fix’s inclusion in installed wallet versions has not been confirmed. Users should check with their wallet provider.
WuBlockchain
WatcherGuru
TheBlock
CoinTelegraph
CoinDesk