summaryrefslogtreecommitdiff
path: root/02/b40059f1c16f27288ecf41da81229da03015a7
blob: eeeafb6533c40ca8783c3df2f94260c5ecf1450a (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
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <justus.ranvier@monetas.net>) id 1YlkBn-00035K-W7
	for bitcoin-development@lists.sourceforge.net;
	Fri, 24 Apr 2015 20:27:08 +0000
Received: from mail-ie0-f169.google.com ([209.85.223.169])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YlkBm-0005XP-H6
	for bitcoin-development@lists.sourceforge.net;
	Fri, 24 Apr 2015 20:27:07 +0000
Received: by iecrt8 with SMTP id rt8so91895822iec.0
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 24 Apr 2015 13:27:01 -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:date:message-id:subject:from:to
	:content-type;
	bh=zdsnHSkLob3T//kGXO7kh53yGRWDOgzI4gLLXqnS9vs=;
	b=bpL4iP+pcP5wd5lDm6ReD0jyQMf9rreKpJiEoQo20h/eye52pzJpnC1h1FBwgfR59M
	O1wViBB36Z/qbYpUyBcytrdQlwucPJotJ5R8fZftDgYnThEx7L5JLBSP9ZHIGGo4YOKF
	ltJXcURU5iE6FI9ARFrHltmXJEV6zO821x5J2mzQFV/1BdR4pYRuZU1z3e2nRv1kGVnN
	dhRRk6do6L7I/BPe1mgRsmDAfaXfu3gBHGoO/mcniiAqE1GOiKltR2RGRsO1SKpa08om
	H8UsFUHZsScekphZI6ix6AAIfJDCBCAgm7OcXTODZRk4pi8k92boa/TfOJL4jnL8312L
	hDJw==
X-Gm-Message-State: ALoCoQkbW4L8UqDQle7yPWjSznR4Pl+drcKtkaWO88WcjTsO4X7U4rNT4fGN38dYFqtcq1fJFoIx
MIME-Version: 1.0
X-Received: by 10.50.126.105 with SMTP id mx9mr893911igb.21.1429905646627;
	Fri, 24 Apr 2015 13:00:46 -0700 (PDT)
Received: by 10.36.205.135 with HTTP; Fri, 24 Apr 2015 13:00:46 -0700 (PDT)
Date: Fri, 24 Apr 2015 22:00:46 +0200
Message-ID: <CAHabJ+Mn0=vfLvTJ+z3tx8cFAAuLD1pLp4rOe3pM6MtCrCxjwg@mail.gmail.com>
From: Justus Ranvier <justus.ranvier@monetas.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b4145d42148e805147dda99
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: 1YlkBm-0005XP-H6
Subject: [Bitcoin-development] Reusable payment codes
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, 24 Apr 2015 20:27:08 -0000

--047d7b4145d42148e805147dda99
Content-Type: text/plain; charset=UTF-8

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1


https://github.com/justusranvier/rfc/blob/payment_code/bips/bip-pc01.mediawiki


This link contains an RFC for a new type of Bitcoin address called a
"payment code"


Payment codes are SPV-friendly alternatives to DarkWallet-style stealth
addresses which provide useful features such as positively identifying
senders to recipients and automatically providing for transaction refunds.


Payment codes can be publicly advertised and associated with a real-life
identity without causing a loss of financial privacy.


Compared to stealth addresses, payment codes require less blockchain data
storage.


Payment codes require 65 bytes of OP_RETURN data per sender-recipient pair,
while stealth addresses require 40 bytes per transaction.


-----BEGIN PGP SIGNATURE-----

Version: GnuPG v1


iQIcBAEBAgAGBQJVOqCRAAoJECpf2nDq2eYjluEP/RVJk+miDIihY4ilIvUbKvMd

JLLqHr7Q1dlZyMIG/UqVWdoP5hzg/16B+q2iAB9jXozPnrDp0mggBh6rIGroevAa

Kqfrs+Rrog1w9auhd67LWORDqav6YIrjTJIxdLxe11IEiq5rWbHPNUEDMzdEmHbz

QfTH7KWAP2BasO5ETXcfu6BcccrXZ3XOKLON2h3NGD/cEDizY+uT2k3QN54z+KxG

NB9scKbzVvsJwkyBrgbV+As9H3k6PnFsojYgAaE9gkp7D2+ahjzUiOH5rv6TbbYR

o2X5MOiTY2/YZEqZPG7IR03ZAgeLVCvXXysjPOfzUKbmTF4w849sm8BuhixzDXHo

2V/HHKoGclIohcODBCWi0tVQXshZt4QkCNJBW5o3nL6Nn2YOp6hmw8YKAHnw3E7h

