Definition
The annex is an optional final element in a Taproot input's witness, recognized by a leading 0x50 byte. It is a piece of reserved space that the current consensus rules commit to in the signature but otherwise ignore. No soft fork has yet assigned it any meaning, so today it carries no data of consequence and simply adds to transaction weight.
Why 0x50
The 0x50 prefix was chosen because it is an unpaired byte value that cannot be confused with a valid key-path or script-path witness. Taproot leaf versions consume even byte values together with their adjacent odd value (for Y-coordinate parity), so reserving a single unpaired byte for the annex preserves the maximum number of future leaf versions. The annex, when present, is always the very last witness element for both spend types.
Intended Future Use
The annex is a forward-compatibility hook. A future upgrade could use it to declare the validation cost of expensive new opcodes without forcing nodes to know the spent script in advance, or to carry other metadata that must be committed to by the signature. Because no rules govern its contents yet, wallets are warned not to include an annex in real transactions, and standard relay policy rejects them to prevent accidental, irreversible fund loss.
The annex is committed to by the signature, so it interacts with the SIGHASH Flags that define signature coverage, and it sits in the same witness structure proven by the control block (Taproot).
In Simple Terms
The annex is an optional final element in a Taproot input’s witness, recognized by a leading 0x50 byte. It is a piece of reserved space…