<p>You clarified in the comments that you are using <a href="https://cloud.google.com/blog/products/data-analytics/introducing-six-new-cryptocurrencies-in-bigquery-public-datasets-and-how-to-analyze-them" rel="nofollow noreferrer">BigQuery datasets</a> and so you are right Taproot transactions should eventually be labelled as <code>witness_v1_...</code>. 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.</p>

CC BY-SA 4.0
2021-11-15T21:15:01.747Z
2021-11-15T21:15:01.747Z
Michael Folkson
<p>From <a href="https://bitcoinmagazine.com/technical/bitcoin-taproot-explainer" rel="nofollow noreferrer">bitcoin magazine</a>, I saw that</p>
<blockquote>
<p>When Taproot/Schnorr goes live soon, they will use the new witness version one to distinguish them from older Segregated Witness transactions.</p>
</blockquote>
<p>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.</p>
<p>Should the new taproot txns be labelled as witness_v1? or is there any other way to identify them on big-query?</p>
<p>Thanks</p>

CC BY-SA 4.0
2021-11-15T20:26:24.633Z
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
Michael Folkson
CC BY-SA 4.0
2021-11-15T20:31:27.000Z
BigQuery is just a data warehouse, I'm assuming it isn't manipulating and presenting  blockchain data to you. Please correct me if wrong!
Michael Folkson
CC BY-SA 4.0
2021-11-15T20:52:53.423Z
Yup, this is processed data from [Big Querys Crypto Bitcoin](https://cloud.google.com/blog/products/data-analytics/introducing-six-new-cryptocurrencies-in-bigquery-public-datasets-and-how-to-analyze-them) 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
Camila Burne
<taproot><database>
How to identify Taproot transaction using big query?
Camila Burne
# How to identify Taproot transaction using big query?

(Asked by: username_0 on 2021-11-15)

From [bitcoin magazine](https://bitcoinmagazine.com/technical/bitcoin-taproot-explainer), 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

**Tags:** taproot, database

> **Comments:**
> **username_1**: 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  
> **username_1**: BigQuery is just a data warehouse, I'm assuming it isn't manipulating and presenting  blockchain data to you. Please correct me if wrong!  
> **username_0**: Yup, this is processed data from [Big Querys Crypto Bitcoin](https://cloud.google.com/blog/products/data-analytics/introducing-six-new-cryptocurrencies-in-bigquery-public-datasets-and-how-to-analyze-them) 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  

---

## 1 answers

### Answer by username_1 on 2021-11-15. Score: 2 | Accepted answer

You clarified in the comments that you are using [BigQuery datasets](https://cloud.google.com/blog/products/data-analytics/introducing-six-new-cryptocurrencies-in-bigquery-public-datasets-and-how-to-analyze-them) 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.


---

