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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1V5MO7-0008B8-4Z
for bitcoin-development@lists.sourceforge.net;
Fri, 02 Aug 2013 20:55:51 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1V5MO5-0005Ej-Da for bitcoin-development@lists.sourceforge.net;
Fri, 02 Aug 2013 20:55:51 +0000
Received: from ishibashi.localnet (6532239hfc101.tampabay.res.rr.com
[65.32.239.101]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 7061527A296E;
Fri, 2 Aug 2013 20:55:37 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 2 Aug 2013 20:55:26 +0000
User-Agent: KMail/1.13.7 (Linux/3.7.10-gentoo; KDE/4.10.5; x86_64; ; )
References: <CAE0e52VWbpeE+BYRhgOX0d9JppMhaXh5VdZVOT45wdybpwU0rg@mail.gmail.com>
In-Reply-To: <CAE0e52VWbpeE+BYRhgOX0d9JppMhaXh5VdZVOT45wdybpwU0rg@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201308022055.34056.luke@dashjr.org>
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 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1V5MO5-0005Ej-Da
Subject: Re: [Bitcoin-development] btc name server
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, 02 Aug 2013 20:55:51 -0000
Chris,
First, an important point: addresses are not wallet ids. They are single-use
destinations for a single transaction. It isn't intended that anyone should
remember them, just that they should send them electronically (or with eg, QR-
Codes). Bitcoin does not (yet?) have a person/wallet identity system, but
there are other mechanisms for this already (eg, PGP).
With regard to your idea, I believe it is satisfied by the new Payment
Protocol that Gavin has been working on. You will be able to publish a URI for
a website which people can reuse to pay you more than once.
Luke
On Friday, August 02, 2013 8:40:27 PM Chris Evans wrote:
> wonder if it would be good idea to have a alias to wallet id nameserver in
> the client software where a person can use a english name to describe a
> wallet public key address? and the software can use it to look up the
> wallet id.
>
> wallet ids are hard to remember/recall.
>
> -chris
> http://tawhakisoft.com/
|
