From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WUZmh-0006pK-1z for bitcoin-development@lists.sourceforge.net; Mon, 31 Mar 2014 10:49:43 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.182 as permitted sender) client-ip=209.85.212.182; envelope-from=natanael.l@gmail.com; helo=mail-wi0-f182.google.com; Received: from mail-wi0-f182.google.com ([209.85.212.182]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WUZmf-0000GU-SN for bitcoin-development@lists.sourceforge.net; Mon, 31 Mar 2014 10:49:43 +0000 Received: by mail-wi0-f182.google.com with SMTP id d1so3046552wiv.9 for ; Mon, 31 Mar 2014 03:49:35 -0700 (PDT) X-Received: by 10.180.99.225 with SMTP id et1mr11461472wib.13.1396262975646; Mon, 31 Mar 2014 03:49:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.54.34 with HTTP; Mon, 31 Mar 2014 03:49:14 -0700 (PDT) In-Reply-To: <5339418F.1050800@riseup.net> References: <5339418F.1050800@riseup.net> From: Natanael Date: Mon, 31 Mar 2014 12:49:14 +0200 Message-ID: To: vv01f Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (natanael.l[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WUZmf-0000GU-SN Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] secure assigned bitcoin address directory X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2014 10:49:43 -0000 Does't BIP70 cover this already via Certificate Authorities? On Mon, Mar 31, 2014 at 12:21 PM, 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. > > [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 >