soft-fork

Entries tagged with this topic. Spans across types and sources — explore connections between people, events, and themes.

5 entries

January 19, 2020 GitHub

BIP 341 — Taproot: SegWit Version 1 Spending Rules

Pieter Wuille ↔ Jonas Nick, Anthony Towns

Taproot — Bitcoin's most significant protocol upgrade since SegWit. Combines Schnorr (BIP 340) with MAST so complex spending conditions look like simple payments on-chain.

December 21, 2015 GitHub

BIP 141 — Segregated Witness (Consensus Layer)

Eric Lombrozo ↔ Johnson Lau, Pieter Wuille

Segregated Witness (SegWit) — Bitcoin's most significant protocol upgrade since creation. Separates signature from transaction data, fixing malleability, enabling Lightning, raising block capacity.

October 1, 2014 GitHub

Peter Todd proposes BIP 65: OP_CHECKLOCKTIMEVERIFY

Peter Todd

Peter Todd proposed BIP 65, introducing OP_CHECKLOCKTIMEVERIFY — an opcode locking transaction outputs until a future time. Deployed as a soft fork, enabling escrow and payment channels.

August 15, 2010 BitcoinTalk

Value overflow incident — 184 billion BTC created in Block 74638

Jeff Garzik ↔ Satoshi Nakamoto, Gavin Andresen

An integer overflow bug (CVE-2010-5139) was exploited to create 184 billion BTC in Block 74638. Satoshi published a fix within 5 hours; the corrected chain overtook the invalid one within 15 hours.

August 15, 2010 bitcoinarchive

The day 184 billion BTC was minted — the centralization paradox, soft-fork rescue, and a 5-hour response

Bitcoin Institute ↔ Satoshi Nakamoto, Jeff Garzik, Gavin Andresen, knightmb

Structural reading of the 2010-08-15 overflow incident — soft-fork rescue mechanics, why a 5-hour response was only achievable then, transaction-shape forensics, and the centralization paradox.