CTV+CSFS: Can we reach consensus on a first step towards covenants?

The discussion revolves around the integration and potential challenges of incorporating legacy scripting within modern blockchain protocols, particularly focusing on a specific use-case deemed less compelling due to these challenges. The author suggests that if legacy script support is considered crucial, it should be introduced as a new segregated witness (segwit) output type. This approach would allow it to be evaluated based on its own merits independently from existing features. Drawing from personal experience with the P2A proposal, the writer underscores the practicality of segregating such features to facilitate clearer assessment and integration.

Further technical recommendations are made for a post-segwit/taproot environment, emphasizing two main strategies. Firstly, the transition to OP_SUCCESSx CTV, which pushes to stack in tascript++, is advocated. This method signifies a move towards more efficient and streamlined scripting processes. Secondly, the proposition of a P2CTV softfork is detailed, specifying its structure: it should either consist of a single <32 bytes data> segment for an upgrade hook (to ensure it wasn't intended for alternate uses), or a combination of <2> and <32 bytes data>, accommodating an unknown witness version with address capabilities. Both scenarios require empty witness data or scriptSig upon spend, maintaining identical hashing checks on spending transactions. These suggestions aim to simplify the handling of legacy scripts by removing the need to consider them, thereby streamlining the review process and enhancing overall protocol efficiency.