From: Wladimir <laanwj@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisignature transaction support in the GUI
Date: Mon, 6 Feb 2012 19:03:35 +0100 [thread overview]
Message-ID: <CA+s+GJDvo9FbX9L2_zf3NC=aYjV6RiC=ssbZg5gDJXWxX6UqPg@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJC7N3k8n335mHa7hU-Lq4uO6mu1QBLX30G+68cBtDSg3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
On Mon, Feb 6, 2012 at 6:27 PM, Wladimir <laanwj@gmail.com> wrote:
> On Mon, Feb 6, 2012 at 5:07 PM, Gavin Andresen <gavinandresen@gmail.com>wrote:
>
>>
>> Advantage of (2) is it should mean more testing of multisig, and fewer
>> bug reports of "I added a multisig address via RPC but I can't send to
>> it using the GUI"
>>
>> My opinion: I think it is worth allowing send-to-multisig-address via
>> the GUI (should be a very simple change to the address validation
>> logic). But creating multisig addresses via the GUI should wait until
>> the next release.
>>
>
> I think we should go with (2), changing the maximum address length and
> validation is very easy. We'd need to
>
And maybe WalletModel::sendCoins has to be changed.
Does CScript.SetBitcoinAddress work for the new address type?
Wladimir
[-- Attachment #2: Type: text/html, Size: 1451 bytes --]
next prev parent reply other threads:[~2012-02-06 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 16:07 [Bitcoin-development] Multisignature transaction support in the GUI Gavin Andresen
2012-02-06 17:27 ` Wladimir
2012-02-06 18:03 ` Wladimir [this message]
2012-02-07 11:52 ` Aidan Thornton
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='CA+s+GJDvo9FbX9L2_zf3NC=aYjV6RiC=ssbZg5gDJXWxX6UqPg@mail.gmail.com' \
--to=laanwj@gmail.com \
--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