From: Gregory Maxwell <gmaxwell@gmail•com>
To: Alan Reiner <etotheipi@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Quote on BIP 16
Date: Sun, 29 Jan 2012 03:14:06 -0500 [thread overview]
Message-ID: <CAAS2fgQhfYfwrT6M8AVDRYETwS0WrXD7iYoxUvcPT3VMJm5ryA@mail.gmail.com> (raw)
In-Reply-To: <4F24D7C1.3070106@gmail.com>
On Sun, Jan 29, 2012 at 12:23 AM, Alan Reiner <etotheipi@gmail•com> wrote:
[snip]
> But gmaxwell has expressed some compelling reasons why plain multi-sig
> might be abused, which maybe suggests we don't want it ever considered
> standard...? I guess I'm not really promoting one thing or another, but
Be careful not to conflate multisig _addresses_ and P2S with multisig
output scripts in general.
Of the issues I raised only the size of the potentially unprunable
transaction outputs is an argument against multisig outputs which
aren't getting packed up in addresses.
Things like negotiated escrow arrangements can work okay either way.
I think P2SH is still better for these for two reasons: Reasonable
anti-spam behavior by network participant may make it hard to make
large output scripts (see above), but this isn't an issue yet... and
P2S(H) lets you use a separate escrow-maker tool for clients paying
into escrow without any knowledge or support of escrow transactions in
that client. This uncoupling is important both for general "feature
velocity" as well as providing a uniform feature set across bitcoin
services (e.g. you negotiate paying someone via escrow, you use a tool
to make a mutually agreed escrow configuration, but your funds are in
MTGOX— no issue if P2SH is widely used).
next prev parent reply other threads:[~2012-01-29 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 4:52 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 [this message]
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
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=CAAS2fgQhfYfwrT6M8AVDRYETwS0WrXD7iYoxUvcPT3VMJm5ryA@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=etotheipi@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