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
123
124
125
126
127
128
129
130
131
|
Return-Path: <cryptaxe@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 7766BC00
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Dec 2017 20:06:34 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com
[209.85.128.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B7B991B4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Dec 2017 20:06:33 +0000 (UTC)
Received: by mail-wr0-f179.google.com with SMTP id g53so1616390wra.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 05 Dec 2017 12:06:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=vFqymty2eaYUghtTFFrNu6IdUNeCeGhIEa5Nq+Dikoc=;
b=on9EIQkcwD8Ek90x+KpsVUHFPcwPKog8KC0gtGiEZldW8RcNaWsnVCVaYtUkz7geOk
fy3X2PI1r7D+HkTXW/Jc/dU0xValeUoQE6MD/EQqmVkGCbz9BIvwm4rrveJdmWN6Cu3n
r3t4Qt5ZZ0OONZKmse25M+KYmsmQQrJxhvBBT5b6jqqKSeIYVGNP5Z0KuTXSa2LZ/R5y
t/H/7sw6rRBhmS4/n6jiQr/ecSQ21uj4ufQksQ9LZAJ9mGXOHTBt6xKkv6sw2Oij8MxX
RccXwbFFXNyRaSZYui8Kc8uQ2nZaWLUeZVgu+WAYLxErD6YfLcFOX3YMVyMs80eQYVcH
RGzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=vFqymty2eaYUghtTFFrNu6IdUNeCeGhIEa5Nq+Dikoc=;
b=FDbq81gCpl7pxdOBOmr5TvOvMlCRxP4bWzKd9nRD5ISAyNyO3S18NTc06LDf1yoic0
rsFKh4VrDtF9iczdZhJNCYtRjHHeGS8irUv9n+y8aBvbCl81XFZam2KEmTGjQceUFT2d
WiRC3wa0rsfbsXyqKc17dbdwt0xKtfyh0cLw6heop/6xRAZ4zkOyge7xbjfxgt3e34Rr
KmfB9pJvvF73dZ+kJayiKN1784EqvgOCSl/yPfblCi9I/kPh9fjGmVwTNa9QpwKmH13w
U96j7D8oUF7374ZUCCeklTT7+fEgQln82AWgNB9XV2PohrHMf6pF1A6rGEmRpI5Dsr8k
J84w==
X-Gm-Message-State: AJaThX5+Q4ESL/0ZRTqXTVPnjaXPfWyMCu6rE9jxLHjjzuF7K1MPWNgK
dP2Wo0GTut8rX1qOt61Pn67UHvjj9I6RfcYXvJE=
X-Google-Smtp-Source: AGs4zMYvHxzANRLUPc3NmAaEYMJpjuJo7v12BRb+Io6+7fCLdEaWzozHO4h437Z/HnYdIUoIHsFVW4LobQPp6L3xaD0=
X-Received: by 10.223.134.134 with SMTP id 6mr17295272wrx.72.1512504392405;
Tue, 05 Dec 2017 12:06:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.146.69 with HTTP; Tue, 5 Dec 2017 12:06:31 -0800 (PST)
Received: by 10.28.146.69 with HTTP; Tue, 5 Dec 2017 12:06:31 -0800 (PST)
In-Reply-To: <FD79573C-4771-464B-A570-E2868BBA0CA5@sprovoost.nl>
References: <AE14915B-37DF-4D94-A0B1-E32A26903807@sprovoost.nl>
<201712051939.33238.luke@dashjr.org>
<FD79573C-4771-464B-A570-E2868BBA0CA5@sprovoost.nl>
From: CryptAxe <cryptaxe@gmail.com>
Date: Tue, 5 Dec 2017 12:06:31 -0800
Message-ID: <CAF5CFkiVD6gUzmJbNGaJShMD3h5mq-RmUkBJEx61Eg6ie7=0MQ@mail.gmail.com>
To: Sjors Provoost <sjors@sprovoost.nl>
Content-Type: multipart/alternative; boundary="001a11459da007f220055f9d5fa6"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE 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: Tue, 05 Dec 2017 20:07:48 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Matt Corallo <matt@chaincode.com>
Subject: Re: [bitcoin-dev] BIP-21 amendment proposal: -no125
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Tue, 05 Dec 2017 20:06:34 -0000
--001a11459da007f220055f9d5fa6
Content-Type: text/plain; charset="UTF-8"
On Dec 5, 2017 12:00 PM, "Sjors Provoost" <sjors@sprovoost.nl> wrote:
...
I don't think all BIPs lend themselves to this pattern. Can you think of
another example?
Not right now, just seemed like a good idea to consider making it useful
for more than one thing (maybe CT or something else could use it in the
future?).
I also suspect each ignored flag requires carefully defined behavior, so
it's probably better to spell that out in the BIP.
Sjors
Agreed, no reason they couldn't reuse the same section of the payment
request URI though. (And define that behavior in the BIP)
--001a11459da007f220055f9d5fa6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Dec 5, 2017 12:00 PM, "Sjors Provoost" <<a href=
=3D"mailto:sjors@sprovoost.nl">sjors@sprovoost.nl</a>> wrote:<br type=3D=
"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">...<br>
<br>
</div>I don't think all BIPs lend themselves to this pattern. Can you t=
hink of another example?</blockquote></div></div></div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">Not right now, just seemed like a good idea to co=
nsider making it useful for more than one thing (maybe CT or something else=
could use it in the future?).=C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockqu=
ote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"> I also suspect each ignored flag requires carefully defin=
ed behavior, so it's probably better to spell that out in the BIP.<br>
<font color=3D"#888888"><br>
Sjors<br></font></blockquote></div></div></div><div dir=3D"auto"><br></div>=
<div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><bl=
ockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><font color=3D"#888888"></font></blockquote></div></d=
iv></div><div dir=3D"auto">Agreed, no reason they couldn't reuse the sa=
me section of the payment request URI though. (And define that behavior in =
the BIP)=C2=A0</div><div dir=3D"auto"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><font color=3D"#888888">
</font></blockquote></div><br></div></div></div>
--001a11459da007f220055f9d5fa6--
|
