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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WinPp-0007K7-6t for bitcoin-development@lists.sourceforge.net; Fri, 09 May 2014 16:12:53 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f181.google.com; Received: from mail-ob0-f181.google.com ([209.85.214.181]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WinPo-0000R9-72 for bitcoin-development@lists.sourceforge.net; Fri, 09 May 2014 16:12:53 +0000 Received: by mail-ob0-f181.google.com with SMTP id wm4so5076331obc.40 for ; Fri, 09 May 2014 09:12:46 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.132.236 with SMTP id ox12mr5234968oeb.81.1399651966704; Fri, 09 May 2014 09:12:46 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.162 with HTTP; Fri, 9 May 2014 09:12:46 -0700 (PDT) In-Reply-To: <20140509154313.GA17107@savin> References: <20140509150325.GA30436@savin> <20140509152715.GA12421@savin> <20140509154313.GA17107@savin> Date: Fri, 9 May 2014 18:12:46 +0200 X-Google-Sender-Auth: NiFi7-Ec3rfNb8zSH6IPGpKjcT0 Message-ID: From: Mike Hearn To: Peter Todd Content-Type: multipart/alternative; boundary=047d7b41cd2848e58904f8f9dedb 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: 1WinPo-0000R9-72 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] ECDH in the payment protocol 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, 09 May 2014 16:12:53 -0000 --047d7b41cd2848e58904f8f9dedb Content-Type: text/plain; charset=UTF-8 > > The exact same way you're proposing: via the payment protocol. > Ah, I see, that's what I was missing. So rather than have an explicit repeated field for nonces, have an algorithm for extracting randomness from one of the scriptSigs. I guess that makes sense. --047d7b41cd2848e58904f8f9dedb Content-Type: text/html; charset=UTF-8
The exact same way you're proposing: via the payment protocol.

Ah, I see, that's what I was missing. So rather than have an explicit repeated field for nonces, have an algorithm for extracting randomness from one of the scriptSigs. I guess that makes sense.
--047d7b41cd2848e58904f8f9dedb--