pull down to refresh

Does anyone know if a mechanism exists to add a time lock to a transaction in combination with the ability to cancel the transaction during the delay?
I am aware that HTLCs (Hashed Time Lock Contracts) in the Lightning network do something similar to this. I am more so envisioning some kind of standardized fraud / scam prevention mechanism, so if someone realizes something is wrong before the transaction completes they can submit a cancellation transaction.
Lots of scammers rely on getting people to act too quickly, and by the time the victim realizes they've made a mistake there is nothing they can do.
Thoughts?
You can time-lock a transaction so that the counterparty has to wait to spend it, but you can spend it right away.
There are ways to simulate a "vault" using pre-signed transactions and ephemeral key-pairs, so that an attacker is forced to wait for a duration before sweeping funds.
It is a cumbersome setup, though. A better solution would be a native opcode for the process of storing funds, which is what the OP_VAULT proposal aims to be.
reply
Thank you very much for the info. This is a rabbit hole worth going down.
I've seen controversy about censorship with covenants and similar proposals, but I don't know enough to be super opinionated.
reply