Add LNHANCE topic page#867
Open
dergigi wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
TumaBitcoiner
requested changes
Jun 16, 2026
|
|
||
| Its designers frame the bundle around practical second-layer and custody use cases. The proposal is meant to improve designs for [Eltoo](/topics/eltoo)-style Lightning channels, [Ark](/topics/ark)-like systems, vaults, payment pools, and other shared-UTXO constructions that benefit from predictable transaction trees and more flexible signature checks. | ||
|
|
||
| LNHANCE remains a proposal. It has not been activated on Bitcoin, and the tradeoffs are still being explored in research, specifications, and proof-of-concept implementations such as the LNHANCE Expedition work funded by OpenSats. |
Contributor
There was a problem hiding this comment.
Suggested change
| LNHANCE remains a proposal. It has not been activated on Bitcoin, and the tradeoffs are still being explored in research, specifications, and proof-of-concept implementations such as the LNHANCE Expedition work funded by OpenSats. | |
| LNHANCE remains a proposal. It has not been activated on Bitcoin, and the tradeoffs are still being explored in research, specifications, and proof-of-concept implementations such as the [LNHANCE Expedition][/blog/fifteenth-wave-of-bitcoin-grants#lnhance] work funded by OpenSats. |
Maybe?
|
|
||
| LNHANCE is a proposed Bitcoin soft fork bundle aimed at making advanced contract constructions easier to express on chain. The proposal combines [OP_CTV](/topics/op-ctv), [OP_CSFS](/topics/op-csfs), `OP_PAIRCOMMIT`, and `OP_INTERNALKEY` to support protocols that need more structured spending conditions than Bitcoin exposes today. | ||
|
|
||
| Its designers frame the bundle around practical second-layer and custody use cases. The proposal is meant to improve designs for [Eltoo](/topics/eltoo)-style Lightning channels, [Ark](/topics/ark)-like systems, vaults, payment pools, and other shared-UTXO constructions that benefit from predictable transaction trees and more flexible signature checks. |
Contributor
There was a problem hiding this comment.
Suggested change
| Its designers frame the bundle around practical second-layer and custody use cases. The proposal is meant to improve designs for [Eltoo](/topics/eltoo)-style Lightning channels, [Ark](/topics/ark)-like systems, vaults, payment pools, and other shared-UTXO constructions that benefit from predictable transaction trees and more flexible signature checks. | |
| Its designers frame the bundle around practical second-layer and custody use cases. The proposal is meant to improve designs for [Eltoo](/topics/eltoo)-style Lightning channels, [Ark](/topics/ark)-like systems, [vaults][/topics/vaults], payment pools, and other shared-UTXO constructions that benefit from predictable transaction trees and more flexible signature checks. |
| ## References | ||
|
|
||
| - [lnhance.org](https://lnhance.org/) | ||
| - [Bitcoin Optech Newsletter #285](https://bitcoinops.org/en/newsletters/2024/01/17/) |
Contributor
There was a problem hiding this comment.
Suggested change
| - [Bitcoin Optech Newsletter #285](https://bitcoinops.org/en/newsletters/2024/01/17/) | |
| - [Bitcoin Optech Newsletter #285](https://bitcoinops.org/en/newsletters/2024/01/17/#new-lnhance-combination-soft-fork-proposed) |
We can link directly to the specific piece of news!
| aliases: ['LNhance', 'LNHANCE soft fork', 'LNhance soft fork'] | ||
| --- | ||
|
|
||
| LNHANCE is a proposed Bitcoin soft fork bundle aimed at making advanced contract constructions easier to express on chain. The proposal combines [OP_CTV](/topics/op-ctv), [OP_CSFS](/topics/op-csfs), `OP_PAIRCOMMIT`, and `OP_INTERNALKEY` to support protocols that need more structured spending conditions than Bitcoin exposes today. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new
LNHANCEtopic page and links the existing fifteenth wave grant post to it.data/topics/lnhance.mdxLNhance soft forkfootnote infifteenth-wave-of-bitcoin-grants.mdxwith an internal topic linkCloses https://github.com/OpenSats/content/issues/260
Build preview:
/topics/lnhance/blog/fifteenth-wave-of-bitcoin-grants