summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorairbreather <airbreather@linux.com>2014-03-10 20:17:32 -0400
committerairbreather <airbreather@linux.com>2014-03-10 20:17:32 -0400
commitc2cd720f268c9d068d0c163505601e3dcccbdea0 (patch)
treef5ce4fc0d8a7696a23aeee346e5426edf087d1ea
parent69ab42039c5a12f19b0145b1295ad29094ea9d6d (diff)
downloadbips-c2cd720f268c9d068d0c163505601e3dcccbdea0.tar.xz
BIP-0030 documentation now reflects reality.
-rw-r--r--bip-0030.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0030.mediawiki b/bip-0030.mediawiki
index fd6ab39..0072d04 100644
--- a/bip-0030.mediawiki
+++ b/bip-0030.mediawiki
@@ -17,7 +17,7 @@ So far, the Bitcoin reference implementation always assumed duplicate transactio
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.
-This rule is to be applied to all blocks whose timestamp is after March 15, 2012, 00:00 UTC (testnet: February 20, 2012 00:00 UTC).
+This rule initially applied to all blocks whose timestamp is after March 15, 2012, 00:00 UTC (testnet: February 20, 2012 00:00 UTC). It was later extended by Commit [https://github.com/bitcoin/bitcoin/commit/ab91bf39b7c11e9c86bb2043c24f0f377f1cf514 Apply BIP30 checks to all blocks except the two historic violations.] to apply to all blocks except the two historic blocks at heights 91842 and 91880 on the main chain that had to be grandfathered in.
==Rationale==
Whatever solution is used, the following law must be obeyed to guarantee sane behaviour: the set of usable