BIP 0012 - Revision history

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

2023-12-26T19:52:57Z

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

← Older revision		Revision as of 19:52, 26 December 2023
Line 47:		Line 47:
	If ''serialized script'' is a large or complicated multi-signature script, then the burden of paying for it (in increased transaction fees due to more signature operations or transaction size) is shifted from the sender to the receiver.		If ''serialized script'' is a large or complicated multi-signature script, then the burden of paying for it (in increased transaction fees due to more signature operations or transaction size) is shifted from the sender to the receiver.

	The main objection to OP_EVAL is that it adds complexity, and complexity is the enemy of security. Also, evaluating data as code has a long record of being a source of security ~~vulnerabilties~~.		The main objection to OP_EVAL is that it adds complexity, and complexity is the enemy of security. Also, evaluating data as code has a long record of being a source of security vulnerabilities.

	That same argument can be applied to the existing Bitcoin 'scripting' system; scriptPubKeys are transmit as data across the network and are then interpreted by every bitcoin implementation. OP_EVAL just moves the data that will be interpreted. It is debatable whether or not the entire idea of putting a little interpreted expression evaluation language at the core of Bitcoin was brilliant or stupid, but the existence of OP_EVAL does not make the expression language less secure.		That same argument can be applied to the existing Bitcoin 'scripting' system; scriptPubKeys are transmit as data across the network and are then interpreted by every bitcoin implementation. OP_EVAL just moves the data that will be interpreted. It is debatable whether or not the entire idea of putting a little interpreted expression evaluation language at the core of Bitcoin was brilliant or stupid, but the existence of OP_EVAL does not make the expression language less secure.

	There is a 1-confirmation attack on old clients that ~~interepret~~ OP_EVAL as a no-op, but it is expensive and difficult in practice. The attack is:		There is a 1-confirmation attack on old clients that interpret OP_EVAL as a no-op, but it is expensive and difficult in practice. The attack is:

	# Attacker creates an OP_EVAL transaction that is valid as seen by old clients, but invalid for new clients.		# Attacker creates an OP_EVAL transaction that is valid as seen by old clients, but invalid for new clients.

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

2022-10-01T00:35:32Z

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

← Older revision		Revision as of 00:35, 1 October 2022
Line 79:		Line 79:
	==Reference Implementation==		==Reference Implementation==

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

	==See Also==		==See Also==

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

2019-09-24T18:00:22Z

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

@@ Line 1: / Line 1: @@
 {{bip}}
 <pre>
    BIP: 12
    Title: OP_EVAL
    Author: Gavin Andresen <gavinandresen@gmail.com>
    Status: Withdrawn
    Type: Standards Track
-   Created: 18-10-2011
+   Created: 2011-10-18
 </pre>
-{{BipMoved|bip-0012.mediawiki}}
+==Abstract==
-[[Category:BIP|W]]
+M-of-N Multisignature Transactions BIP 11

934: Removing redundant parameter.

2015-12-29T13:43:20Z

Removing redundant parameter.

← Older revision		Revision as of 13:43, 29 December 2015
Line 10:		Line 10:
	</pre>		</pre>

	{{BipMoved\|bip-0012.mediawiki~~\|BIP 0012~~}}		{{BipMoved\|bip-0012.mediawiki}}

	[[Category:BIP\|W]]		[[Category:BIP\|W]]

Wumpus: Github move

2013-12-06T07:39:35Z

Github move

@@ Line 10: / Line 10: @@
 </pre>
-==Abstract==
+{{BipMoved|bip-0012.mediawiki|BIP 0012}}
 [[Category:BIP|W]]

Nanotube: Removed protection from "BIP 0012"

2013-01-18T14:57:33Z

Removed protection from "BIP 0012"

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

Genjix at 17:12, 16 April 2012

2012-04-16T17:12:06Z

← Older revision		Revision as of 17:12, 16 April 2012
Line 1:		Line 1:
			{{bip}}

	<pre>		<pre>
	BIP: 12		BIP: 12

Genjix: Protected "BIP 0012": submit bips to genjix ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2012-01-31T21:38:17Z

Protected "BIP 0012": submit bips to genjix ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision		Revision as of 21:38, 31 January 2012
(No difference)

Giszmo: Added to category BIP

2012-01-29T18:21:54Z

Added to category BIP

← Older revision		Revision as of 18:21, 29 January 2012
Line 83:		Line 83:
	M-of-N Multisignature Transactions BIP 11		M-of-N Multisignature Transactions BIP 11

	[[Category:BIP]]		[[Category:BIP\|W]]

Giszmo: Added to category BIP

2012-01-29T18:15:06Z

Added to category BIP

← Older revision		Revision as of 18:15, 29 January 2012
Line 82:		Line 82:

	M-of-N Multisignature Transactions BIP 11		M-of-N Multisignature Transactions BIP 11

			[[Category:BIP]]