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
168
169
170
171
172
173
174
175
176
177
178
179
180
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@jtimon.cc>) id 1Yn51a-0002eA-Ir
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Apr 2015 12:54:06 +0000
Received: from mail-wg0-f49.google.com ([74.125.82.49])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yn51Y-0003oo-QC
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Apr 2015 12:54:06 +0000
Received: by wgyo15 with SMTP id o15so150334239wgy.2
for <bitcoin-development@lists.sourceforge.net>;
Tue, 28 Apr 2015 05:53:58 -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=6mXRDSm0JPU8TUgZxEYAa27unyqjH+zpyMUO8fPFwRM=;
b=YDKq1J5PLb3aq7H9llpMHB2eelQUqiKb47ytRPcMDp29BMrnHM2kte1VUo8VcUC0W6
kDyDzt6bZV/6pJR6F8laMJBAkEpryqeIov2gaTDWgKsn6DRCgn8GKAmAfML5x4sZhnh+
h1n2PaBlOqs14zTrkJhmkte/LWMPaayRlsIBjCKxBQMfh4t9cY2riLj6Bj/ZWwOQREMs
fpoKMCzQDndPdPXrpFJkayLZj6/JqBfQB9RstCLJOyvSop+iaSLyWwU4Rto6yy5ufGJ/
yskSjP3XHOC6fSY99+7tDEMZYtwyP9cS2pcGKqSfkqKoF9lISfVtOmalP8N26el8nT1v
jGTQ==
X-Gm-Message-State: ALoCoQlWGWQzSmu0kEdQ11UxoVBiA1RrqWJwTpC6cSkK/oyiPp5AqLNJK/KY1zYMLO73QRKDgcUr
MIME-Version: 1.0
X-Received: by 10.180.14.67 with SMTP id n3mr28833891wic.92.1430225638656;
Tue, 28 Apr 2015 05:53:58 -0700 (PDT)
Received: by 10.194.124.2 with HTTP; Tue, 28 Apr 2015 05:53:58 -0700 (PDT)
In-Reply-To: <CAPswA9z9K2w-uEHMOrAvAENs5L1iS8PYu2xMOFidDUJvU04O5w@mail.gmail.com>
References: <CAPswA9zzVDxW8_WXg5833r2Z4pxZOppYtNLHMQ=Nw-H72cMz7w@mail.gmail.com>
<A2849710-1069-45A1-89C0-9D8E40C4A8D6@newcastle.ac.uk>
<CAPswA9wNS2J=4YhpqWN8SmzJuUF8mek8XLUYTE+twLX9vM4Jhg@mail.gmail.com>
<CAPswA9wZk_8EjbN8J-VbMGQ6nrZ7SthopJ=HYMtpxhSCsm_neA@mail.gmail.com>
<553D87CE.5000005@thinlink.com>
<CAPswA9xUfr1D6New3hm+1Z1OqSfkAZ8L+VnbFZayG+uJecgaeA@mail.gmail.com>
<CAPswA9w=DMDokS8BrDPTtWa_qpdORbK+V4aNS4DoAKE_F1iVoA@mail.gmail.com>
<CABm2gDrumXjfo7=YmTSkRO0QPtPtUj4PF9yb1m80L60O-HZe6A@mail.gmail.com>
<CAPswA9z9K2w-uEHMOrAvAENs5L1iS8PYu2xMOFidDUJvU04O5w@mail.gmail.com>
Date: Tue, 28 Apr 2015 14:53:58 +0200
Message-ID: <CABm2gDpsv8mp3hjMfT_okaMQmW4AmCiFAz43dBR1M-rzntqfSg@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Kalle Rosenbaum <kalle@rosenbaum.se>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.5 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Yn51Y-0003oo-QC
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 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, 28 Apr 2015 12:54:06 -0000
Forget it, sorry, I misunderstood the proposal entirely, re-reading
with more care...
On Tue, Apr 28, 2015 at 2:41 PM, Kalle Rosenbaum <kalle@rosenbaum.se> wrote:
> Hi Jorge,
>
> I don't think I understand the question. Proof of Payment is used to prove
> that you have the credentials needed for a certain transaction. It does not
> care where in the blockchain the transaction is. Or if it's in the
> blockchain at all.
>
> /Kalle
>
> So at the low level, how does a "proof of payment" differ from just proving
> that a given transaction is in a given block (what SPV nodes take as proof
> of payment today)?
>
> On Apr 27, 2015 2:42 PM, "Kalle Rosenbaum" <kalle@rosenbaum.se> wrote:
>>
>> "Or a really high lock_time, but it would not make it invalid, just
>> delayed."
>>
>> Ok, this was a bad idea, since nodes would have to keep it in memory.
>> Please disregard that idea...
>>
>> Kalle
>>
>> Den 27 apr 2015 14:35 skrev "Kalle Rosenbaum" <kalle@rosenbaum.se>:
>> >
>> > >
>> > > Some more use cases might be:
>> > > Waiting in comfort:
>> > > - Send a payment ahead of time, then wander over and collect the
>> > > goods
>> > > after X confirmations.
>> > >
>> > > Authorized pickup :
>> > > - Hot wallet software used by related people could facilitate the use
>> > > of 1 of N multisig funds. Any one of the N wallets could collect
>> > > goods
>> > > and services purchased by any of the others.
>> >
>> > I like this one, because it shows the power of reusing the transaction
>> > data structure.
>> >
>> > >
>> > > Non-monetary gifts:
>> > > - Sender exports spent keys to a beneficiary, enabling PoP to work as
>> > > a
>> > > gift claim
>> > >
>> > > Contingent services:
>> > > - Without Bob's permission, a 3rd party conditions action on a
>> > > payment
>> > > made from Alice to Bob. For example, if you donated at least .02 BTC
>> > > to
>> > > Dorian, you (or combining scenarios, any of your N authorized family
>> > > members), can come to my dinner party.
>> >
>> > This is an interesting one.
>> >
>> > >
>> > > I tried out your demo wallet and service and it worked as advertised.
>> > >
>> > > Could the same standard also be used to prove that a transaction COULD
>> > > BE created? To generalize the concept beyond actual payments, you
>> > > could
>> > > call it something like proof of payment potential.
>> >
>> > I guess it's possible, but we'd have to remove the txid from the output,
>> > since there is none. This is a way of saying "I'm in control of these
>> > addresses". The other party/parties can then verify the funds on the
>> > blockchain and watch those addresses for changes. Maybe there are some
>> > interesting use cases here. Ideas?
>> >
>> > >
>> > > Why not make these proofs permanently INVALID transactions, to remove
>> > > any possibility of their being mined and spending everything to fees
>> > > when used in this way, and also in cases involving reorganizations?
>> >
>> > Yes. Initially I thought it would be enough that the funds are already
>> > spent, but I think you're right here. Reorgs could be a problem. Worse, you
>> > also might want to prove 0-confirmation transactions, in which case it's a
>> > huge security problem. Someone might intercept the PoP and publish it on the
>> > bitcoin network, spending all the funds. But I still would like wallets to
>> > be able to build/verify PoPs with little or no modifications. Could we
>> > possibly change the version number on the PoP to something other than 1?
>> > Maybe 2^4-1? Or a really high lock_time, but it would not make it invalid,
>> > just delayed. Any suggestions here?
>> >
>> > >
>> > > I agree that PoP seems complementary to BIP70.
>> > >
>> > >
>> >
>> > Thank you very much for your comments!
>> >
>> > /Kalle
>>
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
|
