summaryrefslogtreecommitdiff
path: root/bip-0030.mediawiki
diff options
context:
space:
mode:
authorLuke Dashjr <luke-jr+git@utopios.org>2017-01-19 19:55:44 +0000
committerLuke Dashjr <luke-jr+git@utopios.org>2017-01-19 19:55:46 +0000
commit855eb2200406166032debb719a0eedf0ae4e3860 (patch)
tree7fcd7954fbb538df860e22e49f40af821a03e1a2 /bip-0030.mediawiki
parent872bda33b51b0b28f339e9dfd3c6d16226cf1d46 (diff)
downloadbips-855eb2200406166032debb719a0eedf0ae4e3860.tar.xz
BIPs 30, 32, 62, 66, and 103: License under BSD-2-Clause terms
[Thursday, January 19, 2017] [7:46:36 PM UTC] <luke-jr> sipa: if you get a minute, can you give me at least a text-"verbal" ACK for some copyright license to put on BIPs 30, 32, 62, 66, and 103 please? is BSD-2-Clause okay? [Thursday, January 19, 2017] [7:47:01 PM UTC] <sipa> luke-jr: ACK on 2-clause BSD for 30,32,62,66,103 [Thursday, January 19, 2017] [7:47:13 PM UTC] <sipa> (and for any other BIPs I contributed to)
Diffstat (limited to 'bip-0030.mediawiki')
-rw-r--r--bip-0030.mediawiki5
1 files changed, 5 insertions, 0 deletions
diff --git a/bip-0030.mediawiki b/bip-0030.mediawiki
index 56ef3de..a63b737 100644
--- a/bip-0030.mediawiki
+++ b/bip-0030.mediawiki
@@ -8,11 +8,16 @@
Status: Final
Type: Standards Track
Created: 2012-02-22
+ License: BSD-2-Clause
</pre>
==Abstract==
This document gives a specification for dealing with duplicate transactions in the block chain, in an attempt to solve certain problems the reference implementations has with them.
+==Copyright==
+
+This BIP is licensed under the 2-clause BSD license.
+
==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.