From: Gavin Andresen <gavinandresen@gmail•com>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fw: Quote on BIP 16
Date: Sun, 29 Jan 2012 09:30:10 -0500 [thread overview]
Message-ID: <CABsx9T2A8f64mh2-uSKwrjj9aEo0Z=jHyETQ5J9cka9JwyJqJw@mail.gmail.com> (raw)
In-Reply-To: <1327835984.12365.YahooMailNeo@web121002.mail.ne1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
On Sun, Jan 29, 2012 at 6:19 AM, Amir Taaki <zgenjix@yahoo•com> wrote:
> (oops sorry greg- replied to you by mistake)
>
> That address he gives is 77 characters/bytes (same thing). What I'm asking
> is how can it be so small.
That's an alternative design for multisig addresses that would put a byte
giving the type of transaction and the 20-byte hashes of each of the public
keys involved. They would not have been redeemed using CHECKMULTISIG, but
would use DUP HASH160 CHECKSIG and the arithmetic or logical opcodes to
create the "m of n" condition.
Nobody really liked that solution because it means a new 'type' of bitcoin
address every time we want a new transaction type and long addresses.
Its only advantage is it didn't use CHECKMULTISIG, so there were no
problems with maximum-sigops-per-block.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 1188 bytes --]
next prev parent reply other threads:[~2012-01-29 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 4:52 [Bitcoin-development] " Amir Taaki
2012-01-29 5:10 ` Amir Taaki
2012-01-29 5:15 ` Luke-Jr
2012-01-29 5:23 ` Alan Reiner
2012-01-29 8:14 ` Gregory Maxwell
2012-01-29 5:19 ` Gregory Maxwell
[not found] ` <1327835941.47827.YahooMailNeo@web121006.mail.ne1.yahoo.com>
2012-01-29 11:19 ` [Bitcoin-development] Fw: " Amir Taaki
2012-01-29 14:30 ` Gavin Andresen [this message]
2012-01-29 14:40 ` Luke-Jr
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='CABsx9T2A8f64mh2-uSKwrjj9aEo0Z=jHyETQ5J9cka9JwyJqJw@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(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