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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wendel@314t.com>) id 1VHxdp-0001bR-0c
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Sep 2013 15:08:09 +0000
X-ACL-Warn:
Received: from mail-pb0-f45.google.com ([209.85.160.45])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VHxdn-0007TP-0c
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Sep 2013 15:08:08 +0000
Received: by mail-pb0-f45.google.com with SMTP id mc17so3333558pbc.32
for <bitcoin-development@lists.sourceforge.net>;
Fri, 06 Sep 2013 08:08:00 -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:from:content-type:date:subject:to
:message-id:mime-version;
bh=NZxcUiXn9/lCiCsKfeGbmlF5YYlataQsrhW5ZIYXa8A=;
b=c8cUhT7eyFzrlNiFOeYIk9WTUuYT4WaVu3U9qBbS195AbQhTHLJF0ILqhYwTAXhm2R
GN4mNYTdp7l4AgUWpRbg0N0MsCmFQR6mbxhBghgfGK14gdEtG2f1nXRKR9X8Wp0uZZSj
NWBHZNhgmHffb5AC8Wu0pv6ztZo6QUukJy/iz/JjAs0jOchs04s+iQ3FzVIEQQGs0DG0
DHG/zGZv+GSraejx65Oz3qizTDi4ernCXXTfiQYAxZ18R6Bl6VS4C1APIftUuD89bdj/
6cz1HYLzngga7VfCg9P1dH+PfhRj4jNkRj5ijrxu9X27rDMhFlOdC+dayjgCl6+5+Mlx
IHMw==
X-Gm-Message-State: ALoCoQn1epZgSxCYmNwN5DQo0BBNn2nUzk0cznxCn3n0hay01YzCpGaIooaMtlHvsciP2Qer6e4I
X-Received: by 10.66.249.231 with SMTP id yx7mr4640566pac.116.1378480080566;
Fri, 06 Sep 2013 08:08:00 -0700 (PDT)
Received: from [127.0.0.1] (manning1.torservers.net. [96.44.189.100])
by mx.google.com with ESMTPSA id gh9sm264962pbc.40.1969.12.31.16.00.00
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Fri, 06 Sep 2013 08:08:00 -0700 (PDT)
Sender: Wendell <wendel@314t.com>
From: Wendell <w@grabhive.com>
Content-Type: multipart/signed;
boundary="Apple-Mail=_0C6A3205-05F9-4760-8277-1AC872F55E2C";
protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Fri, 6 Sep 2013 17:07:44 +0200
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-Id: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
Mime-Version: 1.0 (Apple Message framework v1283)
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: 1VHxdn-0007TP-0c
Subject: [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 15:08:09 -0000
--Apple-Mail=_0C6A3205-05F9-4760-8277-1AC872F55E2C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
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
--Apple-Mail=_0C6A3205-05F9-4760-8277-1AC872F55E2C
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-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
iQIcBAEBAgAGBQJSKe/BAAoJECAN2ykHU5Y62OYQAIwype5tED9MIJB3OTmhSlae
8CzssWVEQIfNyjRqNgkCR8ObcvJAnjBaPcdoM7qE6tfUBttiHH1wvmxJTLt3NmC0
o+Q+xc1SFqQXN26RDFh+tytkbBqsmm3prO6hCPLiO+8U8+9ljfleKXS6OvOp4q+e
3iwN/ddgS0dl+BJ9jRGCXRndy1XZeYLhx4nGaOw/GyDDSTgDxM96zXIS3PfQgQhd
CbCtCBy4erSmHTFakANv1dj9BdvmxQ7uU2/YQRqbcZXYoOyubulgMb7QKbRMgEcE
T8pBJzANrCUupI4kHMlXCORyT9yMSV8yKlprjayMJRd9Hp/LGIwoSWctSZATssYe
C1Hy6++pyyjmyCXG02x57CpHNRoQ2ehA0LA9qZy92cPBDX+RCJOrCSuwAo/XlGlp
GXE6gwGRDtz0htdMhBOwR8IvyvFHCWFuNhKbMpVc83L5cpbfzwkwbEY2Z1JTg4V5
TtxwtL/o9EP4SnQtmX0sVDYz8CZpHfIpaD2TeGzE46vuiTl8AWSEb+Ws6Tw5pmY6
yBJCZ6wOiVQaZPVxvK01Fv0vZnudOszVBFP3W/FdnSCZJzQPKCGxCl/mjiICEGfV
DpJSNit5D9TVg3hayiak2kw9F3KTieBF+1tPjTrtojlNlzXQRUyWxpLiuWOVYEUc
/sU3FazZ57zwoDXz8pb+
=KwTD
-----END PGP SIGNATURE-----
--Apple-Mail=_0C6A3205-05F9-4760-8277-1AC872F55E2C--
|
