From: Brandon Black <freedom@reardencode.com>
To: moonsettler <moonsettler@protonmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] LNHANCE a soft-fork package
Date: Thu, 6 Nov 2025 09:34:16 -0800 [thread overview]
Message-ID: <aQzcGITQE3ckHB7K@console> (raw)
In-Reply-To: <g66Df5xz1qORjBz4xirSJNBBCUPo8mWf7InVGww1nRqk_gyJE0utZ-EB_VyT9GN6l1yaxbXHl27y6ii6aK6aAoal4vA2ArU7kQg5LzPs93w=@protonmail.com>
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 bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aQzcGITQE3ckHB7K%40console.
prev parent reply other threads:[~2025-11-06 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 23:05 'moonsettler' via Bitcoin Development Mailing List
2025-11-06 17:34 ` Brandon Black [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aQzcGITQE3ckHB7K@console \
--to=freedom@reardencode.com \
--cc=bitcoindev@googlegroups.com \
--cc=moonsettler@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox