Date: Thu, 22 Oct 2015 21:22:48 -0400
From: Peter Todd <pete@petertodd.org>
To: Justus Ranvier <justus@openbitcoinprivacyproject.org>
Message-ID: <20151023012248.GD22161@savin.petertodd.org>
References: <201510220554.00367.luke@dashjr.org>
	<5628F8D2.1010709@openbitcoinprivacyproject.org>
	<201510222043.17582.luke@dashjr.org>
	<56294E12.60301@openbitcoinprivacyproject.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="cHMo6Wbp1wrKhbfi"
Content-Disposition: inline
In-Reply-To: <56294E12.60301@openbitcoinprivacyproject.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin-development] Reusable payment codes
Precedence: list


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

On Thu, Oct 22, 2015 at 03:58:58PM -0500, Justus Ranvier via bitcoin-dev wr=
ote:
> On 22/10/15 15:43, Luke Dashjr wrote:
> > BIPs should in general not be=20
> > designed around current software
>=20
> I strongly disagree with this statement.
>=20
> There is a version byte in the payment code specification for a reason.
>=20
> Version 1 payment codes are designed to be deployable by wallet
> implementers today, without requiring them to wait on any network-level
> changes whatsoever, which includes IsStandard() redefinitions, or
> yet-to-be-invented-and-deployed filtering schemes.
>=20
> As far as I know, multi-push OP_RETURN outputs are not standard
> transactions and so wallet users can not rely on transactions containing
> them to be relayed through the network, therefore any improvement to the
> protocol which requires that feature is not appropriate for version 1.

FWIW multi-push OP_RETURN outputs will be standard in v0.12.0:

https://github.com/bitcoin/bitcoin/pull/6424

--=20
'peter'[:-1]@petertodd.org
0000000000000000066dc6b040d8be42153f784df37745b46c4ad667e0788781

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

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

iQGrBAEBCACVBQJWKYvlXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwNjZkYzZiMDQwZDhiZTQyMTUzZjc4NGRmMzc3NDViNDZj
NGFkNjY3ZTA3ODg3ODEvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfuY6AgAqqLUTvE4litxuCdN5J+OO5lR
wJuKJySYbmoM0y98r4O/tMghyfP7i1g3s20BDdEHJl0jfgdmqpjs27wQ/9AlWk2r
A+AeQxegflcMgxznR/butyoXSt9f1IiR3forq/ffDu9NbwsuOXNJPo1+Ig95kjY4
Rn7Iq/1d2g17fzHxmxZAcQoOyh8jyjgdwW/RI2kA2KICV+DZ0w+n32r+Gdw1NsiK
SZVG0Tf32anLkpuNsAs9igquDs4KgBbj6lwduvFqL0LlLocbAwS4D9LX9YKbM0ug
yPByx5DXu0jRDt9thOW1V19UyUBVc90ICwuMaLWxiOc5BVY3jdq1uJlsqS36aw==
=7MBN
-----END PGP SIGNATURE-----

--cHMo6Wbp1wrKhbfi--