From: "Michael Grønager" <gronager@ceptacle•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Detecting OP_EVAL scriptPubKeys that are to you
Date: Mon, 31 Oct 2011 09:50:49 +0100 [thread overview]
Message-ID: <267605F1-9DEA-4870-81C3-C27E11850AD2@ceptacle.com> (raw)
In-Reply-To: <CABsx9T09Eksb2=GHaNq+UQnVq5BYeaUn0Uc6SUwZ08-2H_ViGQ@mail.gmail.com>
>
> How would I know that unless you told me?
At least you would have a hunch that something like that had happened as one of your addresses had been part of a transaction (at least in my setup it would pop up immediately...).
>
> I think the right long-term solution is moving away from bitcoin
> addresses as 'pay-to entity' and create an infrastructure where we're
> paying people or organizations.
I am not sure what you mean by this - just recall that the semi anonymously feature of bitcoin is one of its key features.
> But in the short term, I think there
> are lots of benefits to creating a new type of bitcoin address built
> on top of OP_EVAL that will be very easy for all of our existing
> infrastructure to support.
Still, how do you solve the end less expansions of bitcoin addresses that each, depending of a leading 1, 2, 3... means a quite specific script inside the OP_EVAL ??? Its not esthetic...
Cheers,
M
>
> --
> --
> Gavin Andresen
prev parent reply other threads:[~2011-10-31 8:51 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
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 [this message]
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=267605F1-9DEA-4870-81C3-C27E11850AD2@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(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