Sender: Wendell <wendel@314t.com>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Wendell <w@grabhive.com>
In-Reply-To: <CANEZrP3srw4AhtYkM60NBcWYSqEib=wB7Yj4YtqaufW3xd9_0Q@mail.gmail.com>
Date: Tue, 17 Sep 2013 14:05:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BC93E25-27D2-474E-842D-6684E96E9472@grabhive.com>
References: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
	<AFD93558-684C-497C-ADAF-D031095EC2CE@gmail.com>
	<82E79EB0-49D6-492A-AE4A-6A786C7B0AAA@grabhive.com>
	<3B80F433-9039-459B-BC96-A56786DEF6C3@grabhive.com>
	<CANEZrP3srw4AhtYkM60NBcWYSqEib=wB7Yj4YtqaufW3xd9_0Q@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social
	network integration (brainstorm))
Precedence: list

Thanks Mike.

I definitely took all your comments to heart, but we're looking to =
road-test something quickly for the sake of user experience in our own =
wallet. I wouldn't mind us contributing to a BIP once we have a better =
grip on the payment protocol itself, but (for example) I'm still not =
sure that I understand _why_ signed certificates are even required. =
Isn't that likely be an obstacle to adoption for use cases like this?

-wendell

grabhive.com | twitter.com/grabhive | gpg: 6C0C9411

On Sep 17, 2013, at 12:03 PM, Mike Hearn wrote:

> You can prove ownership of a private key by signing a =
challenger-generated nonce with the public part and giving the signature =
back to the challenger - same as with any asymmetric crypto system.
>=20
> As I already noted, the payment protocol is designed to solve that =
problem. You could design a BIP that extended the payment protocol to =
include information about the person who generated it.
>=20
>> On Tue, Sep 17, 2013 at 11:30 AM, Wendell <w@grabhive.com> wrote:
>> Couple of things I just thought about:
>>=20
>> 1- Presume server should only sweep with two (or more, see below) =
revocation certificates being present
>> 2- Need to insert something in the flow so that Alice can verify that =
the uploaded key is actually Bob's (and perhaps vise-versa, given an =
extremely dedicated attacker with a fast connection?).
>>=20
>> Is there a way to do #2 without creating yet another transaction? =
Admittedly I am still really puzzled about the accessibility of public =
keys in Bitcoin!
>>=20
>> Please remember that the idea is to have two wallets securely =
exchange a packet of metadata about a transaction beyond the scope of =
Bitcoin itself (a name, perhaps a small photo, etc) in order to increase =
usability. This will be my last post here on the topic except to reply =
in case anyone else contributes.
>>=20
>> -wendell
>>=20
>> grabhive.com | twitter.com/grabhive | gpg: 6C0C9411