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

[feature]: allow setting to_self_delay with OpenChannel #8635

Open
AndySchroder opened this issue Apr 10, 2024 · 2 comments
Open

[feature]: allow setting to_self_delay with OpenChannel #8635

AndySchroder opened this issue Apr 10, 2024 · 2 comments
Labels
enhancement Improvements to existing features / behaviour

Comments

@AndySchroder
Copy link

We have the max-cltv-expiry option for lnd (

; max-cltv-expiry=2016
) which I believe sets the to_self_delay value for the channel. This seems to be a global value for all channels that are opened. As the fee markets get more competitive, we may need more time to get closing transactions confirmed cheaply. We shouldn't have to restart lnd to change this. Also, we may want to set the time_lock_delta to higher values on certain channels and on those channels we will need an even higher to_self_delay value than normal channels to work properly.

An example of a channel that has a higher time_lock_delta value from a normal channel is if that channel is used for long term HOLD invoices. We may want to offer longer time_lock_delta values to allow routing payments for invoices that define a high cltv_expiry but charge a higher fee on those channels for agreeing to lock up funds for a longer period of time.

Once lightning/bolts#1117 gets complete, would also like the ability to update to_self_delay with UpdateChannelPolicy since we can update time_lock_delta with UpdateChannelPolicy.

@AndySchroder AndySchroder added the enhancement Improvements to existing features / behaviour label Apr 10, 2024
@AndySchroder
Copy link
Author

Also, please add time_lock_delta. I realize this is a policy that can be update with UpdateChannelPolicy, but OpenChannel now allows setting fee_rate and base_fee. It make sense to be able to set all channel policies when opening a channel and not having to quickly update them after opening (and potentially already announcing).

@AndySchroder
Copy link
Author

Also, it looks like there are some new options inbound_base_fee_msat and inbound_fee_rate_ppm in UpdateChannelPolicy. I think these come from #6703 . They should probably be added too if they are not already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements to existing features / behaviour
Projects
None yet
Development

No branches or pull requests

1 participant