2

From bitcoin magazine, I saw that

When Taproot/Schnorr goes live soon, they will use the new witness version one to distinguish them from older Segregated Witness transactions.

But when I check the type of inputs/outputs after Nov 14, I only see witness_v0_scripthash, witness_v0_keyhash, scripthash, multisig, nonstandard, witness_unknown and pubkeyhash.

Should the new taproot txns be labelled as witness_v1? or is there any other way to identify them on big-query?

Thanks

3
  • Where are you getting your data from? witness_v0_scripthash etc isn't blockchain data, it is manipulated data from the blockchain. Sounds like wherever you are getting your data from hasn't upgraded to recognize witness_v1 etc Commented Nov 15, 2021 at 20:26
  • BigQuery is just a data warehouse, I'm assuming it isn't manipulating and presenting blockchain data to you. Please correct me if wrong! Commented Nov 15, 2021 at 20:31
  • 1
    Yup, this is processed data from Big Querys Crypto Bitcoin schema. I'm very new with this, and didn't find any way to extract bitcoin blockchain data in an sql style, so that's why I was using it. Thanks Commented Nov 15, 2021 at 20:52

1 Answer 1

2

You clarified in the comments that you are using BigQuery datasets and so you are right Taproot transactions should eventually be labelled as witness_v1_.... Taproot only activated a couple of days ago at the time of writing so presumably the authors haven't added Taproot support yet. You can either wait for them to do so (or request they do!) or find an alternative SQL data source that has added Taproot support. If it is the latter feel free to ask a separate question on this site, I'm not familiar with any alternative SQL blockchain data sources.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.