From: "Jorge Timón" <jtimon@jtimon•cc>
To: Erik Aronesty <erik@q32•com>,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
Date: Fri, 12 Aug 2016 17:49:23 +0200 [thread overview]
Message-ID: <CABm2gDrBcq5Eipq1Rhq2sap=yKd_gWFtvQAB1Smc13DkNM9EUw@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgJBHq4YL47A5Ms=NhFL_uETBB7Q+XjETpAS=9o8EoSJMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
No, anyone with the bip32 public seed can do the same as the receiver as
"watch only". The only difference is rhat the receiver can actually spend
the coins. As gmaxwell explained, if it's expensive for everyone, it will
be also expensive for the receiver (assuming no interaction after the bip32
public seed is transfered).
Something different would be to give a different bip32 public seed to each
payer. That way they can simply start with zero an increment with each new
payment. With those assumptions, the receiver could start listening to new
addresses only after they receive something in the previous address.
Probably not useful for this case, just thinking out loud about using bip32
public seeds instead of one use addresses when there's going to be several
payments from the same payer to the payee.
On Aug 12, 2016 2:37 PM, "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: 2946 bytes --]
next prev parent reply other threads:[~2016-08-12 15:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 21:22 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 [this message]
2016-08-12 18:39 ` James MacWhyte
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='CABm2gDrBcq5Eipq1Rhq2sap=yKd_gWFtvQAB1Smc13DkNM9EUw@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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