# LNHANCE bips and implementation

**URL:** <https://delvingbitcoin.org/t/lnhance-bips-and-implementation/376>\
**Category:** Protocol Design\
**Created:** [January 7, 2024, 6:40pm UTC](https://delvingbitcoin.org/t/lnhance-bips-and-implementation/376 "2024-01-07T18:40:08Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![reardencode](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/reardencode/32/27_2.png) [@reardencode](https://delvingbitcoin.org/u/reardencode)\
**Post date:** [January 18, 2024, 6:22am UTC](https://delvingbitcoin.org/t/lnhance-bips-and-implementation/376/12 "2024-01-18T06:22:10Z")

</div>

Tonight, I created a PR against @ajtowns 's binana to create numbers for CSFS and INTERNALKEY.

> <https://github.com/bitcoin-inquisition/binana/pull/1>

I also created draft PRs for ctv, internalkey, csfs alone against core.

> <https://github.com/bitcoin/bitcoin/pull/29280>
>
> This pull request forks from #29198 and only includes the implementation of OP\_C…HECKTEMPLATEVERIFY, its tests (except the functional ones), and standardization of bare OP\_CHECKTEMPLATEVERIFY locking scripts.

> <https://github.com/bitcoin/bitcoin/pull/29269>
>
> This pull request forks from #29198 and includes only OP\_INTERNALKEY and its tes…ts.

> <https://github.com/bitcoin/bitcoin/pull/29270>
>
> This pull request forks from #29198 and includes only OP\_CHECKSIGFROMSTACK(VERIF…Y) and their tests.

These 3 PRs include everything from #29198 except activation and functional tests that depend on CTV being active in regtest. They conflict with each other, due to overlap in SCRIPT\_VERIFY\_FLAGS numbers, which I’m not sure the best way to deal with.

---

_[View the full topic](https://delvingbitcoin.org/t/lnhance-bips-and-implementation/376)._