From: Jay F <jayf@outlook•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] btc name server
Date: Fri, 2 Aug 2013 20:18:31 -0700 [thread overview]
Message-ID: <BLU0-SMTP22706C79EE7FF3C1DCEC577C8520@phx.gbl> (raw)
In-Reply-To: <CAJ1JLts7QKa3Et3xhnDFJpC0YV=X7LWjLeVjXgooLHw7WGiNqw@mail.gmail.com>
Namecoin already has an id/ and a/ (alias) namespace for such use:
{ "name" : "id/pichler", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 29397 },
{ "name" : "id/pigeons", "value" : "{ bitcoin:
1BekNv7ezkx8eAjdkrUta2BTp9bbxU9LGG, bitmessage:
BM-opfhTsUKdTezPiWFHxRQtM1ZMDvjKMkHf, ripple: rnziParaNb8nsU4aruQ
dwYE3j5jUcqjzFm}", "expires_in" : 10089 },
{ "name" : "id/pisces", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 32034 },
{ "name" : "id/plattler", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 30999 },
{ "name" : "id/pope", "value" : "{\n \"bitmessage\" :
\"BM-2D7L1Suh1choaKt321Le3bS6PT6nxfWqpR\"\n}", "expires_in" : 29765 },
It's popular enough that it's been squat spammed by a few actors
recently, and several bitmessage IDs are there along with Bitcoin
addresses, etc.
On 8/2/2013 2:16 PM, Rick Wesson wrote:
> 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
> <mailto: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
> <mailto:Bitcoin-development@lists•sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
prev parent reply other threads:[~2013-08-03 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 20:40 Chris Evans
2013-08-02 20:55 ` Luke-Jr
2013-08-02 21:16 ` Rick Wesson
2013-08-03 3:18 ` Jay F [this message]
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=BLU0-SMTP22706C79EE7FF3C1DCEC577C8520@phx.gbl \
--to=jayf@outlook$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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