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 <mh.in.england@gmail.com>) id 1QZNhC-0002SW-6l for bitcoin-development@lists.sourceforge.net; Wed, 22 Jun 2011 13:42:18 +0000 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=mh.in.england@gmail.com; helo=mail-vx0-f175.google.com; Received: from mail-vx0-f175.google.com ([209.85.220.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QZNhB-0007p6-Dj for bitcoin-development@lists.sourceforge.net; Wed, 22 Jun 2011 13:42:18 +0000 Received: by vxa37 with SMTP id 37so871124vxa.34 for <bitcoin-development@lists.sourceforge.net>; Wed, 22 Jun 2011 06:42:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.176.74 with SMTP id cg10mr959490vdc.242.1308750131875; Wed, 22 Jun 2011 06:42:11 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.52.155.38 with HTTP; Wed, 22 Jun 2011 06:42:11 -0700 (PDT) In-Reply-To: <BANLkTi=FTLnU-riNVYssnR9FLdcEeZX7gOS6Zdv1f_XDcJoSSg@mail.gmail.com> References: <18440.87.106.138.84.1308200020.squirrel@lavabit.com> <BANLkTi=FTLnU-riNVYssnR9FLdcEeZX7gOS6Zdv1f_XDcJoSSg@mail.gmail.com> Date: Wed, 22 Jun 2011 15:42:11 +0200 X-Google-Sender-Auth: u6B0QIwMznXWWMSsU1nE4AMp6fI Message-ID: <BANLkTin112Lriqg7cMo3P3WnFvVrcYPEK1d_T5x8Xcgf_gTc8Q@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: bgroff@lavabit.com Content-Type: multipart/alternative; boundary=20cf307f34c2b5cf9204a64d22e6 X-Spam-Score: -0.7 (/) 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 FREEMAIL_FROM Sender email is freemail (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain 0.0 T_TO_NO_BRKTS_FREEMAIL T_TO_NO_BRKTS_FREEMAIL -0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QZNhB-0007p6-Dj 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: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Wed, 22 Jun 2011 13:42:18 -0000 --20cf307f34c2b5cf9204a64d22e6 Content-Type: text/plain; charset=UTF-8 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. --20cf307f34c2b5cf9204a64d22e6 Content-Type: text/html; charset=UTF-8 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.<br> --20cf307f34c2b5cf9204a64d22e6--