Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WUfgz-0002EK-72 for bitcoin-development@lists.sourceforge.net; Mon, 31 Mar 2014 17:08:13 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.160.182 as permitted sender) client-ip=209.85.160.182; envelope-from=jgarzik@bitpay.com; helo=mail-yk0-f182.google.com; Received: from mail-yk0-f182.google.com ([209.85.160.182]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WUfgy-0004Yu-74 for bitcoin-development@lists.sourceforge.net; Mon, 31 Mar 2014 17:08:13 +0000 Received: by mail-yk0-f182.google.com with SMTP id 142so3450244ykq.41 for ; Mon, 31 Mar 2014 10:08:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=xxn3BlV+k1YAgkIQwIYtUovOLlpb2QyZPsR5Zzg9AhY=; b=Pk/QRX45TGQZdn3xzEkiAS6yxRlGbdC6mC3tC1r42b99z3u4tXQp9OvN/tNeuyMmHr fVKd3rXa8nwChpI0WK8AerUL1EFTKp0b19LMF52gDVWvbFMnV5IccyO3/3qzqd78kwCw 1Cv9Gp9HoD6PLs/GbMXeA9PS9i5wxYlMpYa71Ja1O1N+hGq4WQlTUnGEGSQCARc+6zs9 E/HndzfwErkZ+wGw9AjQHHO8OdryYGcHS5j51Ru7RKcFNlKF7UY/kCTZlvBN9WOmFWk6 5WpiKAKWseunWK67X/Z9eieMK+FUqWJnFbBj/ttkVii7VdckdvldcRn39IepSyXt5OLd QdGQ== X-Gm-Message-State: ALoCoQkomAYN0IpTmAXVUA+xX6ltZsfJrnYBrAJYyu2OMkaidN9EDMPnUbrBVOdkyq5hWIUVJ3Da X-Received: by 10.236.180.232 with SMTP id j68mr3598721yhm.122.1396285686551; Mon, 31 Mar 2014 10:08:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.162.214 with HTTP; Mon, 31 Mar 2014 10:07:46 -0700 (PDT) In-Reply-To: <5339418F.1050800@riseup.net> References: <5339418F.1050800@riseup.net> From: Jeff Garzik Date: Mon, 31 Mar 2014 13:07:46 -0400 Message-ID: To: vv01f Content-Type: text/plain; charset=ISO-8859-1 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 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: 1WUfgy-0004Yu-74 Cc: Bitcoin Dev 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 17:08:13 -0000 namecoin + SIN[1] or namecoin + PGP identity. [1] https://en.bitcoin.it/wiki/Identity_protocol_v1 On Mon, Mar 31, 2014 at 6:21 AM, 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 > -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/