Bitcoin Explained - The Technical Side of Bitcoin cover image

Bitcoin Explained - The Technical Side of Bitcoin

Episode 87: The Block 1,983,702 Problem

Dec 21, 2023
Aaron and Sjors discuss the 'block 1,983,702 problem' in the Bitcoin protocol and its potential for loss of funds and consensus failures. They explain how BIP 30 and BIP 34 solved this problem but introduced a new issue for the future. They explore solutions such as segment commitment and propose SegWit as the most reasonable solution for empty blocks in Bitcoin mining.
39:14

Podcast summary created with Snipd AI

Quick takeaways

  • The bug in the Bitcoin protocol that allowed for two identical transactions to exist caused a consensus failure and chaos in the network, leading to the introduction of BIP-30 and BIP-34 as solutions.
  • A proposed solution to address the bug is to make segwit mandatory for every coinbase transaction, which is considered the simplest and most reasonable approach.

Deep dives

The Bug in the Bitcoin Protocol

In this podcast episode, the hosts discuss a bug in the Bitcoin protocol that originated with the first Satoshi bug. The bug allowed for two identical transactions to exist, and the original transaction would essentially disappear when a new one was created. This created a consensus failure in which the ownership records for these identical transactions would diverge, leading to chaos in the network. To address this bug, the BIP-30 rule was introduced in 2012, which ensured that no two transactions with the same hash could exist simultaneously. However, this rule added inefficiencies and was later optimized in 2015. In 2017, it was realized that there could still be exceptions to this rule in earlier coinbase transactions. To prevent any potential exploitation of this bug, the fix was deployed in 2018, and now Bitcoin core nodes start checking BIP-30 from block 1,983,702 onwards. Various other proposals, such as making segwit mandatory or adding the block height to the coinbase transaction, have been discussed as potential solutions. However, the consensus is that BIP-30 still remains the simplest and most reasonable approach. As of now, we have approximately 20 years to find a permanent solution to this bug before Bitcoin core nodes start checking BIP-30 again.

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode