BIP 0011 - Revision history

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/6545b81022212a9f/bip-0011.mediawiki

2022-10-01T00:29:16Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/6545b81022212a9f/bip-0011.mediawiki

← Older revision		Revision as of 00:29, 1 October 2022
Line 58:		Line 58:
	OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.		OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.

	https://github.com/gavinandresen/bitcoin-git/tree/~~op_eval~~		https://github.com/gavinandresen/bitcoin-git/tree/77f21f1583deb89bf3fffe80fe9b181fedb1dd60

	== Post History ==		== Post History ==

	* [https://bitcointalk.org/index.php?topic=46538 OP_EVAL proposal]		* [https://bitcointalk.org/index.php?topic=46538 OP_EVAL proposal]

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/c134a853a9fc0657/bip-0011.mediawiki

2020-08-02T07:57:05Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/c134a853a9fc0657/bip-0011.mediawiki

← Older revision		Revision as of 07:57, 2 August 2020
Line 27:		Line 27:
	* A wallet secured by a "wallet protection service" (WPS). 2-of-2 signatures required transactions will be used, with one signature coming from the (possibly compromised) computer with the wallet and the second signature coming from the WPS. When sending protected bitcoins, the user's bitcoin client will contact the WPS with the proposed transaction and it can then contact the user for confirmation that they initiated the transaction and that the transaction details are correct. Details for how clients and WPS's communicate are outside the scope of this BIP. Side note: customers should insist that their wallet protection service provide them with copies of the private key(s) used to secure their wallets that they can safely store off-line, so that their coins can be spent even if the WPS goes out of business.		* A wallet secured by a "wallet protection service" (WPS). 2-of-2 signatures required transactions will be used, with one signature coming from the (possibly compromised) computer with the wallet and the second signature coming from the WPS. When sending protected bitcoins, the user's bitcoin client will contact the WPS with the proposed transaction and it can then contact the user for confirmation that they initiated the transaction and that the transaction details are correct. Details for how clients and WPS's communicate are outside the scope of this BIP. Side note: customers should insist that their wallet protection service provide them with copies of the private key(s) used to secure their wallets that they can safely store off-line, so that their coins can be spent even if the WPS goes out of business.

	* Three-party escrow (buyer, seller and trusted dispute agent). 2-of-3 signatures required transactions will be used. The buyer and seller and agent will each provide a public key, and the buyer will then send coins into a 2-of-3 CHECKMULTISIG transaction and send the seller and the agent the transaction id. The seller will fulfill their obligation and then ask the buyer to co-sign a transaction ( already signed by seller ) that sends the tied-up coins to him (seller).<br />If the buyer and seller cannot agree, then the agent can, with the cooperation of either buyer or seller, decide what happens to the tied-up coins. Details of how buyer, seller, and agent communicate to gather signatures or public keys are outside the scope of this BIP.		* Three-party escrow (buyer, seller, and trusted dispute agent). 2-of-3 signatures required transactions will be used. The buyer and seller and agent will each provide a public key, and the buyer will then send coins into a 2-of-3 CHECKMULTISIG transaction and send the seller and the agent the transaction id. The seller will fulfill their obligation and then ask the buyer to co-sign a transaction ( already signed by seller ) that sends the tied-up coins to him (seller).<br />If the buyer and seller cannot agree, then the agent can, with the cooperation of either buyer or seller, decide what happens to the tied-up coins. Details of how buyer, seller, and agent communicate to gather signatures or public keys are outside the scope of this BIP.

	==Specification==		==Specification==

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0011.mediawiki

2019-09-24T18:00:25Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0011.mediawiki

@@ Line 1: / Line 1: @@
 {{bip}}
-{{BipMoved|bip-0011.mediawiki}}
+==Motivation==
-==History==
+==Implementation==
-{{infobox BIP
+OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.
-==References==
+* [https://bitcointalk.org/index.php?topic=46538 OP_EVAL proposal]

934: Subsection ==History==

2015-12-29T11:50:08Z

Subsection ==History==

@@ Line 1: / Line 1: @@
 {{infobox BIP
 |name=BIP 0011
@@ Line 11: / Line 17: @@
 |closure=December 13, 2011
 }}'''BIP 0011''' was the first standard [[Bitcoin Improvement Proposal]], authored by [[Gavin Andresen]] after being described by [[ByteCoin]] on [[BitcoinTalk]] two weeks earlier.<ref name="op_eval">{{cite btct|id=46538|title=OP_EVAL proposal|date=2011-10-02}}</ref> ByteCoin had referenced an earlier thread by [[Casascius|Mike Caldwell]], which proposed modifying [[OP_CHECKSIG]] for [[multisignature]] transactions.<ref>{{cite btct|id=45211|title=Proposal to modify OP_CHECKSIG|date=2011-09-22}}</ref>
 ==References==
 <references/>

Taras at 19:01, 14 March 2015

2015-03-14T19:01:45Z

← Older revision		Revision as of 19:01, 14 March 2015
Line 10:		Line 10:
	\|finalized=December 13, 2011		\|finalized=December 13, 2011
	\|closure=December 13, 2011		\|closure=December 13, 2011
	}}'''BIP 0011''' was the first [[Bitcoin Improvement Proposal]], authored by [[Gavin Andresen]] after being described by [[ByteCoin]] on [[BitcoinTalk]] two weeks earlier.<ref>{{cite btct\|id=46538\|title=OP_EVAL proposal\|date=2011-10-02}}</ref>		}}'''BIP 0011''' was the first standard [[Bitcoin Improvement Proposal]], authored by [[Gavin Andresen]] after being described by [[ByteCoin]] on [[BitcoinTalk]] two weeks earlier.<ref name="op_eval">{{cite btct\|id=46538\|title=OP_EVAL proposal\|date=2011-10-02}}</ref> ByteCoin had referenced an earlier thread by [[Casascius\|Mike Caldwell]], which proposed modifying [[OP_CHECKSIG]] for [[multisignature]] transactions.<ref>{{cite btct\|id=45211\|title=Proposal to modify OP_CHECKSIG\|date=2011-09-22}}</ref>
	{{BIP begin}}		{{BIP begin}}
	==Abstract==		==Abstract==

