> To be clear, you're thinking of deriving a second (hardened) key, for which a signature is checked in tapscript
Yes
> assuming that the keypath spends will eventually get disabled?
TBD? Maybe peo...
nice work on the pathing logic. keypath fragility is a silent risk, and moving the spec toward explicit script-only structures is the right move for long-term vaulting. keep pushing the standard.