From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XBl2z-00082B-U4 for bitcoin-development@lists.sourceforge.net; Mon, 28 Jul 2014 13:33:02 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.46 as permitted sender) client-ip=209.85.219.46; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f46.google.com; Received: from mail-oa0-f46.google.com ([209.85.219.46]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XBl2y-0004zl-9G for bitcoin-development@lists.sourceforge.net; Mon, 28 Jul 2014 13:33:01 +0000 Received: by mail-oa0-f46.google.com with SMTP id m1so8632158oag.5 for ; Mon, 28 Jul 2014 06:32:54 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.158.8 with SMTP id wq8mr21966701oeb.40.1406554374724; Mon, 28 Jul 2014 06:32:54 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Mon, 28 Jul 2014 06:32:54 -0700 (PDT) In-Reply-To: <5E988ED7-845D-4982-9240-155AACD20F66@coinqy.com> References: <5E988ED7-845D-4982-9240-155AACD20F66@coinqy.com> Date: Mon, 28 Jul 2014 15:32:54 +0200 X-Google-Sender-Auth: A8VgjxyKTMvoq6Ouz59bkPwBX4c Message-ID: From: Mike Hearn To: Mark van Cuijk Content-Type: multipart/alternative; boundary=047d7bd6ac48dce87f04ff40f595 X-Spam-Score: -0.5 (/) 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 commonly abused enduser mail provider (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 X-Headers-End: 1XBl2y-0004zl-9G Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] "On behalf of" BIP 70 extension proposal 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: Mon, 28 Jul 2014 13:33:02 -0000 --047d7bd6ac48dce87f04ff40f595 Content-Type: text/plain; charset=UTF-8 > > I referred to your idea in > https://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04076.html > which > is indeed not the proposal itself. > Right, gotcha. Had forgotten about that. Indeed there is another signature, which is to authenticate the payment > delegation. If you take it into account in the signature count, then your > proposal has three signatures. > Yes, I see now, you are right. A mandate type system is probably simpler indeed. So what now? To be honest my next priority with BIP70 was to formalise the extensions process, I've been dragging my feet over that because I'm working on other things. And then after that to knock some heads together over at BitPay/Coinbase and get them to put useful text in the memo field instead of random numbers. Baby steps .... --047d7bd6ac48dce87f04ff40f595 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I refer= red to your idea in=C2=A0https://ww= w.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg04076.htm= l=C2=A0which is indeed not the proposal itself.

Right, gotcha. Had forgotten about t= hat.

Indeed there is another signature, which is to authent= icate the payment delegation. If you take it into account in the signature = count, then your proposal has three signatures.

Yes, I see now, you are right. A mandate type system is= probably simpler indeed.

So what now? To be hones= t my next priority with BIP70 was to formalise the extensions process, I= 9;ve been dragging my feet over that because I'm working on other thing= s. And then after that to knock some heads together over at BitPay/Coinbase= and get them to put useful text in the memo field instead of random number= s. Baby steps ....
--047d7bd6ac48dce87f04ff40f595--