Stay up to Date on the Latest in Bitcoin Tech

  1. Weekly summaries of bitcoin-dev, lightning-dev, and delving bitcoin mailing lists
  2. Keep your finger on the pulse of bitcoin tech development and conversations
  3. Perfect for bitcoin builders, educators, and contributors to stay on top of a growing field

Bitcoin TLDR

#64

Jan 20 - Jan 26, 2025

curly arrow

Catch up on This Week's Activity

A significant vulnerability was identified in the Lightning Development Kit (LDK) versions 0.0.125 and below, making funds inaccessible through a liquidity griefing attack by exploiting a flaw in the way LDK handles conflicting HTLC claims on force-closed channels. This vulnerability allowed attackers to render funds unrecoverable by manipulating HTLC transactions, necessitating a manual construction and broadcast of a valid claim transaction for recovery. Users are advised to upgrade to LDK version 0.1, which addresses this issue by revising the logic to handle multiple conflicting aggregated transactions appropriately, ensuring the security of transactions and the recoverability of funds. The discovery of this bug, detailed in a blog post by morehouse, emphasizes the critical need for ongoing code review and the importance of simplicity and readability in software development to prevent such vulnerabilities, particularly in financial applications like those built on the LDK. Further information can be found here.

The fix implemented in LDK 0.1 corrects the vulnerability by changing how confirmed transactions are processed, preventing an attacker from exploiting the bug to lock up HTLCs through conflicting aggregated transactions. This resolution highlights the significance of continuous vigilance and regular auditing in the software development process, especially for platforms facilitating critical financial operations. The incident underscores the ever-present risk of attacks in the cryptocurrency domain and reinforces the necessity for developers and users to keep software updated to mitigate potential security threats.

Read This Week's Newsletters
/icons/grey-bitcoin-icon.svg
FOCUSED ON BITCOIN

100% concentrated on bitcoin and related technologies

/icons/grey-github-icon.svg
OPEN SOURCE

Everything we do is open source. We want your reviews and contributions

/icons/grey-code-icon.svg
BITCOIN TECH

We focus on enabling devs to learn, practice, and build with bitcoin.

Explore Bitcoin Tech Conversations
dancing astronaut

Active Discussions

Check out posts actively getting replies and inspiring conversations.

View All

Historic Conversations

Explore posts from past years in this historic deep dive.

View All

All Activity

Read the most recent individual posts in chronological order.

View All
curvy lines
Latest Bitcoin TLDR Newsletters

Bitcoin TLDR

#64

newsletter icon

Jan 20 - Jan 26, 2025

A significant vulnerability was identified in the Lightning Development Kit (LDK) versions 0.0.125 and below, making funds inaccessible through a liquidity griefing attack by exploiting a flaw in the way LDK handles conflicting HTLC claims on force-closed channels. This vulnerability allowed attackers to render funds unrecoverable by manipulating HTLC transactions, necessitating a manual construction and broadcast of a valid claim transaction for recovery. Users are advised to upgrade to LDK version 0.1, which addresses this issue by revising the logic to handle multiple conflicting aggregated transactions appropriately, ensuring the security of transactions and the recoverability of funds. The discovery of this bug, detailed in a blog post by morehouse, emphasizes the critical need for ongoing code review and the importance of simplicity and readability in software development to prevent such vulnerabilities, particularly in financial applications like those built on the LDK. [Further information can be found here](https://delvingbitcoin.org/t/disclosure-ldk-invalid-claims-liquidity-griefing/1400). The fix implemented in LDK 0.1 corrects the vulnerability by changing how confirmed transactions are processed, preventing an attacker from exploiting the bug to lock up HTLCs through conflicting aggregated transactions. This resolution highlights the significance of continuous vigilance and regular auditing in the software development process, especially for platforms facilitating critical financial operations. The incident underscores the ever-present risk of attacks in the cryptocurrency domain and reinforces the necessity for developers and users to keep software updated to mitigate potential security threats.

Bitcoin TLDR

#63

newsletter icon

Jan 13 - Jan 19, 2025

Sjors Provoost introduced a discussion on the progression of BIP370, aimed at enhancing the Partially Signed Bitcoin Transactions (PSBT) standard for backward compatibility and allowing new additions to transactions. The slow adoption and review by the community have been noted, despite Bitcoin Core's integration efforts through pull request 21283 and the challenges faced by Core Lightning in maintaining compatibility. For those interested in deeper engagement with BIP370, resources and forums for discussion are available at [BIP370 Proposal](https://github.com/bitcoin/bips/blob/master/bip-0370.mediawiki), [BIP174 Standard](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki), [Bitcoin Core Pull Request 21283](https://github.com/bitcoin/bitcoin/pull/21283), and [Stack Exchange discussion](https://bitcoin.stackexchange.com). Andrew Toth discussed a draft for a Bitcoin Improvement Proposal (BIP) that introduces a method for generating provably unspendable keys using a taproot internal key, aiming at enhancing security and privacy within the Bitcoin ecosystem. The proposal encourages community engagement and offers resources for further exploration and contribution to the discussion, with notable references including [Delving Bitcoin discussion](https://delvingbitcoin.org/t/unspendable-keys-in-descriptors/304) and the [GitHub pull request](https://github.com/bitcoin/bips/pull/1746). This effort highlights the community's commitment to advancing Bitcoin's infrastructure through collaborative and open-source development.

Bitcoin TLDR

#62

newsletter icon

Jan 6 - Jan 12, 2025

Ava Chow announced the release of Bitcoin Core version 28.1, featuring enhancements like new peer-to-peer (P2P) configuration options and improved compatibility across various operating systems. This version also addresses certain bug fixes, introduces performance improvements, and updates translations. Users are advised to follow specific upgrade instructions, particularly when migrating from older versions, and can download the update from [Bitcoin Core's official website](https://bitcoincore.org/bin/bitcoin-core-28.1). Significant technical advancements include modifications to address port collisions and improvements in key handling and build systems. In a separate discussion, mcelrath explored the development of covenant-based solutions for Bitcoin mining pools, focusing on secure and accurate transaction management without custody risks. By leveraging covenants, the proposal aims to ensure theft-proof payouts in alignment with a "can't-be-evil" philosophy, offering an alternative to the [FROST federation](https://github.com/pool2win/frost-federation) model. These covenants would enforce specific transaction paths, include safeguards against pool failures, and adjust for dynamic payout changes, highlighting a proactive approach to enhancing transaction security within the Bitcoin ecosystem. Finally, cdecker addressed the dynamics of channel finalization within blockchain networks, emphasizing the limited impact of attack strategies aimed at disrupting this process. The discussion highlighted mechanisms allowing victims to counter outdated updates published by attackers effectively, suggesting that collusive attacks requiring majority control are unlikely to achieve indefinite censorship. This analysis underscores the resilience of blockchain systems against such disruptions, though it acknowledges vulnerabilities in systems reliant on timelock or CSV mechanisms. For more detailed insights, visit [this discussion](https://delvingbitcoin.org/t/broken-multi-party-eltoo-with-bounded-settlement/1364/4).

Read Summaries by Source

Bitcoin Dev

View All

Delving Bitcoin

View All

Lightning Dev (archive)

View All
reading astronaut
curvy lines
What People Have to Say
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧑 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback