You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue: Currently, if you take your xud setup down (with channels open to some other nodes) for >20 minutes and bring it up again, you will need to wait 19 minutes for channels to get re-enabled and swaps to work.
Options
a)--chan-disable-timeout, but this will increase routing failures drastically since nodes will try to route via disabled channels
b) --chan-enable-timeout and configure the timeout to something short and check that it works in both directions. Channels get disabled after 10s but also re-enabled after 10s.
c) ?
The text was updated successfully, but these errors were encountered:
Which option do you prefer? I would vouch for b) with something like 10s, since this is the "proper" way and should work accross Simnet/Testnet/Mainnet.
The issue: Currently, if you take your xud setup down (with channels open to some other nodes) for >20 minutes and bring it up again, you will need to wait 19 minutes for channels to get re-enabled and swaps to work.
As per lightningnetwork/lnd#3328 (comment) we should change lnd's config, question is how.
Options
a)
--chan-disable-timeout
, but this will increase routing failures drastically since nodes will try to route via disabled channelsb)
--chan-enable-timeout
and configure the timeout to something short and check that it works in both directions. Channels get disabled after 10s but also re-enabled after 10s.c) ?
The text was updated successfully, but these errors were encountered: