1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <elombrozo@gmail.com>) id 1VI4oy-00025y-Kl
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Sep 2013 22:48:08 +0000
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;
Received: from mail-pb0-f52.google.com ([209.85.160.52])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VI4oq-0000MX-NE
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Sep 2013 22:48:08 +0000
Received: by mail-pb0-f52.google.com with SMTP id wz12so3744956pbc.39
for <bitcoin-development@lists.sourceforge.net>;
Fri, 06 Sep 2013 15:47:54 -0700 (PDT)
X-Received: by 10.66.234.131 with SMTP id ue3mr6276155pac.35.1378507674342;
Fri, 06 Sep 2013 15:47:54 -0700 (PDT)
Received: from [192.168.1.103] (cpe-72-130-129-115.san.res.rr.com.
[72.130.129.115])
by mx.google.com with ESMTPSA id yg3sm384400pab.16.1969.12.31.16.00.00
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 06 Sep 2013 15:47:53 -0700 (PDT)
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>
X-Mailer: Apple Mail (2.1503)
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(elombrozo[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VI4oq-0000MX-NE
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2013 22:48:08 -0000
--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--
|
