From: Natanael <natanael.l@gmail.com>
To: vv01f <vv01f@riseup.net>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] secure assigned bitcoin address directory
Date: Mon, 31 Mar 2014 12:49:14 +0200 [thread overview]
Message-ID: <CAAt2M19HNUjr2OET5YjOB9YQKptOtVAmcPXWwoaxPHVTLOMYbg@mail.gmail.com> (raw)
In-Reply-To: <5339418F.1050800@riseup.net>
Does't BIP70 cover this already via Certificate Authorities?
On Mon, Mar 31, 2014 at 12:21 PM, vv01f <vv01f@riseup.net> wrote:
> Some users on bitcointalk[0] would like to have their vanity addresses
> available for others easily to find and verify the ownership over a kind
> of WoT. Right now they sign their own addresses and quote them in the
> forums.
> As I pointed out there already the centralized storage in the forums is
> not secury anyhow and signed messages could be swapped easily with the
> next hack of the forums.
>
> Is that use case taken care of in any plans already?
>
> I thought about abusing pgp keyservers but that would suit for single
> vanity addresses only.
> It seems webfinger could be part of a solution where servers of a
> business can tell and proof you if a specific address is owned by them.
>
> [0] https://bitcointalk.org/index.php?topic=502538
> [1] https://bitcointalk.org/index.php?topic=505095
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-03-31 10:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:21 [Bitcoin-development] secure assigned bitcoin address directory vv01f
2014-03-31 10:49 ` Natanael [this message]
2014-03-31 11:14 ` Chris D'Costa
2014-03-31 11:46 ` Natanael
2014-03-31 16:53 ` Chris D'Costa
2014-04-01 11:32 ` Jeff Garzik
2014-04-01 12:20 ` Chris D'Costa
2014-04-01 18:16 ` Daryl Banttari
2014-04-01 22:26 ` Chris D'Costa
2014-04-02 0:59 ` Daryl Banttari
2014-04-02 5:16 ` Chris D'Costa
2014-04-02 12:01 ` Mike Hearn
2014-03-31 11:21 ` Peter Todd
2014-03-31 17:07 ` Jeff Garzik
2014-03-31 18:57 ` Roy Badami
2014-04-01 8:13 ` Chris D'Costa
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=CAAt2M19HNUjr2OET5YjOB9YQKptOtVAmcPXWwoaxPHVTLOMYbg@mail.gmail.com \
--to=natanael.l@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=vv01f@riseup.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