Browse Source
If a remote node tries to establish a transport with us but we already have an open transport with such a node id, there are two sane ways to go, either: - keep existing transport open, reject new transport - close existing transport, establish new transport We could do either; I chose to do the second option here, as that is what lnd and eclair seem to be doing. Previously we would get into an inconsistent state: both transports open, but only one of them stored in lnworker.peers.patch-4
SomberNight
4 years ago
1 changed files with 12 additions and 6 deletions
Loading…
Reference in new issue