Subscribe to our weekly newsletter

Get the latest updates on the community, upcoming topics, and new discussions in your inbox every week.

Summary

The Bitcoin development community has migrated its mailing list to Google Groups as of February 2024, ceasing the use of the old subscription method. Interested parties are encouraged to join the new list via email request or through the Google Groups website and are recommended to opt-in for all messages for better engagement. Furthermore, an email filter for the 'bitcoindev' mailing list might be beneficial for email organization.

Historical records of the mailing list discussions are publicly available without requiring a Google account and have been preserved at gnusha.org. The complete archive can also be downloaded from diyhpl.us, with hash verification available for data integrity. The community has been encouraged to host additional public archives to maintain the decentralized ethos, with Joe Rayhawk receiving acknowledgment for his support during the transition.

In parallel, a draft Bitcoin Improvement Proposal (BIP) has been introduced, focusing on integrating human-readable names into the Bitcoin network to facilitate easier transactions. The draft, available on GitHub, proposes using DNSSEC for converting domain names into bitcoin: URIs, promising to enhance user experience without necessitating modifications to static invoice formats. This move signifies a step towards streamlining Bitcoin transactions for users.

New posts

February 11, 2024 01:16 UTC

delvingbitcoin

Human Readable Bitcoin Payment Instructions

1 reply

  • A Bitcoin Improvement Proposal introduces standardization for domain-based Bitcoin payment instructions.
  • DNSSEC is employed to convert domain names into universally recognized bitcoin: URIs.
  • The system eases transactions by supporting static invoice bitcoin: URI resolution mechanisms.

February 9, 2024 20:32 UTC

bitcoin-dev

bitcoin-dev Mailing List Migration (Action Required)

1 reply

  • The bitcoindev mailing list has moved to Google Groups, requiring members to resubscribe.
  • Comprehensive archives of the old list are accessible online and downloadable with verification hashes.
  • Users are advised to maintain list etiquette, and contributions to moderation infrastructure are acknowledged.

Ongoing Discussions

February 8, 2024 22:19 UTC

delvingbitcoin

Lamport signatures and other CAT tricks

13 replies

  • Cryptographic techniques secure blockchain state channels, using `nLockTime` and hash series.
  • Adding SHA256 to CTV template enhances security against malleability vulnerabilities.
  • Data availability is key; signing critical data strings maximizes efficiency and security.

February 8, 2024 15:24 UTC

delvingbitcoin

Package aware Fee estimator post cluster mempool

10 replies

  • Neglecting transactions with unconfirmed parents doesn't significantly affect fee estimation models.
  • Misclassifying transactions by fee rate can lead to fee estimation inaccuracies.
  • Adapting fee estimation for bundled transactions is crucial due to emerging package relay and validation.

February 8, 2024 14:18 UTC

delvingbitcoin

V3 and some possible futures

3 replies

  • The sibling eviction issue in version 3.1 arises with multi-cluster complexities.
  • System architecture constraints may necessitate foundational re-evaluations.
  • Resolving sibling eviction for multi-cluster configurations requires innovative solutions.

February 8, 2024 14:15 UTC

delvingbitcoin

An overview of the cluster mempool proposal

16 replies

  • The algorithm uses a minheap and CFR to prioritize transactions for eviction.
  • A diagram check post-eviction verifies transaction clusters remain intact.
  • Efficiencies are promised with O(nlogn) complexity, but relay pins are unaddressed.

February 8, 2024 13:51 UTC

delvingbitcoin

V3 transaction policy for anti-pinning

39 replies

  • Recent study unveils small size anchor spends in Lightning Network transactions.
  • Proposal suggests reducing max v3 child size to cut extra fees from RBF.
  • Trade-off discussed for v3 transaction parameters, experts invited for input.

February 8, 2024 08:16 UTC

delvingbitcoin

Analysis of attempting to imbue LN commitment transaction spends with v3 semantics

3 replies

  • Nineteen cryptocurrency transactions showed potential Eclair protocol behaviors with single anchor spends.
  • Eclair's protocol allows unconfirmed inputs but adapts to network feedback for transaction funding.
  • The unlisted transaction IDs of the analyzed transactions prompt further investigative necessity.

February 7, 2024 19:35 UTC

delvingbitcoin

[BUG]: spammers get Bitcoin blockspace at discounted price. Let's fix it

24 replies

  • The "witness discount" aims to deter the use of data affecting nodes.
  • Its use persists despite efforts to limit impactful bytes.
  • The growing Unspent Transaction Output set evidences this strategy's failure.

February 6, 2024 14:10 UTC

delvingbitcoin

OP_VAULT comments

3 replies

  • A new solution for a long-standing issue is proposed.
  • "Collateral" is suggested as a risk mitigation strategy.
  • The effectiveness of collateral in this role requires further exploration.