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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1UcIys-0008Lo-M6
for bitcoin-development@lists.sourceforge.net;
Tue, 14 May 2013 17:25:42 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.54 as permitted sender)
client-ip=209.85.219.54; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f54.google.com;
Received: from mail-oa0-f54.google.com ([209.85.219.54])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UcIyr-0008Vt-SC
for bitcoin-development@lists.sourceforge.net;
Tue, 14 May 2013 17:25:42 +0000
Received: by mail-oa0-f54.google.com with SMTP id o17so950439oag.41
for <bitcoin-development@lists.sourceforge.net>;
Tue, 14 May 2013 10:25:36 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.97.168 with SMTP id eb8mr15110910obb.89.1368552336517;
Tue, 14 May 2013 10:25:36 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.162.230 with HTTP; Tue, 14 May 2013 10:25:36 -0700 (PDT)
In-Reply-To: <CA+8xBpdmxpCPO77Nr=vDwsKAKTEU4PM4ButT3bDUkhA5tzc3Zw@mail.gmail.com>
References: <20130511045342.GA28588@petertodd.org>
<20130511102209.GA27823@netbook.cypherspace.org>
<CAPaL=UV7B2ULcUSBBQNWKc70PzGnveeF2WiWQE7msteZ6TZAbQ@mail.gmail.com>
<20130513105408.GB3393@netbook.cypherspace.org>
<CA+8xBpdmxpCPO77Nr=vDwsKAKTEU4PM4ButT3bDUkhA5tzc3Zw@mail.gmail.com>
Date: Tue, 14 May 2013 10:25:36 -0700
X-Google-Sender-Auth: Mozw1M9laVnnqsBV_gf6mAah7qc
Message-ID: <CANEZrP3zWyDm6rE9_71T0Td46Zg9N8k0HFUSf=DY+4-F0N9snA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: multipart/alternative; boundary=047d7b2e41e6dff3ce04dcb0eb27
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1UcIyr-0008Vt-SC
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] merged mining hashcash & bitcoin (Re:
Coinbase TxOut Hashcash)
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: Tue, 14 May 2013 17:25:42 -0000
--047d7b2e41e6dff3ce04dcb0eb27
Content-Type: text/plain; charset=UTF-8
> I've been thinking about a decentralized way to create an anonymous
> identity
This is the fidelity bond/anonymous passport idea that has been kicked
around in the forums quite a few times. I mentioned it on the tor-talk once
as a solution to the problem that you cannot create Google accounts via Tor
without a phone number. It's a good idea but not new. I have encouraged
people to implement a server that does it and then some integration for
MediaWiki, Wordpress or phpBB, as they're both quite common software that
gets a lot of spam and abuse. For instance we could use it on our own wiki
instead of paying the wiki operator (does anyone know what happens to those
funds by the way?).
You don't need GPG or anything like that - the transactions that spend to
fees also contain pubkeys in the inputs, which you own the private keys
for. So you can sign a challenge nonce from the server to prove ownership
of the "passport"/fidelity bond.
--047d7b2e41e6dff3ce04dcb0eb27
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I've been thinking about a decentralized way to create an anonymous<br>
identity</blockquote><div><br></div><div style>This is the fidelity bond/an=
onymous passport idea that has been kicked around in the forums quite a few=
times. I mentioned it on the tor-talk once as a solution to the problem th=
at you cannot create Google accounts via Tor without a phone number. It'=
;s a good idea but not new. I have encouraged people to implement a server =
that does it and then some integration for MediaWiki, Wordpress or phpBB, a=
s they're both quite common software that gets a lot of spam and abuse.=
For instance we could use it on our own wiki instead of paying the wiki op=
erator (does anyone know what happens to those funds by the way?).</div>
<div style><br></div><div style>You don't need GPG or anything like tha=
t - the transactions that spend to fees also contain pubkeys in the inputs,=
which you own the private keys for. So you can sign a challenge nonce from=
the server to prove ownership of the "passport"/fidelity bond.</=
div>
</div></div></div>
--047d7b2e41e6dff3ce04dcb0eb27--
|
