Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 532552C for ; 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 ; Fri, 12 Aug 2016 18:39:19 +0000 (UTC) Received: by mail-qt0-f170.google.com with SMTP id w38so16587574qtb.0 for ; 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: In-Reply-To: From: James MacWhyte Date: Fri, 12 Aug 2016 18:39:07 +0000 Message-ID: To: Erik Aronesty , Bitcoin Protocol Discussion , Gregory Maxwell 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: > >> On Thu, Aug 11, 2016 at 8:37 PM, Erik Aronesty via bitcoin-dev >> 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 For reasons others have pointed out, it's not really plausible.

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 ;)

On Fri, Aug 12, 2016, 05:36 Erik Aronesty via bitcoin-= dev <bitcoin-de= v@lists.linuxfoundation.org> wrote:
I'm imagining a "publishable seed&qu= ot; such that:

=C2=A0- someone can derive a random bitcoin address f= rom it -=C2=A0 and send funds to it.
=C2=A0- the possible derived addre= ss space is large enough that generating all possible addresses would be a = barrier
=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
=C2=A0- another interested party c= annot easily do so

Perhaps homomorphic encrypt= ion may need to be involved?=C2=A0=C2=A0


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.=C2=A0 =C2=A0I 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 sof= tware

And presumably you're not using the whole 2^31 space else the receiver<= br> also has to do that computation...

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--001a113565163ccebd0539e433f0--