From: Antoine Poinsot <darosior@protonmail•com>
To: Tobin Harding <me@tobin•cc>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] segwit naming ambiguity
Date: Fri, 11 Aug 2023 07:49:15 +0000 [thread overview]
Message-ID: <J49TMTkrBU477h94mrYt_UkLIif_shPrWkS4VPUVTT-g_b2PtPRy7Aa0qEFOibwDEj6X069lWVr8oTMX6QJSNuOSQopLK3ywBfFiQiHMMZk=@protonmail.com> (raw)
In-Reply-To: <ZNW9BenWIhgX95zl@alke>
Hey Tobin,
I would assume `is_segwit()` is true for P2TR, since Taproot is Segwit.
I'm not aware of a different term for "is P2WPKH or P2WSH" that "is Segwit v0". Maybe look into Murch's BIP about wording? He could have a better name for Segwit v0 there.
Cheers,
Antoine
------- Original Message -------
On Friday, August 11th, 2023 at 6:45 AM, Tobin Harding via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Question for OG bitcoin API designers please.
>
> If you were to see the following function
>
> `is_segwit()`
>
> would you assume it returns `true` or `false` for a p2tr transaction?
>
>
> 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?
>
>
> Thanks,
> Tobin.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2023-08-11 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 4:45 Tobin Harding
2023-08-11 7:38 ` symphonicbtc
2023-08-11 7:49 ` Antoine Poinsot [this message]
2023-08-11 10:06 ` Pavol Rusnak
2023-08-11 13:45 ` Andrew Poelstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='J49TMTkrBU477h94mrYt_UkLIif_shPrWkS4VPUVTT-g_b2PtPRy7Aa0qEFOibwDEj6X069lWVr8oTMX6QJSNuOSQopLK3ywBfFiQiHMMZk=@protonmail.com' \
--to=darosior@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=me@tobin$(echo .)cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox