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
|
Return-Path: <sjors@sprovoost.nl>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D5DCFBB3
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 28 Sep 2017 15:45:52 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
[66.111.4.25])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EED3044D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 28 Sep 2017 15:45:51 +0000 (UTC)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by mailout.nyi.internal (Postfix) with ESMTP id 3437920DA6;
Thu, 28 Sep 2017 11:45:51 -0400 (EDT)
Received: from frontend1 ([10.202.2.160])
by compute1.internal (MEProxy); Thu, 28 Sep 2017 11:45:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sprovoost.nl; h=
content-type:date:from:in-reply-to:message-id:mime-version
:references:subject:to:x-me-sender:x-me-sender:x-sasl-enc
:x-sasl-enc; s=fm1; bh=LfN8rhqwhNfNW3mJ1jdOwvz9PQfmETzqPLXRZ97VW
Tw=; b=LBKfCE1lDn6JmeUfBVclRyoO+9gjAG24GRjeOtBPJ643mFpWlxts3UmZx
Km4+xcLUD9+p4QLRQT08oMcHKwd/F8J4aaqYHhG9MsijUko0e8KFS/JdZNLqmgdK
2XYUe3f0HA/QBm4BR54eZn+upzPIfXQ1k2pBLPgAyjDiqWpktb6zgjNg8mUCjdEp
B4RXUs9Q0vqI0F9xMlCmTyi/rD1+ZuJKPMkwOU6gwLfck/U3T7DXVjy4IqIjwsv6
a1alXdXpcNKQUNV/VUsg4mElKlzGD6XRG+oFZidynsvS4uLxBNvxe72df/9Cw+hH
occdNWA/j1NV5221PzE9FKJIOcxJQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=content-type:date:from:in-reply-to
:message-id:mime-version:references:subject:to:x-me-sender
:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=LfN8rhqwhNfNW3mJ1j
dOwvz9PQfmETzqPLXRZ97VWTw=; b=R/0Swp8b1gY+aMR6C8IiTf6n/dIAu44Pid
g3Z1R+BR9+7G5neSQhiYM1VozN66CUJadOk7j7F/DyZB81XbUeme4aEkCUNnHCRJ
vkP6I/2fMoxjccYap78obUwZHAVvv7Bp1vpiXVv6BNvPc38+cOhg5dRES2aDW8CP
onFfFPZh0oJbaEuhlVaU0yuUiQQtQVe6x68MvLj4QBL1TjkY4SLUBQJETShU663T
uXeYER0CGHkagMeslyU4o6K2RCI5WctZZOUpNQ08k7wazWEo1Ar3JxmZKZgZbuwm
gfVK1UsGc4NG8ZQXF6FQpSuHMukRCgRqEx6bSVv/Cu6QY2BKEbuA==
X-ME-Sender: <xms:LxnNWRI3zN2alYi-RX_YcEUI8ABiT0H5LSL-xR4TEtbsXWbj81yYdA>
X-Sasl-enc: UemNMzhYWJIZCo40YHbogkkfpranr6ODFDP0J1C8iV/C 1506613550
Received: from [192.168.0.108] (unknown [78.96.80.234])
by mail.messagingengine.com (Postfix) with ESMTPA id 4C9557E3BA;
Thu, 28 Sep 2017 11:45:50 -0400 (EDT)
From: Sjors Provoost <sjors@sprovoost.nl>
Content-Type: multipart/signed;
boundary="Apple-Mail=_FC300F55-83F4-4EDD-8CBC-5836E2EC1A32";
protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.6\))
Date: Thu, 28 Sep 2017 18:45:47 +0300
References: <20170927160654.GA12492@savin.petertodd.org>
<oqihpf$5gc$1@blaine.gmane.org>
<B5DE4E92-C5B3-4C01-A148-E3C46C897323@sprovoost.nl>
<oqj02k$fj9$1@blaine.gmane.org>
<14496C9C-E291-4415-B07E-859853579D20@sprovoost.nl>
<oqj369$18u$1@blaine.gmane.org>
To: Andreas Schildbach <andreas@schildbach.de>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <oqj369$18u$1@blaine.gmane.org>
Message-Id: <4745C5CF-AA3A-4614-99DA-DE3C985F3D69@sprovoost.nl>
X-Mailer: Apple Mail (2.3445.1.6)
X-Spam-Status: No, score=0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_WEB autolearn=disabled
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, 28 Sep 2017 15:56:28 +0000
Subject: Re: [bitcoin-dev] Address expiration times should be added to
BIP-173
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, 28 Sep 2017 15:45:52 -0000
--Apple-Mail=_FC300F55-83F4-4EDD-8CBC-5836E2EC1A32
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
Op 28 sep. 2017, om 18:06 heeft Andreas Schildbach via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven:
>=20
> On 09/28/2017 04:41 PM, Sjors Provoost via bitcoin-dev wrote:
>=20
>>> The payment request message is just as one-way as an address is. It =
is
>>> already being emailed and printed on an invoice, in fact it often =
acts
>>> as the invoice.
>>=20
>> True and the more complicated fields, like a digital signature, are =
optional. Are you suggesting BIP-70 payment requests should be rendered =
with bech32? How long would those be if it's just the address and =
expiration date?
>=20
> I've not yet progressed that far in segwit support, but I can't think =
of
> a reason why not. You can request coins to any script using the =
payment
> protocol.
>=20
> Regarding size, I've had no problems putting (unsigned) payment =
request
> messages into QR codes. I doubt paying to a native segwit address will
> change much in size. Protobuf is very efficient.
Bech32 is just a replacement for Base58. It's not strictly SegWit =
related. If I understand correctly the only reason it won't be used for =
legacy addresses is to prevent confusion:
https://www.youtube.com/watch?v=3DNqiN9VFE4CU
https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki
Regarding size I'm mostly curious how big it is on a screen or a =
physical paper, as text, not as a QR code. This would involve =
deserializing the protobuf and rendering the result in bech32.
I does sound like there's overlap between BIP-70 and BIP-173 that should =
be resolved.
Perhaps any payment request can be rendered as bech32 and any bech32 =
address can converted to a payment request. Maybe only for a limited set =
of fields (address, expiration, amount). This would be a matter of =
agreeing how the protobuf should be serialized and deserialized. In that =
case the protobuf would not contain the literal bech32 address as a =
string, but instead it would contain the underlying data (public key / =
script hash, network, etc).
Sjors
--Apple-Mail=_FC300F55-83F4-4EDD-8CBC-5836E2EC1A32
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE7ZvfetalXiMuhFJCV/+b28wwEAkFAlnNGSsACgkQV/+b28ww
EAlP1Q//f6SPursatGp4Jp/0HybgK/xl5PBqX29r0sQhhUa8PGxVVq31afok1lGh
jnW2ed7OMZ9AS5hQYyN5QffgxgT+SPkOuHGHLuVMnyxtI6uZdO/jVxYF+Z4731Xy
Z5mvrxF9XlslwEF2Bz8BEWgTueEp7F2wDz42RRuA/X2/1HZ+dk8vXOqxQlL+xnQU
LB9Q8wBQVHlSqtyhkW7OvhY7+HiVSG/K00qLLPBvvm6cNMc6IVJhJQbithhJefEP
KbELvgV8mqp7lZ4XLlqjJLekPmbwADkQFBk4SseVsyyiXrpXDD6NoI0Dxkd+k1xc
Zx+Gqb6NjFygwTw4UXaIp8dsQAfVI/IE/qW51VDALZ05JfS1AYlfmDIm7oot65p9
rGvWq7FoLZCPKP24j5GZMZbnfqY3P7wIYFFMVu8UyTfmOeTRj9+EfGD1yaAvnjwB
9KnG6SSwnHRmUnpPJ53pj8Bp7jXCTOBsZ1JZ+HzkMUuSKOZ/cNXWo9+cyZ4ixH4z
myOUOdALYnOuRqdx2USvhAo7wuw+Fi2tSBiGPR3tYw39BTUIjAY5JGFEVtW0oPmW
VlhG2Kr6REVXXHxCBI6W8YlO2WoCrNkNvUbFtNMyoHNk+qCT2x5wngajwH7CEyhw
qmZdH18A+Jty+AMGAJynJmmFuiYC6e96r535A5/mfCP4rpx+qqQ=
=5UyY
-----END PGP SIGNATURE-----
--Apple-Mail=_FC300F55-83F4-4EDD-8CBC-5836E2EC1A32--
|
