Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_1B159218-1AE8-4151-A0CF-216FC1A082E9";
	protocol="application/pgp-signature"; micalg=pgp-sha256
From: "Dana L. Coe" <dana.coe@bitlox.com>
In-Reply-To: <57B4113E.4010502@jonasschnelli.ch>
Date: Wed, 17 Aug 2016 18:13:29 +0800
Message-Id: <D41B40FA-0C75-496D-937A-0DF733FB87E2@bitlox.com>
References: <57B31EBC.1030806@jonasschnelli.ch>
	<e740b4e0-0597-4f80-2434-70e667b7923c@gmail.com>
	<9c8dd0e5-e333-90c8-965f-10fb29d875a5@thomaskerin.io>
	<57B4113E.4010502@jonasschnelli.ch>
To: Jonas Schnelli <dev@jonasschnelli.ch>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hardware Wallet Standard
Precedence: list


--Apple-Mail=_1B159218-1AE8-4151-A0CF-216FC1A082E9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> On Aug 17, 2016, at 15:24, Jonas Schnelli via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> URI scheme instead of stdio/pipe
> --------------------------------
> The URI scheme is not ugly. Its a modern way =96 implemented in almost =
all
> platforms =96 how applications can interact with each other while not
> directly knowing each other. Registering a URI scheme like =
"bitcoin://"
> has some concrete advantages over just piping through stdio.
>=20
> Also, the stdio/piping approach does not work for mobile platforms
> (where the URI scheme works).
>=20
> The URI scheme does not require any sorts of wallet app level
> configuration (where the stdio/pipe approach would require to =
configure
> some details about the used hardware wallet).

Hi everybody, just thought I=92d throw my opinion in here.

The URI scheme is a nice idea, but this ignores the fact that hardware =
wallet vendors do most of the work on talking between the =
computer/mobile and the wallet on a lower level of communication. In the =
case of BitLox, the base protocol is Google=92s ProtoBuf. The commands =
and transaction data is in a =93schema=94 which is then encoded in =
different methods accessible via ProtoBuf (depending on the data being =
sent). The advantages of this protocol is that it can be implemented on =
a wide variety of platforms. (but that=92s a whole 'nother discussion)

The URI would be handled waaaaay up in the specific application (such as =
the mytrezor wallet software or the various standalone wallets) - =
nowhere near the actual hardware communications layer.

Best regards,
Dana
BitLox

--Apple-Mail=_1B159218-1AE8-4151-A0CF-216FC1A082E9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJXtDjKAAoJEEL86rLDzJPfGxsP/jvzjb4JuykX4wuB2aU2vsBx
mEEDop7N8VgCjuvl3vgdUV6EHdO3i1NqSyE8bUyETfEwPWMqN43YExemh/websSU
hR0AJTDqYgENE9zP4q8iDHK78ZfHfPsgTaRp1P+jjr4IsbK/2sWyijmfb0KBxcOF
pkOKcCuB6qnAbFkqmkl61d7ZHbrAxHsusu8qb50y92q2h0nesKokUQYyyzFWM7hP
UTpD+ll9HIO3+jfaVaW6Bn7cefWp66UbwdqFApCcAK++dZ1HczbYHpcAUCM3BFxw
y5I8DGSlYyzXOdza5qUkcXZta0WxQWIAWYT3uGy/l8p/ewuRaXa5fy16NdoO9wIH
CpPjk4l3Kds0ZnlETYDfeuqNb/z1PZRHzBF6KmFuzmXm+vWLelCRyXzALBfPWDLv
cAYTaSzrxOfWVu3UejiUK5n0/YXNhAuS4Q2vuPh7j1+6hoOaxY9TZoJXktzgNfIO
HDENGibKsIi7D07oXkuZoziA3NlhQ0GdRNNwaZhabel9SaD0IsvcnsDHA+ELHTT/
s2KXMc5EDBI5W4sqqTGQOxA9vKLQvZ9VtnNuUuzaaWsw0r9aBrZ3E22n4sWTPJTS
6E/6Bw2PcMMzCzOQHoXfxaP8BFynoJzg00grC68KzaL0o1Z8v0DT6lrDESD+r95j
GvhYoH9pVPriiifKpEFC
=XNcu
-----END PGP SIGNATURE-----

--Apple-Mail=_1B159218-1AE8-4151-A0CF-216FC1A082E9--