From: Erik Aronesty <erik@q32.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
Date: Thu, 11 Aug 2016 09:55:51 -0400 [thread overview]
Message-ID: <CAJowKg+0Oz7+Gdfm=NSO9MqOqSYV8Uo=nOMtkx3CBrsemK+BtQ@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBi6mPviRRKysbuuOFKoYoyTufpUO_rJxJdB-8=7KGurYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
Sorr, I thought there was some BIP for a public seed such that someone can
generate new random addresses, but cannot trivially verify whether an
address was derived from the seed.
On Wed, Aug 10, 2016 at 1:38 PM, Pieter Wuille <pieter.wuille@gmail.com>
wrote:
> On Wed, Aug 10, 2016 at 7:28 PM, Erik Aronesty via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > By sending a public seed, there's no way for someone to use the
> transmitted
> > address and trace the total amount of payments to it.
>
> Worse. By revealing a public seed, anyone who has seen it (= anyone
> who ever pays you through it) can identity all payments to _any_
> address derived from that seed.
>
> --
> Pieter
>
[-- Attachment #2: Type: text/html, Size: 1201 bytes --]
next prev parent reply other threads:[~2016-08-11 13:55 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 [this message]
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
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='CAJowKg+0Oz7+Gdfm=NSO9MqOqSYV8Uo=nOMtkx3CBrsemK+BtQ@mail.gmail.com' \
--to=erik@q32.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=pieter.wuille@gmail.com \
/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