Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.111 as permitted sender)
	client-ip=62.13.148.111; envelope-from=pete@petertodd.org;
	helo=outmail148111.authsmtp.net; 
Date: Mon, 8 Jun 2015 17:36:11 -0400
From: Peter Todd <pete@petertodd.org>
To: Danny Thorpe <danny.thorpe@gmail.com>
Message-ID: <20150608213611.GB19826@muck>
References: <87k2vhfnx9.fsf@rustcorp.com.au>
	<CAJN5wHVSK-oW+zVZmEMfyFkd+GUHRhFHEjEmKrdvqas3LzY0zw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP"
Content-Disposition: inline
In-Reply-To: <CAJN5wHVSK-oW+zVZmEMfyFkd+GUHRhFHEjEmKrdvqas3LzY0zw@mail.gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Canonical input and output ordering
 in transactions
Precedence: list


--gatW/ieO32f1wygP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 08, 2015 at 02:25:40PM -0700, Danny Thorpe wrote:
> FWIW, The Open Assets colored coin protocol (CoinPrism) places special
> significance on the zeroth input and the position of the OP_RETURN colored
> coin marker output to distinguish colored coin issuance outputs from
> transfer outputs. Reordering the inputs or the outputs breaks the colored
> coin representation.
>=20
> Recommending sorting of the inputs and outputs as a best practice is fine
> (and better than random, IMO), but not as part of IsStandard() or consens=
us
> rules.  There are cases where the order of the inputs and outputs is
> significant.

Timestamping is another case where order matters: if you put the digest
in the last vout you can use SHA256 midstate's to reduce the size of the
timestamp proof.

Anyway, there's no reason to rush re: changes to IsStandard()

--=20
'peter'[:-1]@petertodd.org
0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778

--gatW/ieO32f1wygP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJVdgrIXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxMjdhYjFkNTc2ZGM4NTFmMzc0NDI0ZjEyNjljNDcwMGNj
YWJhMmM0MmQ5N2U3NzgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udzrkgf/ZorTEEarnrxYUQEGPEzbgzEH
49BN2NBAUBwSDO5kjwnr942mj2G+GOZKpnvrZs/WtKlYK3IO7r6QOb77AUphzcHB
UeXd2oVkul4k+rZqOV2JAqcesRIWEWN8igOBftbPcA34j3WpPu9JKU0gYRH0FbpS
FLUJaTgf1vrXRctdQhP0Wwu26ccCUCqUD98zvf/hLVloU/eBtI0pqpDDu8RIsSqS
uPxnMVIYvzhwCle0lvsxUlEdpR5IrzDysZXgh9J9YrtyVqVc2Uzs9PnXRUhboFMh
SJF3FjuVSNyQjIk6UE81FIDbMbXoYsXMf325+yPcrwpKW6Iy3UVd3dBOpZ9D0A==
=5Pf8
-----END PGP SIGNATURE-----

--gatW/ieO32f1wygP--