summaryrefslogtreecommitdiff
path: root/9b/a16f421fed711ae793c7a16a85e6c91bba78c3
blob: cb488fc984d1c6f52dd2f2f0689fae73038b84d8 (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1V4Ptg-0003Dk-Vg
	for bitcoin-development@lists.sourceforge.net;
	Wed, 31 Jul 2013 06:28:33 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=gavinandresen@gmail.com;
	helo=mail-wg0-f53.google.com; 
Received: from mail-wg0-f53.google.com ([74.125.82.53])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1V4Ptf-0007S6-Up
	for bitcoin-development@lists.sourceforge.net;
	Wed, 31 Jul 2013 06:28:32 +0000
Received: by mail-wg0-f53.google.com with SMTP id c11so232017wgh.8
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 30 Jul 2013 23:28:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.170.227 with SMTP id ap3mr20740232wjc.40.1375252105785; 
	Tue, 30 Jul 2013 23:28:25 -0700 (PDT)
Received: by 10.194.82.198 with HTTP; Tue, 30 Jul 2013 23:28:25 -0700 (PDT)
Date: Wed, 31 Jul 2013 16:28:25 +1000
Message-ID: <CABsx9T0Ly67ZNJhoRQk0L9Q0-ucq3e=24b5Tg6GRKspRKKtP-g@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0122e9223df7c504e2c8d50b
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1V4Ptf-0007S6-Up
Subject: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72
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: Wed, 31 Jul 2013 06:28:33 -0000

--089e0122e9223df7c504e2c8d50b
Content-Type: text/plain; charset=ISO-8859-1

I've turned the preliminary payment protocol spec into three BIPs:

https://en.bitcoin.it/wiki/BIP_0070 : Network protocol / messages
https://en.bitcoin.it/wiki/BIP_0071 : MIME types for the messages
https://en.bitcoin.it/wiki/BIP_0072 : bitcoin: URI extension

I expect the wallet-side implementation to be pulled into Bitcoin-Qt Real
Soon:
  https://github.com/bitcoin/bitcoin/pull/2539

There is also a reference implementation of server-side code for generating
payment requests in php and C++ :
  https://github.com/gavinandresen/paymentrequest

-- 
--
Gavin Andresen

--089e0122e9223df7c504e2c8d50b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;ve turned the preliminary payment protocol spec into three BIPs:<div>=
<br></div><div><a href=3D"https://en.bitcoin.it/wiki/BIP_0070">https://en.b=
itcoin.it/wiki/BIP_0070</a> : Network protocol / messages</div><div><a href=
=3D"https://en.bitcoin.it/wiki/BIP_0071">https://en.bitcoin.it/wiki/BIP_007=
1</a> : MIME types for the messages</div>
<div><a href=3D"https://en.bitcoin.it/wiki/BIP_0072">https://en.bitcoin.it/=
wiki/BIP_0072</a> : bitcoin: URI extension</div><div><br></div><div>I expec=
t the wallet-side implementation to be pulled into Bitcoin-Qt Real Soon:</d=
iv>
<div>=A0=A0<a href=3D"https://github.com/bitcoin/bitcoin/pull/2539">https:/=
/github.com/bitcoin/bitcoin/pull/2539</a></div><div><br></div><div>There is=
 also a reference implementation of server-side code for generating payment=
 requests in php and C++ :</div>
<div>=A0=A0<a href=3D"https://github.com/gavinandresen/paymentrequest">http=
s://github.com/gavinandresen/paymentrequest</a><br clear=3D"all"><div><br><=
/div><div>--=A0</div>--<br>Gavin Andresen<br>
</div><div><br></div>

--089e0122e9223df7c504e2c8d50b--