This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0030 [2020/05/07 15:35] nick ↷ Page moved from dido:public:apdx.stds:defact:bitcoin:bips:bip_0030 to dido:public:xapend.stds:defact:bitcoin:bips:bip_0030 |
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0030 [2021/08/06 13:58] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== BIP 0030 - Duplicate transactions (soft fork) ======== | + | ==== BIP 0030 - Duplicate transactions (soft fork) ==== |
| - | [[dido:public:apdx.stds:defact:bitcoin| return to the Bitcoin Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]] |
| <table> | <table> | ||
| Line 9: | Line 9: | ||
| | Comments-Summary | No comments yet. | | | Comments-Summary | No comments yet. | | ||
| | Comments-URI | [[https://github.com/bitcoin/bips/wiki/Comments:BIP-0030]] | | | Comments-URI | [[https://github.com/bitcoin/bips/wiki/Comments:BIP-0030]] | | ||
| - | | Staus | Final | | + | | Status | Final | |
| | Type | Standards Track | | | Type | Standards Track | | ||
| | Created | 2012-02-22 | | | Created | 2012-02-22 | | ||
| Line 17: | Line 17: | ||
| </table> | </table> | ||
| - | : **Note**: The following is an excerpt from the official Bitcoin site. It is provided here as a connivence and is not authoritative. Refer to the original document(s) as the authoritative reference. | + | : **Note**: The following is an excerpt from the official [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]] site. It is provided here as a convenience and is not authoritative. Refer to the original document(s) as the authoritative reference. |
| - | ====== Abstract ====== | + | === Abstract === |
| : //This document gives a specification for dealing with duplicate transactions in the block chain, in an attempt to solve certain problems the reference implementation has with them.// | : //This document gives a specification for dealing with duplicate transactions in the block chain, in an attempt to solve certain problems the reference implementation has with them.// | ||
| - | ====== Copyright ====== | + | === Copyright === |
| : //This BIP is licensed under the 2-clause BSD license.// | : //This BIP is licensed under the 2-clause BSD license.// | ||
| - | ====== Motivation ====== | + | === Motivation === |
| - | ://So far, the Bitcoin reference implementation always assumed duplicate transactions (transactions with the same identifier) didn't exist. This is not true; in particular coinbases are easy to duplicate, and by building on duplicate coinbases, duplicate normal transactions are possible as well. Recently, an attack that exploits the reference implementation's dealing with duplicate transactions was described and demonstrated. It allows reverting fully-confirmed transactions to a single confirmation, making them vulnerable to become unspendable entirely. Another attack is possible that allows forking the block chain for a subset of the network.// | + | ://So far, the Bitcoin reference implementation always assumed duplicate transactions (transactions with the same [[dido:public:ra:xapend:xapend.a_glossary:i:id|identifier]]) didn't exist. This is not true; in particular coinbases are easy to duplicate, and by building on duplicate coinbases, duplicate normal transactions are possible as well. Recently, an attack that exploits the reference implementation's dealing with duplicate transactions was described and demonstrated. It allows reverting fully-confirmed transactions to a single [[dido:public:ra:xapend:xapend.a_glossary:c:confirmation|confirmation]], making them vulnerable to become unspendable entirely. Another attack is possible that allows forking the block chain for a subset of the network.// |