Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.42 as permitted sender)
	client-ip=209.85.219.42; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f42.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
References: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
Date: Sat, 7 Sep 2013 23:44:38 +0200
Message-ID: <CANEZrP1k9xsOESVL6yD+MvaO53Z9Fj_MifnquKi+2fcfk0uP4A@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wendell <w@grabhive.com>
Content-Type: multipart/alternative; boundary=089e0111d5ead44a8a04e5d20f05
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social
 network integration (brainstorm))
Precedence: list

--089e0111d5ead44a8a04e5d20f05
Content-Type: text/plain; charset=UTF-8

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.


On Fri, Sep 6, 2013 at 5:07 PM, Wendell <w@grabhive.com> wrote:

> Hi all,
>
> We're thinking about ways of automatically exchanging contact details
> between wallets, in order to encourage the proliferation of identifiable
> names and photos rather than long and hard-to-verify addresses.
>
> The simplest version goes like this:
>
> 2 BTC Bitcoin is sent to someone, and a data lookup hash is inserted into
> the transaction. When it arrives on the other end, it is indeed looked up,
> and instead of being presented with a dialogue that says "you received 2
> BTC from 13Y94z43Nbbb6wevRyk82CeDoYQ5S28zmA", it's "You received 2 BTC from
> Frank Jones" including a nice photo.
>
> Now. We can simply delete this data in reference to the transaction ID
> after it happens (or delete it after a time), but is there any more
> decentralized way to do it? I would prefer us to run no dedicated servers
> that would ever put us in a position of being coerced into giving data, or
> otherwise altering our system to store it.
>
> Any thoughts about this?
>
> -wendell
>
> grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
>
>
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

--089e0111d5ead44a8a04e5d20f05
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is the sort of thing the payment protocol is for. The=
 recipient would vend a PaymentRequest containing identity details. The sen=
der would submit a Payment containing his/hers. The wallet then understands=
 what to do.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Sep 6=
, 2013 at 5:07 PM, Wendell <span dir=3D"ltr">&lt;<a href=3D"mailto:w@grabhi=
ve.com" target=3D"_blank">w@grabhive.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
Hi all,<br>
<br>
We&#39;re thinking about ways of automatically exchanging contact details b=
etween wallets, in order to encourage the proliferation of identifiable nam=
es and photos rather than long and hard-to-verify addresses.<br>
<br>
The simplest version goes like this:<br>
<br>
2 BTC Bitcoin is sent to someone, and a data lookup hash is inserted into t=
he transaction. When it arrives on the other end, it is indeed looked up, a=
nd instead of being presented with a dialogue that says &quot;you received =
2 BTC from 13Y94z43Nbbb6wevRyk82CeDoYQ5S28zmA&quot;, it&#39;s &quot;You rec=
eived 2 BTC from Frank Jones&quot; including a nice photo.<br>

<br>
Now. We can simply delete this data in reference to the transaction ID afte=
r it happens (or delete it after a time), but is there any more decentraliz=
ed way to do it? I would prefer us to run no dedicated servers that would e=
ver put us in a position of being coerced into giving data, or otherwise al=
tering our system to store it.<br>

<br>
Any thoughts about this?<br>
<br>
-wendell<br>
<br>
<a href=3D"http://grabhive.com" target=3D"_blank">grabhive.com</a> | <a hre=
f=3D"http://twitter.com/grabhive" target=3D"_blank">twitter.com/grabhive</a=
> | gpg: 6C0C9411<br>
<br>
<br>-----------------------------------------------------------------------=
-------<br>
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!<br>
Discover the easy way to master current and previous Microsoft technologies=
<br>
and advance your career. Get an incredible 1,500+ hours of step-by-step<br>
tutorial videos with LearnDevNow. Subscribe today and save!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D58041391&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D58041391&amp;iu=3D/4140/ostg.clktrk</a><br>___________________=
____________________________<br>

Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>

--089e0111d5ead44a8a04e5d20f05--