Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VAK5o-0007BI-8j for bitcoin-development@lists.sourceforge.net; Fri, 16 Aug 2013 13:29:28 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.161 as permitted sender) client-ip=62.13.148.161; envelope-from=pete@petertodd.org; helo=outmail148161.authsmtp.com; Received: from outmail148161.authsmtp.com ([62.13.148.161]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1VAK5m-0001KG-A7 for bitcoin-development@lists.sourceforge.net; Fri, 16 Aug 2013 13:29:28 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt6.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id r7GDTIhN038768; Fri, 16 Aug 2013 14:29:18 +0100 (BST) Received: from petertodd.org (petertodd.org [174.129.28.249]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r7GDTBHT031305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 16 Aug 2013 14:29:15 +0100 (BST) Date: Fri, 16 Aug 2013 09:29:11 -0400 From: Peter Todd To: Mike Hearn Message-ID: <20130816132911.GA16201@petertodd.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: d88c3b96-0677-11e3-b5c5-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdwQUGUATAgsB AmUbWlBeUlR7WGY7 ag1VcwRfa1RMVxto VEFWR1pVCwQmQxt2 cnpsKn1ydARFeHs+ bUdkVj4PVEwpdhR0 RFNUE2oBeGZhPWMC AkULch5UcAFPdx8U a1UrBXRDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4hPwZ0 HEpEQF0A X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 174.129.28.249/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1VAK5m-0001KG-A7 Cc: Bitcoin Development Subject: Re: [Bitcoin-development] BIP 32.5 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Aug 2013 13:29:28 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 16, 2013 at 01:32:39PM +0200, Mike Hearn wrote: > and analysing it is really hard (plus it inverts the threat model - if you > trust your computer and not your hardware wallet, why do you have a > hardware wallet?) Myself I would trust neither the hardware wallet nor my computer... So looks like the first version of the TREZOR won't support multisig - how far away are we from support? What about other manufacturers? P2SH support is probably going to be a major sticking point. The payment protocol is all well and good, but it doesn't (yet) help getting money to the individual. bitcoinj P2SH support for sending would be a major help here - lots of person-to-person trades happen via Android wallets. --=20 'peter'[:-1]@petertodd.org 000000000000000b9656276a0fdab028ca759c3fd7f951fb20196c264b5cd1ce --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlIOKScACgkQpEFN739thozoVwCggdl5/JlBAc/p5JIzst/CVHHU ZiEAnRzitO/yC/eaFOd+we8iqrMJar54 =x1eb -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv--