Key Derivation for Single Key P2TR Outputs

The five-minute read

One action, walked through

1. Open BIP 86 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This document suggests a derivation scheme for HD wallets whose keys are involved in single key P2TR ([[bip-0341.mediawiki|BIP 341]]) outputs as the Taproot internal key.
3. Name the object that changes: P2TR.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 86 at the status the text itself states: Deployed.
• The object that has to change is P2TR. A neighbouring document with a similar name is not this one.
• Wallet support is not the same as consensus validity.

What happened after the paper

The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is covered by the signed bytes in Key Derivation for Single Key P2TR Outputs?
• Can the same signature be replayed on another chain, account, or message?
• Which primitive does the text require: P2TR?

Terms

BIP 86

The public text titled Key Derivation for Single Key P2TR Outputs.

Deployed

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A signature that does not commit to what the user saw can be replayed into a different spend, a different chain, or a different message.

What the design proposes

• This document suggests a derivation scheme for HD wallets whose keys are involved in single key P2TR ([[bip-0341.mediawiki|BIP 341]]) outputs as the Taproot internal key.
• With the usage of single key P2TR transactions, it is useful to have a common derivation scheme so that HD wallets that only have a backup of the HD seed can be likely to recover single key Taproot outputs.
• Although there are now solutions which obviate the need for fixed derivation paths for specific script types, many software wallets and hardware signers still use seed backups which lack derivation path and script information.

How the mechanism is specified

• Taken from the specification, the next constraint is: With the usage of single key P2TR transactions, it is useful to have a common derivation scheme so that HD wallets that only have a backup of the HD seed can be likely to recover single key Taproot outputs.
• Locate P2TR in BIP 86 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A signature scheme is not a privacy system. It hides the signer only if the protocol says so.
• Wallet support is not the same as consensus validity.
• The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 86 when a pitch says 'Key Derivation for Single Key P2TR Outputs' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.