summaryrefslogtreecommitdiff
path: root/bip-0030.mediawiki
diff options
context:
space:
mode:
authorairbreather <airbreather@linux.com>2014-03-09 17:28:18 -0400
committerairbreather <airbreather@linux.com>2014-03-09 17:28:18 -0400
commit69ab42039c5a12f19b0145b1295ad29094ea9d6d (patch)
treecd24e8a90471f2a81fe8b0942d777c4bbc6f3787 /bip-0030.mediawiki
parent6c06f31adadea2daa1707eede8056dd3c4daec20 (diff)
downloadbips-69ab42039c5a12f19b0145b1295ad29094ea9d6d.tar.xz
Documenting the timestamp for BIP-0030
Per the linked commit, this rule became active for blocks with timestamps after on March 15, 2012 at 00:00 UTC (February 20, 2012 at 00:00 UTC for testnet).
Diffstat (limited to 'bip-0030.mediawiki')
-rw-r--r--bip-0030.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0030.mediawiki b/bip-0030.mediawiki
index cd725b8..fd6ab39 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 a point in time that is yet to be decided.
+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).
==Rationale==
Whatever solution is used, the following law must be obeyed to guarantee sane behaviour: the set of usable