Add LNHANCE topic page #867
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,18 @@ | ||||||
| --- | ||||||
| title: 'LNHANCE' | ||||||
| summary: 'A proposed Bitcoin soft fork bundle that combines new script features to enable richer Lightning, Ark, vault, and shared-UTXO designs.' | ||||||
| category: 'Bitcoin' | ||||||
| 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. | ||||||
|
|
||||||
| 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
|
||||||
|
|
||||||
| 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
Maybe? |
||||||
|
|
||||||
| ## 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
We can link directly to the specific piece of news! |
||||||
| - [LNHANCE-Expedition](https://github.com/LNHANCE-Expedition) | ||||||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added issues for
OP_PAIRCOMMIT(#871) andOP_INTERNALKEY(#872)