Vaulting (Was: Automatically reverting ("transitory") soft forks)



Summary:

In this email conversation, Billy Tetrud and Russel are discussing the Original MES vault and how it commits to the destination address during unvaulting. Russel is trying to understand how OP_COV works in relation to this. They discuss two possibilities for how the intended destination could be predetermined and hardcoded or specified as a number indicating the number of stack items in the pattern. However, they note that both options are quite cumbersome and expensive to spend with. Next, Billy explains his understanding of the COV proposal in MES, which lets you check that the output's scriptPubKey matches the corresponding script item from the stack, but with wildcard values using OP_PUBKEY and OP_PUBKEYHASH as placeholders. He notes that if COV was used alone, these wildcards would be third-party malleable, but signing the transaction with the hot wallet key removes the malleability. There's no need to rotate anything into place.


Updated on: 2023-06-15T19:38:44.065243+00:00