Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.169 as permitted sender)
	client-ip=209.85.216.169; envelope-from=brian.erdelyi@gmail.com;
	helo=mail-qc0-f169.google.com; 
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Brian Erdelyi <brian.erdelyi@gmail.com>
In-Reply-To: <54CE3816.6020505@bitwatch.co>
Date: Mon, 2 Feb 2015 13:40:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com>
References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com>
	<54CE3816.6020505@bitwatch.co>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal to address Bitcoin malware
Precedence: list

Another concept...

It should be possible to use multisig wallets to protect against =
malware.  For example, a user could generate a wallet with 3 keys and =
require a transaction that has been signed by 2 of those keys.  One key =
is placed in cold storage and anther sent to a third-party.

It is now possible to generate and sign transactions on the users =
computer and send this signed transaction to the third-party for the =
second signature.  This now permits the use of out of band transaction =
verification techniques before the third party signs the transaction and =
sends to the blockchain.

If the third-party is malicious or becomes compromised they would not =
have the ability to complete transactions as they only have one private =
key.  If the third-party disappeared, the user could use the key in cold =
storage to sign transactions and send funds to a new wallet.

Thoughts?=