public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] btc name server
Date: Fri, 2 Aug 2013 20:55:26 +0000	[thread overview]
Message-ID: <201308022055.34056.luke@dashjr.org> (raw)
In-Reply-To: <CAE0e52VWbpeE+BYRhgOX0d9JppMhaXh5VdZVOT45wdybpwU0rg@mail.gmail.com>

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/



  reply	other threads:[~2013-08-02 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 20:40 [Bitcoin-development] btc name server Chris Evans
2013-08-02 20:55 ` Luke-Jr [this message]
2013-08-02 21:16 ` Rick Wesson
2013-08-03  3:18   ` Jay F

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201308022055.34056.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox