summaryrefslogtreecommitdiff
path: root/f6/4f1e68782cc7d07c9137ddf811be4b12bfa527
blob: cade97c142b4227219bc1c63fa445c63cfab07c3 (plain)
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
152
153
154
Return-Path: <earonesty@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 28AB3724
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Aug 2016 12:36:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f175.google.com (mail-yw0-f175.google.com
	[209.85.161.175])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3A932135
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Aug 2016 12:36:33 +0000 (UTC)
Received: by mail-yw0-f175.google.com with SMTP id j12so14260250ywb.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Aug 2016 05:36:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc;
	bh=QCNGoG9HS7KyDU/kF+C4ISeONf/Jx6P7O976MmoGwKs=;
	b=nQUPu7F+G6IatpgmHszsEGjZQD+vW4Kolh+y2jBv9DP8FkbyOmoS5mWXc3xP55amC3
	hfy+xU8iyqNKg94ljfzabEvXNcKgY0Gnk4n09bc2Oxyb5GXC70Nj9DN0HbJ71g8Ss9M7
	gq+d2XqinklD9rRh98MO/ReK8U96rwHNhY4LeLkkkodTd9osaE0jHnLfKt7JkabjSuwp
	DC30Aul2UIzhaQs8DXu9cgUnEGzNpKX3AcJs8X3HFnB+JkT72Q6j/uXHxUAUE+7RvEi2
	DpNPodVddNY7ZA00KnDLFzXMrLNV3EQlHdzD5uLt4Zhd6zj7psEYbnWsZVEZarll/PR3
	GGKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
	:date:message-id:subject:to:cc;
	bh=QCNGoG9HS7KyDU/kF+C4ISeONf/Jx6P7O976MmoGwKs=;
	b=BDzl37aPPeVR1feaEgA/wfSDavkX4zYe0Oy4aErhGLGtRG9ZpaUbZvMH4wkKxdytwB
	FUyVNXUFgTjudN/sUlqEics3IcK9IYG7IDoA7OFjucAz2fC2Jb078qH9m1apLw91VyQt
	Bj6N2kLDUtlWW+xFsWoYt7baOKPJFYmX3/wZw5TIQ1aie6LoqFz4Den5xalByvIlLROX
	Yc2xpk09UZbQs3bCGMK8CxJdXop/CV9DDcd2QUDaorU8sA8omNL0XbhZSonMkSXBs94+
	hlmgWHQjgvIANDJGaAyxWIhALZQllbwLfSjwHQz/5VIgrsQTHaNNnUb6XbYq9+6zAkeD
	S9Kw==
X-Gm-Message-State: AEkooutgRkxbUYSONN7CSFVX4wbGplsiH2uyX9gwEh6vgERrOMaFQj6sKCPXazC1izjKDFxBVF0BzMaiPrUs1w==
X-Received: by 10.129.83.193 with SMTP id h184mr11500483ywb.52.1471005392391; 
	Fri, 12 Aug 2016 05:36:32 -0700 (PDT)
MIME-Version: 1.0
Sender: earonesty@gmail.com
Received: by 10.37.88.214 with HTTP; Fri, 12 Aug 2016 05:36:31 -0700 (PDT)
In-Reply-To: <CAAS2fgTrUKvG9Eff6jNhtKfiV9v8oMDsEA9rJaViYsw50Ub5sA@mail.gmail.com>
References: <CAL9WuQUUeR3cuUXHxUfBTNJ-+r0iJ-7Z8KRNub0G3NBujnkqcw@mail.gmail.com>
	<CABqynxJ3uph-4A+Ynq70CLa2kCCspTRsFWpKo_eP1FmVxZqSwQ@mail.gmail.com>
	<CALd2G5dERuX2n33MGZJ+mtM8WnvtzZcWDFFUfNFZEGJFkkHLDg@mail.gmail.com>
	<CAL9WuQUt+CMG2bEX+yv3LrFV7qn-=OSdn02ZxxPQci-3_ykPNQ@mail.gmail.com>
	<CAL9WuQXsbBJ0UwdS+o=UqJCcsebcPa9Ug5A=uNtc6Z+9CNEFPg@mail.gmail.com>
	<CAAS2fgR-weACn_Ezg8-uZuSH0QT5dfLEFE5WO2VDi0nx8H1e9g@mail.gmail.com>
	<CAE-z3OXeJHvjyF_phVh2u9S45_xss=C9ykL=BN=n=BxTx+AbrQ@mail.gmail.com>
	<CAJowKg+yh+PgTE14=+pPUXFdB_AGrsgk3cNSFnTGDYecsxDP5g@mail.gmail.com>
	<CAFh0iXOLN6B27Fkc=GXo-j3VwA0hkNggCiQOhR35R52yQGwSwg@mail.gmail.com>
	<CAL9WuQXH8TAKRabPSrZzMzpFBwmujdv-uSXJLeTt9u3H9WAFGw@mail.gmail.com>
	<CAJowKgK0N9VJZsm4fbZ5VvteUjoQkh9-xhg1yfcD3NRTuFV78Q@mail.gmail.com>
	<CAPg+sBi6mPviRRKysbuuOFKoYoyTufpUO_rJxJdB-8=7KGurYw@mail.gmail.com>
	<CAJowKg+0Oz7+Gdfm=NSO9MqOqSYV8Uo=nOMtkx3CBrsemK+BtQ@mail.gmail.com>
	<CAE-z3OU7XgqivsGLXMyd2_cVRE3Kw2FNLGBU261q39=hq9TnEw@mail.gmail.com>
	<CAJowKgL39qFpGAVTkNoUUR7-M2VJxqkQ=X6yK3aTsGLRAo59Jw@mail.gmail.com>
	<CAAS2fgTrUKvG9Eff6jNhtKfiV9v8oMDsEA9rJaViYsw50Ub5sA@mail.gmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Fri, 12 Aug 2016 08:36:31 -0400
