Subscribe to our weekly newsletter

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

Summary

Recent advancements in Bitcoin technology propose a new transaction replacement policy, One-Shot Replace-By-Fee-Rate (OSRBF), to enhance transaction efficiency and protect against pinning attacks, with research backed by Fulgur Ventures confirming its robustness against bandwidth exhaustion attacks. In anticipation of a time overflow issue by the year 2106, the BitBlend solution offers a dual time representation system, avoiding hard forks while ensuring Bitcoin's longevity, with a comprehensive white paper available for community evaluation.

The release of Bitcoin Core v26.0 marks a significant upgrade with the inclusion of Antoine Riard's full-RBF peering code, facilitating nodes that adopt mempoolfullrbf=1 to improve the network's transaction handling capabilities, with the code available on GitHub. In parallel, the launch of bipbounty.org seeks to incentivize the development of Bitcoin Improvement Proposals (BIPs) through a bug bounty model, enhancing protocol research and development.

Stratum v2, incorporating encryption via the Noise Protocol Framework, is undergoing integration with Bitcoin Core, aiming to potentially incorporate features from BIP324 to further refine the protocol. Meanwhile, the discovery of a vulnerability in the anti-MEVil mechanism exposes potential manipulation in transaction validation, calling for attention to anti-DoS rules. Additionally, advancements in MATT contracts for fraud proofs present significant reductions in data overhead and transaction costs, with the game-in-the-head technique promising to streamline multi-party protocols and improve efficiency within networks such as Lightning.

New posts

January 20, 2024 21:33 UTC

bitcoin-dev

Full-RBF Peering Bitcoin Core v26.0 Released

1 reply

  • Bitcoin Core v26.0 introduces full-RBF, which allows certain nodes to broadcast and connect with peers.
  • Full-RBF adoption is optional but could improve the Bitcoin network if more users participate.
  • Peter Todd runs v26.0 nodes with enhanced settings; the code is available on GitHub for download.

January 20, 2024 17:00 UTC

delvingbitcoin

Games in the head (and fraud proofs for the plebs)

1 reply

  • The novel fraud proof optimization reduces data and costs for two-party MATT contracts.
  • This method allows hashing and committing to simplifying transactions and reduce proof rounds.
  • Implementing k-section protocols in pools can cut fraud proof transactions to five, enhancing efficiency.

January 19, 2024 16:56 UTC

delvingbitcoin

Ephemeral Anchors and MEVil

2 replies

  • An anomaly in the "anti-MEVil" mechanism allows manipulation of transactions via increased ephemeral anchor values.
  • Bob uses Alice's trimmed funds to create a conflict, demonstrated through four illustrated transactions.
  • Anti-DoS rules unintentionally incentivize adversaries to inflate fees, affecting transaction validation.

January 19, 2024 13:53 UTC

delvingbitcoin

BIPBounty.org is Open for Your BIPs

1 reply

  • The Bitcoin community reviews new BIPs proposing substantial core alterations.
  • Bipbounty.org, under a non-profit, aids protocol research with bug bounties.
  • Donors can fund specific BIPBounties or general Bitcoin development initiatives.

January 18, 2024 18:23 UTC

bitcoin-dev

One-Shot Replace-By-Fee-Rate

1 reply

  • A new Bitcoin transaction replacement policy focuses on fee-rate rather than total fee.
  • The policy requires a substantial fee-rate increase for transaction replacement.
  • It offers miners more immediate revenue and resists bandwidth exhaustion attacks.

January 16, 2024 13:50 UTC

bitcoin-dev

BitBlend Proposal for 2106

1 reply

  • BitBlend2106 proposes a non-disruptive fix to Bitcoin's 2106 timestamp overflow issue.
  • The approach uses dual timestamp representation to ensure compatibility without a hard fork.
  • The developer seeks community feedback on the proposal, available for review online.

January 15, 2024 13:54 UTC

delvingbitcoin

Stratum v2 Noise Protocol: BIP324 nuggets?

1 reply

  • Stratum v2 enhances Bitcoin mining communication with end-to-end encryption via the Noise Protocol.
  • It's considering BIP324 elements; common cryptographic functions hint at potential compatibility.
  • Future protocol improvements could facilitate a gradual shift to BIP324 without major overhauls.

Ongoing Discussions

January 19, 2024 23:56 UTC

delvingbitcoin

Warnet + Increase Tx Relay Rate

9 replies

  • The blog discusses a 100-node network simulation on Bitcoin transaction behavior and initial balances.
  • The simulation showed no performance change with/without an update, questioning its effectiveness.
  • Author considers Kubernetes to better simulate higher transaction rates and network scenarios.

January 19, 2024 21:27 UTC

