1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1WTWXY-0002dT-2F
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Mar 2014 13:09:44 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WTWXW-0007mT-Ad
for bitcoin-development@lists.sourceforge.net;
Fri, 28 Mar 2014 13:09:44 +0000
Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1WTWXP-0001WF-G6; Fri, 28 Mar 2014 14:09:35 +0100
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>
X-Mailer: Apple Mail (2.1510)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1396012182;
1e6caed8;
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WTWXW-0007mT-Ad
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP 70 refund field
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 28 Mar 2014 13:09:44 -0000
--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 <<a href="mailto:mike@plan99.net">mike@plan99.net</a>> 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. </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->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.</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. </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--
|
