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"
Subject: Re: [bitcoin-dev] Progress on bech32 for future Segwit Versions
	(BIP-173)
Precedence: list

--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&#39;s=C2=A0r5n8 address. Y=
ou can see this with Rusty&#39;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&#39;s wallet behaved similarly, se=
nding to the same, incorrect address. Rusty&#39;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&#39;s tea=
m to let them know about this.</span></div><div>- Blockchain.info&#39;s exp=
lorer suffers similarly, &quot;Unable to decode output address&quot; 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&#39;=
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--