When spending a Taproot script-path output with SIGHASH_ANYPREVOUT (BIP118), I want to understand what exactly is committed to regarding the script tree.
Specifically: if two UTXOs have the same executed leaf (same TapLeaf hash) but different TapTree structures (different Merkle paths), will the same APO signature validate against both?
I constructed a multi-round Eltoo chain on Inquisition signet, and observed that the APO signature can still be reused across rounds and successfully spend the output. I also confirmed that the same APO signature can spend two different UTXOs with identical scripts and amounts (tx1, tx2).
This suggests that the signature commits to the TapLeaf hash, but not the full Merkle path — and I’d like to confirm whether this is the correct interpretation.
