Subscribe to our weekly newsletter

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

Summary

Recent discussions at the MIT DCI session unveiled a novel approach to applying Lamport signatures for Bitcoin transactions, circumventing the need for OP_CAT by leveraging the variable length of ECDSA signatures. This method, which involves utilizing the 's-value' variations of ECDSA signatures to indirectly sign transaction lengths, introduces a unique cryptographic challenge in maintaining security, necessitating an estimated 1000 signatures per transaction. Despite its innovative potential, the approach is currently more theoretical than practical, facing hurdles such as susceptibility to various attacks and the practicality of generating a substantial number of signatures to ensure security.

Ali Sherief and Erik Aronesty raised significant concerns and suggestions pertaining to the practical aspects of Bitcoin development. Sherief highlighted the difficulties in obtaining reproducible legacy transactions for effective testing, underscoring the necessity for access to raw transactions and private keys. Aronesty, on the other hand, inquired about reliable platforms for posting bounties for privacy-layer reviews and implementations, pointing out a resource gap in the cryptocurrency development landscape. Additionally, Fractal Encrypt suggested improvements to Bitcoin's decoderawtransaction functionality to include transaction fee information, aiming to enhance fee verification accuracy despite self-acknowledged limitations in technical expertise.

Discussions also touched on broader implications for Bitcoin's future, with concerns about transaction selection centralization and the potential for censorship. A deterministic algorithm for transaction selection was proposed as a solution to preserve decentralization, with decentralized mining pools like P2Pool or Braidpool suggested as facilitators. Moreover, the evolving Coinjoin process was examined, with recent innovations aimed at simplifying participation and enhancing privacy through "rolling coinjoin" transactions, highlighted by an electrum plugin development for joinstr. These discussions underscore ongoing efforts to address privacy, security, and decentralization challenges in Bitcoin's ecosystem.

New posts

May 4, 2024 15:00 UTC

bitcoin-dev

A Fool's Errand or should I try?

1 reply

  • The sender proposes enhancing `decoderawtransaction` to include fee and sats/vB.
  • Suggests modifying it to fetch UTXO details for accurate fee calculation.
  • Expresses hope to contribute the enhancement back to the community through a pull request.

May 3, 2024 21:19 UTC

delvingbitcoin

Pools without covenants
  • Coinjoin simplification involves `SIGHASH_ALL | SIGHASH_ANYONECANPAY` and Nostr channels.
  • A novel solution offers pool joining/leaving flexibility, with an electrum plugin under development.
  • Security and broader applications, including Discreet Log Contracts, highlight the evolving technology.

May 3, 2024 19:59 UTC

bitcoin-dev

bitcoin bounty program
  • Erik Aronesty seeks a reliable bounty program for a privacy-layer Pull Request enhancement.
  • He plans to establish bounties for professional review and implementation of a Bitcoin Improvement Proposal.
  • He notes a gap in resources for specific bounty postings in cryptocurrency development.

April 30, 2024 11:43 UTC

bitcoin-dev

Test cases for signing legacy inputs in transactions

2 replies

  • Ali Sherief highlights difficulties in testing legacy transactions due to missing debug info.
  • The use of OpenSSL for signatures introduces non-determinism, reducing test reliability.
  • There's a community need for legacy transactions with private keys for better testing methodologies.

April 29, 2024 12:26 UTC

delvingbitcoin

Deterministic tx selection for censorship resistance

2 replies

  • The discussion highlights concerns about Bitcoin's transaction selection leading to potential centralization.
  • Proposes a deterministic algorithm for transaction selection to combat censorship and maintain decentralization.
  • Acknowledges that while this method may improve validation and reduce bandwidth, it doesn't fully eliminate censorship.

April 29, 2024 00:30 UTC

bitcoin-dev

Signing a Bitcoin Transaction with Lamport Signatures (no changes needed)

6 replies

  • Ethan Heilman introduced an innovative method for Bitcoin transactions using Lamport signatures.
  • This method bases its security on creating signatures that vary in size, needing about 1000 for robustness.
  • Despite its potential, the approach faces challenges like susceptibility to various attacks, promoting further refinement.

Ongoing Discussions

May 5, 2024 12:14 UTC

delvingbitcoin

CISA and Privacy

3 replies

  • The necessity for a new output script type emerges from CISA's requirements.
  • Incorporating it into P2TR requires a hardfork, posing operational challenges.
  • Adopting bech32m for the new script ensures consistency and eases integration.

May 4, 2024 10:57 UTC

delvingbitcoin

Basic vault prototype using OP_CAT

18 replies

  • Golang's simplicity and efficiency make it accessible, contrasting Rust's complexity.
  • Golang is ideal for web servers and data processing due to its syntax and standard library.
  • Choosing between Golang and Rust depends on project needs and developer expertise.

May 4, 2024 07:45 UTC

delvingbitcoin

Satoshi Style Message Signing

3 replies

  • The absence of comprehensive documentation in a project is discussed, highlighting a need for updates.
  • A pull request by sipa, found at GitHub, serves as a key reference point.
  • Extended discussions on this topic are accessible through a BitcoinTalk forum, offering broader insights.

May 4, 2024 00:11 UTC

bitcoin-dev

BIP 322 use case

3 replies

  • Luke Dashjr discusses signed messages for KYC, suggesting simpler user affirmation over cryptographic proof.
  • BIP322's main goal, enabling contract agreements before fund transfers, lacks significant interest.
  • Despite challenges, BIP322 has seen wallet adoption, hinting at its utility and the need for further development.

May 2, 2024 21:17 UTC

delvingbitcoin

LIMO: combining the best parts of linearization search and merging

8 replies

  • Double LIMO algorithm introduces set-linearizations for organizing transactions with novel concepts.
  • The algorithm uses slope algebra and `chunksets` for optimal transaction linearization.
  • Variations of Double LIMO allow dynamic improvement of transaction organization efficiency.

April 30, 2024 22:20 UTC

bitcoin-dev

Great Consensus Cleanup Revival

7 replies

  • The forward blocks proposal offers replayability for transactions, enhancing older software compatibility.
  • It introduces major upgrades as soft forks using the timewarp bug for smoother scalability.
  • Fixing the timewarp bug could prevent backward-compatible scaling, highlighting decision-making gravity.

April 30, 2024 18:46 UTC

bitcoin-dev

The Future of Bitcoin Testnet

39 replies

  • Matthew Bagazinski identifies Testnet's value issue due to its scarcity, affecting its functionality.
  • Peter Todd suggests stopping halving events to increase coin circulation, meeting resistance.
  • Alternatives aim to change scarcity and valuation by adjusting the supply and subsidy rates.

April 30, 2024 02:28 UTC

delvingbitcoin

Exploding Keys - Covenant construction

2 replies

  • Cryptographic mechanism allows A, B, C to sign transactions with an "explodable key."
  • Proposed solution includes a commitment mechanism with specific transaction parameters.
  • Approach enables one-time payment pool but limits dual-path transaction model usability.