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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
|
Return-Path: <clarkmoody@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 432EE5A8
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 18 Oct 2018 22:28:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com
[209.85.208.180])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 824CF7EC
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 18 Oct 2018 22:28:10 +0000 (UTC)
Received: by mail-lj1-f180.google.com with SMTP id r83-v6so29142782ljr.7
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 18 Oct 2018 15:28:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=clarkmoody-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=MVviVyv2MrL2jMpr2oHdpOWjFtj2uszByb/9RHsb20k=;
b=nLjUjbsWbsgMhu5SQcdxYlt2Di32nwamAHyNl+PtEq4IHxs5SHQVpOyC/mfNpXGlqR
IgNX5brh10ebxubdE+TnUjIzGCrOMvQv5dLL04zP/MZPxte1wJOELdctc9G8IetVGZhB
XggIjmBzogsGCC40Qn4XXHNCW1OoYQcdSpEHYHog4SRYiB45WCySnHlO+Yl3bi3G1zdm
V+2cBZESrqX8SWkQMTmdeS2lMxzsNKiKNDzKYpretSqoPbBKskzydlOMEk/7mZ+UrnWr
rln27bGUbzV+C6JKD/JKZ2/73B4TO9MZ+t59ozaKZvYd+S+Mv6A3pATnN8ZGay6F07VY
PNVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=MVviVyv2MrL2jMpr2oHdpOWjFtj2uszByb/9RHsb20k=;
b=F10Y8AOs199UB2aNk655YElSFARgwuNGvsXdP7tsnhirdHDE3DwSVmK6QIIb1CuKhf
3hQL2VR/REHntAzD1gBT+uMEEkTKsyor3CtYlJt5SY04Iud3h/k7OH8n9y2MkuQUtGQI
d7BqSy98ZiXxKDtgX44rWdei4ZrT0bgawF2QXdSOkjdABpFEnIq7uY+VfE54ZszxIpJ4
PIP5zDpLOEiOK2oRUUuHOmeGeDrR7jljIF3uRtQZ2LK39sJLB8C0HY0a81inX8FiVogM
Ux7BvBeU5Sk6Q/B9ybuPKK/Y3W+xsE726fig+szRNa2luCfy6g7qWDB2ycRbBOkDLCHi
RdKA==
X-Gm-Message-State: ABuFfoj5lLbg/7njHpvriJ5sMWH1uQQ6Qwhv8Pt02AWhPt1gdp1trLIZ
Rce4ewTwPQkbZqYaHLBOTEiKvVwCY2KCPH1i2ubD/tli
X-Google-Smtp-Source: ACcGV61C60vA+EQI+6P7IPpgBPd4ogOPOiWKmREJZ8NDbKS6bvh/OniWSxkS2Q1q+00m9vAQvZSE4vvaerd+HG91n5Y=
X-Received: by 2002:a2e:8703:: with SMTP id
m3-v6mr20569127lji.109.1539901688657;
Thu, 18 Oct 2018 15:28:08 -0700 (PDT)
MIME-Version: 1.0
References: <CACUQsLKTHVE7pe=0-zuMTGZWbUaJFp5=CNZCQE0477B7LZRsbg@mail.gmail.com>
<CAHGSxGuqf2vKOWtW-_hfdqfsH8a_QTaWBsrUViV8A39dk1KA6A@mail.gmail.com>
<871627c9-8679-5f82-a76f-cec9ffa28379@c3d2.de>
In-Reply-To: <871627c9-8679-5f82-a76f-cec9ffa28379@c3d2.de>
From: Clark Moody <clark@clarkmoody.com>
Date: Thu, 18 Oct 2018 17:27:41 -0500
Message-ID: <CAHGSxGssNaVn_CAK252D_N8hzLFLnBFO8XPJLrCAHVw9+gCLWQ@mail.gmail.com>
To: vv01f@c3d2.de,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000243e9e0578884d7b"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, 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: Thu, 18 Oct 2018 23:29:28 +0000
Subject: Re: [bitcoin-dev] BIP for segwit compatibility URIs
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: Thu, 18 Oct 2018 22:28:11 -0000
--000000000000243e9e0578884d7b
Content-Type: text/plain; charset="UTF-8"
I agree with spelling out the `address` field.
As for "value is either an address or an array of addresses", there is no
standard for specifying an array in a URI, and processing different
querystring schemes is application-specific. (see
https://stackoverflow.com/a/9547490)
Since those app-specific methods don't necessarily preserve order, which is
important here, the most compatible fallback is a delimiter-separated list
under one parameter. Most languages have library functions for splitting
strings on commas.
-Clark
On Thu, Oct 18, 2018 at 5:13 PM vv01f via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I already pointed out a while ago that the separator could be the & and
> the returning value is either an address or an array of addresses.
> So no comma or other delimiter needed.
> also I would suggest to call the parameter `address` and not a shortcut
> for it as we are used to `message` and `amount` spelled out as well.
>
> On 18.10.2018 16:20, Clark Moody via bitcoin-dev wrote:
> > Since we don't know what sort of address changes will happen later on,
> you
> > could make this future-proof by passing a list of addresses to `addr`.
> >
> > The syntax is
> >
> > bitcoin:<address>[?addr=<address>[,<address>[,<address>]]]
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--000000000000243e9e0578884d7b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,0)">I agree with s=
pelling out the `address` field.</div><div class=3D"gmail_default" style=3D=
"font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div>=
<div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-si=
ze:small;color:rgb(0,0,0)">As for "value is either an address or an ar=
ray of addresses", there is no standard for specifying an array in a U=
RI, and processing different querystring schemes is application-specific. (=
see <a href=3D"https://stackoverflow.com/a/9547490">https://stackoverflow.c=
om/a/9547490</a>)</div><div class=3D"gmail_default" style=3D"font-family:ta=
homa,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"g=
mail_default" style=3D"font-family:tahoma,sans-serif;font-size:small;color:=
rgb(0,0,0)">Since those app-specific methods don't necessarily preserve=
order, which is important here, the most compatible fallback is a delimite=
r-separated list under one parameter. Most languages have library functions=
for splitting strings on commas.<br></div><div><div dir=3D"ltr" class=3D"g=
mail_signature"><div><br></div><div><br></div><div>-Clark</div><div></div><=
/div></div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">=
On Thu, Oct 18, 2018 at 5:13 PM vv01f via bitcoin-dev <<a href=3D"mailto=
:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.o=
rg</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I already pointed=
out a while ago that the separator could be the & and<br>
the returning value is either an address or an array of addresses.<br>
So no comma or other delimiter needed.<br>
also I would suggest to call the parameter `address` and not a shortcut<br>
for it as we are used to `message` and `amount` spelled out as well.<br>
<br>
On 18.10.2018 16:20, Clark Moody via bitcoin-dev wrote:<br>
> Since we don't know what sort of address changes will happen later=
on, you<br>
> could make this future-proof by passing a list of addresses to `addr`.=
<br>
> <br>
> The syntax is<br>
> <br>
> bitcoin:<address>[?addr=3D<address>[,<address>[,<=
address>]]]<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--000000000000243e9e0578884d7b--
|
