From: Gavin Andresen <gavinandresen@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>,
Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Multisignature transations
Date: Fri, 30 Sep 2011 13:57:38 -0400 [thread overview]
Message-ID: <CABsx9T0SJUNxzN90dzuTpKPxXQ8xNfOQXecftM0HN7bxN3XP_Q@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQG7iFPqSGNdCPCm=b11oHfsDW_d3NM472PJuvk-crjcA@mail.gmail.com>
RE: 2 of 3 being far more useful:
So create a clean pull request, unit tests, and test plan for an
"IsStandard" 2-of-3 transaction, either using CHECKMULTISIG or
groffers proposal:
0
OVER 2SWAP CHECKSIG SWAP HASH160 {pk1hash} EQUAL BOOLAND ADD
OVER 2SWAP CHECKSIG SWAP HASH160 {pk2hash} EQUAL BOOLAND ADD
OVER 2SWAP CHECKSIG SWAP HASH160 {pk3hash} EQUAL BOOLAND ADD
2 GREATERTHANOREQUAL
The low-level support is relatively easy, reporting these transactions
in listtransactions and figuring out if or how to report them in your
wallet balance is tricky.
I generated and then spent three multisig transactions on testnet:
http://blockexplorer.com/testnet/block/0000000000cfe382f690777e3b52ea255717122465db6fcfd80efdf2d0080d8b
Code I used to send them is:
https://github.com/gavinandresen/bitcoin-git/tree/multisig_testing
(that code is NOT intended for mainline bitcoin, I just needed a way
of testing the new transactions).
--
--
Gavin Andresen
prev parent reply other threads:[~2011-09-30 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 16:07 Gavin Andresen
2011-09-30 16:25 ` Mike Hearn
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 [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=CABsx9T0SJUNxzN90dzuTpKPxXQ8xNfOQXecftM0HN7bxN3XP_Q@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@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