From: Michael Gronager <gronager@ceptacle.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP0032
Date: Mon, 27 May 2013 15:39:19 +0200 [thread overview]
Message-ID: <51A36207.90307@ceptacle.com> (raw)
In-Reply-To: <51A35B2C.7060802@ceptacle.com>
Which again means that the statement regarding Audits through the Master
Public key, M, is wrong - only incoming and outgoing transaction of
_publicly_ derived wallets will be part of the audit... Privately
derived wallets cannot be obtained, though you could, without loss of
security, share also the addition points from privately derived wallets:
(m/i')*G, but there is no concept of a single public master key.
==
Audits: M
In case an auditor needs full access to the list of incoming and
outgoing payments, one can share the master public extended key. This
will allow the auditor to see all transactions from and to the wallet,
in all accounts, but not a single secret key.
==
next prev parent reply other threads:[~2013-05-27 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 9:41 [Bitcoin-development] BIP0032 Michael Gronager
2013-05-27 13:10 ` Michael Gronager
2013-05-27 13:39 ` Michael Gronager [this message]
2013-05-27 17:21 ` Amir Taaki
2013-05-27 20:45 ` Pieter Wuille
2013-05-28 5:16 Tamas Blummer
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=51A36207.90307@ceptacle.com \
--to=gronager@ceptacle.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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