1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 546FC1BB
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Oct 2015 01:22:58 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148110.authsmtp.com (outmail148110.authsmtp.com
[62.13.148.110])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 5D60963
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Oct 2015 01:22:53 +0000 (UTC)
Received: from mail-c247.authsmtp.com (mail-c247.authsmtp.com [62.13.128.247])
by punt20.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t9N1MqsK019063;
Fri, 23 Oct 2015 02:22:52 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t9N1MnqS040834
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Fri, 23 Oct 2015 02:22:51 +0100 (BST)
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)
X-Server-Quench: 94675023-7924-11e5-bcde-0015176ca198
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAEUF1YAAgsB AmMbW1ZeUl97XGE7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRRV/ B2NAE3pycwVOe3o+ YENlWD5SWEJ9cEZ/
QVNTHG8CeGZhPWUC AhMMIh5UcAJPfxhD OQF+XXtDAzANdhEy
HhM4ODE3eDlSNhEd cSsMMVkVQEBOEjMi ShQFBTAiG1EwDx8+
MgcvIFoRVF4YI0A/ N0dpUlUUPgR6
X-Authentic-SMTP: 61633532353630.1038:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 23 Oct 2015 01:26:42 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin-development] Reusable payment codes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2015 01:22:58 -0000
--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--
|
