Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QZPsH-0002u7-N0 for bitcoin-development@lists.sourceforge.net; Wed, 22 Jun 2011 16:01:53 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of lavabit.com designates 72.249.41.33 as permitted sender) client-ip=72.249.41.33; envelope-from=bgroff@lavabit.com; helo=karen.lavabit.com; Received: from karen.lavabit.com ([72.249.41.33]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QZPsG-00051E-Rs for bitcoin-development@lists.sourceforge.net; Wed, 22 Jun 2011 16:01:53 +0000 Received: from a.earth.lavabit.com (a.earth.lavabit.com [192.168.111.10]) by karen.lavabit.com (Postfix) with ESMTP id 5514C11BB60; Wed, 22 Jun 2011 11:01:47 -0500 (CDT) Received: from lavabit.com (pppoe-212.28.72.39.araxinfo.com [212.28.72.39]) by lavabit.com with ESMTP id 6TY50CCQGI3I; Wed, 22 Jun 2011 11:01:47 -0500 Received: from 212.28.72.39 (SquirrelMail authenticated user bgroff) by lavabit.com with HTTP; Wed, 22 Jun 2011 12:01:47 -0400 (EDT) Message-ID: <26145.212.28.72.39.1308758507.squirrel@lavabit.com> In-Reply-To: References: <18440.87.106.138.84.1308200020.squirrel@lavabit.com> Date: Wed, 22 Jun 2011 12:01:47 -0400 (EDT) From: bgroff@lavabit.com To: "Mike Hearn" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid X-Headers-End: 1QZPsG-00051E-Rs Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] [PULL] Add scriptPubKey enforced sendescrow and redeemescrow API calls X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2011 16:01:53 -0000 > Oh, one other thing - as you point out yourself, escrow is only one use > case > for multsig transactions. So I suggest you don't use the word in the > patch. > Maybe instead call them multisign or multipay transactions. Agreed. I'll rename to multisign. -- Bobby Groff