Date: Fri, 11 Aug 2023 13:45:35 +0000
From: Andrew Poelstra <apoelstra@wpsoftware.net>
To: Tobin Harding <me@tobin.cc>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ZNY7f8tRfKHi73Uj@camus>
References: <ZNW9BenWIhgX95zl@alke>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="XxnP3vfVQL6HUXlF"
Content-Disposition: inline
In-Reply-To: <ZNW9BenWIhgX95zl@alke>
Subject: Re: [bitcoin-dev] segwit naming ambiguity
Precedence: list


--XxnP3vfVQL6HUXlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 11, 2023 at 02:45:57PM +1000, Tobin Harding via bitcoin-dev wro=
te:
> Question for OG bitcoin API designers please.
>=20
> If you were to see the following function
>=20
>     `is_segwit()`
>=20
> would you assume it returns `true` or `false` for a p2tr transaction?
>=20
>=20
> Currently we (rust-bitcoin) are being liberal with the use of `v0` but
> its a pretty ugly. Is there an official, or widely used, name for segwit =
v0?
>

As others have said, I think `is_segwit` should match all segwit
versions. Pavol also sorta answered your "widely used name" question
though he didn't draw attention to it -- segwit v0 outputs are called
"p2wsh" or "p2wpkh".

But I don't know any term that covers "p2wsh or p2wpkh but not p2tr".
Other than "segwit_v0", which we are currently using, and which I agree
is a bit of a mouthful.


--=20
Andrew Poelstra
Director of Research, Blockstream
Email: apoelstra at wpsoftware.net
Web:   https://www.wpsoftware.net/andrew

The sun is always shining in space
    -Justin Lewis-Webster


--XxnP3vfVQL6HUXlF
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEkPnKPD7Je+ki35VexYjWPOQbl8EFAmTWO38ACgkQxYjWPOQb
l8HAvwgAl7rgvJq+5cZCenntjwaa6lKnriNerZZ5G+kuwCbkhUS63bisLeNKhzu1
gRUHRnfLpJIWVaN2Qg0is5KmNl06Gz0MjAmlKEz/To2u9KfkvJL2kXRdMDhFOUeW
Ku7UHc8ey02ASUJeguG2IFuOWAgKPSIubxJRCnffoDssy89Zm40fWfX8EE5cMMog
4fD8IZbziOGxJ0XDj43P8pkeHOoYhpYq+3I8FpV+DX7EtV8R0ZZ/SFB8QrSeg/jW
2422lUApKxB5LDdCOGl8j56cITyrbWyC4fHBH9kUMx5J075PXze/mcL+s6kyFCTB
IrtySiue2WdsVGgPv7fsmiKpFz2yBg==
=/lX4
-----END PGP SIGNATURE-----

--XxnP3vfVQL6HUXlF--