dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0030
Differences
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/19 18:14] char |
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:ra:xapend.stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]] |
| <table> | <table> | ||
| Line 17: | Line 17: | ||
| </table> | </table> | ||
| - | : **Note**: The following is an excerpt from the official Bitcoin site. It is provided here as a convenience 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 === | ||
| Line 26: | Line 26: | ||
| === 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.// |
dido/public/ra/xapend/xapend.b_stds/defact/bitcoin/bips/bip_0030.1589926451.txt.gz · Last modified: 2020/05/19 18:14 by char
