Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AD023DB7 for ; Thu, 21 Jun 2018 20:28:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp105.ord1c.emailsrvr.com (smtp105.ord1c.emailsrvr.com [108.166.43.105]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 56DF2334 for ; Thu, 21 Jun 2018 20:28:17 +0000 (UTC) Received: from smtp6.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id AECD8A0293; Thu, 21 Jun 2018 16:28:16 -0400 (EDT) X-Auth-ID: peter@coinkite.com Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: peter-AT-coinkite.com) with ESMTPSA id 66757A0290; Thu, 21 Jun 2018 16:28:16 -0400 (EDT) X-Sender-Id: peter@coinkite.com Received: from coinkite.com ([UNAVAILABLE]. [216.223.137.93]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:465 (trex/5.7.12); Thu, 21 Jun 2018 16:28:16 -0400 Date: Thu, 21 Jun 2018 16:28:15 -0400 From: "Peter D. Gray" To: Jonas Schnelli Message-ID: <20180621202814.GE99379@coinkite.com> Reply-To: Peter Gray References: <5b6b9d44-8e6c-2799-438e-d311e221bb57@satoshilabs.com> <8CF4BD50-0ECE-4F96-B978-397116CD76CE@jonasschnelli.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HeFlAV5LIbMFYYuh" Content-Disposition: inline In-Reply-To: <8CF4BD50-0ECE-4F96-B978-397116CD76CE@jonasschnelli.ch> Organization: Coinkite Cryptobank (www.coinkite.com) User-Agent: Mutt/1.6.0 (2016-04-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 21 Jun 2018 20:29:04 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] BIP 174 thoughts X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 20:28:17 -0000 --HeFlAV5LIbMFYYuh Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 19, 2018 at 05:20:34PM +0200, Jonas Schnelli wrote: =2E.. >=20 > I don=E2=80=99t see any reasons why space would be an issue. >=20 > HWWs probably can=E2=80=99t handle PBST natively since it is not optimise= d for > presenting various informations in a signing-verification. The Coldcard hardware wallet is PSBT native and does work directly from PSB= T. > A single stream-in of a PSBT through USB (or similar channel) will not wo= rk in > many cases since HWW come often with very restrictive RAM constraints. For the Coldcard, we expect a PSBT to be 'uploaded' over USB (can also be provided on MicroSD card) and we work in-place with it, scanning over it a few different times. If the user approves the transaction, we produce a signed PSBT or final transaction and that gets downloaded. We support 256k byte PSBT files with hundreds of inputs/outputs (IIRC, and exact limits still TBD) and are operating in a system with only 25k free RAM after startup. > Furthermore, I forget to mention in my last mail, that registering (or de= fining) > a mime-type for PSBT would probably a great usability feature. > (Send PSBT by email/messanger and with dbl-click to open feature, etc.) +1 for mimetype, especially since it's a binary format. --- Peter D. Gray || Founder, Coinkite || Twitter: @dochex || GPG: A3A31B= AD 5A2A5B10 --HeFlAV5LIbMFYYuh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJbLApeAAoJEKOjG61aKlsQl+MH/25njF1nMNH8/nF5Vn9/N5KA 5aKC+QPh3m0mM01uYUvsmM2wlDlZtDkCMowus1cqeqPXu+xyFBnESvHlpI8hjm5k nJsaz6Dd6zXC1xoxAq9aLcF7O9ntJxCAzSOAMFDbubwf11ixFBPefXoV4OeUARB0 D5mhvb6MNmXl2ZCarLlFJ2VIlIPdHhjyBbdB2STu1CaRynJZmuIF6Dia2M1MlSsH bw8kvo6BEgyxeyX0HiyGeuUBtZbpbVf4ZL6AHdN76P1wfQlgkcLVYVgVx7VoVpBC C5jgbcRLNPKH5M0SI1xUvYttqFnXP9aLAfpKtT2UackmGKFe8zvdW2cyi+s5y8w= =IHUQ -----END PGP SIGNATURE----- --HeFlAV5LIbMFYYuh--