Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.52 as permitted sender)
	client-ip=209.85.160.52; envelope-from=elombrozo@gmail.com;
	helo=mail-pb0-f52.google.com; 
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_7A4EC4FC-CE49-475A-94E8-DAB64AF7A560";
	protocol="application/pgp-signature"; micalg=pgp-sha1
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
Date: Fri, 6 Sep 2013 15:47:50 -0700
Message-Id: <AFD93558-684C-497C-ADAF-D031095EC2CE@gmail.com>
References: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
To: Wendell <w@grabhive.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social
	network integration (brainstorm))
Precedence: list


--Apple-Mail=_7A4EC4FC-CE49-475A-94E8-DAB64AF7A560
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Why not just use the transaction hash itself for the lookup? Also, =
presumably you'd want to encrypt the data so that only the recipient of =
the transaction can do this lookup.

-Eric

On Sep 6, 2013, at 8:07 AM, Wendell <w@grabhive.com> wrote:

> Hi all,
>=20
> 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.
>=20
> The simplest version goes like this:
>=20
> 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.
>=20
> 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.
>=20
> Any thoughts about this?
>=20
> -wendell
>=20
> grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
>=20
> =
--------------------------------------------------------------------------=
----
> 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=3D58041391&iu=3D/4140/ostg.c=
lktrk_______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--Apple-Mail=_7A4EC4FC-CE49-475A-94E8-DAB64AF7A560
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJSKluWAAoJEAA1EyJsW9n+zUAQAORY0blYMUed1+nC9SBv8K4f
QeCtKLrD1ODSXQ6pxq7Zxjk45Icq3RtJKxP4WZDpqB2riYAUkjZ6tJuVVVJi3I3s
z77ymZdeKwP0qR0/tu055lTwnJOnubYrdf18m5xFoxbiFcb0LDLZPXJtXthXKKWd
mVJTuzmlRwxXDKNr9F7iDPkQQ2qpdPFXtNvf3yk8epapYpQ50H31yXXUGkrXHuuL
7aSBfuW1GpeMbTFEFPtfr48ThgpK3sPGNioFBpasntK+B2GW8QVD6agx5DgL0bTp
4MhiuF8SHHKSgnp0Ijt6empgIYCZbhMjCkuFFRZVv3g7X+KIsxFOSf8PrwjAlaaA
3ZH0c4afa7PitoX364X88lWuszT/gH3nxvWOVCvDiCPRxr/s4Bf8BJ6aGolKouN9
wUuzXPeTJ/nj1o6N2qYpjOTsgJwasK/tKqveJ0fbTtfLCCph+n4i2aD4bmcG2FH/
vqMr1WB1pNxnXLZPSD+FYRZDgRcmnac+cWOrBcEB94KJHHCIaEGrW3JmzzFUeOfj
N5923+r5ZG0TzfgvdRpGKswYg1v4OoJgirNuf6eShWWN/Q0ypq/GuOVkLpMDVa9W
MIY3j0RZoy9cGT/e52dgr7GOQshu6KZPWAXJpIY3cnexfhdalecVslA8JEMdD047
BV2lazf1Oe7XGmdqaQ8B
=Yzzv
-----END PGP SIGNATURE-----

--Apple-Mail=_7A4EC4FC-CE49-475A-94E8-DAB64AF7A560--