From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TgvQf-0004BZ-IG for bitcoin-development@lists.sourceforge.net; Fri, 07 Dec 2012 10:45:13 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TgvQa-0005DC-5l for bitcoin-development@lists.sourceforge.net; Fri, 07 Dec 2012 10:45:13 +0000 Received: by mail-oa0-f47.google.com with SMTP id h1so272514oag.34 for ; Fri, 07 Dec 2012 02:45:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.227.5 with SMTP id rw5mr3016065obc.47.1354877102871; Fri, 07 Dec 2012 02:45:02 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.128.139 with HTTP; Fri, 7 Dec 2012 02:45:02 -0800 (PST) In-Reply-To: References: <20121128233619.GA6368@giles.gnomon.org.uk> <20121129170713.GD6368@giles.gnomon.org.uk> <20121129185330.GE6368@giles.gnomon.org.uk> <50C03BDA.6010600@petersson.at> Date: Fri, 7 Dec 2012 11:45:02 +0100 X-Google-Sender-Auth: v8gKRq15umXEbYQu1Lj1PJzUbr8 Message-ID: From: Mike Hearn To: Gavin Andresen Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.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 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: 1TgvQa-0005DC-5l Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts 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: Fri, 07 Dec 2012 10:45:13 -0000 > OK. I want to keep the signature field required, though, so how about: > > signature: digital signature over a protocol buffer serialized variation of > the SignedPaymentRequest message where signature is a zero-byte array and > fields are serialized in numerical order (all current protocol buffer > implementations serialize fields in numerical order), using the public key > in pki_data. Looks good to me.