delvingbitcoin

64 bit arithmetic soft fork

33 replies

  • Misconceptions about Bitcoin opcode impacts on memory versus disk space are clarified.
  • BIP62 addresses transaction malleability, not disk space optimization.
  • Proposals advocate for standard number formats and reflections on wallet implications.

January 19, 2024 17:36 UTC

delvingbitcoin

OP_CHECKSIGFROMSTACKVERIFY ECDSA useful?

4 replies

  • The Super Testnet promotes DER-encoded ECDSA signatures for consistent transaction validation.
  • ECDSA's efficiency and DER's universal encoding enhance cryptographic interoperability.
  • Uniform ECDSA signing across scripts could simplify and secure the network's proof of work.

January 19, 2024 00:59 UTC

delvingbitcoin

Lightning transactions with v3 and ephemeral anchors

22 replies

  • HTLCs pose risks where Bob's actions could tie up Alice's significant channel funds.
  • Bob incurs minimal cost by not completing transactions, strategically pressuring Alice.
  • Bob's tactic doesn't profit him but uses the funds as leverage to disrupt Alice.

January 18, 2024 20:39 UTC

delvingbitcoin

On consensus changes in bitcoin 2024

19 replies

  • Bitcoin's primary development goal is to enhance scalability for future suitability.
  • The focus extends beyond current issues to long-term network growth and improvement.
  • Efforts aim to sustain Bitcoin as a robust currency for an expanding user base over time.

January 18, 2024 16:34 UTC

delvingbitcoin

Thoughts on scaling and consensus changes (2023)

5 replies

  • Bitcoin's value is based on scarcity, transparent supply, and permissionless transactions.
  • Technological advances in block size and mining could boost Bitcoin's utility and value.
  • Improving scale and security without losing key features could enhance Bitcoin's worth.

January 18, 2024 07:56 UTC

delvingbitcoin

Deploying new taproot leaf versions

2 replies

  • The proposal suggests adding a new `SigVersion` to change Bitcoin's opcode behaviors.
  • This method allows backward-compatible soft forks, evolving Bitcoin's scripting capabilities.
  • The commit demonstrates practical application within the current Bitcoin system architecture.

January 18, 2024 06:22 UTC

delvingbitcoin

LNHANCE bips and implementation

13 replies

  • A Pull Request for CSFS and INTERNALKEY enhancements is made in 'binana' repo.
  • Draft PRs for csfs and internalkey are proposed separately in Bitcoin Core repository.
  • Future CTV feature may be split into two PRs to simplify testing and integration.

January 17, 2024 17:29 UTC

bitcoin-dev

BIP process friction

10 replies

  • The email acknowledges complexities in Bitcoin policy change processes and their standardization.
  • It suggests formalizing default policy changes as BIPs for clarity and tracking.
  • The sender proposes revising policy change methods and respects the recipient's BIP contributions.

January 16, 2024 17:08 UTC

bitcoin-dev

Compressed Bitcoin Transactions

15 replies

  • Tom Briar discusses a schema saving up to 30% transaction size in Bitcoin communications.
  • The schema maintains reversibility, except for optional Txid/Vout compression.
  • Further details can be found in "compressed_transactions.md" and the BIP-324 GitHub link.

January 16, 2024 14:20 UTC

delvingbitcoin

Unspendable keys in descriptors

24 replies

  • A mismatch exists between key order in wallet policies and descriptor templates.
  • An example shows the expected key sequence doesn't match the actual `pubkeyA||pubkeyB`.
  • Aligning descriptor templates with wallet policies' structure may resolve inconsistencies.

January 16, 2024 10:40 UTC

bitcoin-dev

[BUG]: Bitcoin blockspace price discrimination put simple transactions at disadvantage

9 replies

  • Transaction size and fees largely dictate blockchain network priorities, not just type.
  • P2WPKH, from SegWit, increases block capacity and improves malleability by separating witness data.
  • P2TR, Taproot's upgrade, boosts privacy and efficiency, especially for smart contract transactions.

January 16, 2024 08:18 UTC

bitcoin-dev

MuSig2 derivation, descriptor, and PSBT field BIPs

2 replies

  • X-only public keys save space but add complexities in cryptographic protocols.
  • Careful coordination in multisignature schemes like FROST is crucial for security.
  • Developers must balance optimization with security when using x-only pubkeys.

January 15, 2024 06:56 UTC

delvingbitcoin

LN-Symmetry Project Recap

11 replies

  • The blog post highlights using route hints for private channel hops via a GitHub link.
  • It discusses issues in transactions, notably with large sums like 25 sBTC in certain channels.
  • The author shares real-world troubleshooting experiences with Bitcoin's second-layer tech.