Content-Type: multipart/signed;
	boundary="Apple-Mail=_5F05938D-E5D9-4487-982F-5FC382551AA8";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CANEZrP3mEWq-kfZb_HdW53K=gAhY=660mRq6+unGV4XppVQimw@mail.gmail.com>
Date: Fri, 28 Mar 2014 13:55:57 +0100
Message-Id: <47379042-C1B6-4E22-8FF7-4EE9FDC095AC@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>
	<CANEZrP3mEWq-kfZb_HdW53K=gAhY=660mRq6+unGV4XppVQimw@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP 70 refund field
Precedence: list


--Apple-Mail=_5F05938D-E5D9-4487-982F-5FC382551AA8
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_8AA41925-0DA8-4D9F-9A6A-CE89780158C0"


--Apple-Mail=_8AA41925-0DA8-4D9F-9A6A-CE89780158C0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 28.03.2014, at 13:27, Mike Hearn <mike@plan99.net> wrote:

> 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.
>=20
> 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.

What is too abstract in a contact list ? If the payment comes with a tag =
like refund the UI could display as such and if it comes with e.g. VAT =
then that.=20

--Apple-Mail=_8AA41925-0DA8-4D9F-9A6A-CE89780158C0
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 28.03.2014, at 13:27, Mike Hearn &lt;<a href="mailto:mike@plan99.net">mike@plan99.net</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>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" &nbsp;or whatever extra charge arises later.</div>
</div></blockquote><div><br></div><div>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.</div>
</div></div></div>
</blockquote></div><br><div>What is too abstract in a contact list ? If the payment comes with a tag like refund the UI could display as such and if it comes with e.g. VAT then that.&nbsp;</div></body></html>
--Apple-Mail=_8AA41925-0DA8-4D9F-9A6A-CE89780158C0--

--Apple-Mail=_5F05938D-E5D9-4487-982F-5FC382551AA8
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

iQEcBAEBAgAGBQJTNXFdAAoJEPZykcUXcTkclfoIAJNbrqoJLlEbTlfiUZ4s6Kev
u44WS5hbSwKXC9FFixtENBDJvnck+3wjrhalrqzDAGsT6yYKZJq1ucQSfiTlf3IK
Z7f8lyTuzGlTeIdiw+dnlM88/i/9kDbWybHqadHG6/7Sp3BHkbQmpy5EsN6yVunG
La6brCmYui5X1M0LFJPOSbYkWxYicCQ6efXYoIc3eFYPIstY26PdBfOV4ZlMaAR5
sirY6XgjQh1Z0V2HXubsRpgMHZa97A5HEQ3V/OhD54RVynmxMoDq/mADYFka/L1M
m8KvOhOklWBXJ8acvRTQILAVebOdqJqR92lui9RblMSo1MW9rPL5MHkt+7OhQaQ=
=NSr9
-----END PGP SIGNATURE-----

--Apple-Mail=_5F05938D-E5D9-4487-982F-5FC382551AA8--