From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 2E77BC0052 for ; Tue, 20 Oct 2020 10:30:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 1497F8725C for ; Tue, 20 Oct 2020 10:30:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Js61D0KfRzPE for ; Tue, 20 Oct 2020 10:30:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from newmail.dtrt.org (li1228-87.members.linode.com [45.79.129.87]) by hemlock.osuosl.org (Postfix) with ESMTPS id 12A9D87186 for ; Tue, 20 Oct 2020 10:30:41 +0000 (UTC) Received: from harding by newmail.dtrt.org with local (Exim 4.92) (envelope-from ) id 1kUouV-0001zl-FX; Tue, 20 Oct 2020 06:30:31 -0400 Date: Tue, 20 Oct 2020 06:29:52 -0400 From: "David A. Harding" To: Rusty Russell Message-ID: <20201020102952.4iwpugi5dxawufgo@ganymede> References: <87imblmutl.fsf@rustcorp.com.au> <20201008145938.vrmm33f6sugdc7qm@ganymede> <87r1q0e06p.fsf@rustcorp.com.au> <877drn2g6q.fsf@rustcorp.com.au> <878sc120f5.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zkh2orzeju3f2qzq" Content-Disposition: inline In-Reply-To: <878sc120f5.fsf@rustcorp.com.au> User-Agent: NeoMutt/20180716 Cc: Bitcoin Protocol Discussion , John Barboza 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2020 10:30:43 -0000 --zkh2orzeju3f2qzq Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 20, 2020 at 11:12:06AM +1030, Rusty Russell wrote: > Here are my initial results: A while ago, around the Bitcoin Core 0.19.0 release that enabled relaying v1+ segwit addresses, Mike Schmidt was working on the Optech Compatibility Matrix[1] and tested a variety of software and services with a v1 address using the original BIP341 specification (33 byte pubkeys; we now use 32 byte keys). Here's a summary of his results, posted with his permission: - abra: Bech32 not supported. - binance: Does not pass front end javascript validation - bitgo: Error occurs during sending process, after validation. - bitmex: Bech32 not supported. - bitrefill: Address does not pass validation. - bitstamp: Address text input doesn=E2=80=99t allow bech32 addresses due to character limits. - blockchain.info: Error occurs during sending process, after validation. - brd: Allows sending workflow to complete in the UI. Transaction stays as pending in the transaction list. - casa: Fails on signing attempt. - coinbase: Fails address validation client side in the UI. - conio: Server error 500 while attemping to send. - copay: Allows v1 address to be entered in the UI. Fails during broadcast. - edge: Allows sending workflow to complete. Transaction stays in pending state. Appears to causes issues with the balance calculation as well as ability to send subsequent transactions. - electrum: Error message during broadcasting of transaction. - green: Fails on validation of the address. - jaxx: Fails on validation of the address. - ledger live: Fails when transaction is sent to the hardwave device for signing. - mycelium: Fails during address validation. - purse: Transaction can be created and broadcast, relayed by peers compatible with Bitcoin Core v0.19.0.1 or above. - river: Transaction can be created and broadcast, relayed by peers compatible with Bitcoin Core v0.19.0.1 or above. - samourai: Fails on broadcast of transaction to the network. - trezor: Fails on validation of the address. - wasabi: Fails on validation of the address. - xapo: Xapo allows users to create segwit v1 transactions in the UI. However, the transaction gets stuck as pending for an indeterminate period of time I would guess that some of the failures / stuck transactions might now be successes if the backend infrastructure has upgraded to Bitcoin Core >=3D 0.19. -Dave [1] https://bitcoinops.org/en/compatibility/ --zkh2orzeju3f2qzq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEgxUkqkMp0LnoXjCr2dtBqWwiadMFAl+OvCAACgkQ2dtBqWwi adOQ9w/+MmGwngzLABGgfAzWh19A3Rs+ZvY0ygJqMz1BdFeBrlLnqkNqGZ7B4I5a g00RoRQPUEGQz3D6n40QqFlgXHWQZJjO/46QHeSbpEvF//HL9G4h3TuRYIGGlZ7G vEf875iA7/qpIFGcIlzlZs3+64890gmPKZD/lKtZRBfaD8s9Mz9zj5vsrlnMiZsc 9yGbrJyK+qMTQurIlymZAb/P1FiH6AJELGaOpMtNQmnDe8lXbCe01ctSsDiBxjIX SVth10Kx1GrajL0owTzhSuiO14+9EkEMYnYu1xhDm3Jqmp9jeaWlMjtDJIJEICZs OAu3giuH7f6YbXVDVIcV8ZzdRPKa90Y6A8fwQO7BcH8EhPvyWSqMQtiTRVQB1zr2 EFjB4aMqgpxRftnDYOmDWc1ZLJ4uuL5s8L2rjHL1Mm+Yb/ITAV3Ft7Uf6IvPLs6i d8N5Hf5Xz9seiQMSeBn54vGqlcBuoqe2hXQ6MC9J4mPX8D1Ph6ZI3WAncKtGG0RO ajMa1RqDJXOgg9XDvPZQT2wovYsv3xS+B2mGi5PI5SN3M4WeAPz7l5sEN4vjuaJi xEALYeYiSzn8X0d6XHJIefFzUa6Gw0S4ML8QP84IUvBV3W/3OMPQAl4eCkkxKT8l RxgteXrHB0EYfgaQLSrQcPDR9w9EEarMMLA6XUpkgEwZMVQbD7s= =YTBV -----END PGP SIGNATURE----- --zkh2orzeju3f2qzq--