Timeline for P2TR bech32m mismatch
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2021 at 0:37 | comment | added | Pieter Wuille | The 0x0000...0001 key is used for the address of one of the outputs of the test transaction there. The input keys are all random, and listed in the vector data. | |
| Nov 14, 2021 at 0:27 | history | edited | m1xolyd1an |
add nodejs tag
|
|
| Nov 14, 2021 at 0:24 | comment | added | m1xolyd1an | Oh excellent news! I must have misunderstood your post when you said you used the 0x0...01 key because I couldn't locate this P2TR address in the test vectors post but now I'm looking at it again it must have been the input which explains why that address doesn't appear here github.com/bitcoin/bips/pull/1225#issuecomment-958124970 | |
| Nov 13, 2021 at 16:17 | comment | added | Pieter Wuille |
Indeed, I also get bc1pmfr3p9j00pfxjh0zmgp99y8zftmd3s5pmedqhyptwy6lm87hf5sspknck9 for the key-only P2TR address for private key 0x000...0001.
|
|
| Nov 13, 2021 at 16:12 | comment | added | Ava Chow♦ | Which test vector does not match? I don't see one for a private key of 1. AFAICT, you have the correct address. | |
| Nov 13, 2021 at 7:21 | history | asked | m1xolyd1an | CC BY-SA 4.0 |