Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Pay to Taproot is the native SegWit v1 output format. It commits directly to a public key which can optionally be tweaked with the hash of a script tree. This combines capabilities of previous output formats which were usually based on either a public key hash or a script hash. P2TR addresses are Bech32m encoded and start with the prefix `bc1p`.
3
votes
1
answer
401
views
Tests for Pay To Taproot addresses?
I am working on a tool and want to see if my P2TR conversions/encodings are outputting the correct P2TR address. … Is this the correct P2TR for this private key. …
4
votes
0
answers
492
views
P2TR bech32m mismatch
When attempting to create a p2tr address using the private key 0x0000...01 I get, bc1pmfr3p9j00pfxjh0zmgp99y8zftmd3s5pmedqhyptwy6lm87hf5sspknck9 which does not match the provided test vectors provided … 1225
However if I search this bech32m address in github or google I find others arriving at this same address for key 0x0000..01 so I know I at least have the bech32m encoding right, but not right for p2tr …