Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.48 as permitted sender)
	client-ip=209.85.216.48; envelope-from=brian.erdelyi@gmail.com;
	helo=mail-qa0-f48.google.com; 
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Brian Erdelyi <brian.erdelyi@gmail.com>
In-Reply-To: <CAFVoEQQHVcY0Ad-4c2wnH+WF_7M-o5SNwVr-nce_9bQ794cwDQ@mail.gmail.com>
Date: Tue, 3 Feb 2015 16:09:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5F8FC20-C6E9-4C42-A5C5-24B337EE7F95@gmail.com>
References: <etPan.54d0b945.46e87ccd.7f23@Williams-MBP>
	<CAFVoEQQHVcY0Ad-4c2wnH+WF_7M-o5SNwVr-nce_9bQ794cwDQ@mail.gmail.com>
To: Adam Weiss <adam@signal11.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin
	malware
Precedence: list


> Regardless, I think a standard for passing partially signed =
transactions around might make sense (maybe a future extension to =
BIP70), with attention to both PC <-> small hardware devices and pushing =
stuff around on the Internet.  It would be great if users had a choice =
of hardware signing devices, local software and third-party cosigning =
services that would all interoperate out of the box to enable easy =
multisig security, which in the BTC world subsumes the goals of 2FA.

I think a standard for passing partially signed transactions is a great =
idea as well.  This would support interoperability of wallets/clients =
and third-party services (if users choose to use them).

Brian Erdelyi=