Taras at 18:56, 14 March 2015

2015-03-14T18:56:42Z

← Older revision		Revision as of 18:56, 14 March 2015
Line 10:		Line 10:
	\|finalized=December 13, 2011		\|finalized=December 13, 2011
	\|closure=December 13, 2011		\|closure=December 13, 2011
	}}'''BIP 0011''' was the first [[Bitcoin Improvement Proposal]], authored by [[Gavin Andresen]].		}}'''BIP 0011''' was the first [[Bitcoin Improvement Proposal]], authored by [[Gavin Andresen]] after being described by [[ByteCoin]] on [[BitcoinTalk]] two weeks earlier.<ref>{{cite btct\|id=46538\|title=OP_EVAL proposal\|date=2011-10-02}}</ref>
	~~__NOTOC__~~{{BIP begin}}		{{BIP begin}}
	==Abstract==		==Abstract==

Line 55:		Line 55:
	OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.		OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.
	{{end}}		{{end}}
	~~[[Category:BIP\|C]]~~
			==References==
			<references/>

Taras at 18:48, 14 March 2015

2015-03-14T18:48:46Z

← Older revision		Revision as of 18:48, 14 March 2015
Line 1:		Line 1:
	~~{{bip}}~~{{infobox BIP		{{infobox BIP
	\|name=BIP 0011		\|name=BIP 0011
	\|longtitle=M-of-N Standard Transactions		\|longtitle=M-of-N Standard Transactions
Line 10:		Line 10:
	\|finalized=December 13, 2011		\|finalized=December 13, 2011
	\|closure=December 13, 2011		\|closure=December 13, 2011
	}}		}}'''BIP 0011''' was the first [[Bitcoin Improvement Proposal]], authored by [[Gavin Andresen]].
	{{~~BipMoved\|bip-0011.mediawiki\|~~BIP ~~0011~~}}		__NOTOC__{{BIP begin}}
	~~=Text=~~
	==Abstract==		==Abstract==

Line 55:		Line 54:

	OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.		OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.
			{{end}}
	[[Category:BIP\|C]]		[[Category:BIP\|C]]

Taras at 18:38, 14 March 2015

2015-03-14T18:38:25Z

@@ Line 1: / Line 1: @@
-{{bip}}
+{{bip}}{{infobox BIP
-<pre>
+One argument against using OP_CHECKMULTISIG is that old clients and miners count it as "20 sigops" for purposes of computing how many signature operations are in a block, and there is a hard limit of 20,000 sigops per block-- meaning a maximum of 1,000 multisig transactions per block. Creating multisig transactions using multiple OP_CHECKSIG operations allows more of them per block.
-{{BipMoved|bip-0011.mediawiki|BIP 0011}}
+The counter-argument is that these new multi-signature transactions will be used in combination with OP_EVAL (see the OP_EVAL BIP), and '''will''' be counted accurately. And in any case, as transaction volume rises the hard-coded maximum block size will have to be addressed, and the rules for counting number-of-signature-operations-in-a-block can be addressed at that time.
 [[Category:BIP|C]]

Wumpus: Github move

2013-12-06T07:38:35Z

Github move

@@ Line 11: / Line 11: @@
 </pre>
-==Abstract==
+{{BipMoved|bip-0011.mediawiki|BIP 0011}}
 [[Category:BIP|C]]

Nanotube: Removed protection from "BIP 0011"

2013-01-18T14:58:45Z

Removed protection from "BIP 0011"

← Older revision		Revision as of 14:58, 18 January 2013
(No difference)