public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: bgroff@lavabit•com
To: "Gavin Andresen" <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [PULL] Add scriptPubKey enforced sendescrow and redeemescrow API calls
Date: Wed, 22 Jun 2011 15:33:12 -0400 (EDT)	[thread overview]
Message-ID: <37401.137.56.163.46.1308771192.squirrel@lavabit.com> (raw)
In-Reply-To: <59140.77.247.181.162.1308759826.squirrel@lavabit.com>

> Gavin said:
>> 3DUP ADD  ADD HASH160 ...hash(pubkey1+2+3)... EQUALVERIFY 2 3 ROLL
>> CHECKMULTISIGVERIFY

On second thought, I'm not sure this is workable.  You would have to
distribute each party's pubkey ahead of time, otherwise you run the risk
that a party falls off the face of the earth and then you can't provide
the pubkeys to have hash(pubkey1+2+3) EQUALVERIFY.

If you have to distribute the pubkeys ahead of time, then the reduction in
address length becomes moot.

So it seems to be either distribute the pubkeys or distribute the
hash160(pubkey)'s.

--
Bobby Groff





  reply	other threads:[~2011-06-22 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  4:53 bgroff
2011-06-22 13:24 ` Mike Hearn
2011-06-22 13:42   ` Mike Hearn
2011-06-22 16:01     ` bgroff
2011-06-22 14:08   ` Gavin Andresen
2011-06-22 14:49     ` Mike Hearn
2011-06-22 15:32       ` Gavin Andresen
2011-06-22 16:02         ` Mike Hearn
2011-06-22 16:23         ` bgroff
2011-06-22 19:33           ` bgroff [this message]
2011-06-22 20:44         ` bgroff

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=37401.137.56.163.46.1308771192.squirrel@lavabit.com \
    --to=bgroff@lavabit$(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