Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option_zero_reserve (FEATURE 64/65) #1140

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

t-bast
Copy link
Collaborator

@t-bast t-bast commented Feb 16, 2024

Lightning channels require nodes to lock some of their channel funds into a channel reserve, which cannot be used for payments made on that channel. This guarantees that both nodes always have an output in the commitment transaction, which they will lose if they publish a revoked commitment.

While this requirement is generally useful, it creates inefficiencies since that liquidity can't be used to relay payments, and provides a bad user experience. In some settings, we may want to remove that channel reserve and allow nodes to use all of their channel funds.

The option_zero_reserve feature lets nodes advertise that they allow their peers to disable the channel reserve on their side, and may lift the same requirement in response.

This is an alternative to #1133

Lightning channels require nodes to lock some of their channel funds
into a channel reserve, which cannot be used for payments made on
that channel. This guarantees that both nodes always have an output
in the commitment transaction, which they will lose if they publish
a revoked commitment.

While this requirement is generally useful, it creates inefficiencies
since that liquidity can't be used to relay payments, and provides a
bad user experience. In some settings, we may want to remove that
channel reserve and allow nodes to use all of their channel funds.

The `option_zero_reserve` feature lets nodes advertise that they
allow their peers to disable the channel reserve on their side,
and may lift the same requirement in response.
@Impa10r
Copy link

Impa10r commented Sep 13, 2024

Any traction on this? Will this option work with already opened channels, or only affect the future ones?

@t-bast
Copy link
Collaborator Author

t-bast commented Sep 13, 2024

This is implemented on our side, this proposal is waiting for reviews and implementation by the other teams.
It will only apply to new channels for now, but could be applied to existing channels via #1117 in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants