public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: James MacWhyte <macwhyte@gmail.com>
To: Erik Aronesty <erik@q32.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>,
	Gregory Maxwell <greg@xiph.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
Date: Fri, 12 Aug 2016 18:39:07 +0000	[thread overview]
Message-ID: <CAH+Axy6WAk+ru8zJ3zU5L9-Rv3mY-YBg2V+U=yE7f5BnaNGqRw@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgJBHq4YL47A5Ms=NhFL_uETBB7Q+XjETpAS=9o8EoSJMQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 2629 bytes --]

  parent reply	other threads:[~2016-08-12 18:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 21:22 [bitcoin-dev] BIP Number Request: Addresses over Audio Daniel Hoffman
2016-08-08 22:06 ` Justin Newton
2016-08-08 22:35   ` Daniel Hoffman
2016-08-08 22:59   ` Trevin Hofmann
2016-08-09  1:50     ` Daniel Hoffman
2016-08-09 23:06       ` Daniel Hoffman
2016-08-10  0:17         ` Jannes Faber
2016-08-10  0:27         ` Chris Riley
2016-08-10  0:36         ` Luke Dashjr
2016-08-10  1:09         ` Thomas Daede
2016-08-10  1:53           ` Daniel Hoffman
2016-08-10  2:14         ` Gregory Maxwell
2016-08-10 10:41           ` Tier Nolan
2016-08-10 11:42             ` Erik Aronesty
2016-08-10 11:49               ` Theo Chino
2016-08-10 16:01                 ` Daniel Hoffman
2016-08-10 17:28                   ` Erik Aronesty
2016-08-10 17:38                     ` Pieter Wuille
2016-08-10 17:55                       ` Daniel Hoffman
2016-08-10 22:31                         ` James MacWhyte
2016-08-11 13:55                       ` Erik Aronesty
2016-08-11 15:13                         ` Tier Nolan
2016-08-11 20:37                           ` Erik Aronesty
2016-08-12  0:36                             ` Gregory Maxwell
2016-08-12 12:36                               ` Erik Aronesty
2016-08-12 15:49                                 ` Jorge Timón
2016-08-12 18:39                                 ` James MacWhyte [this message]
2016-08-13  4:41                                   ` Daniel Hoffman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+Axy6WAk+ru8zJ3zU5L9-Rv3mY-YBg2V+U=yE7f5BnaNGqRw@mail.gmail.com' \
    --to=macwhyte@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=erik@q32.com \
    --cc=greg@xiph.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox