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: <CANEZrP1k9xsOESVL6yD+MvaO53Z9Fj_MifnquKi+2fcfk0uP4A@mail.gmail.com>
Date: Mon, 9 Sep 2013 09:26:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8641358D-7484-42AF-9449-C226EF4FB6B4@grabhive.com>
References: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
	<CANEZrP1k9xsOESVL6yD+MvaO53Z9Fj_MifnquKi+2fcfk0uP4A@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

OK, I was under the impression that this was mostly developed for =
merchants. I've seen some discussion here that seemed to suggest it =
requiring some non-trivial (for an end user) steps like getting a =
CA-signed certificate.

-wendell

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

On Sep 7, 2013, at 11:44 PM, Mike Hearn wrote:

> This is the sort of thing the payment protocol is for. The recipient =
would vend a PaymentRequest containing identity details. The sender =
would submit a Payment containing his/hers. The wallet then understands =
what to do.