Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.172 as permitted sender)
	client-ip=209.85.214.172; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f172.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <C95DB811-9E6A-4EA2-AE8F-83595C3AC817@gmail.com>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
	<CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>
	<CANEZrP06gk-JhKaNpvYUTfjFq9AGnCay9=pjUGpVMjMSuX3_ew@mail.gmail.com>
	<CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
	<6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com>
	<CAJHLa0PYfuJg3daPvzPFZpFz7ezH2RHpJ8zyz2g1NDKppM7rWA@mail.gmail.com>
	<BBF86C9B-6B3D-4A03-AC7B-35619C47091F@gmail.com>
	<CABsx9T13yksenx5aYd4HVqTyVjARx9aTHy=Neu64p6k9FnRRVw@mail.gmail.com>
	<C95DB811-9E6A-4EA2-AE8F-83595C3AC817@gmail.com>
Date: Wed, 25 Jun 2014 10:25:43 +0200
Message-ID: <CANEZrP0ce4MMX2hOhcGVWt23L_CMn6Cmj9_Okqd0BR9seQXJew@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gmail <will.yager@gmail.com>
Content-Type: multipart/alternative; boundary=001a11330d028b3e7104fca4d26a
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Precedence: list

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

>
> I agree. It would be even sillier to start specifying container formats
> for random one-off "that would be kind of nice, I guess" features.
>

No, it'd be sensible.

Here's a list I drew up a long time ago of features I imagined adding to
the payment protocol:

https://bitcointalk.org/index.php?topic=270055.msg2890147#msg2890147

The protocol is there to contain features! There is zero benefit to
slavishly following some religious notion of purity or minimalism here. The
shared resource in question is just varint encoded integers. So, we should
be guided by what will help our users and what will help adoption.

Anyway, Gavin asked me to start handling more BIP 70 stuff a few weeks ago.
I want to use something simple to set up the extensions process more
formally. IMO we need a "living document" version of the payment protocol
with all the different extensions out there folded into it, to simplify
programming tasks and ensure field numbers don't collide.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
<div class=3D"">I agree. It would be even sillier to start specifying conta=
iner formats for random one-off &quot;that would be kind of nice, I guess&q=
uot; features.</div></blockquote><div><br></div><div>No, it&#39;d be sensib=
le.</div>
<div><br></div><div>Here&#39;s a list I drew up a long time ago of features=
 I imagined adding to the payment protocol:</div><div><br></div><div><a hre=
f=3D"https://bitcointalk.org/index.php?topic=3D270055.msg2890147#msg2890147=
">https://bitcointalk.org/index.php?topic=3D270055.msg2890147#msg2890147</a=
></div>
<div><br></div><div>The protocol is there to contain features! There is zer=
o benefit to slavishly following some religious notion of purity or minimal=
ism here. The shared resource in question is just varint encoded integers. =
So, we should be guided by what will help our users and what will help adop=
tion.</div>
<div><br></div><div>Anyway, Gavin asked me to start handling more BIP 70 st=
uff a few weeks ago. I want to use something simple to set up the extension=
s process more formally. IMO we need a &quot;living document&quot; version =
of the payment protocol with all the different extensions out there folded =
into it, to simplify programming tasks and ensure field numbers don&#39;t c=
ollide.</div>
</div></div></div>

--001a11330d028b3e7104fca4d26a--