Basic vault prototype using OP_CAT

Basic vault prototype using OP_CAT

Original Postby rijndael

Posted on: April 11, 2024 22:23 UTC

In addressing the challenges and potential vulnerabilities associated with using input/output ordering for covenant identification without an enforcement mechanism, the discussion highlights a particular case involving a vault.

A suggested mitigation strategy involves introducing a requirement for a signature check to complement the existing script. This approach stems from recognizing the conceptual value of incorporating a "trigger key" as part of the solution, an idea initially overlooked but now acknowledged as beneficial and slated for future implementation.

Further consideration extends to the broader applicability of safeguarding mechanisms within such systems. Specifically, the conversation references the practice of covering the index of the input in the signature message, an approach detailed within the full specification in bip341. This method suggests a viable means of enforcing that the covenant input occupies a specific index, thereby enhancing the security and predictability of transactions.

The issue of determining a reasonable threshold for what constitutes 'dust' or negligible output values in transactions was also addressed. The choice of considering outputs valued at 546 as 'dust' was mentioned, indicating a practical approach to defining minimal transaction output values based on observed data, albeit acknowledging this as an area of subjective judgment.