Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.46 as permitted sender)
	client-ip=209.85.219.46; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f46.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <48ED312A-A1F9-4081-9718-04DD45804313@bitsofproof.com>
References: <CANEZrP0AwR3WgHfwYWcrC9Z_MHPDwymWXAQwp7D8XZ+o2FsK8g@mail.gmail.com>
	<lh3m7i$v18$1@ger.gmane.org>
	<CA+s+GJCf9o6VEky=JXgrG8v39hyQtPz71yuftF_jyp0bX9WHsA@mail.gmail.com>
	<122FC5AD-2117-4CAF-817F-45B00F57D549@bitsofproof.com>
	<CANEZrP30UsWsBJ-pzb=LQP-MB+PDE0buRdRbuUiOJxANLF9cpw@mail.gmail.com>
	<48ED312A-A1F9-4081-9718-04DD45804313@bitsofproof.com>
Date: Fri, 28 Mar 2014 13:27:18 +0100
Message-ID: <CANEZrP3mEWq-kfZb_HdW53K=gAhY=660mRq6+unGV4XppVQimw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Tamas Blummer <tamas@bitsofproof.com>
Content-Type: multipart/alternative; boundary=001a11c30a049d7a4704f5a9d2a3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP 70 refund field
Precedence: list

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

>
> It is not more effort than an auto remembered call-in phone number. You
> delete if you do not care. The difference however is that it would be a
> clean protocol for repeated payments in both directions for whatever
> reason, where "refund" is and "payment" are not special compared to "1st
> installment", "overpayed back" or "tip"  or whatever extra charge arises
> later.
>

I think that'd be too abstract. The purpose of the refund field is that so
if/when you receive a payment there, the wallet UI can do something
intelligent, like show you in your transactions list that a certain payment
was refunded using language the user will understand. If it's modelled at
the protocol level without that then it makes producing good UI's harder.

--001a11c30a049d7a4704f5a9d2a3
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:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><div>It=
 is not more effort than an auto remembered call-in phone number. You delet=
e if you do not care. The difference however is that it would be a clean pr=
otocol for repeated payments in both directions for whatever reason, where =
&quot;refund&quot; is and &quot;payment&quot; are not special compared to &=
quot;1st installment&quot;, &quot;overpayed back&quot; or &quot;tip&quot; =
=C2=A0or whatever extra charge arises later.</div>
</div></div></blockquote><div><br></div><div>I think that&#39;d be too abst=
ract. The purpose of the refund field is that so if/when you receive a paym=
ent there, the wallet UI can do something intelligent, like show you in you=
r transactions list that a certain payment was refunded using language the =
user will understand. If it&#39;s modelled at the protocol level without th=
at then it makes producing good UI&#39;s harder.</div>
</div></div></div>

--001a11c30a049d7a4704f5a9d2a3--