New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Pay to Taproot outputs and Bech32m addresses #567
Comments
To give a concrete example, in transaction b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41, the input addresses should be |
Yes, we plan to support Taproot in both the interface and the API. Not sure though if we’ll be converting existing |
Great, thanks for the update. |
Hi @Har01d. I just wanted to bump this issue since Taproot will be activated in a few days. |
Hi @xekyo, yes, we'll be rolling out Taproot for Bitcoin, Groestlcoin, and Bitcoin Testnet in a day or two. |
Here's the official announcement: https://twitter.com/Blockchair/status/1458817396433731585 We'll be reindexing Bitcoin to include some of the Bitcoin Testnet is fully reindexed and is ready for testing. |
Please add Currently only xpub, ypub, and zpub are supported. |
I'm reaching out to ask about Blockchair's plans to prepare for the upcoming Taproot softfork in November.
As you probably know, the BIP341/BIP342 "Taproot" proposal is going to activate on Bitcoin mainnet on block 709632 (expected around November 20th, 2021). This will introduce the "Pay to Taproot" output type using the new "bech32m" address format specified in BIP350. I was wondering whether Blockchair is preparing to index and display bech32m addresses by the time that Taproot activates.
The text was updated successfully, but these errors were encountered: