public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christopher Gilliard <christopher.gilliard@gmail.com>
To: yanmaani@cock.li
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Decentralized Naming Protocol BIP
Date: Thu, 22 Apr 2021 14:32:19 -0700	[thread overview]
Message-ID: <CAK=nyAztjLQV0tEaFdGCBMD5KcXag8qk_-nYapQZgWR+z8akXw@mail.gmail.com> (raw)
In-Reply-To: <7745d0c91c7e63bfe6095c250d7fcaf4@cock.li>

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

Yeah, kinda, but without the alt and integrated into the other systems that
I've proposed and it maps names to onion addresses instead of ips. It's
needed for some of the applications I've been thinking about.

On Thu, Apr 22, 2021 at 1:55 PM <yanmaani@cock.li> wrote:

> You appear to have reinvented Namecoin ;)
>
> On 2021-04-21 20:28, Christopher Gilliard via bitcoin-dev wrote:
> > I have created an additional BIP that is associated with the recent
> > BIPs that I have sent to the mailing list. This one defines a
> > decentralized naming protocol. The BIP can be found
> > here:https://github.com/cgilliard/bips/blob/naming/bip-XXXX.mediawiki
> >
> > Please reply with any feedback, questions, or comments.
> >
> > Regards,
> > Chris
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

      reply	other threads:[~2021-04-22 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 20:28 [bitcoin-dev] Decentralized Naming Protocol BIP Christopher Gilliard
2021-04-22 20:55 ` yanmaani
2021-04-22 21:32   ` Christopher Gilliard [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='CAK=nyAztjLQV0tEaFdGCBMD5KcXag8qk_-nYapQZgWR+z8akXw@mail.gmail.com' \
    --to=christopher.gilliard@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=yanmaani@cock.li \
    /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