Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <aaxiomfinity@gmail.com>) id 1V5M9L-00008r-AB for bitcoin-development@lists.sourceforge.net; Fri, 02 Aug 2013 20:40:35 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.193 as permitted sender) client-ip=209.85.214.193; envelope-from=aaxiomfinity@gmail.com; helo=mail-ob0-f193.google.com; Received: from mail-ob0-f193.google.com ([209.85.214.193]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V5M9J-0000PC-ID for bitcoin-development@lists.sourceforge.net; Fri, 02 Aug 2013 20:40:35 +0000 Received: by mail-ob0-f193.google.com with SMTP id dn14so820647obc.8 for <bitcoin-development@lists.sourceforge.net>; Fri, 02 Aug 2013 13:40:28 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.199.5 with SMTP id eq5mr747580icb.1.1375476028000; Fri, 02 Aug 2013 13:40:28 -0700 (PDT) Received: by 10.64.251.164 with HTTP; Fri, 2 Aug 2013 13:40:27 -0700 (PDT) Date: Fri, 2 Aug 2013 13:40:27 -0700 Message-ID: <CAE0e52VWbpeE+BYRhgOX0d9JppMhaXh5VdZVOT45wdybpwU0rg@mail.gmail.com> From: Chris Evans <aaxiomfinity@gmail.com> To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=20cf303346050bd22104e2fcf857 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 (aaxiomfinity[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: 1V5M9J-0000PC-ID Subject: [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:40:35 -0000 --20cf303346050bd22104e2fcf857 Content-Type: text/plain; charset=ISO-8859-1 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/ --20cf303346050bd22104e2fcf857 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div><div>wonder if it would be good idea to have a a= lias to wallet id nameserver in the client software where a person can use = a english name to describe a wallet public key address?=A0 and the software= can use it to look up the wallet id. <br> <br></div>wallet ids are hard to remember/recall.<br><br></div>-chris <br><= /div><a href=3D"http://tawhakisoft.com/">http://tawhakisoft.com/</a><br><br= ></div> --20cf303346050bd22104e2fcf857--