public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: vv01f <vv01f@riseup.net>, Natanael <natanael.l@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] secure assigned bitcoin address directory
Date: Mon, 31 Mar 2014 13:21:14 +0200	[thread overview]
Message-ID: <20140331112114.GB30139@tilt> (raw)
In-Reply-To: <CAAt2M19HNUjr2OET5YjOB9YQKptOtVAmcPXWwoaxPHVTLOMYbg@mail.gmail.com> <5339418F.1050800@riseup.net>

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

On Mon, Mar 31, 2014 at 12:21:03PM +0200, vv01f 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.

Good timing! I'm at a hackathon right now working with a group to come
up with a standard for adding Bitcoin addresses to OpenPGP keys. You're
correct in thinking that doing so with standard Bitcoin addresses is a
privacy problem, however we can also define new types of Bitcoin
addresses that address the privacy issue; stealth addresses can handle
the case where you want to pay someone without a formal payment request,
and integrating OpenPGP into the payment protocol handles the scenario
where you want to send or pay to a formal payment request.


On Mon, Mar 31, 2014 at 12:49:14PM +0200, Natanael wrote:
> Does't BIP70 cover this already via Certificate Authorities?

Incidentally on my todo list is to come up for a reasonable standard for
taking X.509 certificates and using them to sign OpenPGP user IDs.
Essentially the certificate authority is then making the statement that
a keypair is authorized to sign on behalf of a domain-name, and in turn
that keypair signs that the email address on the user ID is correct.
It's a best of both worlds option in the same spirit of keybase.io

-- 
'peter'[:-1]@petertodd.org
0000000000000000f4f5ba334791a4102917e4d3f22f6ad7f2c4f15d97307fe2

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

  parent reply	other threads:[~2014-03-31 11:21 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
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 [this message]
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=20140331112114.GB30139@tilt \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=natanael.l@gmail.com \
    --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