Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=etotheipi@gmail.com;
	helo=mail-vx0-f175.google.com; 
Message-ID: <4EAB2C8E.6040103@gmail.com>
Date: Fri, 28 Oct 2011 18:28:30 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Bitcoin-development] Multi-sig tx execution ideas
Precedence: list

I just posted BIP 0010 to gist : https://gist.github.com/1321518

The goal is to provide a standard method for proposing how to spend 
multi-sig TxOuts, and collect signatures without actually having to 
understand BTC under-the-hood.  I envision, even without any program 
installed, moderately-interested users could figure out this process 
without a third-party.  The addition of an installed program that 
automatically detects .txdp files and intelligently presents the 
information to the users, could bring this functionality to even more 
users.  Perhaps I'm too optimistic, though...

This is, of course, open for discussion/improvement.  I've talked 
briefly with Gavin about this, and he suggested Base64 instead of hex 
for the block-encoding.  I'd lean towards Base58 because developers 
already have it in their codebase.  Also, the separation of fields by 
underscore characters could be changed.  Spaces would make it easier for 
C++ to read them in using stream operators "<<" and ">>".

-Alan