/wIgk5f+NOLl/iIxoAxAdavEj5P6N4ic+OB6MAjnhEilWfBvCIpqWLGNvrtOhEa9

EnPHcgb4ILBu4OionJhsNpJ/O95C0OEypMm25MIS+rQcV4Uxe5IOS2OuT/GreLET

n/7Y0mJbqYbLBjVsfS+DNjvsgyJl5AxhcMrdVyXJjSYVcCoRhcoX5Ceidd+YkbHI

OMs5f63tM1Rgi/WY4Ct80SD5EbULZuu8j1KJ9HPGuMt081JSBH+L5isiKuazPeO+

SGApMBd4Q89fKzL2djae

=Dypr

-----END PGP SIGNATURE-----

--047d7b4145d42148e805147dda99
Content-Type: text/html; charset=UTF-8

<div dir="ltr">
<p style="margin:0px">-----BEGIN PGP SIGNED MESSAGE-----</p>
<p style="margin:0px">Hash: SHA1</p>
<p style="margin:0px"><br></p>
<p style="margin:0px"><a href="https://github.com/justusranvier/rfc/blob/payment_code/bips/bip-pc01.mediawiki">https://github.com/justusranvier/rfc/blob/payment_code/bips/bip-pc01.mediawiki</a></p>
<p style="margin:0px"><br></p>
<p style="margin:0px">This link contains an RFC for a new type of Bitcoin address called a &quot;payment code&quot;</p>
<p style="margin:0px"><br></p>
<p style="margin:0px">Payment codes are SPV-friendly alternatives to DarkWallet-style stealth addresses which provide useful features such as positively identifying senders to recipients and automatically providing for transaction refunds.</p>
<p style="margin:0px"><br></p>
<p style="margin:0px">Payment codes can be publicly advertised and associated with a real-life identity without causing a loss of financial privacy.</p>
<p style="margin:0px"><br></p>
<p style="margin:0px">Compared to stealth addresses, payment codes require less blockchain data storage.</p>
<p style="margin:0px"><br></p>
<p style="margin:0px">Payment codes require 65 bytes of OP_RETURN data per sender-recipient pair, while stealth addresses require 40 bytes per transaction.</p>
<p style="margin:0px"><br></p>
<p style="margin:0px">-----BEGIN PGP SIGNATURE-----</p>
<p style="margin:0px">Version: GnuPG v1</p>
<p style="margin:0px"><br></p>
<p style="margin:0px">iQIcBAEBAgAGBQJVOqCRAAoJECpf2nDq2eYjluEP/RVJk+miDIihY4ilIvUbKvMd</p>
<p style="margin:0px">JLLqHr7Q1dlZyMIG/UqVWdoP5hzg/16B+q2iAB9jXozPnrDp0mggBh6rIGroevAa</p>
<p style="margin:0px">Kqfrs+Rrog1w9auhd67LWORDqav6YIrjTJIxdLxe11IEiq5rWbHPNUEDMzdEmHbz</p>
<p style="margin:0px">QfTH7KWAP2BasO5ETXcfu6BcccrXZ3XOKLON2h3NGD/cEDizY+uT2k3QN54z+KxG</p>
<p style="margin:0px">NB9scKbzVvsJwkyBrgbV+As9H3k6PnFsojYgAaE9gkp7D2+ahjzUiOH5rv6TbbYR</p>
<p style="margin:0px">o2X5MOiTY2/YZEqZPG7IR03ZAgeLVCvXXysjPOfzUKbmTF4w849sm8BuhixzDXHo</p>
<p style="margin:0px">2V/HHKoGclIohcODBCWi0tVQXshZt4QkCNJBW5o3nL6Nn2YOp6hmw8YKAHnw3E7h</p>
<p style="margin:0px">/wIgk5f+NOLl/iIxoAxAdavEj5P6N4ic+OB6MAjnhEilWfBvCIpqWLGNvrtOhEa9</p>
<p style="margin:0px">EnPHcgb4ILBu4OionJhsNpJ/O95C0OEypMm25MIS+rQcV4Uxe5IOS2OuT/GreLET</p>
<p style="margin:0px">n/7Y0mJbqYbLBjVsfS+DNjvsgyJl5AxhcMrdVyXJjSYVcCoRhcoX5Ceidd+YkbHI</p>
<p style="margin:0px">OMs5f63tM1Rgi/WY4Ct80SD5EbULZuu8j1KJ9HPGuMt081JSBH+L5isiKuazPeO+</p>
<p style="margin:0px">SGApMBd4Q89fKzL2djae</p>
<p style="margin:0px">=Dypr</p>
<p style="margin:0px">-----END PGP SIGNATURE-----</p></div>

--047d7b4145d42148e805147dda99--