[bitcoin-dev] Congestion Control via OP_CHECKOUTPUTSHASHVERIFY proposal

ZmnSCPxj ZmnSCPxj at protonmail.com
Wed May 22 02:51:52 UTC 2019

Good morning Jeremy,

>If a sender needs to know the recipient can remove the covenant before spending, they may request a signature of an challenge string from the recipients

The recipients can always choose to destroy the privkey after providing the above signature.
Indeed, the recipients can always insist on not cooperating to sign using the taproot branch and thus force spending via the `OP_CHECKOUTPUTSHASHVERIFY`.


More information about the bitcoin-dev mailing list