Key paths and committed script paths

Taproot changes how a Bitcoin output can commit to spending conditions. A key-path spend uses a signature for an output key, while a script-path spend reveals the applicable script and the information needed to prove its inclusion in the commitment. Unused alternative scripts need not all be published during that script-path spend. BIP-341 specifies the output and spending rules, while related BIPs define Schnorr signatures and the script-language changes used with the upgrade.

A cooperative spending example

Imagine participants who can agree on an ordinary cooperative spend but also need a fallback condition if cooperation fails. A Taproot design can commit to that alternative while allowing a cooperative key-path spend that does not disclose the unused script structure. If the fallback is exercised, the relevant branch is revealed. The exact signing arrangement still requires appropriate wallet and protocol support; Taproot does not automatically combine arbitrary signatures or make a poorly designed recovery policy work correctly.

Privacy gains have a specific scope

Hiding unused spending branches is not the same as hiding the entire transaction graph. Observers can still inspect transaction inputs, outputs, and amounts, and a revealed script can expose information about the exercised condition. Wallet behavior, address reuse, and other activity also affect privacy. Research should therefore describe which information a particular spend conceals instead of claiming that Taproot makes Bitcoin anonymous.

It likewise does not change a token inscription or application into a consensus endorsement; those applications build their own conventions on top of available transaction features.