diff options
| author | Pieter Wuille <pieter.wuille@gmail.com> | 2012-03-03 17:45:11 +0100 |
|---|---|---|
| committer | Pieter Wuille <pieter.wuille@gmail.com> | 2012-03-03 17:45:11 +0100 |
| commit | 9559aeb7a1a272edf19834c286300cc3d57cd0d4 (patch) | |
| tree | c890f028f5100cbb17fad337938053884007b4a8 | |
| parent | 4d436a8bb4ac0bf06b5b23e1af9f402d077168e2 (diff) | |
BIP 30: date fixed
| -rw-r--r-- | bip-0030.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0030.md b/bip-0030.md index 77d6195..c77810c 100644 --- a/bip-0030.md +++ b/bip-0030.md @@ -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 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. +This rule is to be applied to all blocks whose timestamp is after march 15, 2012, 0:00 UTC (unix timestamp 1331769600). ==Rationale== Whatever solution is used, the following law must be obeyed to guarantee sane behaviour: the set of usable |