Content-Type: multipart/signed;
	boundary="Apple-Mail=_2B7819AC-B2E7-444F-8244-540B45D4A1C6";
	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: <CANEZrP3xcRrPsR+nCDAWgTaXg=ADGH1KjrwgLew7V2eC9ghexg@mail.gmail.com>
Date: Fri, 28 Mar 2014 14:09:34 +0100
Message-Id: <5223FF53-CDA4-419D-A4B0-204DC3441626@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>
	<47379042-C1B6-4E22-8FF7-4EE9FDC095AC@bitsofproof.com>
	<CANEZrP3xcRrPsR+nCDAWgTaXg=ADGH1KjrwgLew7V2eC9ghexg@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=_2B7819AC-B2E7-444F-8244-540B45D4A1C6
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_16FF50AF-B023-4836-B9CD-E67A2F7D69B4"


--Apple-Mail=_16FF50AF-B023-4836-B9CD-E67A2F7D69B4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 28.03.2014, at 14:00, Mike Hearn <mike@plan99.net> wrote:

> 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
>=20
> How is this any different? The tag in this case is the address and the =
payment is being delivered by the block chain (direct submission for =
user->merchant is easier than merchant->user) so we can't stuff extra =
data anywhere else. Then the UI knows it was a refund payment and not =
for anything else.
>=20

The difference is the concept of setting up a channel that allows both =
parties to create valid addresses of the other by exchanging some kind =
of master keys. The initial handshake with the protocol would agree on =
tags of individual address indexes if used. The wallets would have to =
observe those agreed inidices and evtl. extend range. Payments could go =
back and forth. Either party might delete the channel information and =
stop observing keys as soon as he does no longer expect a payment from =
the other. This would be an explicit operation, like deleting a contact.

> I don't see the relevance of VAT here.

It was an example label. I would not be suprised if with widespread use =
of payments some government would require VAT collected separately. It =
is just a guess and has no weight in my prior arguments.=20

--Apple-Mail=_16FF50AF-B023-4836-B9CD-E67A2F7D69B4
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 14:00, 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>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>
</div></blockquote></div><br></div><div class="gmail_extra">How is this any different? The tag in this case is the address and the payment is being delivered by the block chain (direct submission for user-&gt;merchant is easier than merchant-&gt;user) so we can't stuff extra data anywhere else. Then the UI knows it was a refund payment and not for anything else.</div>
<div class="gmail_extra"><br></div></div></blockquote><div><br></div><div>The difference is the concept of setting up a channel that allows both parties to create valid addresses of the other by exchanging some kind of master keys. The initial handshake with the protocol would agree on tags of individual address indexes if used. The wallets would have to observe those agreed inidices and evtl. extend range. Payments could go back and forth. Either party might delete the channel information and stop observing keys as soon as he does no longer expect a payment from the other. This would be an explicit operation, like deleting a contact.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">I don't see the relevance of VAT here.</div></div>
</blockquote></div><br><div>It was an example label. I would not be suprised if with widespread use of payments some government would require VAT collected separately. It is just a guess and has no weight in my prior arguments.&nbsp;</div></body></html>
--Apple-Mail=_16FF50AF-B023-4836-B9CD-E67A2F7D69B4--

--Apple-Mail=_2B7819AC-B2E7-444F-8244-540B45D4A1C6
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

iQEcBAEBAgAGBQJTNXSOAAoJEPZykcUXcTkclxcH+wWpgLqA/g8/wbG1EgxUrB9d
OI8+OyCZcXqhzBPyEY/VzWTGHMIEZpp1RpBjZabPA0pmf6ahDCzNWRivCLzHdiGH
avebEsWIBL73HipG+X9cZusCdDQv03dEbhyqnZBosvsMlQ9P1dreohRQmUta+kje
hzNHQAhjS1cIVK95qRJWCf0QXmoQksHE9YBmqTTh0xeOKec8bmcRUokVqltHTUw6
s2SD3bjv52AWNgLE3IzmyS4XyMcK7CiAIaj64E10L0kPqOMAQqZrdQgWlLbGPeiC
wNkdBXo8arpbTW/1D3u8ENn3RlohQrOjnuh11TlK50Rvq75y4Uu05Tf7equvyBk=
=pgzO
-----END PGP SIGNATURE-----

--Apple-Mail=_2B7819AC-B2E7-444F-8244-540B45D4A1C6--