<div class="gmail_quote">On Mon, Feb 6, 2012 at 5:07 PM, Gavin Andresen <span dir="ltr"><<a href="mailto:gavinandresen@gmail.com">gavinandresen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Advantage of (2) is it should mean more testing of multisig, and fewer<br>
bug reports of "I added a multisig address via RPC but I can't send to<br>
it using the GUI"<br>
<br>
My opinion: I think it is worth allowing send-to-multisig-address via<br>
the GUI (should be a very simple change to the address validation<br>
logic). But creating multisig addresses via the GUI should wait until<br>
the next release.<br></blockquote><div><br></div>I think we should go with (2), changing the maximum address length and validation is very easy. We'd need to</div><div class="gmail_quote"><ul><li>Change BitcoinAddressValidator::MaxAddressLength to 35</li>
<li>The addresses are validated with walletmodel->validateAddress which in turn calls CBitcoinAddress addressParsed(addr) and then isValid(). Does this work for the new addresses?</li></ul></div><div class="gmail_quote">
The set of allowed characters is still the same, so BitcoinAddressValidator doesn't have to be changed.</div><div class="gmail_quote"><br></div><div class="gmail_quote">Advanced dialogs for constructing the addresses / adding them to the address book could wait for 0.7.0.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">Wladimir</div><div class="gmail_quote"><br></div>