Bitcoin Lightning fix blocks a probe linking private channels to onchain funding
LDK’s October 25 fix rejects a funding-location lookup used by a probe requiring connections to both endpoints of an unannounced channel. Read the full story on CryptoSlateUnderstand the crypto stories that matter and what to watch next. Get The Catalyst in your inbox
Lightning Development Kit (LDK), software used to build Bitcoin Lightning applications, has a privacy fix that blocks a documented probe linking an unannounced channel to the Bitcoin output backing it. The probe exploited how LDK forwarded onion messages, turning a guessed channel identifier into confirmation of a connection between two suspected nodes.
Bitcoin Optech highlighted the change on October 30. An unannounced channel stays out of the public network map, but that alone did not prevent LDK’s message-forwarding lookup from confirming its funding link.
Related ReadingA real short-channel ID, or SCID, works like blockchain coordinates. The Lightning specification defines it using the block height, the transaction’s position within that block and the output’s position within that transaction. Together, those identify the particular Bitcoin output funding a channel.
An attacker can derive a candidate ID from an output’s location without yet knowing whether it belongs to a channel between the suspected nodes. The documented probe supplies that missing confirmation. It requires the attacker to connect to both endpoints and construct an onion-message path through them that returns to the attacker.
Before the fix, LDK’s channel lookup could resolve a real SCID even for an unannounced channel once its funding confirmed. If the message returned successfully, the attacker could confirm that the guessed output and the channel between those nodes matched.