Malleability, Mt. Gox and BIP 62
BIP 62 (2014) listed the ways a third party could change a transaction’s ID without invalidating its signature, and proposed rules to close them one by one.
Mt. Gox
Blamed a long-known Bitcoin “design issue”, suspended bitcoin withdrawals, and said it would allow them again once a fix was “approved and standardized”.
Bitcoin developers
Malleability was known and wallets and exchanges could handle it in their own software. Their 11 February alert said emergency protocol fixes were not required.
The largest exchange of the day blamed the protocol for its frozen withdrawals, which turned a known quirk into a public fight over who was responsible.
BIP 62 never activated and is now Closed. Segregated Witness (BIP 141, active August 2017) moved signatures out of the transaction ID, and BIP 141 calls this approach superior to BIP 62’s canonical-signature rules.
- Feb 2014Mt. Gox halts bitcoin withdrawals. [1]
- 10 Feb 2014Mt. Gox blames transaction malleability in a statement posted to Bitcointalk. [1]
- 11 Feb 2014bitcoin.org alert: emergency protocol fixes not required. [1]
- 12 Mar 2014BIP 62 is assigned. [1]
- Aug 2017SegWit activates and fixes unintended malleability for signed SegWit inputs. [1] [2]
“Bitcoin transactions are subject to a design issue that has been largely ignored, while known to at least a part of the Bitcoin core developers and mentioned on the BitcoinTalk forums.”
statement posted on Bitcointalk · 10 Feb 2014 · source
“Emergency fixes to the Bitcoin protocol are not required and future improvements are already being discussed.”
bitcoin.org · 11 Feb 2014 · source
“‘There is really nothing to worry about in this case’ is the best and most... correct advice I can give.”
The Verge · 10 Feb 2014 · source