From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisignature transations
Date: Fri, 30 Sep 2011 09:25:49 -0700 [thread overview]
Message-ID: <CANEZrP2fqvivhnjSDsLiYdYJ09E7y+=EmsVH3BvLmA4tGri7bQ@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T2QzafV-uzn7yL01gs2mrzLaP0FCgjt_O--Ldw+s-Xm9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
>
> This adds initial support for three new types of transactions:
> (a and b)
> (a or b)
> (a and b) or c
>
Does this mean dispute mediation (2-of-3) will not be supported? I thought
the plan was also to allow CHECKMULTISIG for smallish numbers of keys.
[-- Attachment #2: Type: text/html, Size: 431 bytes --]
next prev parent reply other threads:[~2011-09-30 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 16:07 [Bitcoin-development] Multisignature transations Gavin Andresen
2011-09-30 16:25 ` Mike Hearn [this message]
2011-09-30 16:32 ` Gregory Maxwell
2011-09-30 17:21 ` Gavin Andresen
[not found] ` <CAAS2fgRRws5iG_oirKbgmyySZMZ4tzOC2Nq_12psqeuSH4GyDg@mail.gmail.com>
2011-09-30 17:29 ` Gregory Maxwell
2011-09-30 17:57 ` Gavin Andresen
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='CANEZrP2fqvivhnjSDsLiYdYJ09E7y+=EmsVH3BvLmA4tGri7bQ@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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