From: Gregory Maxwell <gmaxwell@gmail•com>
To: "Michael Grønager" <gronager@ceptacle•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Detecting OP_EVAL scriptPubKeys that are to you
Date: Wed, 26 Oct 2011 10:03:20 -0400 [thread overview]
Message-ID: <CAAS2fgTx8gEztUt-UrDObMCQtfdzZc52fzS6c1q8mm+a-TjwjQ@mail.gmail.com> (raw)
In-Reply-To: <7A50EE90-0FFC-45FB-A27F-786AEB23A8CA@ceptacle.com>
On Wed, Oct 26, 2011 at 4:58 AM, Michael Grønager <gronager@ceptacle•com> wrote:
> I think it is a very important feature to be able to extract transaction to/from you only from your private keys. In the standard transactions this is easily accomplished - in the case you only want to find the addr to tx mapping:
The additional material _IS_ then part of the private key. It's not
something seperate. Its something you need to know in order to author
the address. This was fundamentally my argument. Not that you could
hide information, but that information was already hidden.
Right now under conventional uses I can't identify all the
transactions that land in your wallet, because I don't know the keys
it contains. With the proposal it's the same situation.
> This possibility is used today in:
> * blockexplorer
> * bitcoin-js
> * my own tiered implementation for thin clients
[snip]
> So, if we introduce a standard (multikey) payment that hides the address (or makes it overly complicated to extract it) it will be a major problem for the projects that I listed above.
These projects will be able to use the _same_ procedure to extract the
identifying information. Except now instead of
ripemd160(sha256(pubkey)) it will be more like ripemd160(sha256([some
extra bytes generated by the wallet holder]||pubkey)) that you
extract. If the former is not a problem for these applications, why
is the latter?
next prev parent reply other threads:[~2011-10-26 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 10:49 Mike Hearn
2011-10-25 13:21 ` Gavin Andresen
2011-10-25 14:49 ` Gregory Maxwell
2011-10-25 16:47 ` Alan Reiner
2011-10-26 8:58 ` Michael Grønager
2011-10-26 14:03 ` Gregory Maxwell [this message]
2011-10-26 15:00 ` Gavin Andresen
2011-10-27 7:32 ` Michael Grønager
2011-10-27 9:08 ` Gregory Maxwell
2011-10-28 10:24 ` Michael Grønager
2011-10-29 17:01 ` Gavin Andresen
2011-10-31 8:50 ` Michael Grønager
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=CAAS2fgTx8gEztUt-UrDObMCQtfdzZc52fzS6c1q8mm+a-TjwjQ@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gronager@ceptacle$(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