summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPieter Wuille <pieter.wuille@gmail.com>2012-03-03 16:51:15 +0100
committerPieter Wuille <pieter.wuille@gmail.com>2012-03-03 16:51:15 +0100
commit4d436a8bb4ac0bf06b5b23e1af9f402d077168e2 (patch)
tree511efa336ac4b3d4e925a79581313850a254c99d
parentc00721d90f6a1687d8d6268978c9a435d5b14a25 (diff)
downloadbips-4d436a8bb4ac0bf06b5b23e1af9f402d077168e2.tar.xz
Minor improvements to BIP 30
-rw-r--r--bip-0030.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0030.md b/bip-0030.md
index 6ef98ca..77d6195 100644
--- a/bip-0030.md
+++ b/bip-0030.md
@@ -15,7 +15,7 @@ So far, the Bitcoin reference implementation always assumed duplicate transactio
==Specification==
To counter this problem, the following network rule is introduced:
-*Blocks are not allowed to contain a transaction whose identifier matches that of an earlier, not-fully-spent transaction in the same chain.
+*Blocks are not allowed to contain a transaction whose hash matches that of an earlier transaction in the same chain, unless that earlier transaction was already fully spent before said block.
This rule is to be applied to all blocks whose timestamp is after a point in time that is yet to be decided.
@@ -41,7 +41,7 @@ The addition of this rule only makes some previously-valid blocks invalid. This
A patch for the reference client can be found on https://github.com/sipa/bitcoin/tree/nooverwritetx
==Acknowledgements==
-Thanks to Russell O'Connor for finding and demonstrating this problem, and helping test the patch.
+Thanks to Russell O'Connor for finding and demonstrating this problem and helping test the patch, and to Ben Reeves for pointing out a few weaknesses in the implementation.
[[Category:Developer]]
[[Category:Technical]]