ScanTool v1.0.2

This is a bug fix release. It only affects the identification of tap script field types in ordinals.

Schnorr signatures can only be identified by their lengths. There are no other easily identifiable features about them. They are always 64 bytes long. In the bitcoin blockchain, if they have a sighash byte appended, they are 65 bytes long. Previously, if a segregated witness field or tap script field was 64 or 65 bytes long and the input spend type was identified as Taproot Script Path, the field was assumed to be a Schnorr signature.

Ordinals are an exception to this rule. Ordinals encode many different types of data into various fields in the tap script. These fields can easily be 64 or 65 bytes in length, but they are not Schnorr signatures. Since actual signatures do not appear in ordinal scripts under normal circumstances, it is better to assume that such fields in ordinal scripts are data fields and not signatures.

Transaction a98d2360e6c87c742df8fdbca97f6bbba6b1f58849c6a3a104210b6925f859fa is one example of this.