X-Google-Sender-Auth: RkOsHP7uxAvAVVWE3k9FAItXuRY
Message-ID: <CAJowKgJBHq4YL47A5Ms=NhFL_uETBB7Q+XjETpAS=9o8EoSJMQ@mail.gmail.com>
To: Gregory Maxwell <greg@xiph.org>
Content-Type: multipart/alternative; boundary=001a114d6f1ce0664a0539df2116
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2016 12:36:37 -0000

--001a114d6f1ce0664a0539df2116
Content-Type: text/plain; charset=UTF-8

I'm imagining a "publishable seed" such that:

 - someone can derive a random bitcoin address from it -  and send funds to
it.
 - the possible derived address space is large enough that generating all
possible addresses would be a barrier
 - the receiver, however, knowing the private key, can easily scan the
blockchain fairly efficiently and determine which addresses he has the keys
to
 - another interested party cannot easily do so

Perhaps homomorphic encryption may need to be involved?


On Thu, Aug 11, 2016 at 8:36 PM, Gregory Maxwell <greg@xiph.org> wrote:

> On Thu, Aug 11, 2016 at 8:37 PM, Erik Aronesty via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > Still not sure how you can take a BIP32 public seed and figure out if an
> > address was derived from it though.   I mean, wouldn't I have to compute
> all
> > 2^31 possible public child addresses?
>
> Which would take a quad core laptop about 8 hours with competent software
>
> And presumably you're not using the whole 2^31 space else the receiver
> also has to do that computation...
>

--001a114d6f1ce0664a0539df2116
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;m imagining a &quot;publishable seed&quot; such=
 that:<br><br>=C2=A0- someone can derive a random bitcoin address from it -=
=C2=A0 and send funds to it. <br>=C2=A0- the possible derived address space=
 is large enough that generating all possible addresses would be a barrier<=
br></div><div>=C2=A0- the receiver, however, knowing the private key, can e=
asily scan the blockchain fairly efficiently and determine which addresses =
he has the keys to<br></div><div>=C2=A0- another interested party cannot ea=
sily do so<br></div><div><br></div><div>Perhaps homomorphic encryption may =
need to be involved?=C2=A0=C2=A0 <br></div><div><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Aug 11, 2016 at 8:3=
6 PM, Gregory Maxwell <span dir=3D"ltr">&lt;<a href=3D"mailto:greg@xiph.org=
" target=3D"_blank">greg@xiph.org</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><span class=3D"">On Thu, Aug 11, 2016 at 8:37 PM, Erik Arone=
sty via bitcoin-dev<br>
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.<wbr>linuxfoundation.org</a>&gt; wrote:<br>
&gt; Still not sure how you can take a BIP32 public seed and figure out if =
an<br>
&gt; address was derived from it though.=C2=A0 =C2=A0I mean, wouldn&#39;t I=
 have to compute all<br>
&gt; 2^31 possible public child addresses?<br>
<br>
</span>Which would take a quad core laptop about 8 hours with competent sof=
tware<br>
<br>
And presumably you&#39;re not using the whole 2^31 space else the receiver<=
br>
also has to do that computation...<br>
</blockquote></div><br></div>

--001a114d6f1ce0664a0539df2116--