summaryrefslogtreecommitdiff
path: root/bip-0017.mediawiki
diff options
context:
space:
mode:
authorPeter Todd <pete@petertodd.org>2013-10-21 00:44:39 -0400
committerPeter Todd <pete@petertodd.org>2013-10-21 00:44:39 -0400
commit16fe80c1c61b0d78581af78854e419f7ab544c69 (patch)
tree3dc3b7a9871db50e990c2640f6f3ad9d84a27a67 /bip-0017.mediawiki
parent57488fbd8b6d2d581b12864ce7a07149e19a177d (diff)
Archive Revision as of 17:37, 28 April 2013
https://en.bitcoin.it/w/index.php?title=BIP_0017&oldid=37378
Diffstat (limited to 'bip-0017.mediawiki')
-rw-r--r--bip-0017.mediawiki11
1 files changed, 7 insertions, 4 deletions
diff --git a/bip-0017.mediawiki b/bip-0017.mediawiki
index 0cd5d70..d10ab8a 100644
--- a/bip-0017.mediawiki
+++ b/bip-0017.mediawiki
@@ -1,9 +1,11 @@
+{{bip}}
+
<pre>
BIP: 17
Title: OP_CHECKHASHVERIFY (CHV)
Author: Luke Dashjr <luke+bip17@dashjr.org>
- Status: Withdrawn
- Type: Standards Track
+ Status: Draft
+ Type: Withdrawn
Created: 18-01-2012
</pre>
@@ -26,7 +28,7 @@ OP_CHECKHASHVERIFY will re-define the existing OP_NOP2 opcode, and will function
* If the hashes match, do nothing, proceed as if an OP_NOP; if they do not match, the script fails immediately.
* Note that in the case of a matched hash, the top stack item (the hash being compared with) is <u>not</u> popped off the stack. This is for backward compatibility.
-This opcode reassignment shall be applied when validating transactions in blocks only with timestamps after February 20, 2012 (see the Backwards Compatibility section for details).
+This opcode reassignment shall be applied when validating transactions in blocks only with timestamps after February 23, 2012 (see the Backwards Compatibility section for details).
A new standard transaction type that is relayed and included in mined blocks is defined:
@@ -82,7 +84,7 @@ To gracefully upgrade and ensure no long-lasting block-chain split occurs, more
To judge whether or not more than 50% of hashing power supports this BIP, miners are asked to upgrade their software and put the string "p2sh/CHV" in the input of the coinbase transaction for blocks that they create.
-On February 3, 2012, the block-chain will be examined to determine the number of blocks supporting pay-to-script-hash for the previous 7 days. If at least 60% contain "p2sh/CHV" in their coinbase, then all blocks with timestamps after 18 Feb 2012, 00:00:00 GMT shall have their pay-to-script-hash transactions validated.
+On February 8, 2012, the block-chain will be examined to determine the number of blocks supporting pay-to-script-hash for the previous 7 days. If at least 60% contain "p2sh/CHV" in their coinbase, then all blocks with timestamps after 23 Feb 2012, 00:00:00 GMT shall have their pay-to-script-hash transactions validated.
If a majority of hashing power does not support the new validation rules, then rollout will be postponed (or rejected if it becomes clear that a majority will never be achieved).
@@ -100,3 +102,4 @@ OP_NOP2 is used, so existing OP_EVAL (BIP 12) transactions in the block chain ca
* [[BIP 0011|M-of-N Multisignature Transactions (BIP 11)]]
* Example BIP 17 transaction chain: [http://blockexplorer.com/tx/b8fd633e7713a43d5ac87266adc78444669b987a56b3a65fb92d58c2c4b0e84d a] [http://blockexplorer.com/tx/eb3b82c0884e3efa6d8b0be55b4915eb20be124c9766245bcc7f34fdac32bccb b] [http://blockexplorer.com/tx/055707ce7fea7b9776fdc70413f65ceec413d46344424ab01acd5138767db137 c] [http://blockexplorer.com/tx/6d36bc17e947ce00bb6f12f8e7a56a1585c5a36188ffa2b05e10b4743273a74b d]
+[[Category:BIP|D]]