A Taproot key path spend reveals no script: its witness carries a single Schnorr signature, checked against the 32-byte public key already in the output being spent.
Sources and checks
T1BIP 341, TaprootBIP, says this directly
If there is exactly one element left in the witness stack, key path spending is used:
Specification, Script validation rules, read 2026-11-20
T1BIP 340, Schnorr Signatures for secp256k1BIP, supports part of it
Encoding only the X coordinate, resulting in 32-byte public keys and 64-byte signatures.
Design, encoding choices, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
if (!checker.CheckSchnorrSignature(stack.front(), program, SigVersion::TAPROOT, execdata, serror)) {
VerifyWitnessProgram, Taproot key path branch, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if (!checker.CheckSchnorrSignature(stack.front(), program, SigVersion::TAPROOT, execdata, serror)) {'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 17:27 UTCblock 976,759
Published Revision 1, run 2026-11-20-seed-taproot