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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kalle@rosenbaum.se>) id 1Z4wRq-0001Hi-9P
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 19:23:02 +0000
X-ACL-Warn:
Received: from mail-qk0-f178.google.com ([209.85.220.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4wRo-0001wT-3Z
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 19:23:02 +0000
Received: by qkdm188 with SMTP id m188so14425746qkd.1
for <bitcoin-development@lists.sourceforge.net>;
Tue, 16 Jun 2015 12:22:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=hUSqRymnxatYSBN2fiSJb86mYSqU6ZgEWNvqF3WMuIw=;
b=Dh+xeiOzuLlamld0PV8Is8SJhJKMLEkoRzT0s6ZTyLR1bYVatQXlGifyhLl9knl8mY
oPL1tTTGz6/mkqfYeEyRo8o+TtzO88v09o2N5623R0n4yyUVbFREFdPMPmkTd8T/nw5J
wusFYgN1Pkn7rbjsLHoeZaIbexrSFP/IN6dJWkqP9uGEqQyN8uU5pdF+0SI6sXPmzghO
Vhz1BBW9a2xdlfn3qL+X+jqcAo8LT3d71I0e7sa2Zb/ohwCgEd3zfZ8rC1fH/kvU0ao0
7Mm+ahaEDZsqKApkfobJSI14f2/noABvIVJsJOgihyhHIJv3j0tmxysaMDsQu4FPZZ6A
iylA==
X-Gm-Message-State: ALoCoQnfHGjSHd+EjNUDP0cuaz6M9LuTNMqush28srHW0K1laE4hlI9M5mS1Nh+254TN6XBMQVmi
MIME-Version: 1.0
X-Received: by 10.140.80.170 with SMTP id c39mr2834243qgd.55.1434482574507;
Tue, 16 Jun 2015 12:22:54 -0700 (PDT)
Received: by 10.96.145.9 with HTTP; Tue, 16 Jun 2015 12:22:54 -0700 (PDT)
In-Reply-To: <CAPg+sBjp-BmSXhanOuKE0DN1wdfVwCtFwiAbPse1GLxy3+L3nA@mail.gmail.com>
References: <CAPswA9w5Sgg6AV=9Pqx5sqbkdrwv9LmwoxmMu7xZsQSNXtmZnQ@mail.gmail.com>
<CAPg+sBjtovFpLoibpVGLsNJXexBcoiYzjrvctraXntCUZBJsGg@mail.gmail.com>
<CAPswA9zhB4GV=JJ28RRLFNrkVwExUv36zujmuAjwPd6rG6rvzQ@mail.gmail.com>
<CALJP9GCBJiofY7k2RJ460CuLuWQunHcx7EcLi1-d07v76Y-E2g@mail.gmail.com>
<CAPswA9wqdbU0z8ydBt+9M0iQX0VSi1ce=dg3fR2_2bx3-vEqzA@mail.gmail.com>
<CAPswA9z_xKY6v9=Ejh=01mZN0QCVo1e0RY1FTzXzS39i3tjgAw@mail.gmail.com>
<CAPswA9xk5QYAXxQ6ES3cnNPeB1FTiiSJgLahLEkSk4CLpoM_QQ@mail.gmail.com>
<CAPg+sBiWykR6RaHhbyYQbL=A5t1TmHgEmS_sC7jj9d3SUTMO9g@mail.gmail.com>
<CAPswA9zycU0pwZKaHU9J3Tvg=ovLJ8TZ9OH6ebTPONaRaiOE8g@mail.gmail.com>
<CAPg+sBhuth22+vAHyS2iwpze8X=-b2wJQ5s1z2FhZ1jsLXobgQ@mail.gmail.com>
<CAPswA9yB3wfV1auXR=ggXjh+f1C3Qpkv8qP1miQwkc8R2_aBLg@mail.gmail.com>
<CAPg+sBjp-BmSXhanOuKE0DN1wdfVwCtFwiAbPse1GLxy3+L3nA@mail.gmail.com>
Date: Tue, 16 Jun 2015 21:22:54 +0200
Message-ID: <CAPswA9zzKvh6G+NqzTmhrNXMSWOPtZ2DGW2t_2Jrisy8x9m2qw@mail.gmail.com>
From: Kalle Rosenbaum <kalle@rosenbaum.se>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z4wRo-0001wT-3Z
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for Proof of Payment
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: Tue, 16 Jun 2015 19:23:02 -0000
Thank you for your comments Pieter! Please find my answers below.
2015-06-16 16:31 GMT+02:00 Pieter Wuille <pieter.wuille@gmail.com>:
> On Mon, Jun 15, 2015 at 1:59 PM, Kalle Rosenbaum <kalle@rosenbaum.se> wrote:
>>
>> 2015-06-15 12:00 GMT+02:00 Pieter Wuille <pieter.wuille@gmail.com>:
>> I'm not sure if we will be able to support PoP with CoinJoin. Maybe
>> someone with more insight into CoinJoin have some input?
>
>
> Not really. The problem is that you assume a transaction corresponds to a
> single payment. This is true for simple wallet use cases, but not compatible
> with CoinJoin, or with systems that for example would want to combine
> multiple payments in a single transaction.
>
Yes, you are right. It's not compatible with CoinJoin and the likes.
>
> 48 bits seems low to me, but it does indeed solve the problem. Why not 128
> or 256 bits?
The nonce is limited because of the OP_RETURN output being limited to
40 bytes of data: 2 bytes version, 32 bytes txid, 6 bytes nonce.
>
>> > Why does anyone care who paid? This is like walking into a coffeshop,
>> > noticing I don't have money with me, let me friend pay for me, and then
>> > have
>> > the shop insist that I can't drink it because I'm not the buyer.
>>
>> If you pay as you use the service (ie pay for coffee upfront), there's
>> no need for PoP. Please see the Motivation section. But you are right
>> that you must have the wallet(s) that paid at hand when you issue a
>> PoP.
>>
>> >
>> > Track payments, don't try to assign identities to payers.
>>
>> Please elaborate, I don't understand what you mean here.
>
>
> I think that is a mistake. You should not assume that the wallet who held
> the coins is the payer/buyer. That's what I said earlier; you're implicitly
> creating an identity (the one who holds these keys) based on the
> transaction. This seems fundamentally wrong to me, and not necessary. The
> receiver should not care who paid or how, he should care what was payed for.
You are saying that it's a problem that the wallet used to pay, must
also be used to issue the PoP? That may very well be a problem in some
cases. People using PoP should of course be aware of it's limitations
and act accordingly, i.e. don't pay for concert tickets for a friend
and expect your friend to be able to enter the arena with her wallet.
As Tom Harding noted, it is possible to transfer keys to your friend's
wallet, but that might not be desirable if those keys are also used
for other payments. Also that would weaken the security of an HD
wallet, since a chain code along with a private key would reveal all
keys in that tree. Another solution is that your friend forwards the
PoP request to your wallet, through twitter or SMS, and you send the
PoP for her. Maybe that forwarding mechanism can be built into wallets
and automated so that the wallet automatically suggests to sign the
PoP for your friend. This is probably something to investigate
further, but not within the scope of this BIP.
Of course the simplest solution would be to send money to your friend
first so that she can pay for the ticket from her own wallet, but
that's not always feasible.
>
> The easiest solution to this IMHO would be an extension to the payment
> protocol that gives you (or your wallet) a token in return for paying, and
> that knowledge of that token is used to gain access to the services you
> provide.
>
That token would then be reusable. Someone stealing it would be able
to use it as much as she wants. That is what I want to avoid with PoP.
The BIP proposal briefly mentions something like this in the
rationale. I also had a discussion about this with Mike Hearn on this
list on Mars 13 that I think covers most pros and cons of the
different approaches.
While your suggestion does indeed separate the transaction from the
proof of payment, it also assumes that the token is held in the wallet
that pays. Otherwise you would need to keep it in another safe place,
remember it's reusable. Where would that be? How would you transfer
that token to your friend?
Thank you again for your comments. I appreciate it.
Best regards,
Kalle
> --
> Pieter
>
|
