🔖 Title: segwit naming ambiguity
🏷️ Categories: bitcoin-dev
nostr:naddr1qqjrzvpexqmxgvp495er2d35956rjv3k95ux2cfj95mnzvp38qmrsen9xscryqg5waehxw309aex2mrp0yhxgctdw4eju6t0qy2hwumn8ghj7etyv4hzumn...
📅 Original date posted:2023-08-11
🗒️ Summary of this message: The author is asking for clarification on the expected return value of the function `is_segwit()` for a p2tr transaction and if there is an official name for segwit v0.
📝 Original message:
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.
🗒️ Summary of this message: The author is asking for clarification on the expected return value of the function `is_segwit()` for a p2tr transaction and if there is an official name for segwit v0.
📝 Original message:
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.
1
