summaryrefslogtreecommitdiff
path: root/e7/0cecae6e8934f3e8a4848a52749f4462509ab6
blob: c29c5ac927e1ecf1edb7d3f191740340f9fff9b6 (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
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 532552C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Aug 2016 18:39:23 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f170.google.com (mail-qt0-f170.google.com
	[209.85.216.170])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5112F2C8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Aug 2016 18:39:19 +0000 (UTC)
Received: by mail-qt0-f170.google.com with SMTP id w38so16587574qtb.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Aug 2016 11:39:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to; 
	bh=XpemrAS83nqVhMdlgFhVMxggAl0W181DAnu9Gb94eZw=;
	b=rgT87ZBDHc2/5gt/rGw5PkU7c2lLdCl0lE6yR9Oy15Ylo1G/y61hZNn+qY62iThxw/
	bhkun/ndNKgbaS3Uo5F3Br6C9VHYC4BZDdvnEfsRlPZjnQHyNrS8lDXrz9v76l4DhKl0
	2KWpwmQkOUdn15ulcl1vQ/lsCEg2RS4be5SyvBdp8Anr+qggpCxkdkyIPXCl6PePmdlg
	00DNRjnfrVcQ6Lfpf9M6RDGUG7GJJI/+EseCOI88B2W/SlfAsSVmXLlVJ0JTAcM/jyRk
	DObH9IYwWaoYJa/M9gta8QZ16ryxbZUQAcAxaLRtfN2Lo8aw2WD4BnYbZPReZlHxh5xo
	P3nQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to;
	bh=XpemrAS83nqVhMdlgFhVMxggAl0W181DAnu9Gb94eZw=;
	b=MZHLaWUUHarRUqDMhehIIOeaZqYM30C5bcM/F5TGyE3p7zciX5LvdWqipBeF66AmjW
	D2fLShau2YwnxBaJ5MjZ16Ljq25rRMxsVa/NsaFcqi6/mh+g7zO5tiigITCXeV/nEO/w
	FsdA3EGqV/o5alI+R9oR4vCKoGLMgyTJf1wMksB8jIVrZ1s2Dg+CQWMIRftaDqszsjN5
	EW488OP7F771yW5eEf6Mom6I0d1QSPH7J4yW13bfGy6p22q3GK7cipZ26JDMIls8jSz5
	12lid05870DMHjLzbNGKE5o07fKm6ok0UUrO9RyyaM5zidFioENm9DIsGD6M5I6Wy5Xg
	sV7w==
X-Gm-Message-State: AEkoouvsx1wTryVZx0sK75qFaqindpx3oott7fb4yzVGPHXV6H/GYyln+t/k2dgUMz17brTy6YPrgAfm9vT4ig==
X-Received: by 10.200.55.137 with SMTP id d9mr19054345qtc.46.1471027158500;
	Fri, 12 Aug 2016 11:39:18 -0700 (PDT)
MIME-Version: 1.0
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>
	<CAJowKgJBHq4YL47A5Ms=NhFL_uETBB7Q+XjETpAS=9o8EoSJMQ@mail.gmail.com>
In-Reply-To: <CAJowKgJBHq4YL47A5Ms=NhFL_uETBB7Q+XjETpAS=9o8EoSJMQ@mail.gmail.com>
From: James MacWhyte <macwhyte@gmail.com>
Date: Fri, 12 Aug 2016 18:39:07 +0000
Message-ID: <CAH+Axy6WAk+ru8zJ3zU5L9-Rv3mY-YBg2V+U=yE7f5BnaNGqRw@mail.gmail.com>
To: Erik Aronesty <erik@q32.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Gregory Maxwell <greg@xiph.org>
Content-Type: multipart/alternative; boundary=001a113565163ccebd0539e433f0
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.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 18:39:23 -0000

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

For reasons others have pointed out, it's not really plausible.

Either way, this has nothing to do with transmitting data over audio.
Please start a new thread if you want to discuss your idea instead of
hijacking this one. Thanks ;)

On Fri, Aug 12, 2016, 05:36 Erik Aronesty via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> 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...
>>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<span>For reasons others have pointed out, it&#39;s not really plausible.</=
span><div><br></div><div>Either way, this has nothing to do with transmitti=
ng data over audio. Please start a new thread if you want to discuss your i=
dea instead of hijacking this one. Thanks ;)<br><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr">On Fri, Aug 12, 2016, 05:36 Erik Aronesty via bitcoin-=
dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-de=
v@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div dir=3D"ltr"><div>I&#39;m imagining a &quot;publishable seed&qu=
ot; such that:<br><br>=C2=A0- someone can derive a random bitcoin address f=
rom it -=C2=A0 and send funds to it. <br>=C2=A0- the possible derived addre=
ss space is large enough that generating all possible addresses would be a =
barrier<br></div><div>=C2=A0- the receiver, however, knowing the private ke=
y, can easily scan the blockchain fairly efficiently and determine which ad=
dresses he has the keys to<br></div><div>=C2=A0- another interested party c=
annot easily do so<br></div><div><br></div><div>Perhaps homomorphic encrypt=
ion may need to be involved?=C2=A0=C2=A0 <br></div><div><br></div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Aug 11, 2016=
 at 8:36 PM, Gregory Maxwell <span dir=3D"ltr">&lt;<a href=3D"mailto:greg@x=
iph.org" target=3D"_blank">greg@xiph.org</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><span>On Thu, Aug 11, 2016 at 8:37 PM, Erik Aronesty =
via bitcoin-dev<br>
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.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>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>

--001a113565163ccebd0539e433f0--