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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gronager@ceptacle.com>) id 1TdH4j-0000tW-Cz
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 09:03:29 +0000
X-ACL-Warn:
Received: from 2508ds5-oebr.1.fullrate.dk ([90.184.5.129]
helo=mail.ceptacle.com)
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1TdH4i-0004OV-FS for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 09:03:29 +0000
Received: from localhost (localhost [127.0.0.1])
by mail.ceptacle.com (Postfix) with ESMTP id 8F65726C3F6D
for <bitcoin-development@lists.sourceforge.net>;
Tue, 27 Nov 2012 09:43:46 +0100 (CET)
X-Virus-Scanned: amavisd-new at ceptacle.com
Received: from mail.ceptacle.com ([127.0.0.1])
by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new,
port 10024) with ESMTP id vl4tnd1kfcdq
for <bitcoin-development@lists.sourceforge.net>;
Tue, 27 Nov 2012 09:43:46 +0100 (CET)
Received: from [109.105.106.200] (unknown [109.105.106.200])
by mail.ceptacle.com (Postfix) with ESMTPSA id 52C6A26C3F5B
for <bitcoin-development@lists.sourceforge.net>;
Tue, 27 Nov 2012 09:43:46 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Michael Gronager <gronager@ceptacle.com>
In-Reply-To: <CACwuEiNZobcpR4g=1AH=JReZFzHmH=6exNGTaPBBjm+q5eR9vg@mail.gmail.com>
Date: Tue, 27 Nov 2012 09:43:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <895A1D97-68B4-4A2F-B4A1-34814B9BA8AC@ceptacle.com>
References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>
<CACwuEiP7CGeZZGW=mXwrFAAqbbwbrPXTPb8vOEDuO9_96hqBGg@mail.gmail.com>
<CAAS2fgSY8hHiCJYEDv=y48hYRJJtB-R5EBX8JLz6NivBm+Z9PQ@mail.gmail.com>
<CACwuEiMjf8WYOpfmzHUHMa-sy2VsJHaUNj1cj722Y=P_sosbvw@mail.gmail.com>
<CAJ1JLtuJ8HQri7++2bodc2ACRrE7Y48oy0HkPR8d400MooHaqA@mail.gmail.com>
<CACwuEiMgcv09U2P9dD58x-oMXMSg==fPYo0yRLsqzyuax96Eqw@mail.gmail.com>
<CAJ1JLttTPi9XNwCGyvbvx8TXqbLyk0KxFRHxv_8UB+tEQrKvvA@mail.gmail.com>
<CACwuEiNZobcpR4g=1AH=JReZFzHmH=6exNGTaPBBjm+q5eR9vg@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
X-Mailer: Apple Mail (2.1499)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1TdH4i-0004OV-FS
Subject: Re: [Bitcoin-development] Payment Protocol Proposal:
Invoices/Payments/Receipts
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, 27 Nov 2012 09:03:29 -0000
Short comments:
* What if the SignedReceipt is not received AND the transactions IS =
posted on the p2p. Then you have payed for the goods, but you don't have =
a receipt. This could happen both from malice or system failures.
** Suggestion - sign the invoice with the key to which to send the =
transaction, the proof of payment, equivalent to a signed receipt is =
then in the blockchain.
This scheme would work both with or without x509, if you want to include =
x509, the message in the invoice could simply be signed by the x509 =
certificate as well.
PRO: Any user can send signed invoices, not only those with a x509 cert.
PRO: No limbo situation with no SignedReceipt
CON: This disables the use of anything but payment to key/address incl =
multisig etc.
However, the wast majority of use will anyway be payment to key/address.
Support of general pay to script could be supported through the payment =
scheme proposed earlier by Mike: No non-fee payments are accepted, =
except in a group - i.e. it is up to the merchant to generate the final =
transaction incl the fees, and that one could be to a general script. =
This also keeps the support of pay to general script needed for a client =
to a minimum.
Cheers,
Michael
|
