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
Comments
Also, please add |
Also, it looks like there are some new options |
We have the
max-cltv-expiry
option for lnd (lnd/sample-lnd.conf
Line 448 in 6377f98
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 thetime_lock_delta
to higher values on certain channels and on those channels we will need an even higherto_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 longertime_lock_delta
values to allow routing payments for invoices that define a highcltv_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
withUpdateChannelPolicy
since we can updatetime_lock_delta
withUpdateChannelPolicy
.The text was updated successfully, but these errors were encountered: