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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <harald.schilly@gmail.com>) id 1RbeBm-00016K-63
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Dec 2011 20:15:30 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.175 as permitted sender)
client-ip=209.85.210.175; envelope-from=harald.schilly@gmail.com;
helo=mail-iy0-f175.google.com;
Received: from mail-iy0-f175.google.com ([209.85.210.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RbeBl-0003sM-AZ
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Dec 2011 20:15:30 +0000
Received: by iakh37 with SMTP id h37so1792828iak.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 16 Dec 2011 12:15:24 -0800 (PST)
Received: by 10.50.45.225 with SMTP id q1mr10502742igm.89.1324066524125; Fri,
16 Dec 2011 12:15:24 -0800 (PST)
MIME-Version: 1.0
Sender: harald.schilly@gmail.com
Received: by 10.50.10.168 with HTTP; Fri, 16 Dec 2011 12:14:53 -0800 (PST)
In-Reply-To: <1324066230.24980.YahooMailNeo@web121004.mail.ne1.yahoo.com>
References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
<1323979147.27319.140661012141129@webmail.messagingengine.com>
<4EEB7E98.8030006@dot-bit.org>
<CAJna-HjXp4XEHnbmX0HKsMDmnxoWQQMmqujN+D9nLV0Zz_omcg@mail.gmail.com>
<1324066230.24980.YahooMailNeo@web121004.mail.ne1.yahoo.com>
From: Harald Schilly <harald@schil.ly>
Date: Fri, 16 Dec 2011 21:14:53 +0100
X-Google-Sender-Auth: Rz8uWPmrOdV1QMB-pkTqb7eqxM8
Message-ID: <CAGG4CB6sirBDSRyDWm_Ez7VxwbO0ETjR+HNdJdk7ze_HA7i3uw@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.5 (-)
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
(harald.schilly[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: 1RbeBl-0003sM-AZ
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
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, 16 Dec 2011 20:15:30 -0000
On Fri, Dec 16, 2011 at 21:10, Amir Taaki <zgenjix@yahoo.com> wrote:
> Especially when we already have bitcoin addresses with their own checksums-
> what value do IBANs add?
Well, I'm not an expert like you, but one benefit would be to be
compatible with existing software solutions that are based on using
IBANs.
H
|
