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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1RbujA-00055R-0I
for bitcoin-development@lists.sourceforge.net;
Sat, 17 Dec 2011 13:55:04 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.47 as permitted sender)
client-ip=209.85.160.47; envelope-from=laanwj@gmail.com;
helo=mail-pw0-f47.google.com;
Received: from mail-pw0-f47.google.com ([209.85.160.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rbuj8-0004sn-QC
for bitcoin-development@lists.sourceforge.net;
Sat, 17 Dec 2011 13:55:03 +0000
Received: by pbcc11 with SMTP id c11so3036924pbc.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 17 Dec 2011 05:54:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.211.99 with SMTP id nb3mr24419224pbc.41.1324130096544; Sat,
17 Dec 2011 05:54:56 -0800 (PST)
Received: by 10.142.161.12 with HTTP; Sat, 17 Dec 2011 05:54:56 -0800 (PST)
In-Reply-To: <201112170132.26201.luke@dashjr.org>
References: <201112170132.26201.luke@dashjr.org>
Date: Sat, 17 Dec 2011 14:54:56 +0100
Message-ID: <CA+s+GJAm9yBh=eu+KiN1kJou+0xQ39sSZ8JGM4nWsqt25gbK=g@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=e89a8ff1c7080a79ff04b44a1099
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
(laanwj[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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Rbuj8-0004sn-QC
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Pubkey addresses
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: Sat, 17 Dec 2011 13:55:04 -0000
--e89a8ff1c7080a79ff04b44a1099
Content-Type: text/plain; charset=UTF-8
I don't see reason why not. It could just be another, longer, address type.
The advantage being that it allows for shorter transactions in the block
chain (right?).
Wladimir
On Sat, Dec 17, 2011 at 7:32 AM, Luke-Jr <luke@dashjr.org> wrote:
> IMO, we should standardize and support public key addresses. While not
> ideal
> for humans, because of their length, it's a better fit for large QR Codes
> IMO.
>
>
> ------------------------------------------------------------------------------
> Learn Windows Azure Live! Tuesday, Dec 13, 2011
> Microsoft is holding a special Learn Windows Azure training event for
> developers. It will provide a great way to learn Windows Azure and what it
> provides. You can attend the event by watching it streamed LIVE online.
> Learn more at http://p.sf.net/sfu/ms-windowsazure
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--e89a8ff1c7080a79ff04b44a1099
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div><br></div>I don't see reason why not. It could just be another, lo=
nger, address type. The advantage being that it allows for shorter transact=
ions in the block chain (right?).=C2=A0<div><div><br></div><div>Wladimir<br=
><br>
<div class=3D"gmail_quote">On Sat, Dec 17, 2011 at 7:32 AM, Luke-Jr <span d=
ir=3D"ltr"><<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>></=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
IMO, we should standardize and support public key addresses. While not idea=
l<br>
for humans, because of their length, it's a better fit for large QR Cod=
es IMO.<br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Windows Azure Live! =C2=A0Tuesday, Dec 13, 2011<br>
Microsoft is holding a special Learn Windows Azure training event for<br>
developers. It will provide a great way to learn Windows Azure and what it<=
br>
provides. You can attend the event by watching it streamed LIVE online.<br>
Learn more at <a href=3D"http://p.sf.net/sfu/ms-windowsazure" target=3D"_bl=
ank">http://p.sf.net/sfu/ms-windowsazure</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>
--e89a8ff1c7080a79ff04b44a1099--
|
