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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <drak@zikula.org>) id 1W1aGr-0003Tb-NW
for bitcoin-development@lists.sourceforge.net;
Fri, 10 Jan 2014 11:29:01 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
designates 74.125.82.48 as permitted sender)
client-ip=74.125.82.48; envelope-from=drak@zikula.org;
helo=mail-wg0-f48.google.com;
Received: from mail-wg0-f48.google.com ([74.125.82.48])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W1aGq-0004zL-Sr
for bitcoin-development@lists.sourceforge.net;
Fri, 10 Jan 2014 11:29:01 +0000
Received: by mail-wg0-f48.google.com with SMTP id x13so3881217wgg.15
for <bitcoin-development@lists.sourceforge.net>;
Fri, 10 Jan 2014 03:28:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=D/66s+0U2OKOlK8Pm7BVAvfdeti0F80Xgxo9aljDEDU=;
b=MAOLhZnhMzSN1wMsuc1ICYaNhhSMwiT+Wx7nCJh7TGtNy8W56Y74iWWybuTLZjI+XQ
5oZb3YAAHi83QGs9mqcVleQL10Ax+PC467kdrliJxzUNPIyITKPET31dUWoXROGYgXFg
7ZPMy/W4MQB6Gfu5SJK/z5mJNvqwO8Mwo0OCthf+aSu97eKvnaK9AcWxl9LS/jlgm1Bm
xAW6A1X7rRFRkQ8bm9CkZGw6nDIYxX4G46AxhyKjXCOpnhv+gDjINqjwHk0kOUdJLKH5
jK+BPh3an+aizk5hK8WfR1DmO5BDpNYPB2FZQ+lDyW4c1zbrMbSw0ol9r88OOuvDr6iM
7prg==
X-Gm-Message-State: ALoCoQkJZe/vfo2nA3/gWFpWKl1MUBcAVJsZUQMe1qJKDrlpq8Ingqm+bToFHqNOYAjdtxSAQYrv
X-Received: by 10.180.97.39 with SMTP id dx7mr2242068wib.10.1389353334658;
Fri, 10 Jan 2014 03:28:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.30.8 with HTTP; Fri, 10 Jan 2014 03:28:33 -0800 (PST)
In-Reply-To: <20140110102037.GB25749@savin>
References: <20140106120338.GA14918@savin>
<op.w9c5o7vgyldrnw@laptop-air.hsd1.ca.comcast.net>
<20140110102037.GB25749@savin>
From: Drak <drak@zikula.org>
Date: Fri, 10 Jan 2014 11:28:33 +0000
Message-ID: <CANAnSg1TDFrEugAp_srg=kMHLJ9KUTrT1NKmQhfH0cNRPiscbw@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=f46d04428f22faf17f04ef9c07e9
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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1W1aGq-0004zL-Sr
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Stealth Addresses
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, 10 Jan 2014 11:29:01 -0000
--f46d04428f22faf17f04ef9c07e9
Content-Type: text/plain; charset=UTF-8
On 10 January 2014 10:20, Peter Todd <pete@petertodd.org> wrote:
> Oh, sorry, I forgot to mention it in my first write-up but you can
> easily make stealth addresses include a second pubkey for the purpose of
> the communication that either isn't used in the scriptPubKey at all, or
> is part of a n-of-m multisig. (n>=2) Interestingly that also means you
> can give a third-party that key and out-source the effort of scanning
> the blockchain for you.
That seems pretty exciting to me. What is the chance of this becoming a BIP?
Drak
--f46d04428f22faf17f04ef9c07e9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
0 January 2014 10:20, Peter Todd <span dir=3D"ltr"><<a href=3D"mailto:pe=
te@petertodd.org" target=3D"_blank">pete@petertodd.org</a>></span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><span style=3D"color:rgb(34,34,34)">Oh, sorry, I forgot t=
o mention it in my first write-up but you can</span><br></div>
easily make stealth addresses include a second pubkey for the purpose of<br=
>
the communication that either isn't used in the scriptPubKey at all, or=
<br>
is part of a n-of-m multisig. (n>=3D2) Interestingly that also means you=
<br>
can give a third-party that key and out-source the effort of scanning<br>
the blockchain for you.</blockquote><div><br></div><div>That seems pretty e=
xciting to me. What is the chance of this becoming a BIP?</div><div><br></d=
iv><div>Drak=C2=A0</div></div></div></div>
--f46d04428f22faf17f04ef9c07e9--
|
