I was surprised to learn that there are only 20 key-path and 5 script-path spends of P2TR outputs on SigNet yet. Had assumed more people played around with taproot on SigNet.

Maybe it's to early for e.g. wallets to be testing this or they test on regtest.


@0xb10c Perhaps a tutorial/blog is in order? :) It is fiddly ie you can't generate a bech32m address in the Core wallet. You have to import a Taproot descriptor and then the wallet should be able to recognize it and spend from it with 22.0. Other ways of spending from P2TR addresses aren't supported.

@0xb10c I agree that it is surprising that more long term Core contributors haven't done it yet but for the less technical it isn't obvious.

Sign in to participate in the conversation
Bitcoin Mastodon

Bitcoin Maston Instance