From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z1AfU-0000bz-C6 for bitcoin-development@lists.sourceforge.net; Sat, 06 Jun 2015 09:45:32 +0000 X-ACL-Warn: Received: from mail-ig0-f170.google.com ([209.85.213.170]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z1AfR-0002Ou-Lm for bitcoin-development@lists.sourceforge.net; Sat, 06 Jun 2015 09:45:32 +0000 Received: by igblz2 with SMTP id lz2so30271938igb.1 for ; Sat, 06 Jun 2015 02:45:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=gHJdJNMQX0PUBYYF3Z6pYQYC1sv6vipgMoDSHaOz8n0=; b=JRc/yalshdCQhcX+mDS3hKeSGIclyoftLHPCI4zOtZIAtS6776wak13bQWcb7cGFoM r71+3pMOwirmJmgLpfkb0HBuPxjfCzjXrGdmqN+sMfgPQ8ykpDjB+HfVj6CB4hCyC28a H0SbdwCnsAK84JzXPPqSmS8ltvTysHhuJ78cc5DSLlBqJMnjWUfblcdc8OL3qXlkoWN4 1xYhjOY+7A0QUpmHe5ij70riFVB0kDtGVJh251+2MUf4fo2ZVgkpr6GsNPtcFKEMOaDU +WCiU7riNd+gXSinbERu+Aksm0xquGxnMasRzBx1iEy1U5XdseYWe21D7GjW1Rjz52pu L1hg== X-Gm-Message-State: ALoCoQlPSuGD/IQGngIfpZmKD0Q0BFvIwJZ32Vx5gYlg7ICN2QfB9D+jJsG0uvrUQVn6FTMci9pA MIME-Version: 1.0 X-Received: by 10.50.27.6 with SMTP id p6mr2773324igg.46.1433583924204; Sat, 06 Jun 2015 02:45:24 -0700 (PDT) Received: by 10.107.10.197 with HTTP; Sat, 6 Jun 2015 02:45:23 -0700 (PDT) X-Originating-IP: [172.56.17.6] Received: by 10.107.10.197 with HTTP; Sat, 6 Jun 2015 02:45:23 -0700 (PDT) In-Reply-To: <20150606082447.GA12749@amethyst.visucore.com> References: <87k2vhfnx9.fsf@rustcorp.com.au> <20150606082447.GA12749@amethyst.visucore.com> Date: Sat, 6 Jun 2015 02:45:23 -0700 Message-ID: From: Mark Friedenbach To: Wladimir Content-Type: multipart/alternative; boundary=047d7b10ce478eee470517d644db X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1Z1AfR-0002Ou-Lm Cc: Bitcoin Development Subject: Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions 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: Sat, 06 Jun 2015 09:45:32 -0000 --047d7b10ce478eee470517d644db Content-Type: text/plain; charset=UTF-8 Certainly, but I would drop discussion of IsStandard or consensus rules. On Jun 6, 2015 1:24 AM, "Wladimir J. van der Laan" wrote: > On Fri, Jun 05, 2015 at 09:46:17PM -0700, Mark Friedenbach wrote: > > Rusty, this doesn't play well with SIGHASH_SINGLE which is used in > > assurance contracts among other things. Sometimes the ordering is set by > > the signing logic itself... > > But in that case (unconstrained) randomization can't be used either. This > is posed as an alternative to randomization. So in that regard, the > proposal still makes sense. > I think this move to verifyable, deterministic methods where possible is > good. > > Wladimir > --047d7b10ce478eee470517d644db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Certainly, but I would drop discussion of IsStandard or cons= ensus rules.

On Jun 6, 2015 1:24 AM, "Wladimir J. van de= r Laan" <laanwj@gmail.com&g= t; wrote:
On Fri, = Jun 05, 2015 at 09:46:17PM -0700, Mark Friedenbach wrote:
> Rusty, this doesn't play well with SIGHASH_SINGLE which is used in=
> assurance contracts among other things. Sometimes the ordering is set = by
> the signing logic itself...

But in that case (unconstrained) randomization can't be used either. Th= is is posed as an alternative to randomization. So in that regard, the prop= osal still makes sense.
I think this move to verifyable, deterministic methods where possible is go= od.

Wladimir
--047d7b10ce478eee470517d644db--