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
|
Return-Path: <schmidty@gmail.com>
Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 3B7FAC0889
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Nov 2020 19:50:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by whitealder.osuosl.org (Postfix) with ESMTP id 1F87086CCD
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Nov 2020 19:50:23 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from whitealder.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id TJioLDhjXYxS
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Nov 2020 19:50:22 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-il1-f174.google.com (mail-il1-f174.google.com
[209.85.166.174])
by whitealder.osuosl.org (Postfix) with ESMTPS id F146B86CA6
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Nov 2020 19:50:21 +0000 (UTC)
Received: by mail-il1-f174.google.com with SMTP id q1so2079891ilt.6
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 06 Nov 2020 11:50:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=UKv+sJHY+vrPdrSP0D+gakxNerh3sfveHzDHZZjIcZo=;
b=lSr4zJzoT6dJX9znvXH6bk8YSrcI9ZZEVYdvNCBZmc9yUwsRWA15kS0hM/Ut3HXbZ6
0BX+8dDNajA5qg8WR+r6iUN3RSgCwiYYIKVq3I9t2Nc8fM2JhkUyXQGsWjVD/jBCuFaq
/jOGANZ+YIjLypiU1grC3gZNcMboRTgoC+3rblPwZ1HcFZr2H+M3YAum8BPaq+J5vXHH
64Jq16aoqNbGSpT5w6GGLpiwgHKNSgw2dTLezRGXB/6vUmMc45TQrtMVhigZwbC4rAFS
f1A9A/N1RUqFPYKhYuxrDA5VklMwxHlbLq7PmnB5frDA2JzLKRBJVaGiP98QbPgv7Xl/
0eeA==
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=UKv+sJHY+vrPdrSP0D+gakxNerh3sfveHzDHZZjIcZo=;
b=hutRHAHxzHBd62l1mZobBwbngJxuBCB4C6W+2/E7pykbKD7U4v8CINRqWL/l2sHV1t
1ztSoURrEKPOn3hB8zCdRRBWTZes7Dsmx+Ht6mP24Va/5AJzwzZryqipR88OUp8g4NNp
Uz9B18BnhEoO0oGkqV7hgb6yWLBpCz9keldqIAfJCkRqaHZMNwh+L3q7BttI0BI6cS97
HjMsn0HdxBVhchEgp5B24oW9PvybR9AbPzX/BkaU+YcIEMqEwAhmreloToX+m2z+SnPb
biUCSL2cAqkcbnEAJgeZ6LAabgmLez6875RxeMhdfOJ/Lsp4c10AwAg+LZ152sfbdELl
1TgQ==
X-Gm-Message-State: AOAM532XNZL+CiPZMn8JCUiawNRpGhfBKO/0Zr5g1ngtWRKIlPo964YZ
MPZP9yG40wv5uLKQgoEc6nJHscEtMTFZobAcrdyYjakwVnq0gK85
X-Google-Smtp-Source: ABdhPJy072Y80WdmMEra4Ie4jhSatVsNemAhpxA9Ac8YFOc4/JL5qd7K67nPZoCk935IQzTNdHz8HQ3Ad9zWv+tQFas=
X-Received: by 2002:a92:9845:: with SMTP id l66mr2423415ili.65.1604692220895;
Fri, 06 Nov 2020 11:50:20 -0800 (PST)
MIME-Version: 1.0
References: <87imblmutl.fsf@rustcorp.com.au>
<20201008145938.vrmm33f6sugdc7qm@ganymede>
<87r1q0e06p.fsf@rustcorp.com.au>
<sYf9B0e3UaSdMfdBfChon1Vr7BRFdH_6mgzuXIt_xbtlKtdqns9JJp90dRlNfvwBoRq57YEVrKbKX-dHDWz7TE0gobU4u8dGGJTcFFz2n60=@wuille.net>
<877drn2g6q.fsf@rustcorp.com.au>
<S6FCoLsmwaQUhrtSURemcTcG8tUWTXYkBf-0Q0hxCpObfJQ0TXNcmJrQhoqy7ttWwtGnvyS-bJ5RSXJoPizAgjuMognzVnu3SM3wMujKy88=@wuille.net>
<878sc120f5.fsf@rustcorp.com.au> <20201020102952.4iwpugi5dxawufgo@ganymede>
<Kw_jwhASjriebJpsuUyi0u9EQmIVR1pQ3Jocqd9VeVDlmoH9s36bFAwr3PXu_pJd-Xly-hKun_yenLwbJvVIYWmlAiF5lMxuquLO2pTmlLo=@wuille.net>
<CAMeZzJeG00q9DPQacidto5H16Ryb6ou6tnMDK1jnAuncnVXnsA@mail.gmail.com>
In-Reply-To: <CAMeZzJeG00q9DPQacidto5H16Ryb6ou6tnMDK1jnAuncnVXnsA@mail.gmail.com>
From: Mike Schmidt <schmidty@gmail.com>
Date: Fri, 6 Nov 2020 13:49:44 -0600
Message-ID: <CAMeZzJdQuS1-0qPvY+0-yqRfVXgZV_2hmHB5hZwykm5WxjUkgg@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000ccea7805b375852d"
X-Mailman-Approved-At: Fri, 06 Nov 2020 19:51:31 +0000
Subject: Re: [bitcoin-dev] Progress on bech32 for future Segwit Versions
(BIP-173)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Fri, 06 Nov 2020 19:50:23 -0000
--000000000000ccea7805b375852d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Well I sure picked a bad couple weeks to volunteer to send a bunch of
Bitcoin test transactions...
While I tested less than I would have liked, there are some notable results=
:
- Green wallet segwit v1 send resulted in funds being sent to the wrong
address (bc1qmfr3p9j00pfxjh0zmgp99y8zftmd3s5pmedqhyptwy6lm87hf5sstpn3we
instead of my intended destination, Pieter's r5n8 address. You can see this
with Rusty's test transaction as well:
ef1662fd2eb736612afb1b60e3efabfdf700b1c4822733d9dbe1bfee607a5b9b
Blockstream is aware of the issue and has fixes.
- Blockchain.com's wallet behaved similarly, sending to the same, incorrect
address. Rusty's blockchain.com transaction for reference:
64b0fcb22d57b3c920fee1a97b9facec5b128d9c895a49c7d321292fb4156c21
I will be reaching out to Blockchain's team to let them know about this.
- Blockchain.info's explorer suffers similarly, "Unable to decode output
address" when viewing a tx with v1 output, and inability to display address
details for a v1 address
- Bitgo accepts a v1 send address, but then a =E2=80=9CServer error=E2=80=
=9D during send
occurs
- Coinbase (web) reported on final step of sending: Your send failed Please
enter a valid email or Bitcoin address
- brd sends successfully to v1
- bitrefill, casa, xapo, wasabi, all previously failed address validation,
and still fail address validation
- binance, bitmex, kraken, all previously failed address validation, but
now accept v1 addresses. I did not attempt full send with these services,
simply passing initial validations.
- While Riccardo noted that Aqua successfully sent to Pieter's address
(b48a59fa9e036e997ba733904f631b1a64f5274be646698e49fd542141ca9404) Ive been
informed Aqua has disabled send to v1 addresses for now.
--000000000000ccea7805b375852d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Well I sure picked a bad couple weeks to volunteer to send=
a bunch of Bitcoin test transactions...<div><br></div><div>While I tested =
less than I would have liked, there are some notable results:</div><div><br=
></div><div>- Green wallet segwit v1 send resulted in funds being sent to t=
he wrong address (bc1qmfr3p9j00pfxjh0zmgp99y8zftmd3s5pmedqhyptwy6lm87hf5sst=
pn3we instead of my intended destination, Pieter's=C2=A0r5n8 address. Y=
ou can see this with Rusty's test transaction as well:=C2=A0<span style=
=3D"color:rgb(0,0,0);white-space:pre-wrap">ef1662fd2eb736612afb1b60e3efabfd=
f700b1c4822733d9dbe1bfee607a5b9b Blockstream is aware of the issue and has =
fixes.</span></div><div>- Blockchain.com's wallet behaved similarly, se=
nding to the same, incorrect address. Rusty's <a href=3D"http://blockch=
ain.com">blockchain.com</a> transaction for reference:=C2=A0<span style=3D"=
color:rgb(0,0,0);white-space:pre-wrap">64b0fcb22d57b3c920fee1a97b9facec5b12=
8d9c895a49c7d321292fb4156c21 I will be reaching out to Blockchain's tea=
m to let them know about this.</span></div><div>- Blockchain.info's exp=
lorer suffers similarly, "Unable to decode output address" when v=
iewing a tx with v1 output, and inability to display address details for a =
v1 address</div><div>- Bitgo=C2=A0accepts a v1 send address, but then a =E2=
=80=9CServer error=E2=80=9D during send occurs</div><div>- Coinbase (web) r=
eported on final step of sending: Your send failed Please enter a valid ema=
il or Bitcoin address</div><div>- brd sends successfully to v1</div><div>- =
bitrefill, casa, xapo, wasabi, all previously failed address validation, an=
d still fail address validation</div><div>- binance, bitmex, kraken, all pr=
eviously failed address validation, but now accept v1 addresses. I did not =
attempt full send with these services, simply passing initial validations.<=
/div><div>- While Riccardo noted that Aqua successfully sent to Pieter'=
s address (b48a59fa9e036e997ba733904f631b1a64f5274be646698e49fd542141ca9404=
) Ive been informed Aqua has disabled send to v1 addresses for now.</div><d=
iv><br></div><div><br></div><div><br></div></div>
--000000000000ccea7805b375852d--
|
