From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VIvs5-0000ww-TT for bitcoin-development@lists.sourceforge.net; Mon, 09 Sep 2013 07:26:53 +0000 X-ACL-Warn: Received: from mail-ee0-f49.google.com ([74.125.83.49]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VIvs4-000272-Hy for bitcoin-development@lists.sourceforge.net; Mon, 09 Sep 2013 07:26:53 +0000 Received: by mail-ee0-f49.google.com with SMTP id d41so2907278eek.22 for ; Mon, 09 Sep 2013 00:26:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=IRZnLKGwmmNCDb5MbZIpmiIEmE1E7NXM6pvDzjRAKhw=; b=WfqCJ/9BmUuKv4DLwVDO6qf0tybjnbJSjgS+TToheQDe8xMXpvNoUV1zIn9FXkiLZC d+Ud2BhVNcarT2FSyKRHJskxQmBxMlOvY0hZSoWJhrWV33ukDUOs+3VFRnUJ7q4Ydil7 i3AbTvwT0tBOg++7ry1YmwxGyOy8jyegHqqmOrmppekYwMs14rBPRkcqDTmP4PvyHX2m aLmQ5yFuP8hEi57cFDxfqDHmvk2z7ChnJnnsb+sTjMghDyuJoVIkVp5y8MqMhxUiNiNW 2XYFvlb3422ycjZ37pkBNsxizd/NTHb4MQPvjX9bZF/TwEZjUjR179aDkDZHXd690LdO acYA== X-Gm-Message-State: ALoCoQkBm8gAVafslmmrLsahVf3cFyZVSlGJpPsweZ5Y7X7BH+vywpsPniyJpaqAG/2Za/mm5U6Z X-Received: by 10.14.39.73 with SMTP id c49mr124459eeb.61.1378711605673; Mon, 09 Sep 2013 00:26:45 -0700 (PDT) Received: from [127.0.0.1] (tor18.anonymizer.ccc.de. [31.172.30.1]) by mx.google.com with ESMTPSA id r48sm19683402eev.14.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 09 Sep 2013 00:26:44 -0700 (PDT) Sender: Wendell Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Wendell In-Reply-To: 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> To: Mike Hearn X-Mailer: Apple Mail (2.1283) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1VIvs4-000272-Hy Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social network integration (brainstorm)) 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, 09 Sep 2013 07:26:54 -0000 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.