public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tobin Harding <me@tobin.cc>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] segwit naming ambiguity
Date: Fri, 11 Aug 2023 14:45:57 +1000	[thread overview]
Message-ID: <ZNW9BenWIhgX95zl@alke> (raw)

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.


             reply	other threads:[~2023-08-11  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  4:45 Tobin Harding [this message]
2023-08-11  7:38 ` [bitcoin-dev] segwit naming ambiguity symphonicbtc
2023-08-11  7:49 ` Antoine Poinsot
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=ZNW9BenWIhgX95zl@alke \
    --to=me@tobin.cc \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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