M of 2 DRAFT - Revision history

Giszmo: Added to category BIP

2012-01-29T18:22:29Z

Added to category BIP

← Older revision		Revision as of 18:22, 29 January 2012
Line 133:		Line 133:
	* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]		* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]

	[[Category:BIP\|~~Draft~~]]		[[Category:BIP\|D]]

2012-01-29T18:17:42Z

Added to category BIP

← Older revision		Revision as of 18:17, 29 January 2012
Line 132:		Line 132:
	* The [[BIP 0013\|Address format for Pay to Script Hash BIP]]		* The [[BIP 0013\|Address format for Pay to Script Hash BIP]]
	* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]		* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]

			[[Category:BIP\|Draft]]

2012-01-16T16:14:20Z

← Older revision		Revision as of 16:14, 16 January 2012
(No difference)

2012-01-16T15:47:53Z

2012-01-16T15:43:39Z

Security

← Older revision		Revision as of 15:43, 16 January 2012
Line 73:		Line 73:
	==Security==		==Security==

	Although it may appear insecure totalling the sum of the public keys this ~~is not actually~~ the case.		Although it may appear insecure totalling the sum of the public keys the author does not believe this to be the case.

	You could deduce the target value by looking at the the sum of M + pubKey1 + pubKey2 + N from a previous transaction.		You could deduce the target value by looking at the the sum of M + pubKey1 + pubKey2 + N from a previous transaction.

2012-01-16T15:42:27Z

Security

← Older revision		Revision as of 15:42, 16 January 2012
Line 102:		Line 102:
	Resulting in equal brute force time.		Resulting in equal brute force time.

	What does affect security is ability to adjust M (either 1 or 2) without needing to generate a new SHA256 pair. This effectively halves the key space to 2^255 keys however it is still far far out of the realm of brute force possibility. Regardless use of a 20 byte hash limits the key space ~~size~~ to 2^160 so it actually has no effect on security at all.		What does affect security is ability to adjust M (either 1 or 2) without needing to generate a new SHA256 pair. This effectively halves the key space to 2^255 keys however it is still far far out of the realm of brute force possibility. Regardless use of a 20 byte hash limits the key space to 2^160 so it actually has no effect on security at all.

	==Rationale==		==Rationale==

2012-01-16T15:36:05Z

Security

← Older revision		Revision as of 15:36, 16 January 2012
Line 88:		Line 88:

	<pre>		<pre>
	while(m + myKeyA + myBogusKeyB + n != ~~targetScriptHash~~) {		while(m + myKeyA + myBogusKeyB + n != target) {
	++myBogusKeyB;		++myBogusKeyB;
	}</pre>		}</pre>
Line 96:		Line 96:
	<pre>		<pre>
	myKeyA = SHA256(myKeyA);		myKeyA = SHA256(myKeyA);
	while(m + myKeyA + SHA256(myBogusKeyB + n) != ~~targetScriptHash~~) {		while(m + myKeyA + SHA256(myBogusKeyB + n) != target) {
	++myBogusKeyB;		++myBogusKeyB;
	}</pre>		}</pre>

2012-01-16T15:35:51Z

Security

← Older revision		Revision as of 15:35, 16 January 2012
Line 96:		Line 96:
	<pre>		<pre>
	myKeyA = SHA256(myKeyA);		myKeyA = SHA256(myKeyA);
	while(m + myKeyA + SHA256(myBogusKeyB) + n != targetScriptHash) {		while(m + myKeyA + SHA256(myBogusKeyB + n) != targetScriptHash) {
	++myBogusKeyB;		++myBogusKeyB;
	}</pre>		}</pre>

2012-01-16T15:34:20Z

Security

← Older revision		Revision as of 15:34, 16 January 2012
Line 78:		Line 78:

	<pre>		<pre>
	uint256 target = Previously Redeemed (m+p1+p2+n)		uint256 target = Previously Redeemed M+P1+P2+N
	uint256 myKeyA = SHA256();		uint256 myKeyA = SHA256();
	uint256 myBogusKeyB = 0;		uint256 myBogusKeyB = 0;

2012-01-16T15:33:49Z

Security

← Older revision		Revision as of 15:33, 16 January 2012
Line 78:		Line 78:

	<pre>		<pre>
	uint256 target = Previously Redeemed ~~Tx Target;~~		uint256 target = Previously Redeemed (m+p1+p2+n)
	uint256 myKeyA = SHA256();		uint256 myKeyA = SHA256();
	uint256 myBogusKeyB = 0;		uint256 myBogusKeyB = 0;

← Older revision		Revision as of 18:17, 29 January 2012
Line 132:		Line 132:
	* The [[BIP 0013\|Address format for Pay to Script Hash BIP]]		* The [[BIP 0013\|Address format for Pay to Script Hash BIP]]
	* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]		* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]

			[[Category:BIP\|Draft]]

← Older revision		Revision as of 15:47, 16 January 2012
Line 130:		Line 130:
	==See Also==		==See Also==

	* https://bitcointalk.org/index.php?topic=46538
	* The [[BIP 0013\|Address format for Pay to Script Hash BIP]]		* The [[BIP 0013\|Address format for Pay to Script Hash BIP]]
	* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]		* M-of-N Multisignature Transactions [[BIP 0011\|BIP 11]]