{"type":"rich","version":"1.0","title":"Peter D. Gray [ARCHIVE] wrote","author_name":"Peter D. Gray [ARCHIVE] (npub10v…t058y)","author_url":"https://yabu.me/npub10vqyu8x3f0lfttk98xc28ppuyufaz4df8x4aspa9w9xz5z05snzq7t058y","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2018-06-21\n📝 Original message:On Tue, Jun 19, 2018 at 05:20:34PM +0200, Jonas Schnelli wrote:\n...\n\u003e \n\u003e I don’t see any reasons why space would be an issue.\n\u003e \n\u003e HWWs probably can’t handle PBST natively since it is not optimised for\n\u003e presenting various informations in a signing-verification.\n\nThe Coldcard hardware wallet is PSBT native and does work directly from PSBT.\n\n\u003e A single stream-in of a PSBT through USB (or similar channel) will not work in\n\u003e many cases since HWW come often with very restrictive RAM constraints.\n\nFor the Coldcard, we expect a PSBT to be 'uploaded' over USB (can\nalso be provided on MicroSD card) and we work in-place with it,\nscanning over it a few different times. If the user approves the\ntransaction, we produce a signed PSBT or final transaction and that\ngets downloaded.\n\nWe support 256k byte PSBT files with hundreds of inputs/outputs\n(IIRC, and exact limits still TBD) and are operating in a system\nwith only 25k free RAM after startup.\n\n\u003e Furthermore, I forget to mention in my last mail, that registering (or defining)\n\u003e a mime-type for PSBT would probably a great usability feature.\n\u003e (Send PSBT by email/messanger and with dbl-click to open feature, etc.)\n\n+1 for mimetype, especially since it's a binary format.\n\n---\nPeter D. Gray  ||  Founder, Coinkite  ||  Twitter: @dochex  ||  GPG: A3A31BAD 5A2A5B10\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 496 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180621/be77e362/attachment.sig\u003e"}