Connect and listen to BOLT compatible nodes #436
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
if you're the first person connecting to a node using --con, there is nobody who could have authenticated you, except via a local lit-af instance. This prevents two lit-af instances running on the same machine, as well as causing some sort of problem for people running multiple instances of lit on a single mahine
bolt compatibility stuff
still need to take care of other stuff to make sure that pubkey is used uniformly inside lit
but we can't do anything more since the wire protocol and the rpc stuff hasn't been changed to deal with that yet
|
Rebased as #437 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The connection will be short-lived (15s), but the log statements would let you verify that you're connected. Start lnd, use
getinfoand try connecting to lit's pubkey (available in lit's log).This needs a rebase on latest master since a PR was merged after I started working on this. @delbonis could you do that please? (since your PR was last merged).