How the Probe Worked
A software update for the Lightning Development Kit, released on October 25, addresses a vulnerability that allowed external observers to link private payment channels to their on-chain Bitcoin funding transactions. The fix targets a specific probing technique that could expose the financial origins of a channel.
Breaking news
Bitcoin Miners Face Hardware Shortage as AI Boom Strains Chip Supply
Claude AI Forecasts Chainlink Plunge in 2027
XRP Crashes to $0.87 as ETF Assets Fall Below $1 Billion
Ethereum price analysis: Did ETH hit its macro bottom after a 30% monthly drop?The vulnerability worked by exploiting a funding-location lookup. An attacker would need to establish connections to both suspected endpoints. They would also need to guess the real short-channel ID, which is derived from the funding output. Once these conditions were met, the probe could successfully map a private channel to its public Bitcoin transaction.
The attack relied on the structure of Lightning Network channel identifiers. Each channel has a short ID that is mathematically derived from its funding transaction. An attacker could enumerate possible short IDs and test them against connected nodes. If a node accepted the ID, the channel was confirmed. This created a direct link between the private channel and its public funding output, undermining the privacy that Lightning was designed to provide.
Which Wallets and Deployments Include the Fix
The LDK fix rejects the funding-location lookup that enabled this probe. Nodes running the updated software will no longer respond to these specific queries, breaking the chain of evidence an attacker would need.
The patch is included in the latest LDK releases. Users of Lightning wallets built on LDK should update to the newest version to ensure protection. The fix is critical for nodes that have not yet announced their channels publicly.
Frequently Asked Questions
Does this fix apply to all Lightning implementations? No, the fix is specific to LDK. Other implementations may have their own vulnerabilities or may already handle this probe differently. Users should check their wallet's release notes for confirmation.
Will existing channels be safe after updating? Yes, once the updated software is deployed, the probe will be rejected. However, any data already leaked before the update cannot be un-leaked.
How do I know if my wallet is vulnerable? Check your wallet's version history. If it predates the October 25 LDK release, it likely lacks the fix. Updating to the latest version resolves the issue.


