As the original proposer of LNHANCE, let it be known that I still think it's a great direction for bitcoin script improvements. This set of opcodes is carefully crafted to offer significant utility with minimal footguns or even sharp corners.
I am also a fan of the competing TEMPLATEHASH+CSFS+IKEY proposal which removes the blunted corner of modifying legacy script while adding the blunted corner of committing to the annex. It also removes the hacky sibling commitment via scriptSig, loses the ability to use simple vaults with legacy ECDSA-only signing infrastructure, and saves just under 8vB in a typical lightning symmetry uncontested force close scenario. Both are excellent directions to move bitcoin script and I hope to see one of the two enforced on the network in the (not too distant) future. Best, --Brandon -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aQzcGITQE3ckHB7K%40console.
