MIME-Version: 1.0
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
In-Reply-To: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
From: James MacWhyte <macwhyte@gmail.com>
Date: Tue, 21 Jun 2016 20:56:40 +0000
Message-ID: <CAH+Axy7OtGgbtmz+grfuob419PwQJiYfZsQnMEs=_McZFBqu2A@mail.gmail.com>
To: Erik Aronesty <erik@q32.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114fac884e92490535d00ff5
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
Precedence: list

--001a114fac884e92490535d00ff5
Content-Type: text/plain; charset=UTF-8

Thanks for starting this discussion, Erik.


> Should this be a new BIP?  I know netki's BIP75 is out there - but I think
> it's too specific and too reliant on the domain name system.
>

This is not quite accurate. BIP75 is designed to be independent of any name
resolution system. You could use it with a static URL that you share, for
example, or even use it to implement a mesh-network payment system over
bluetooth. Netki's wallet names do use DNS, but that isn't related to this
discussion.

What BIP75 *does* do is provide a way for a client to get a new payment
address for every payment. I personally think it is better than BIP47 for
the uses you mentioned (subscriptions, etc).

I'm glad you brought up identity methods other than x509. At breadwallet we
are thinking about how to establish the most universal system, and letting
users identify themselves with any of a selection of identity systems is
ideal. I think the pki_data slot should be constantly expanded to allow new
identity types, but they should be explained/standardized in the BIPs that
add them and use universal names. "netki://" wouldn't be appropriate, for
example, if their method is open sourced and possibly used by others--it
should instead be given a product name like "dnswallet://" or something
more clever.

James

--001a114fac884e92490535d00ff5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for starting this discussion, Erik.<br><br><div><di=
v class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><di=
v><br></div><div>Should this be a new BIP?=C2=A0 I know netki&#39;s BIP75 i=
s out there - but I think it&#39;s too specific and too reliant on the doma=
in name system.<br></div></div></blockquote><div>=C2=A0</div><div><font col=
or=3D"#212121" face=3D"helvetica neue, helvetica, arial, sans-serif">This i=
s not quite accurate. BIP75 is designed to be independent of any name resol=
ution system. You could use it with a static URL that you share, for exampl=
e, or even use it to implement a mesh-network payment system over bluetooth=
. Netki&#39;s wallet names do use DNS, but that isn&#39;t related to this d=
iscussion.</font></div><div><font color=3D"#212121" face=3D"helvetica neue,=
 helvetica, arial, sans-serif"><br></font></div><div><font color=3D"#212121=
" face=3D"helvetica neue, helvetica, arial, sans-serif">What BIP75 *does* d=
o is provide a way for a client to get a new payment address for every paym=
ent. I personally think it is better than BIP47 for the uses you mentioned =
(subscriptions, etc).</font></div><br class=3D"inbox-inbox-Apple-interchang=
e-newline"><div>I&#39;m glad you brought up identity methods other than x50=
9. At breadwallet we are thinking about how to establish the most universal=
 system, and letting users identify themselves with any of a selection of i=
dentity systems is ideal. I think the pki_data slot should be constantly ex=
panded to allow new identity types, but they should be explained/standardiz=
ed in the BIPs that add them and use universal names. &quot;<span style=3D"=
line-height:1.5">netki://&quot; wouldn&#39;t be appropriate, for example, i=
f their method is open sourced and possibly used by others--it should inste=
ad be given a product name like &quot;dnswallet://&quot; or something more =
clever.<br><br>James<br><br><br></span></div></div></div></div>

--001a114fac884e92490535d00ff5--