public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Rick Wesson <rick@support-intelligence.com>
To: Chris Evans <aaxiomfinity@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] btc name server
Date: Fri, 2 Aug 2013 14:16:09 -0700	[thread overview]
Message-ID: <CAJ1JLts7QKa3Et3xhnDFJpC0YV=X7LWjLeVjXgooLHw7WGiNqw@mail.gmail.com> (raw)
In-Reply-To: <CAE0e52VWbpeE+BYRhgOX0d9JppMhaXh5VdZVOT45wdybpwU0rg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

I'd raised this topic before suggesting to leverage DNS as its kinda useful
for mapping names to numbers.

Expect no support.

-rick

On Fri, Aug 2, 2013 at 1:40 PM, Chris Evans <aaxiomfinity@gmail.com> 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/
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 1921 bytes --]

  parent reply	other threads:[~2013-08-02 21:40 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
2013-08-02 21:16 ` Rick Wesson [this message]
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='CAJ1JLts7QKa3Et3xhnDFJpC0YV=X7LWjLeVjXgooLHw7WGiNqw@mail.gmail.com' \
    --to=rick@support-intelligence.com \
    --cc=aaxiomfinity@gmail.com \
    --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