BIP 86: Key Derivation for Single Key P2TR Outputs #1137

1. 
   achow101 commented at 3:01 am on June 26, 2021: member

   This BIP specifies a suggested derivation path to use for single key P2TR outputs, following BIP 43/44.

   Test vectors and the actual derivation path value for the purpose will be set after receiving a BIP number.

2. 
   dr-orlovsky commented at 1:24 pm on June 26, 2021: contributor

   Have you seen by earlier ideas around more generic support for both single- and multisig wallets for P2TR in bitcoin-dev?

   https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-February/018381.html

3. 
   achow101 commented at 4:17 pm on June 26, 2021: member

   Have you seen by earlier ideas around more generic support for both single- and multisig wallets for P2TR in bitcoin-dev?

   Yes, but I think more complicated derivation schemes can come later. Using the system we already have is the path of least resistance and will allow for faster adoption of Taproot in current wallets.

4. achow101 force-pushed on Jun 27, 2021
5. achow101 renamed this:
   New BIP: Derivation scheme for Single Key P2TR based accounts
   New BIP: Key Derivation for Single Key P2TR Outputs
   on Jun 27, 2021
6. in bip-taproot-bip44.mediawiki:58 in 4f9b44b3d6 outdated

   53+===Address derivation===
   54+
   55+
   56+[[bip-0341.mediawiki#cite_ref-22-0|BIP 341]] states: "If the spending conditions do not require a
   57+script path, the output key should commit to an unspendable script path instead of having no
   58+script path. This can be achieved by computing theoutput key point as
   

   ---

   ---

   

   junderw commented at 10:17 pm on June 27, 2021:

   0script path. This can be achieved by computing the output key point as
   

   ---

   

   achow101 commented at 5:00 pm on July 2, 2021:

   FIxed
7. andrewkozlik cross-referenced this on Jun 29, 2021 from issue Support Taproot by tsusanka
8. achow101 force-pushed on Jul 2, 2021
9. luke-jr renamed this:
   New BIP: Key Derivation for Single Key P2TR Outputs
   BIP 86: Key Derivation for Single Key P2TR Outputs
   on Jul 2, 2021
10. luke-jr added the label New BIP on Jul 2, 2021
11. 
    luke-jr commented at 7:56 pm on July 2, 2021: member

    Assigned BIP number 86
12. achow101 force-pushed on Jul 2, 2021
13. achow101 force-pushed on Jul 2, 2021
14. achow101 force-pushed on Jul 2, 2021
15. achow101 force-pushed on Jul 2, 2021
16. Specify BIP 86: Key Derivation for Single Key P2TR Outputs 330b56b358
17. achow101 force-pushed on Jul 2, 2021
18. luke-jr merged this on Jul 2, 2021
19. luke-jr closed this on Jul 2, 2021

    ---

20. 
    benthecarman commented at 12:32 pm on July 3, 2021: contributor

    Is there a extended key version defined for BIP 86 like there was in BIP 84?

    https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki#extended-key-version

21. 
    achow101 commented at 4:29 pm on July 3, 2021: member

    Is there a extended key version defined for BIP 86 like there was in BIP 84?

    This intentionally does not define one.

22. 
    benthecarman commented at 4:43 pm on July 3, 2021: contributor

    Is there a extended key version defined for BIP 86 like there was in BIP 84?

    This intentionally does not define one.

    I think it’d be worthwhile adding the reasoning to the BIP

23. LeHoang88 approved
24. LeHoang88 approved
25. 
    Rspigler commented at 8:20 pm on July 8, 2021: contributor

    I’ve been away, so apologies for the post-merge comments.

    I agree with @achow101 ’s comments on the ML - I believe this is mostly unnecessary with the use of descriptors, but as long as this is for single-sig only, ACK, as it can help with adoption. Hopefully we will eventually move away from this however.

26. 
    benma commented at 4:41 pm on July 10, 2021: none

    Small post-merge comment: The test vectors contain addresses, so it would be great if the BIP mentioned that the addresses are bech32m (BIP-350).

Contributors
achow101 dr-orlovsky junderw luke-jr benthecarman LeHoang88 Rspigler benma

Labels
New BIP