-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[bug]: edge not found
when option-scid-alias=true
#9444
Comments
second part of the log
|
Hi @feelancer21, I’ve been unable to reproduce the issue locally so far. To help with further investigation, could you please provide the following details (with any sensitive data masked)?
Additionally, could you clarify whether this issue occurs with both public and private channels, or only for one type? Finally, for confirmation, you're still able to see the channels listed in |
Conf of the node opened the channels
Conf of the node accepted the channels
|
Background
I have activated
option-scid-alias
on both my testnet3 nodes, but not activatedprotocol.zero-conf
.I then opened around 15 public and private channels between the nodes. 5 of them are now in an
edge not found
state on both nodes (public and private as well). A policy update is also no longer possible for these.For one of the channels I know that a policy update was still possible yesterday. But overnight the edge seems to have disappeared.
Below you can find the debug log for one channel from the receiving side.
Maybe the problem is related to #7229.
Your environment
2 testnet3 nodes. Both with lnd 0.18.4
protocol.option-scid-alias=true
protocol.zero-conf
is not setLogs
The text was updated successfully, but these errors were encountered: