Pay to script hash - Revision history

Evoskuil: /* History */ fix bip9 url

2017-12-30T23:34:55Z

History: fix bip9 url

← Older revision		Revision as of 23:34, 30 December 2017
Line 21:		Line 21:
	== History ==		== History ==

	The first activation window failed and another was set to be active on 1 April 2012, in v0.6.0rc2<ref>[https://github.com/bitcoin/bitcoin/commit/46aa2a6bdd5ec512dd2e364b298e6e73c3e61354 Move BIP16 switchover time to April 1 (gavinandresen)]</ref>. Users running v0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. Later soft fork activation techniques, such as [[BIP 0034\|BIP 34]] and [[BIP ~~00009~~\|BIP 9]], reflect on block history to determine activation (also from miner signaling) in order to prevent this problem.		The first activation window failed and another was set to be active on 1 April 2012, in v0.6.0rc2<ref>[https://github.com/bitcoin/bitcoin/commit/46aa2a6bdd5ec512dd2e364b298e6e73c3e61354 Move BIP16 switchover time to April 1 (gavinandresen)]</ref>. Users running v0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. Later soft fork activation techniques, such as [[BIP 0034\|BIP 34]] and [[BIP 0009\|BIP 9]], reflect on block history to determine activation (also from miner signaling) in order to prevent this problem.

	After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>. Later soft fork activation techniques raised the signaling enforcement threshold from 55% to 95% in order to mitigate this problem.		After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>. Later soft fork activation techniques raised the signaling enforcement threshold from 55% to 95% in order to mitigate this problem.

Evoskuil: Style, links

2017-12-30T23:32:24Z

Style, links

← Older revision		Revision as of 23:32, 30 December 2017
Line 21:		Line 21:
	== History ==		== History ==

	The first activation window failed and another was set to be active on April 1 2012, in v0.6.0rc2<ref>[https://github.com/bitcoin/bitcoin/commit/46aa2a6bdd5ec512dd2e364b298e6e73c3e61354 Move BIP16 switchover time to April 1 (gavinandresen)]</ref>. Users running v0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. Later soft fork activation techniques, such as BIP~~-34<ref>[https://github.com/bitcoin/bips/blob/master/bip-~~0034~~.mediawiki~~ BIP-34]~~</ref>~~ and BIP~~-9<ref>[https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki~~ BIP-9]~~</ref>~~, reflect on block history to determine activation (also from miner signaling) in order to prevent this problem.		The first activation window failed and another was set to be active on 1 April 2012, in v0.6.0rc2<ref>[https://github.com/bitcoin/bitcoin/commit/46aa2a6bdd5ec512dd2e364b298e6e73c3e61354 Move BIP16 switchover time to April 1 (gavinandresen)]</ref>. Users running v0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. Later soft fork activation techniques, such as [[BIP 0034\|BIP 34]] and [[BIP 00009\|BIP 9]], reflect on block history to determine activation (also from miner signaling) in order to prevent this problem.

	After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>. Later soft fork activation techniques raised the signaling enforcement threshold from 55% to 95% in order to mitigate this problem.		After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>. Later soft fork activation techniques raised the signaling enforcement threshold from 55% to 95% in order to mitigate this problem.

Evoskuil: Accommodate single window (fixed props) activation box.

2017-12-30T23:29:47Z

Accommodate single window (fixed props) activation box.

← Older revision		Revision as of 23:29, 30 December 2017
Line 3:		Line 3:
	\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender		\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender
	\|coinbase=/P2SH/		\|coinbase=/P2SH/
	\|~~starttime1=2012-01-25 00:00:00~~		\|starttime=2012-03-08 00:00:00
	~~\|timeout1=2012-02-01 00:00:00~~		\|timeout=2012-03-15 00:00:00
	~~\|starttime2~~=2012-03-08 00:00:00
	\|~~timeout2~~=2012-03-15 00:00:00
	\|supermajority=55%		\|supermajority=55%
	\|activated=Block #173805<br/>2012-04-01 00:00:00		\|activated=Block #173805<br/>2012-04-01 00:00:00

Evoskuil: Add both activation windows, add links and more information on failed activations, add testnet activation.

2017-12-30T23:27:56Z

Add both activation windows, add links and more information on failed activations, add testnet activation.

← Older revision		Revision as of 23:27, 30 December 2017
Line 3:		Line 3:
	\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender		\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender
	\|coinbase=/P2SH/		\|coinbase=/P2SH/
	\|~~starttime~~=2012-01-25 00:00:00		\|starttime1=2012-01-25 00:00:00
	\|~~timeout~~=2012-02-01 00:00:00		\|timeout1=2012-02-01 00:00:00
			\|starttime2=2012-03-08 00:00:00
			\|timeout2=2012-03-15 00:00:00
	\|supermajority=55%		\|supermajority=55%
	\|activated=Block #173805<br/>2012-04-01 00:00:00		\|activated=Block #173805<br/>2012-04-01 00:00:00
Line 21:		Line 23:
	== History ==		== History ==

	The first activation window failed and another was set to ~~start~~ on ~~15 March~~ 2012. Users running 0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>.		The first activation window failed and another was set to be active on April 1 2012, in v0.6.0rc2<ref>[https://github.com/bitcoin/bitcoin/commit/46aa2a6bdd5ec512dd2e364b298e6e73c3e61354 Move BIP16 switchover time to April 1 (gavinandresen)]</ref>. Users running v0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. Later soft fork activation techniques, such as BIP-34<ref>[https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki BIP-34]</ref> and BIP-9<ref>[https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki BIP-9]</ref>, reflect on block history to determine activation (also from miner signaling) in order to prevent this problem.

			After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>. Later soft fork activation techniques raised the signaling enforcement threshold from 55% to 95% in order to mitigate this problem.

			Testnet activated following its first window, which was two weeks earlier than the first (failed) mainnet window<ref>[https://github.com/bitcoin/bitcoin/commit/8f188ece3c82c4cf5d52a3363e7643c23169c0ff Remove -bip16 and -paytoscripthashtime command-line arguments (gavinandresen)]</ref>.

	342ftSRCvFHfCeFFBuz4xwbeqnDw6BGUey is a Bitcoin [[address]] notable for being the first [[P2SH]]-compatible address receiving bitcoins on the production network.		342ftSRCvFHfCeFFBuz4xwbeqnDw6BGUey is a Bitcoin [[address]] notable for being the first [[P2SH]]-compatible address receiving bitcoins on the production network.

Evoskuil: Add history of failed initial activation and update activation date/block to match actual (vs. BIP-indicated) activation. Add discussion on forked rc1 nodes.

2017-12-30T22:39:38Z

Add history of failed initial activation and update activation date/block to match actual (vs. BIP-indicated) activation. Add discussion on forked rc1 nodes.

← Older revision		Revision as of 22:39, 30 December 2017
Line 6:		Line 6:
	\|timeout=2012-02-01 00:00:00		\|timeout=2012-02-01 00:00:00
	\|supermajority=55%		\|supermajority=55%
	\|activated=Block #~~166832~~<br/>2012-02-15 00:00:00 ~~<!-- is this correct? -->~~		\|activated=Block #173805<br/>2012-04-01 00:00:00
	}}'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.		}}'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.

Line 20:		Line 20:

	== History ==		== History ==

			The first activation window failed and another was set to start on 15 March 2012. Users running 0.6.0rc1 who did not upgrade for the delay, activated early and got stuck on block 170,060<ref>[https://bitcointalk.org/index.php?topic=63165.msg788832#msg788832 bitcointalk topic 63165]</ref> when an invalid transaction according to their nodes was mined. After activation problems were then caused by the remaining 45% of miners producing invalid blocks for several months<ref>[https://blog.bitmex.com/bitcoins-consensus-forks/ A Complete History of Bitcoin’s Consensus Forks]</ref>.

	342ftSRCvFHfCeFFBuz4xwbeqnDw6BGUey is a Bitcoin [[address]] notable for being the first [[P2SH]]-compatible address receiving bitcoins on the production network.		342ftSRCvFHfCeFFBuz4xwbeqnDw6BGUey is a Bitcoin [[address]] notable for being the first [[P2SH]]-compatible address receiving bitcoins on the production network.
	Its payment was mined in [[block]] 160720; note that it was spent prior to the enforcement of [[BIP 0016\|BIP 16]], so it's not a good example to understand P2SH.		Its payment was mined in [[block]] 160720; note that it was spent prior to the enforcement of [[BIP 0016\|BIP 16]], so it's not a good example to understand P2SH.

			==References==

Evoskuil: Fixing activation block to match specified activation date.

2017-12-28T13:09:23Z

Fixing activation block to match specified activation date.

← Older revision		Revision as of 13:09, 28 December 2017
Line 6:		Line 6:
	\|timeout=2012-02-01 00:00:00		\|timeout=2012-02-01 00:00:00
	\|supermajority=55%		\|supermajority=55%
	\|activated=Block #~~105571~~<br/>2012-02-15 00:00:00 <!-- is this correct? -->		\|activated=Block #166832<br/>2012-02-15 00:00:00 <!-- is this correct? -->
	}}'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.		}}'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.

Evoskuil: Boxed summary has bip13 reference but should be bip16.

2017-12-03T07:26:51Z

Boxed summary has bip13 reference but should be bip16.

← Older revision		Revision as of 07:26, 3 December 2017
Line 1:		Line 1:
	{{infobox miner activated fork\|title=Pay to Script Hash		{{infobox miner activated fork\|title=Pay to Script Hash
	\|bipnumber=[[~~BIP_0013~~\|BIP 13]]		\|bipnumber=[[BIP_0016\|BIP 16]]
	\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender		\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender
	\|coinbase=/P2SH/		\|coinbase=/P2SH/

Taras at 22:59, 29 November 2017

2017-11-29T22:59:05Z

← Older revision		Revision as of 22:59, 29 November 2017
Line 1:		Line 1:
	'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.		{{infobox miner activated fork\|title=Pay to Script Hash
			\|bipnumber=[[BIP_0013\|BIP 13]]
			\|purpose=Allow the recipient of a transaction to specify the redeem script instead of the sender
			\|coinbase=/P2SH/
			\|starttime=2012-01-25 00:00:00
			\|timeout=2012-02-01 00:00:00
			\|supermajority=55%
			\|activated=Block #105571<br/>2012-02-15 00:00:00 <!-- is this correct? -->
			}}'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.

	Using P2SH, you can send bitcoins to an address that is secured in various unusual ways without knowing anything about the details of how the security is set up. You just send bitcoins to the ~34-character P2SH address. The recipient might need the signatures of several people to spend these bitcoins, or a password might be required, or the requirements could be completely unique.		Using P2SH, you can send bitcoins to an address that is secured in various unusual ways without knowing anything about the details of how the security is set up. You just send bitcoins to the ~34-character P2SH address. The recipient might need the signatures of several people to spend these bitcoins, or a password might be required, or the requirements could be completely unique.

JonathanCross: Linking to address and formatting "3" prefix as code.

2016-01-29T15:34:40Z

Linking to address and formatting "3" prefix as code.

← Older revision		Revision as of 15:34, 29 January 2016
Line 1:		Line 1:
	'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash (~~addresses~~ starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.		'''Pay to script hash''' (P2SH) transactions were standardised in [[BIP 0016\|BIP 16]]. They allow transactions to be sent to a script hash ([[address]] starting with 3) instead of a public key hash (addresses starting with 1). To spend bitcoins sent via P2SH, the recipient must provide a [[script]] matching the script hash and data which makes the script evaluate to true.

	Using P2SH, you can send bitcoins to an address that is secured in various unusual ways without knowing anything about the details of how the security is set up. You just send bitcoins to the ~34-character P2SH address. The recipient might need the signatures of several people to spend these bitcoins, or a password might be required, or the requirements could be completely unique.		Using P2SH, you can send bitcoins to an address that is secured in various unusual ways without knowing anything about the details of how the security is set up. You just send bitcoins to the ~34-character P2SH address. The recipient might need the signatures of several people to spend these bitcoins, or a password might be required, or the requirements could be completely unique.
Line 5:		Line 5:
	== Addresses ==		== Addresses ==

	[[BIP 0013\|BIP 13]] specifies the address format. Bitcoin P2SH addresses always start with 3.		[[BIP 0013\|BIP 13]] specifies the address format. Bitcoin P2SH addresses always start with <code>3</code>.

	== Example ==		== Example ==

Rusty: Save others from trying to understand that non-BIP16 spending script!

2015-05-27T06:35:17Z

Save others from trying to understand that non-BIP16 spending script!

← Older revision		Revision as of 06:35, 27 May 2015
Line 6:		Line 6:

	[[BIP 0013\|BIP 13]] specifies the address format. Bitcoin P2SH addresses always start with 3.		[[BIP 0013\|BIP 13]] specifies the address format. Bitcoin P2SH addresses always start with 3.

			== Example ==

			Transaction 40eee3ae1760e3a8532263678cdf64569e6ad06abc133af64f735e52562bccc8 paid to P2SH address 3P14159f73E4gFr7JterCCQh9QjiTjiZrG. You can see the redeem script in transaction 7edb32d4ffd7a385b763c7a8e56b6358bcd729e747290624e18acdbe6209fc45 which spends that output, using <code>OP_FALSE <sig> { OP_1 <pubkey> OP_1 OP_CHECKMULTISIG }</code>.

	== History ==		== History ==

	342ftSRCvFHfCeFFBuz4xwbeqnDw6BGUey is a Bitcoin [[address]] notable for being the first [[P2SH]]-compatible address receiving bitcoins on the production network.		342ftSRCvFHfCeFFBuz4xwbeqnDw6BGUey is a Bitcoin [[address]] notable for being the first [[P2SH]]-compatible address receiving bitcoins on the production network.
	Its payment was mined in [[block]] 160720.		Its payment was mined in [[block]] 160720; note that it was spent prior to the enforcement of [[BIP 0016\|BIP 16]], so it's not a good example to understand P2SH.