Apparently (credit 0xB10C) there are only 20 key-path and 5 script-path spends of P2TR outputs on the Signet blockchain today (July 7th 2021). How can I increase this number today with say the Bitcoin Core wallet in the upcoming 22.0 release? If there are multiple ways (of varying levels of complexity) please outline them all.

1 Answer 1


This is a draft answer (incomplete).

To get set up on Signet ie sync the Signet chain and claim some Signet Bitcoin, follow these instructions. (You can run a Signet node in parallel with your mainnet node, ie same hardware)

You now have funds at a non-P2TR (i.e. SegWit v0, bech32) Signet address. Now you need to generate a P2TR address to send funds to so you have funds at a P2TR address (so you can spend from it).

You can't generate a P2TR (SegWit v1, bech32m) address in the wallet using getnewaddress:

./bitcoin-cli -signet -rpcwallet=insert_wallet_name getnewaddress "" "bech32m"


error code: -12
error message:
Error: No bech32m addresses available.

So you need to construct a Taproot descriptor manually and then import it into your descriptor wallet.

An example Taproot descriptor is:


which describes a P2TR output with the c6... x-only pubkey as internal key and two script paths.

If you only want to do a key path spend you only need the equivalent of:


You can import a tr(xprv/insert_xpriv_here) descriptor so that your descriptor wallet has the private key to spend from it.

To do: Send signet Bitcoin to this descriptor wallet, spend back to a SegWit v0 address (sendtoaddress) Include generation of xprv?


This was also discussed on the bitcoin-dev mailing list.

  • 2
    Can you add an example for how to import the descriptor? I'm trying importdescriptors "tr(c6047f9441ed7d6d3045406e95c07cd85c778e4b8cef3ca7abac09b95c709ee5)" (in the console of Bitcoin Core 22.0) but I always get Error parsing JSON.
    – Andreas
    Oct 7, 2021 at 8:17
  • 1
    @Andreas: Let me know if "Import a taproot descriptor (of the form "tr(KEY)"), as active descriptor (with active=true), where KEY can be a tprv.../* or any other supported key expression." from Pieter's mailing list post resolves your problem. Thanks Oct 10, 2021 at 12:57
  • 1
    The importdescriptors RPC takes as argument a list of objects, each with a decriptor and a few other parameters. Look at the RPC help (help importdescriptors) and the examples there. Oct 10, 2021 at 13:59

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.